You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@spamassassin.apache.org by bu...@bugzilla.spamassassin.org on 2006/10/19 13:26:38 UTC

[Bug 5136] New: With 3.1.7 'whitelist_from_rcvd' in local.cf no longer adding -100

http://issues.apache.org/SpamAssassin/show_bug.cgi?id=5136

           Summary: With 3.1.7 'whitelist_from_rcvd' in local.cf no longer
                    adding -100
           Product: Spamassassin
           Version: 3.1.7
          Platform: Sun
        OS/Version: Solaris
            Status: NEW
          Severity: major
          Priority: P1
         Component: spamc/spamd
        AssignedTo: dev@spamassassin.apache.org
        ReportedBy: paul.mcilfatrick@bt.com


The following line:

whitelist_from_rcvd phones@xxx.yyy.zzz xxx.yyy.zzz

in our local.cf file was working OK in version SpamAssassin 3.1.4 with the score
of e-mails to phones@xxx.yyy.zzz being reduced by -100.

Yesterday, I used Cpan to upgrade to 3.1.7 and now the score of e-mails to
phones@xxx.yyy.zzz are no longer being reduced by -100!

I ran spamassassin -D --lint and it reported that the local.cf file was being
read OK.

Is the local.cf no longer being parsed correctly?



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

[Bug 5136] With 3.1.7 'whitelist_from_rcvd' in local.cf no longer adding -100

Posted by bu...@bugzilla.spamassassin.org.
http://issues.apache.org/SpamAssassin/show_bug.cgi?id=5136





------- Additional Comments From felicity@apache.org  2006-10-19 08:13 -------
Generally speaking, issues like these should first be sent to the users@ list.

You also don't provide enough information to answer your question.  Please
attach a non-modified message along with a non-modified config file showing the
whitelist entry.



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

[Bug 5136] With 3.1.7 'whitelist_from_rcvd' in local.cf no longer adding -100

Posted by bu...@bugzilla.spamassassin.org.
http://issues.apache.org/SpamAssassin/show_bug.cgi?id=5136


sidney@sidney.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |INVALID




------- Additional Comments From sidney@sidney.com  2006-10-19 14:11 -------
To add to Theo's comment "Please attach...", please only do that _after_ you
have asked about this on the users list and dealt with what is most likely a
misconfiguration problem that happened during the upgrade.

By the way, I would suggest looking at how you have defined trusted and internal
networks as described on the wiki at
http://wiki.apache.org/spamassassin/TrustPath as one of the symptoms listed
there is whitelist_from_recvd not working.

I'm closing this bug as INVALID to indicate that it most likely is a
configuration problem and not a SpamAssassin bug. However, once you track down
the cause using the wiki and people on the users mailing list, if it is a result
of a bug in SpamAssassin or a bug in the 3.1.7 upgrade procedure, please feel
free to reopen this bug and let us know.




------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

[Bug 5136] With 3.1.7 'whitelist_from_rcvd' in local.cf no longer adding -100

Posted by bu...@bugzilla.spamassassin.org.
http://issues.apache.org/SpamAssassin/show_bug.cgi?id=5136





------- Additional Comments From paul.mcilfatrick@bt.com  2006-10-20 06:50 -------
Resolved the issue.

Unknown to us our machines were changed from using a locally controlled DNS
server to use a new company DNS server. After a lot of investgation we found out
that the new DNS server had been set up to NOT support reverse DNS lookup which
of course meant that that SpamAssassin's whitelist_from_rcvd stopped working!

Sorry for raising this bug in error.





------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.