From owner-freebsd-questions@FreeBSD.ORG Mon Feb 27 16:58:10 2012 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2C83C1065679 for ; Mon, 27 Feb 2012 16:58:10 +0000 (UTC) (envelope-from jon@radel.com) Received: from wave.radel.com (wave.radel.com [216.143.151.4]) by mx1.freebsd.org (Postfix) with ESMTP id A2EA28FC0A for ; Mon, 27 Feb 2012 16:58:09 +0000 (UTC) Received: by wave.radel.com (CommuniGate Pro PIPE 4.1.6) with PIPE id 10571415; Mon, 27 Feb 2012 11:58:09 -0500 Received: from [192.168.43.246] (account jon@radel.com HELO winesap.local) by wave.radel.com (CommuniGate Pro SMTP 4.1.6) with ESMTP-TLS id 10571413; Mon, 27 Feb 2012 11:58:03 -0500 Message-ID: <4F4BB61A.1060600@radel.com> Date: Mon, 27 Feb 2012 11:58:02 -0500 From: Jon Radel User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2 MIME-Version: 1.0 To: "Bender, Chris" References: <863259E16B6C464DAD1E9DD10BB31154059CFBAE@wmsexg01.corp.cellularatsea.com> <4F48BAF6.9070204@ifdnrg.com> <863259E16B6C464DAD1E9DD10BB31154059CFBE7@wmsexg01.corp.cellularatsea.com> <4F48EC21.7040805@ifdnrg.com> <863259E16B6C464DAD1E9DD10BB31154059CFBEE@wmsexg01.corp.cellularatsea.com> <4F48F45F.4080304@ifdnrg.com> <863259E16B6C464DAD1E9DD10BB31154059CFBF4@wmsexg01.corp.cellularatsea.com> <4F492262.5090505@radel.com> <7409DAB4-F76A-493B-9A50-A663E6F6802E@cellularatsea.com> <4F4BB19A.8040005@radel.com> In-Reply-To: Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="------------ms080506060205070603050200" X-Radel.com-MailScanner-Information: Please contact Jon for more information X-Radel.com-MailScanner: Found to be clean X-Mailer: CommuniGate Pro CLI mailer X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-questions@freebsd.org Subject: Re: Email issues, relay failure X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Feb 2012 16:58:10 -0000 This is a cryptographically signed message in MIME format. --------------ms080506060205070603050200 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable On 2/27/12 11:45 AM, Bender, Chris wrote: > I was thinking about just reloading the pf.conf but I have never worked= > with pf so > I am worried other things might break. My thought was by doing that the= > Adaptive part of the pfctl would be restarted? Any pf.conf file I've ever seen does something sensible after reload.=20 I suspect one could write something perverse that blows up on restart,=20 but that would making rebooting the machine problematic.... > > Does that make sense would reloading the rules wash the adaptive > behavior away or > Would all that still be in some sort of bruteforce file to protect the > firewall? pf can load data from files when it starts or just manage things in a=20 fashion that is transient upon restart. Hard to say what's happening in = your case w/o a clue as to what's in pf.conf. I'd suggest that you at the very least whitelist internal SMTP speakers=20 that you expect to get e-mail from on a regular basis, even if you do=20 throttling of SMTP connections in general. Much less messy.... --=20 --Jon Radel jon@radel.com --------------ms080506060205070603050200--