This is the mail archive of the
cygwin-talk
mailing list for the cygwin project.
Re: Your setting Return-Path to YOU in your cygwin@cygwin postings
- From: Dave Korn <dave dot korn dot cygwin at googlemail dot com>
- To: The Vulgar and Unprofessional Cygwin-Talk List <cygwin-talk at cygwin dot com>
- Date: Wed, 04 Mar 2009 16:39:41 +0000
- Subject: Re: Your setting Return-Path to YOU in your cygwin@cygwin postings
- References: <49ADA916.40700@columbus.rr.com> <49ADBA0D.6040405@gmail.com> <49ADEF5E.3060804@columbus.rr.com> <49ADF5B5.5000102@gmail.com> <49AE0F52.1060006@columbus.rr.com> <49AE6F03.5040003@gmail.com> <980E7CF9434CB68895B336D3@orees.hpl.hp.com>
- Reply-to: The Vulgar and Unprofessional Cygwin-Talk List <cygwin-talk at cygwin dot com>
Owen Rees wrote:
> --On Wednesday, March 04, 2009 12:07:31 +0000 Dave Korn wrote:
>
>> Note also how all those paths have a Mail-Followup-To header pointing
>> at the list. Any mailer that does not respect that when you hit Reply is
>> broken and does not comply with internet standards. The Return-Path is
>> for automated error messages *only*, not replies of any sort.
>
> Can you give a link to the relevant internet standard please. I could
> not find it in RFC5322 (nor in RFC2822 which it obsoletes (nor in
> RFC0822 which it obsoletes)). RFC2369 which defines mailing list command
> specification header fields also says nothing about that field.
>
> As far as I can tell, the standards define Reply-To and Return-Path but
> not Mail-Followup-To.
Yes, you're right. Looking at the history, it's never made it to the status
of an STD, but there was an IETF draft proposal (which is actually one stage
more advanced than an RFC):
http://www.ietf.org/proceedings/98dec/I-D/draft-ietf-drums-mail-followup-to-00.txt
and there are some more details at:
http://cr.yp.to/proto/replyto.html
So it's only a de-facto standard. Any mailer which doesn't want to
implement it is free to do so, but it is still incorrect if it uses
Return-Path for replies.
cheers,
DaveK