Hi Matt Kettler,
> Suggestion: the SpamAssassin machine might need it's trusted networks
> manualy set. If SA fails to figure this out, it will default to checking
> every header for dialup IPs.
I think you misunderstood me. My problem isn't what _my_ spamassassin says
about _my_ users' mails, but what other peoples spamassassin says about my
users' mails. I can't change the configuration of _their_ SA.
And also what my spamassassin is saying about mails to my users from other
people who have dialup IPs and "incorrect" smtp servers. I can't add all
their server to my trusted_networks.
SA is a really great tool, there is just that tiny detail where I
disagree. Maybe we can start a serious discussion (or vote) here?
> I've also heard rumors that the documentation doesn't match the code. The
> docs claim you can truncate IPs but I've had at least one person report
> that trusted_networks didn't work until the put in the whole IP with CIDR
> mask. (ie: 192.168/16 did not work, 192.168.0.0/16 did, which is contrary
> to the man page)
Hm, does it work without CIDR mask. Like this:
trusted_networks 192.168.123.45 192.168.123.46 192.168.123.47
I thought so until now, but you make me wonder whether I never noticed...?
Thanks,
Andy.
--
o _ _ _
------- __o __o /\_ _ \\o (_)\__/o (_) -o)
----- _`\<,_ _`\<,_ _>(_) (_)/<_ \_| \ _|/' \/ /\\
---- (_)/ (_) (_)/ (_) (_) (_) (_) (_)' _\o_ _\_v
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Weinberg's Principle:
An expert is a person who avoids the small errors while
sweeping on to the grand fallacy.
