I am using fetchmail to retrieve messages from my work account.
However, messages sent to my work account from coworkers are being
tagged with various dynamic IP rules. My setup is something like this:
CoWorker (dialup) --> mail server (office) <-- fetchmail (home) <--
spamassassin
When a message of this sort is retrieved, I get these rule hits:
4.2 HELO_DYNAMIC_IPADDR Relay HELO'd using suspicious hostname (IP addr
1)
1.4 SPF_SOFTFAIL SPF: sender does not match SPF record (softfail)
[SPF failed: Please see http://spf.pobox.com/why.html?sender=blahblahblah]
-2.6 BAYES_00 BODY: Bayesian spam probability is 0 to 1%
[score: 0.0000]
2.0 RCVD_IN_SORBS_DUL RBL: SORBS: sent directly from dynamic IP
address
[24.245.33.51 listed in dnsbl.sorbs.net]
1.9 RCVD_IN_NJABL_DUL RBL: NJABL: dialup sender did non-local SMTP
[24.245.33.51 listed in combined.njabl.org]
-0.1 AWL AWL: From: address is in the auto white-list
From reading this thread:
http://thread.gmane.org/gmane.mail.spam.spamassassin.general/83423/focus=83423
it looks like there isn't a simple workable solution. It seems like the
sender is in the right by sending mail through my work's SMTP server
(the problem would go away if they sent through a relay first, but I
can't dictate how people send messages TO me). As Raimar tried in the
thread above, I added my work server to trusted_networks, and
internal_networks but that's not the right way to handle this, apparently.
Is there a workable solution that doesn't require me to whitelist all my
coworker's IP ranges?
Chris
