Re: send-email garbled header with trailing doublequote in email

From: Andrea Arcangeli <aarcange@redhat.com>
Date: Nov 2, 2016, 21:38 UTC
Message-ID: <20161102213805.GJ4611@redhat.com>
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