On Mon, Nov 22, 2021 at 01:30:30PM -0600, Aaron Poffenberger wrote:
I'm happy to try changing configuration using an unpatched version, but I have to be careful sending too many test messages to ATT/sbcglobal.net. They have an itchy RBL trigger.
I'd appreciate if you would try it out.Due to the US holiday coming up, I won't be able to take a closer look until next week, so if you have time please do try verifying a failure and then retrying exactly the same thing except for swapping *only* the message-id via 'set message_id_format = "<%z...@example.com>"'.
I'm curious what you and the other say changes in the headers under the various conditions of setting hostname or message_id_format. The only changes I'm seeing in the headers when hostname is set is the fqdn of the Message-ID.
We're concerned with the SMTP envelope, which won't be reflected in the headers saved in your Sent folder. That is usually the cause for these kinds of errors, because the MTA itself isn't usually digging inside the message itself (except for spam processing).
$hostname is used by mutt_fqdn() and mutt_default_from(). The $smtp_url handling uses it for an initial EHLO. Bouncing can also use this. Email addresses without a hostname can also ending up using it.
So there are some possibilities it's leaking into the "envelope from" somehow, but I haven't looked deeply at the flow yet. Maybe $use_envelope_from is set in your muttrc, or the envelope from is being set in msmtp some other way dependent on your $hostname.
-- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA
signature.asc
Description: PGP signature
