On Wed, Jan 14, 2004 at 02:56:39PM -0500, CertaintyTech wrote: > I have setup two instances of qmail so that my users can avoid longer > transfer times for messages. Messages are first sent to a qmail-smtpd > instance (w/no Q-S) on external interface and then messages are > smtprouted to second instance on 127.0.0.1 interface where they are then > run thru Q-S. Now the users don't have to wait for scanning to complete > which helps a lot on bigger messages. This scenario works good with one > exception: tcpserver on the second instance on 127.0.0.1 sees ALL mail > as originating from the external interface and therefore sets > RELAYCLIENT="" for every message regardless of it actual origin. The > downside of this is that Q-S won't run spamassassin since it thinks that > each message originates from a trusted relay. Now I could set > QS_SPAMASSASSIN="on" in tcpserver rules file which would force > spamassassin to run but I don't want to do that.
Why not? What's wrong with forcing the running of SA? What's the downside? -- Cheers Jason Haar Information Security Manager, Trimble Navigation Ltd. Phone: +64 3 9635 377 Fax: +64 3 9635 417 PGP Fingerprint: 7A2E 0407 C9A6 CAF6 2B9F 8422 C063 5EBB FE1D 66D1 ------------------------------------------------------- This SF.net email is sponsored by: Perforce Software. Perforce is the Fast Software Configuration Management System offering advanced branching capabilities and atomic changes on 50+ platforms. Free Eval! http://www.perforce.com/perforce/loadprog.html _______________________________________________ Qmail-scanner-general mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/qmail-scanner-general
