From: Andrea Arcangeli <aarcange@redhat.com>
To: Jeff King <peff@peff.net>
Cc: git@vger.kernel.org
Subject: Re: send-email garbled header with trailing doublequote in email
Date: Wed, 2 Nov 2016 22:38:05 +0100 [thread overview]
Message-ID: <20161102213805.GJ4611@redhat.com> (raw)
In-Reply-To: <20161102211118.sc4j3fezfqxg23i3@sigill.intra.peff.net>
Hello,
On Wed, Nov 02, 2016 at 05:11:18PM -0400, Jeff King wrote:
> In fact, it is not even git that does this, but rather what
> Mail::Address happens to output (though git has fallback routines if
> that module isn't available that do the same thing).
If it's something in perl it should be fixed there indeed. I didn't
debug what exactly was wrong, so I sent it here first.
> But in either case, in my test, the actual email address is still
> extracted correctly and fed to the MTA, so the mail is delivered.
The email is delivered to the right email for me too, but to see the
problem you need to check the email itself, and look how the To: field
looks in the actual email in your mail client or web interface.
Don't you see whatever@yourhostname without spaces and @yourhostname
instead of the email domain?
If you still can't reproduce, maybe it's a different perl
Mail::Address, I'm using dev-perl/MailTools-2.140.0
From who receives the email it just looks garbled, but --dry-run
showed a correct To/Cc list so it was undetectable that it would end
up garbled during the real email delivery.
> So I'm not sure what you wanted to happen that didn't. Did you want
> --dry-run to complain about the bogus address? Did the message not get
> delivered for you? Something else?
If --dry-run complained and failed instead of passing and then sending
an email with garbled To/Cc list, it'd be more than enough. Either
that or it should generate a mail header that matches the output of
--dry-run so the review of --dry-run becomes meaningful again.
Thanks,
Andrea
next prev parent reply other threads:[~2016-11-02 21:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-02 20:27 send-email garbled header with trailing doublequote in email Andrea Arcangeli
2016-11-02 21:11 ` Jeff King
2016-11-02 21:38 ` Andrea Arcangeli [this message]
2016-11-02 22:04 ` Jeff King
2016-11-02 22:29 ` Andrea Arcangeli
2016-11-03 14:18 ` Jeff King
2016-11-03 14:33 ` demerphq
2016-11-04 0:03 ` Andrea Arcangeli
2016-11-04 0:11 ` Jeff King
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=20161102213805.GJ4611@redhat.com \
--to=aarcange@redhat.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
/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).