On 2021-11-22 09:50 -0800, Kevin J. McCarthy <ke...@8t8.us> wrote:
> On Mon, Nov 22, 2021 at 11:22:33AM -0600, Aaron Poffenberger wrote:
> > I know this is related to Message-ID because if I go into muttrc(5)
> > and put `set hostname="example.com"` and send again to
> > u...@sbcglobal.net, the message goes through without issue.
> 
> Well, setting $hostname can affect other things too.
> 
> Without the patch, if you *just* change your $message_id_format to
> "<%z...@example.com>" you are saying it goes through.  Are you using $smtp_url
> or a local MTA?  Are there any other possible variables?

I use msmtp:

set sendmail=/usr/local/bin/msmtp

In my case just setting hostname was enough to fix it.

Setting message_id_format would probably work as well, but it would
also mean all emails sent through other email domains would have
Message-IDs from a different domain. In my case I send from 5
different email domains.

> 
> The behavior you are describing is highly unusual, as the MTA is usually
> just looking at the EHLO and envelope addresses.
> 
> > Also, as noted in my original, setting the fqdn of the Message-ID to
> > the fqdn of the From address make sense. When I'm sending email from
> > my laptop through gmail.com, the Message-ID picks-up the fqdn of my
> > laptop rather than using gmail.com.
> 
> The purpose of the Message-ID is to be unique.  Setting to the RHS to the
> local machine reduces the scope of randomness needed on the left side.
> There's no need or sense behind using the from domain.

Mail.app uses <GUID>@<from fqdn>. The Google web interface uses
<hash>@mail.gmail.com. Notifications come from
<hash>@notifications.gmail.com.

> 
> -- 
> Kevin J. McCarthy
> GPG Fingerprint: 8975 A9B3 3AA3 7910 385C  5308 ADEF 7684 8031 6BDA


Perhaps there's a better solution for those of use who mail through
multiple email domains.

The goal, then, would be to set the fqdn of the Message-ID by From. My
solution automates that, but is perhaps too naive.

Cheers,

--Aaron

Reply via email to