RE: Re[2]: Help - How to unwind an SRS address?
Mark <[email protected]> Mon, 22 Nov 2004 07:21:48 GMT
| Newsgroups | gmane.mail.spam.srs.general |
|---|---|
| Organization | Asarian-host |
| Message-ID | <[email protected]> |
> -----Original Message----- > From: [email protected] > [mailto:[email protected]] On Behalf Of Stuart > D. Gathman > Sent: maandag 22 november 2004 6:06 > To: [email protected] > Subject: RE: Re[2]: [srs-discuss] Help - How to unwind an SRS address? > > On Sun, 21 Nov 2004, Mark wrote: > > > Yes. The problem is, of course, programs like SA, who like to have a > > go at SPF too. With no SRS 'original' Return-Path to be found any > > more, they are stuck (I'm sure something can be done with HELO, > > in those cases; but that offers no real substitute for per-virtual > > domain SPF policies). > > SPF is performed on the SRS address. That is the whole point of SRS. > The only possible reason to unwind SRS or SES is because you want to > compare the original MAIL FROM with some rfc2822 header, or at least > display it to the end user (although if the user is knowlegeable enough > for the information to be useful, they should really see the full > SRS/SRS whatever MAIL FROM). Exactly. :) That was my point precisely; if you 'unwind' the SRS address before writing the Return-Path, an LDA like procmail, or processing agent like SA, can no longer do the SPF check on the SRS address. Best, therefore, to leave the SRS address exposed to the recipient in at least the Return-Path. - Mark System Administrator Asarian-host.org --- "If you were supposed to understand it, we wouldn't call it code." - FedEx