-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On December 19, 2002 12:55, Ross Vandegrift wrote: > Hello everyone, > > I need a more intelligent mail routing setup. The primary MX > for our domain is a sendmail machine that runs spamassassin. It scans > email, and then (via an entry in the mailertable) routes it to the > Novell Netware server (running Mercury) for user mailbox delivery. > > Right now, our outgoing mail server spends lots of time trying > to send bounce messages for all the spam we get to invalid usernames. > The primary MX host just routes mail to the delivery server. How have > you guys handled this problem? Ideally, I'd rather not have two > machines with real work to do spend so much time trying to send out > bounce messages to non-existent spammer addresses.
It's been a quite a while since I worked with Sendmail so I don't know the equivalent, but under postfix I would use the fallback_relay setting. That would have the primary MX try once to deliver, and on first failure, it would hand the mail off to a different machine, which would work on it at leisure. That would apply to -all- mail that failed first delivery, though, not just SA rejected mail. Alternatively, if the system is simply queue-bogged rather than actually CPU/memory loaded you could run simultaneous instances, to avoid needing a second box and the associated overhead. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE+AjkdkPEFhVei73QRAkO8AJ48MaaXD0IwKVut02x8VPGm319bbwCfWbly 14M+oLLi2Cf/Rs4iSrgQfVg= =tZpV -----END PGP SIGNATURE----- ------------------------------------------------------- This SF.NET email is sponsored by: Geek Gift Procrastinating? Get the perfect geek gift now! Before the Holidays pass you by. T H I N K G E E K . C O M http://www.thinkgeek.com/sf/ _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
