http://bugzilla.spamassassin.org/show_bug.cgi?id=2537
------- Additional Comments From [EMAIL PROTECTED] 2004-02-27 08:51 ------- I think that the real problem here (in comments 11 and 12) is that SA has no way of recognising SMTP auth (or POP before SMTP) connections. I can't see any way of configuring trusted_networks to differentiate between the following two cases: 1) Spammer zombie machine using it's own SMTP engine connects to your SMTP server from a dynamic IP address somewhere outside your network (let's say a comcast cable modem). 2) A (legit) roaming user connects to you from a dynamic IP somewhere outside your network (using SMTP auth). In the first case, you want SA to check the dynamic IP for listing in the DUL. If it's listed, you want to hammer the email with a high score, since that type of connection (dynamic IP outside your network connecting directly to your SMTP server) shouldn't ever happen. In the second case, SA needs some way of knowing that this connection is ok. Parsing the Received headers for SMTP auth might work. For ad-hoc methods like POP before SMTP, ad-hoc SA solutions may have to be applied. That issue is completely seperate from this bug, though. ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
