Bug 2932 - When sender and receiver are at the same server, IP checks are wrongly performed
Summary: When sender and receiver are at the same server, IP checks are wrongly performed
Status: RESOLVED WORKSFORME
Alias: None
Product: Spamassassin
Classification: Unclassified
Component: Rules (show other bugs)
Version: 2.61
Hardware: PC Linux
: P5 normal
Target Milestone: 3.1.0
Assignee: SpamAssassin Developer Mailing List
URL:
Whiteboard:
Keywords:
Depends on: 2462
Blocks:
  Show dependency tree
 
Reported: 2004-01-16 05:32 UTC by Magnus von Koeller
Modified: 2004-12-08 02:38 UTC (History)
0 users


Attachment Type Modified Status Actions Submitter/CLA Status
Email showing the headers that trigger this condition text/plain None Magnus von Koeller [NoCLA]
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Magnus von Koeller 2004-01-16 05:32:20 UTC 
When sender and receiver of an email have accounts at exactly the same server, for 
example if I send myself an email, SpamAssassin performs checks on the message 
as if the E-Mail had been sent directly from that IP - therefore applying all rules 
regarding dynamic IP addresses. 
SpamAssassin seems to wrongly assume that this email was sent directly from a 
dynamic IP when, in fact, it had been sent to the standard non-public relaying SMTP 
server of my webhosting provider which also happens to be the receiving system for 
this email address because both addresses are hosted at the same server.
Comment 1 Magnus von Koeller 2004-01-16 05:35:55 UTC 
Created attachment 1698 [details]
Email showing the headers that trigger this condition

Although this email didn't trigger any of the checks because I'm currently
behind a permanent IP, it shows the exact same Received: headers that would
trigger the checks if the IP had been dynamic.
Comment 2 Daniel Quinlan 2004-08-27 17:18:06 UTC 
more accuracy and performance bugs going to 3.1.0 milestone
Comment 3 Daryl C. W. O'Shea 2004-11-28 17:52:50 UTC 
Setting internal and trusted networks to cover the local provider's own dynamic
IP range solves this problem.

The patch in bug 2462 takes care of the problem of roaming users suffering the
same fate as described here.  It also solves the problem described if
non-roaming users use SMTP auth.

In any case, the problem as described is a configuration error so the bug can
probably be closed.
Comment 4 Daryl C. W. O'Shea 2004-12-08 04:08:35 UTC 
This bug is really a configuration error.
Comment 5 Justin Mason 2004-12-08 11:38:01 UTC 
ok, closing as config error