From: Junio C Hamano <gitster@pobox.com>
To: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Cc: "brian m. carlson" <sandals@crustytoothpaste.net>,
Stewart Smith <trawets@amazon.com>,
git@vger.kernel.org, Todd Zullinger <tmz@pobox.com>
Subject: Re: [PATCH] git-send-email: Add --no-validate-email option
Date: Thu, 30 Jun 2022 14:03:22 -0700 [thread overview]
Message-ID: <xmqqzghtdftx.fsf@gitster.g> (raw)
In-Reply-To: <220630.868rpee6d3.gmgdl@evledraar.gmail.com> ("Ævar Arnfjörð Bjarmason"'s message of "Thu, 30 Jun 2022 13:18:55 +0200")
Ævar Arnfjörð Bjarmason <avarab@gmail.com> writes:
> I'm suggesting that we replace our own validation with that of the SMTP
> server's, yes they're don't 1=1 correspond, but I think the part of the
> Venn diagram of where that matters is too small to worry about.
>
> It has the advantage of side-stepping issues with not having
> Email::Valid, as well as those cases where we're being overzelous about
> RFC validation, but our local SMTP is willing to try to deliver the
> mail.
>
> It's not like authors of MTAs haven't heard of that character limit, but
> they're also aware that that certain parts of the spec are loosely
> enforced, and that trying delivery is often better than rejecting a mail
> out of RFC pedantry.
I am not sure if that is a healthy direction to go.
If a local outbound relay is written with the knowledge that it will
never be talking to the SMTP at the final mailbox directly, I would
expect that it may not implement any validation at all, relying on
the "next hop" smarthost to reject anything invalid it throws at it.
So...
prev parent reply other threads:[~2022-06-30 21:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-20 0:44 [PATCH] git-send-email: Add --no-validate-email option Stewart Smith
2022-06-20 8:28 ` Ævar Arnfjörð Bjarmason
2022-06-21 0:11 ` brian m. carlson
2022-06-21 16:00 ` Junio C Hamano
2022-06-21 22:12 ` Ævar Arnfjörð Bjarmason
2022-06-22 0:48 ` brian m. carlson
2022-06-30 11:18 ` Ævar Arnfjörð Bjarmason
2022-06-30 21:03 ` Junio C Hamano [this message]
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=xmqqzghtdftx.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=sandals@crustytoothpaste.net \
--cc=tmz@pobox.com \
--cc=trawets@amazon.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 NNTP newsgroup(s).