On 2011-05-21, Andrea Conti <[email protected]> wrote: > On 21/05/11 06.13, Pandu Poluan wrote: >> Hello list! >> >> Due to the increase of spam/phishing emails received by my office, I >> decided to explore the idea of implementing a spamfiltering 'frontend' >> in front of my email server. >> >> Here's how I plan to do it: >> >> fetchmail (G) --> postfix (G) --> amavisd+spamassassin+database (G) >> --> postfix (G) --> current email back-end (WS) --> clients (W) > > Having a second postfix instance between amavisd and the email server is > going to make things way more complicated. Amavisd is perfectly capable > of speaking smtp/lmtp by itself, so unless you need to perform complex > mail routing you could directly send the filtered mail to the windows > server. > > Other than that, I have very similar setup > (fetchmail->postfix->amavis->cyrus-imap, where all hops but the first > are done with lmtp) that has been working quite well for the past few years. > > HTH, > andrea
Hmm... interesting points. But can it still do the 2nd part of the equation, that is, perform outgoing routing? I had thought that I'll need amavisd to re-inject the email to postfix so that postfix can do mail routing, i.e., mails to my domain get routed to the Windows server, while outgoing emails get routed to my ISP's mail relay. Of course I can have postfix to skip amavisd for outgoing emails, but then I guess I'll lose amavisd's automated whitelisting (the so-called 'pen pal' feature). Rgds, -- Pandu E Poluan - IT Optimizer My website: http://pandu.poluan.info/
