On Monday 20 January 2003 19:52, Kendrick Vargas wrote: Thanks for the clarification. i have to admit that I'd never worked with LMTP before I undertook this project...
Anyways, with the AMaViS virus filtering, could you clarify a bit? Does your MX point to an AMaViS server which then forwards to your Postfix/Cyrus box? (MX) --> [AMaViS-smtp1] --> [Postfix-smtp2] ? Or is it something different? For some reason I thought that most filtering solutions worked between the SMTP process and the message store (as in a /bin/deliver replacement). (Oh, and I'm assuming that hosting multiple domains doesn't complicate this?) If you wouldn't mind sharing a config file I'd appreciate it ... Thanks, Thomas > The deliver method is gonna be more costly in terms of resources than > lmtp. Every time postfix is going to deliver the mail, it has to spawn a > shell which loads the binary every time, chews up memory, etc, just to > deliver mail. With lmtp, cyrus is allready spawning and listening on a > socket and all postfix has to do is open and write to the socket. Not to > mention that you'll have permissions and security issues with the deliver > method over the lmtp method. > > If you're worried about filter flexibility, don't. Postfix is very > flexible in this sense. I use AMaViS with my server (several domains) and > I have it running as a local only smtp daemon, and I essentially redirect > email through it to provide the filtering. It's alot safer this way. I > have spam filtering defined as a postfix content filter but I could do it > as a smtp redirect as well. > -peace
