On 4/19/2010 12:11 AM, Alex wrote:
The "warn_if_reject" feature predates "reject_unauth_pipelining", which you
seem to be using successfully. I strongly suspect there was some other
error -- probably a simple typo in your config -- that kept warn_if_reject
from working for you.
I'm trying to do:
warn_if_reject = reject_rbl_client backscatter.spameatingmonkey.net
But it appears that's only available in later versions, so I've tried
this, and it also doesn't work:
warn_if_reject = reject_maps_rbl backscatter.spameatingmonkey.net
warn_if_reject should proceed a restriction in your
smtpd_recipient_restrictions.
smtpd_recipient_restrictions =
permit_mynetworks
...
warn_if_reject reject_msps_rbl
I misquoted HISTORY about when reject_unauth_pipelining was
introduced, actually should have been:
19990905
...
Feature: reject_unauth_pipelining SMTP restriction that
rejects mail from clients that improperly use SMTP
command
pipelining.
The part I quoted was about adding the
"smtpd_data_restrictions" feature.
So it's possible that your postfix doesn't support
warn_if_reject, which was added in Nov 2001.
You can check your postfix version and release date with
postconf mail_version mail_release_date
Will reject_rhsbl_sender and reject_rhsbl_client work in old versions?
Don't know... HISTORY says those features were added in Sept
2002. Check your mail_release_date and mail_version, and if
they look promising, give it a try.
The reason you don't get flamed for running ancient postfix is
that even ancient postfix is fairly secure. You're just
missing new features and bug fixes. But I would worry about
the OS and the other software that may be running on a box
with such an old postfix.
-- Noel Jones
