On Tue, Jun 23, 2009 at 09:21:52AM +0100, Steve wrote:
> Silly question. Currently I have Postfix using Spamassassin as a content
> filter thus;
>
> smtp inet n - - - 10 smtpd
> -o content_filter=spamassassin
> ...
> spamassassin unix - n n - - pipe
> user=spamd argv=/usr/bin/spamc -f -e
> /usr/sbin/sendmail -oi -f ${sender} ${recipient}
>
> It's nice and dandy but could this be changed to filter and reject at an
> SMTP level rather than after accepting the message? My thoughts are
> along this line;
>
> Spamassassin is much slower in processing than Postfix and there will be
> a bottleneck
>
> Spamassassin is a content filter and can only work *after* the LF . LF
>
> Then to offset this;
>
> I'm only running a small server with a few mails per minute - so it's
> not going to kill it.
>
> I can block at SMTP level with Postfix native Body Filter.
>
> The reason I ask is this bounce;
>
> ...
> <[email protected]>: host mail.varna.net[217.145.80.1] said: 550 5.7.1
> Blocked by
> SpamAssassin (in reply to end of DATA command)
> ...
>
> I'm still discovering great things with Postfix everyday, so my
> experience is no way as good as most people here - so excuse the stupid
> question. Each day is a learning curve.
Good question sir.
I am contemplating howto use spamassassin effectively with postfix.
I look forward to the thread.
--
Member - Liberal International This is [email protected]
Ici [email protected] God, Queen and country! Beware Anti-Christ rising!
Never Satan President Republic!
Rudeness is the weak man's imitation of strength. -Eric Hoffer
