On 04/12/16 14:26, Noel Jones wrote:
On 4/12/2016 11:38 AM, Curtis Villamizar wrote:
On 04/12/16 06:25, Wietse Venema wrote:
Curtis Villamizar:
I recently had a problem with mail where an ESP was in three
blacklists
plus SPF failed and spamassassin tossed some mail. That ESP is
down to
one blacklist now. A sender got to me out-of-band and I dug up the
maillog from a few days earlier and informed them about how good
their
ESP was serving them. btw- If I had been using postscreen back
then, I
could not have found this in the logs based on sender email.
Incorrect. In the recommended configuration, postscreen will log
IP address, helo, sender, and recipient.
Wietse
My inexperience with debugging problems with postscreen logs is
showing.
Curtis
Note the helpful logging of helo/sender/recipient requires the
offending test be set to "enforce" rather than "drop". This is
noted in the docs.
See the various postscreen_*_action parameters for details, such as:
http://www.postfix.org/postconf.5.html#postscreen_dnsbl_action
-- Noel Jones
I have nothing set to drop. Just been running postscreen for such a
short time and on a little used domain (not this one) that mostly gets
spammed a lot but gets a small amount of legit email from people that
forgot that I told them not to use it. So I haven't had to debug a "got
a bounce" issue with postscreen.
Thanks for the heads up. By the time I run postscreen on a domain that
matters I hope to have a good configuration.
Curtis
