On Mon, 2010-03-08 at 20:44 +0000, Ned Slider wrote: > Brian wrote: > >> That's Postfix 2.3.3 on RHEL5 BTW :-) > >> > >> $ rpm -q postfix > >> postfix-2.3.3-2.1.el5_2.x86_64 > >> > > Tell me Ned, how do you get Postfix (2.3.3 on RHEL5) to reject at SMTP > > time without using a the milter or something hideous like > > Amavis-crashalot? Perhaps if they added some features to that old > > dinosaur it would become a bit more useful as an MTA :-) > > > > > > See this guide I've written: > > http://wiki.centos.org/HowTos/postfix_restrictions > > Specifically, > > # /etc/postfix/main.cf > # Recipient restrictions: > smtpd_recipient_restrictions = > reject_unknown_recipient_domain > Yes, but that does not answer my question {and is once more Postfix biased} AFAIK Postfix is totally unable to reject mail at SMTP time that Spamassassin decides IS SPAM without the aid of a milter or policy deamon of some kind. Unless you know different?
Natively It can happily do it after accepting the mail (hint - a bit late then...) with an after queue filter, but this is prone to the phenomenon that is 'Postscatter' -sending the message back to the (often) forged sender. This is kind of ironic given how the Postfix Posse bang on about 'not accepting' mail of criteria 'x'. Postfix, much that I love it, has some gaping holes in it's feature set. It really is an MTA for the 1990's. The need to bolt in an Sendmail Milter to get it to reject Spamassassin tagged mail at the SMTP stage is a glaring example IHMO - But all this is very much OT.
