Re: Mailing lists - assumptions
Theodore Ts'o <[email protected]> Sat, 19 Apr 2014 14:42:20 -0400
| Newsgroups | gmane.ietf.rfc822 |
|---|---|
| Message-ID | <[email protected]> |
On Sat, Apr 19, 2014 at 11:00:35AM -0700, Ned Freed wrote: > You want any downstream delivery errors to be reported to the original sender, > so ideally you'd leave the MAIL FROM unchanged. But now an SPF check on the > MAIL FROM will fail because alum.mit.edu's IP address isn't going to be > allowed list. > > The usual way this is solved is with a more complex forwarding address, > one that incorporates a timestamp and a verifier. As I noted > previously the Sender Rewriting Scheme is one way to do this, but of > course you can use any encoding you want since only your systems have > to understand it. You mean like this: Return-path: <SRS0=/[email protected]> :-) Sure, it's a bit ticklish, but it's obviously implementable. - Ted _______________________________________________ ietf-822 mailing list [email protected] https://www.ietf.org/mailman/listinfo/ietf-822