http://bugzilla.spamassassin.org/show_bug.cgi?id=2462
------- Additional Comments From [EMAIL PROTECTED] 2004-03-29 14:22 ------- Why can't we have a configuration option that lists the local MTAs that only accept mail from trusted clients? Then there would be no need to parse various SMTP_AUTH indicators or do anything special for POP-before-SMTP, and it would handle any other authorization method. The effect of the option would be to disable the one Received header rule of notfirsthop when the MTA is in the list. The simplest form of the option would be to accept all, i.e, disable the one Received header header to notfirsthop. That would be used when the delivering MTA does not accept unauthorized connections from outside the network. This will not help if an ISP uses the same MTA to receive mail from other MTAs, to receive mail from authorized clients, and to deliver the mail locally. But at that point I would say it is their configuration problem. If they want a way to distinguish between mail that arrives authenticated and mail that arrives unauthenticated they should logically separate the server that they tell users to use to send mail and the ones that their MX records point to. ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
