From: Owen Rees <owen.rees@hp.com>
To: The Vulgar and Unprofessional Cygwin-Talk List <cygwin-talk@cygwin.com>
Subject: Re: Your setting Return-Path to YOU in your cygwin@cygwin postings
Date: Wed, 04 Mar 2009 12:30:00 -0000 [thread overview]
Message-ID: <980E7CF9434CB68895B336D3@orees.hpl.hp.com> (raw)
In-Reply-To: <49AE6F03.5040003@gmail.com>
--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.
--
Owen Rees
========================================================
Hewlett-Packard Limited. Registered No: 690597 England
Registered Office: Cain Road, Bracknell, Berks RG12 1HN
next prev parent reply other threads:[~2009-03-04 12:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <49ADA916.40700@columbus.rr.com>
[not found] ` <49ADBA0D.6040405@gmail.com>
[not found] ` <49ADEF5E.3060804@columbus.rr.com>
[not found] ` <49ADF5B5.5000102@gmail.com>
[not found] ` <49AE0F52.1060006@columbus.rr.com>
2009-03-04 11:59 ` Dave Korn
2009-03-04 12:30 ` Owen Rees [this message]
2009-03-04 16:30 ` Dave Korn
2009-03-04 16:45 ` Christopher Faylor
2009-03-04 17:04 ` Owen Rees
2009-03-04 18:16 ` Dave Korn
2009-03-05 10:57 ` Owen Rees
2009-03-05 13:18 ` Dave Korn
2009-03-05 15:56 ` Owen Rees
2009-03-05 18:32 ` Morgan Gangwere
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=980E7CF9434CB68895B336D3@orees.hpl.hp.com \
--to=owen.rees@hp.com \
--cc=cygwin-talk@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).