From: "brian m. carlson" <sandals@crustytoothpaste•net>
To: Drew DeVault <sir@cmpwn•com>
Cc: git@vger•kernel.org, contact@emersion•fr
Subject: Re: send-email: change the default value of sendmail.validate
Date: Sun, 1 Jul 2018 18:15:46 +0000 [thread overview]
Message-ID: <20180701181546.GD7965@genre.crustytoothpaste.net> (raw)
In-Reply-To: <20180629190751.GA2559@miku>
[-- Attachment #1: Type: text/plain, Size: 1213 bytes --]
On Fri, Jun 29, 2018 at 03:07:51PM -0400, Drew DeVault wrote:
> The purpose of this configuration option is to prevent your emails from
> blowing up on SMTP servers (rather than Extended SMTP servers). However,
> I find it often confuses people whose patches are otherwise correct, and
> they don't know how to solve the issue.
>
> I haven't seen an SMTP server in a very long time which doesn't support
> extended SMTP. The default behavior should probably change. If not, the
> error message should be more clear about action items to address the
> issue.
>
> I'll send a patch around to change this shortly.
Can you say a bit more about the exact error message you're seeing?
Are you suggesting that we not limit lines to 998 octets? I've seen
lots of mail servers that do reject mail over 998 octets. I've
configured Postfix to do so because being strict on mail standards is a
great way to stop spam.
If that's the issue you're seeing, it might be better to either
automatically encode those patches as binary patches or teach git
send-email and git am how to automatically handle quoted-printable.
--
brian m. carlson: Houston, Texas, US
OpenPGP: https://keybase.io/bk2204
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 867 bytes --]
next prev parent reply other threads:[~2018-07-01 18:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-29 19:07 send-email: change the default value of sendmail.validate Drew DeVault
2018-07-01 18:15 ` brian m. carlson [this message]
2018-07-02 0:17 ` Drew DeVault
2018-07-02 1:52 ` brian m. carlson
2018-07-02 2:05 ` Drew DeVault
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=20180701181546.GD7965@genre.crustytoothpaste.net \
--to=sandals@crustytoothpaste$(echo .)net \
--cc=contact@emersion$(echo .)fr \
--cc=git@vger$(echo .)kernel.org \
--cc=sir@cmpwn$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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