Re: Why SRS really sucks
Hannah Schroeter <[email protected]> Wed, 26 Apr 2006 19:28:43 +0200
| Newsgroups | gmane.mail.spam.srs.general |
|---|---|
| Organization | Schlund + Partner AG |
| Message-ID | <[email protected]> |
Hello! On Mon, Mar 27, 2006 at 09:48:01PM +0200, Stephan Menzel wrote: >[...] >> We're discussing an MTA examining the local part of MAIL FROM: where >> the domain is not the MTA's domain, and trying to parse out meaning >> from it (beyond a simple one-to-one comparison). Are you doing THAT? >Well, if I understand you right here, yes we do. >But consider a scenario with many user dependend configurations. Let's say, >you offer SPF checks for your users. And some users have it activated with a >setting like 'deliver to spam folder', some users say 'no, I want this >blocked' and there will also be users who say 'I don't want any SPF >checkings'. Same thing goes not only for SPF but for many other spam >protection modules you might invoke there like internal or external >blacklists etc. >In this case, you have almost no chance to give the error right after MAIL >FROM. You must be able to know, which user this mail will be adressed to to >determine which settings apply. Regarding the RFC, afaik this won't let you >any option other than receiving the DATA. >Or did I get you wrong here? You did get something wrong: You know the recipient after RCPT TO, so at *that* point you can lookup the user's settings and apply recipient-specific policy to perhaps deny the mail. No need to wait for the DATA command or even the completion of the DATA phase. Kind regards, Hannah.