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: Thu, 05 Mar 2009 15:56:00 -0000 [thread overview]
Message-ID: <62743174EA5B5317274570F1@orees.hpl.hp.com> (raw)
In-Reply-To: <49AFD35C.8080401@gmail.com>
--On Thursday, March 05, 2009 13:27:56 +0000 Dave Korn wrote:
> This is how the internet has always worked: someone proposes an idea,
> some other people support it in software, everyone tries it out and if it
> works good it gets widely-adopted. The whole standardisation process is
> very much an after-the-fact matter of documenting what the de facto
> standards are and providing a gold-standard for interoperability so that
> any little misaligned wrinkles between the various implementations can be
> ironed out.
If the idea had been proposed this century...
> The most widespread use is in NDRs, which add "Return-Path: <>" so that
> you don't get bounces, loops and explosions of NDRs for NDRs for NDRs and
> so on.
The Return-Path header would be used only if a message is being relayed via
some non-SMTP mail transport that understands internet message headers and
an error occurs in that non-SMTP environment.
In transit via SMTP messages SHOULD NOT contain a Return-Path header. The
reverse path is carried in the SMTP envelope and delivery errors are
reported using the SMTP envelope addresses.
--
Owen Rees; speaking personally, and not on behalf of HP.
========================================================
Hewlett-Packard Limited. Registered No: 690597 England
Registered Office: Cain Road, Bracknell, Berks RG12 1HN
next prev parent reply other threads:[~2009-03-05 15:56 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
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 [this message]
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=62743174EA5B5317274570F1@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).