From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-kernel@vger.kernel.org
Subject: Re: VGER's filters..
Date: 4 Apr 2003 12:36:20 -0800 [thread overview]
Message-ID: <b6kqc4$2td$1@cesium.transmeta.com> (raw)
In-Reply-To: 20030404181054.GT29167@mea-ext.zmailer.org
Followup to: <20030404181054.GT29167@mea-ext.zmailer.org>
By author: Matti Aarnio <matti.aarnio@zmailer.org>
In newsgroup: linux.dev.kernel
>
> With Yahoo I had at first immense problems to get any email from them,
> as their SMTP email sender uses INVALID protocol:
>
> <<- MAIL FROM: <yahoo-dev-null@yahoo-inc.com>
> ->> 501 5.1.7 strangeness between ':' and '<': <yahoo-dev-null@yahoo-inc.com>
> When you read really carefully RFC 821 / 2821 syntax about that,
> you will see that it does not allow space in that place.
> Sendmail does, and that has forced others to extend the syntax alike.
>
Sendmail, and a whole bunch of other mailers, have taken the more
liberal approach of allowing any RFC 822-compliant address in this
place (which is a *lot* more liberal than an RFC 821-compliant
reverse-path.) This is consistent with the "be liberal in what you
accept, conservative in what you send" philosophy of network
interoperability.
I suspect in Sendmail it naturally falls out of using a single set of
canonicalization rules for all syntax.
-hpa
--
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
Architectures needed: ia64 m68k mips64 ppc ppc64 s390 s390x sh v850 x86-64
next prev parent reply other threads:[~2003-04-04 20:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-04 18:10 VGER's filters Matti Aarnio
2003-04-04 20:36 ` H. Peter Anvin [this message]
2003-04-04 21:05 ` Matti Aarnio
2003-04-04 23:04 ` H. Peter Anvin
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='b6kqc4$2td$1@cesium.transmeta.com' \
--to=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.