This patch changes mutt_gen_msgid (and related) to allow use of the
fqdn of the From address when generating the @ portion of the
Message-ID.
I use mutt to send email from more than one mail domain. I found that
some MTAs reject emails where fqdn of the Message-ID does not have a
reverse look-up,
On Mon, Nov 22, 2021, Aaron Poffenberger wrote:
> some MTAs reject emails where fqdn of the Message-ID does not have a
> reverse look-up, returning the error:
What do you mean by "reverse look-up" here?
A FQDN might have an A/ or MX record, not a PTR record.
> @*sbcglobal.net*: 550 5.7.1 Con
On 2021-11-22 16:48 +, Claus Assmann wrote:
> On Mon, Nov 22, 2021, Aaron Poffenberger wrote:
>
> > some MTAs reject emails where fqdn of the Message-ID does not have a
> > reverse look-up, returning the error:
>
> What do you mean by "reverse look-up" here?
> A FQDN might have an A/ or
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.
It's likely not related to the Message-Id
On 2021-11-22 09:27 -0800, Will Yardley 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 w
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 thi
On Mon, Nov 22, 2021, Aaron Poffenberger wrote:
> @*sbcglobal.net*: 550 5.7.1 Connections not accepted from
> servers without a valid sender domain.alph758 Fix reverse DNS for 198.51.100.1
Do you have the real DSN? Does it say during which stage this error
happened? Or does your server log show i
On Mon, Nov 22, 2021 at 10:09:16AM -0600, Aaron Poffenberger wrote:
Lastly, the patch updates the documentation and changes the default
message_id_format from "<%z@%f>", to "<%z@%F>" so that Message-IDs are
always generated using the fqdn of the From address.
I'm against changing the default.
On 2021-11-22 09:50 -0800, Kevin J. McCarthy 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 thro
Kevin J. McCarthy wrote in
:
|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.
|
|We
On 2021-11-22 10:02 -0800, Kevin J. McCarthy wrote:
> On Mon, Nov 22, 2021 at 10:09:16AM -0600, Aaron Poffenberger wrote:
> > Lastly, the patch updates the documentation and changes the default
> > message_id_format from "<%z@%f>", to "<%z@%F>" so that Message-IDs are
> > always generated using th
On 2021-11-22 17:54 +, Claus Assmann wrote:
> On Mon, Nov 22, 2021, Aaron Poffenberger wrote:
>
> > @*sbcglobal.net*: 550 5.7.1 Connections not accepted from
> > servers without a valid sender domain.alph758 Fix reverse DNS for
> > 198.51.100.1
>
> Do you have the real DSN? Does it say duri
On 2021-11-22 12:18 -0600, Aaron Poffenberger wrote:
> On 2021-11-22 10:02 -0800, Kevin J. McCarthy wrote:
> > On Mon, Nov 22, 2021 at 10:09:16AM -0600, Aaron Poffenberger wrote:
> > > Lastly, the patch updates the documentation and changes the default
> > > message_id_format from "<%z@%f>", to "
On Mon, Nov 22, 2021 at 12:06:29PM -0600, Aaron Poffenberger wrote:
On 2021-11-22 09:50 -0800, Kevin J. McCarthy 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"
On 2021-11-22 10:38 -0800, Kevin J. McCarthy wrote:
> On Mon, Nov 22, 2021 at 12:06:29PM -0600, Aaron Poffenberger wrote:
> > On 2021-11-22 09:50 -0800, Kevin J. McCarthy wrote:
> > > On Mon, Nov 22, 2021 at 11:22:33AM -0600, Aaron Poffenberger wrote:
> > > > I know this is related to Message-ID
On 2021-11-22 12:33 -0600, Aaron Poffenberger wrote:
> On 2021-11-22 12:18 -0600, Aaron Poffenberger wrote:
> > On 2021-11-22 10:02 -0800, Kevin J. McCarthy wrote:
> > > On Mon, Nov 22, 2021 at 10:09:16AM -0600, Aaron Poffenberger wrote:
> > > > Lastly, the patch updates the documentation and ch
* Aaron Poffenberger [11-22-21 14:30]:
> On 2021-11-22 10:38 -0800, Kevin J. McCarthy wrote:
> > On Mon, Nov 22, 2021 at 12:06:29PM -0600, Aaron Poffenberger wrote:
> > > On 2021-11-22 09:50 -0800, Kevin J. McCarthy wrote:
> > > > On Mon, Nov 22, 2021 at 11:22:33AM -0600, Aaron Poffenberger wrot
On 2021-11-22 14:37 -0500, Patrick Shanahan wrote:
>
> you do realize that att utilized yahoo mail, not an att system?
>
"AT&T dumps Yahoo after 15-year partnership"
https://www.marketwatch.com/story/att-dumps-yahoo-after-15-year-partnership-2016-05-04
$ host att.net
att.net has address 144.160
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 t
* Aaron Poffenberger [11-22-21 14:46]:
> On 2021-11-22 14:37 -0500, Patrick Shanahan wrote:
> >
> > you do realize that att utilized yahoo mail, not an att system?
> >
>
> "AT&T dumps Yahoo after 15-year partnership"
> https://www.marketwatch.com/story/att-dumps-yahoo-after-15-year-partnership-
20 matches
Mail list logo
