http://bugzilla.spamassassin.org/show_bug.cgi?id=2537
------- Additional Comments From [EMAIL PROTECTED] 2004-02-21 12:50 ------- Perhaps a minor man page addition (like below) to the trusted_networks setting would suffice to close the bug? Also might want to spell out that all local MX machines may have to go into internal_networks. Other than the documentation (and SMTP auth, a different issue), things appear to be working properly here, right? Below is a suggested snippet for the man page. I'm not certain I'm 100% correct in the usage, though. -- trusted_networks should contain all the IP ranges that you expect will use your mail servers for outgoing mail. You want to add your dialup pool(s), DSL users, etc. here, especially if your dialup pool is from a different IP range than your mail servers. Basicly, if you're adding the IP range to your MTA's list of hosts allowed to relay (adding aaa.bbb.ccc RELAY to the access file on Sendmail), you want to add the IP range to trusted_networks. internal_networks should include all of your MX servers. This defines the "edge" of your network. This allows SpamAssassin to know where to start looking for RBLs, and where to watch for dynamic IPs. -- ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
