On Fri, Jun 24, 2011 at 09:47:09PM -0700, Rich Wales wrote:
> This question came up after I tried to use the abuse.net mail relay
> test site (http://verify.abuse.net/relay.html) to verify that my
> server was not misconfigured as an open relay. But since their
> site that tries a laundry list
On 6/24/2011 11:47 PM, Rich Wales wrote:
Now I understand why this is failing. I guess I'm going to need to do
something different with my SMTPD restrictions -- possibly move all my
existing client restrictions to be at the end of my list of recipient
restrictions (after reject_unauth_destinatio
> That is ignored in the context of a "RCPT TO" command (thus in all of
> the top-level restriction classes when smtpd_delay_reject = yes) for
> a recipient that would fail "reject_unauth_destination". For such a
> recipient do you really need DNSWL whitelisting? Normally, clients
> allowed to send
On Fri, Jun 24, 2011 at 08:12:28PM -0700, Rich Wales wrote:
> In http://www.postfix.org/postconf.5.html#smtpd_client_restrictions, I
> read that "for safety", permit_dnswl_client and permit_rhswl_client are
> silently ignored when they would override reject_unauth_destination.
That is ignored in
I'm using Postfix 2.8.1 on an Ubuntu Maverick server.
As suggested in http://www.postfix.org/SMTPD_ACCESS_README.html, I am
using separate SMTPD client, HELO, sender, and recipient restriction
lists (with various blacklist checks, as well as some client whitelist
checks, placed as appropriate in t
