Kevin J. McCarthy wrote in
<[email protected]>:
|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
|>[email protected], 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
|"<%[email protected]>" you are saying it goes through. Are you using
|$smtp_url or a local MTA? Are there any other possible variables?
|
|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.
Fwiw it likely is SMTP related. My MUA has a smtp-hostname
variable in addition to deal with this:
smtp-hostname
[Option][v15-compat] Normally Mailx uses the variable from[432] to
derive the necessary ‘USER@HOST’ information in order to issue a
‘MAIL FROM:<>’ SMTP mta[476] command. Setting smtp-hostname[566]
can be used to use the ‘USER’ from the SMTP account (mta[476] or
the user[605] variable chain) and the given ‘HOST’ (hostname[443]
if the empty string is given, or the local hostname as a last
resort). This often allows using an address that is itself valid
but hosted by a provider other than from which (in from[432]) the
message is sent. Setting this variable also influences generated
‘Message-ID:’ and ‘Content-ID:’ header fields. If the [Option]al
IDNA support is available (see idna-disable[444]) variable assign‐
ment is aborted when a necessary conversion fails.
The problem came up with Yandex i think disliking me sending mail
via my Sourceforge account by then, .. yes, the examples show
# Here is a pretty large one which does not allow sending mails
# if there is a domain name mismatch on the SMTP protocol level,
# which would bite us if the value of from does not match, e.g.,
# for people who have a sXXXXeforge project and want to speak
# with the mailing list under their project account (in from),
# still sending the message through their normal mail provider
define XandeX {
set folder=~/spool/XandeX inbox=+syste.mbox sent=+sent
set from='Your Name <[email protected]>'
shortcut pop %:pop3s://pop.yaXXex.com
shortcut imap %:imaps://imap.yaXXex.com
set mta=smtps://USER:[email protected]:465 \
hostname=yaXXex.com smtp-hostname=
}
--steffen
|
|Der Kragenbaer, The moon bear,
|der holt sich munter he cheerfully and one by one
|einen nach dem anderen runter wa.ks himself off
|(By Robert Gernhardt)
