Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: SpamAssassin: devel

[Bug 6764] New: When used with fetchmail, SA can inappropriately test

 

 

SpamAssassin devel RSS feed   Index | Next | Previous | View Threaded


bugzilla-daemon at bugzilla

Feb 22, 2012, 10:45 AM

Post #1 of 1 (96 views)
Permalink
[Bug 6764] New: When used with fetchmail, SA can inappropriately test

https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6764

Bug #: 6764
Summary: When used with fetchmail, SA can inappropriately test
Product: Spamassassin
Version: 3.3.1
Platform: PC
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: spamassassin
AssignedTo: dev [at] spamassassin
ReportedBy: mark [at] markporthouse
Classification: Unclassified


The problem only occurs in the rare scenario where:
bob [at] domain sends an email to alice [at] domain
and
spamassassin is running on a second server, the personaldomain.tld server
and
alice [at] personaldomain fetches the mail of alice [at] domain from their
domain.tld mailbox into their personaldomain.tld server mailbox using
fetchmail.

In this scenario spamassassin on personaldomain.tld tests the smtp transaction
between the sending PC (which may be on a dynamic IP address) and the
domain.tld receiving server.

In no circumstances would anyone wish to use SA to test the transaction between
the sending mail client and the SMTP server used by that mail client (normally
you would test the transaction between the sender's SMTP server and the
recipient's SMTP server). Yet, this is what is happening in this instance
(probably because their isn't another transaction that you would want to test).

In this scenario there is no need to test the fetchmail transaction (a
fetchmail transaction would never be tested), which might be why spamassassin
is looking at the transaction into the recipient's server - which in this rare
case of the sender's smtp server being the recipient's server means that the
transaction being looked at is the one between mail client and the smtp server
set for that mail client.

Spamassassin cannot, after all, look at the internal mail server process which
receives the authenticated SMTP from the sending client and passes it into the
recipient's mailbox.

Basically, in this rare scenario, Spamassassin, on the server running
fetchmail, should not do any tests.

However, I'm not sure how it could be programmed to deduce that it is
experiencing this scenario where it should not do any tests!

--
Configure bugmail: https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

SpamAssassin devel RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact Gossamer Threads
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.