Re: Mailing lists - assumptions

On 19/04/2014 19:00, Ned Freed wrote:
>
>> The way alum.mit.edu handles email forwarding for life is they provide
>> an authenticated submission service for MIT alumni[1].  This handles SPF
>> and DKIM on the outgoing side, and on the forwarding side, it looks to
>> the e-mail provider that that an address such as "[email protected]"
>> is a mailing list.
> This isn't the issue; the issue is what the MAIL FROM address gets set to
> when a message is forwarded.
>
> 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.

Do you want delivery errors to be reported to the original sender? Are 
you sure?

If I send a message to '[email protected]', do I really want lots of 
delivery errors from random people I've never heard of? Wouldn't it make 
more sense for those delivery errors to be reported to the list 
administrator?

I know we have this problem with our MTA where people send mail to 
'[email protected]', and that user has a forward to a gmail account. It 
confuses the original sender if they receive a delivery failure report 
from Google, because they never sent a message to Google at all. So, we 
normally set things up so the MAIL FROM is changed to go to 
[email protected]. That way, if a forward is set incorrectly, 
they can sort it out, and the company's contacts don't get confused.





-


Paul Smith Computer Services
Tel: 01484 855800
Vat No: GB 685 6987 53

_______________________________________________
ietf-822 mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/ietf-822