Mailing List Archive: [srs-discuss] Problems effectively using SPF with SRS

[srs-discuss] Problems effectively using SPF with SRS

Sep 20, 2004, 3:41 PM

Post #1 of 4 (4320 views)

Let's say that I want to whitelist hotmail.com, because they publish SPF records and ratelimit outgoing mail on a per user basis. My email address is forwarded to another email address, which is where I am implementing my whitelist. Assume the forwarder implements SRS.

How can I make my whitelist work? The From: header is not checked with SPF, so that's worthless. Since the message was SRS-forwarded, I can't reliably tell who the original sender is. At least, I don't think so. Can anyone tell me how to do this?

-------
To unsubscribe, change your address, or temporarily deactivate your subscription,
please go to http://v2.listbox.com/member/?listname=srs-discuss@v2.listbox.com

Re: [srs-discuss] Problems effectively using SPF with SRS [ In reply to ]

mengwong at dumbo

Sep 20, 2004, 3:44 PM

Post #2 of 4 (4124 views)

Permalink

On Mon, Sep 20, 2004 at 10:41:55PM +0000, Steve Meyers wrote:
|
| How can I make my whitelist work? The From: header is not checked with SPF, so that's worthless. Since the message was SRS-forwarded, I can't reliably tell who the original sender is. At least, I don't think so. Can anyone tell me how to do this?
|

you can pick apart the SRS encoded return path to tell who
the original return path was...

-------
To unsubscribe, change your address, or temporarily deactivate your subscription,
please go to http://v2.listbox.com/member/?listname=srs-discuss@v2.listbox.com

Re: [srs-discuss] Problems effectively using SPF with SRS [ In reply to ]

steve-list-srs at spamwiz

Sep 20, 2004, 3:59 PM

Post #3 of 4 (4095 views)

Permalink

Meng Weng Wong wrote:
> you can pick apart the SRS encoded return path to tell who
> the original return path was...

Doesn't that depend on the SRS implementation though? I was under the
impression that there was no standard for the encoding. In fact, don't
some implementations use a database to store the info?

Steve

-------
To unsubscribe, change your address, or temporarily deactivate your subscription,
please go to http://v2.listbox.com/member/?listname=srs-discuss@v2.listbox.com

Re: [srs-discuss] Problems effectively using SPF with SRS [ In reply to ]

mengwong at dumbo

Sep 20, 2004, 4:19 PM

Post #4 of 4 (4119 views)

Permalink

On Mon, Sep 20, 2004 at 04:59:30PM -0600, Steve Meyers wrote:
| Meng Weng Wong wrote:
| >you can pick apart the SRS encoded return path to tell who
| >the original return path was...
|
| Doesn't that depend on the SRS implementation though? I was under the
| impression that there was no standard for the encoding. In fact, don't
| some implementations use a database to store the info?
|

well, there's the conventional SRS encoding, and there's the
stuff that other people are welcome to come up with.

The conventional encoding preserves the original address.

I should note that using SUBMITTER, which allows you to
preserve MAIL FROM, would get around this problem entirely,
but SUBMITTER is not widely deployed at all.

-------
To unsubscribe, change your address, or temporarily deactivate your subscription,
please go to http://v2.listbox.com/member/?listname=srs-discuss@v2.listbox.com