Re: Use From-address fqdn for Message-ID Generation

2021-11-24 Thread Aaron Poffenberger
On 2021-11-24 05:47 +, Claus Assmann wrote: > On Tue, Nov 23, 2021, Aaron Poffenberger wrote: > > > > > I know this is related to Message-ID... > > > > I'll back off this claim because I can't prove it beyond doubt. I've > > Of course you could. I explained how to do it, but (so far) you > h

Re: Use From-address fqdn for Message-ID Generation

2021-11-24 Thread Derek Martin
On Tue, Nov 23, 2021 at 04:40:28PM -0600, Aaron Poffenberger wrote: > As for making the fqdn of the From-address available during Message-ID > generation, I see value in it regardless. But it's not my software. I > don't get to decide. I'll leave it as it always was: a suggestion. At any rate, thi

Re: Use From-address fqdn for Message-ID Generation

2021-11-23 Thread Claus Assmann
On Tue, Nov 23, 2021, Aaron Poffenberger wrote: > > > I know this is related to Message-ID... > > I'll back off this claim because I can't prove it beyond doubt. I've Of course you could. I explained how to do it, but (so far) you haven't done that -- hence all those replies from people being sc

Re: Use From-address fqdn for Message-ID Generation

2021-11-23 Thread Derek Martin
On Tue, Nov 23, 2021 at 05:52:00PM -0600, Aaron Poffenberger wrote: > On 2021-11-23 17:28 -0600, Derek Martin wrote: > > > My mail domain has had correct reverse DNS entries for ages. As soon > > > as I received the error I verified it from multiple hosts to be sure. > > > > Well, the IP you gave

Re: Use From-address fqdn for Message-ID Generation

2021-11-23 Thread Aaron Poffenberger
On 2021-11-23 17:28 -0600, Derek Martin wrote: > > My mail domain has had correct reverse DNS entries for ages. As soon > > as I received the error I verified it from multiple hosts to be sure. > > Well, the IP you gave for it does not resolve, as I already showed > you--not on my laptop at home,

Re: Use From-address fqdn for Message-ID Generation

2021-11-23 Thread Derek Martin
On Tue, Nov 23, 2021 at 04:40:28PM -0600, Aaron Poffenberger wrote: > On 2021-11-23 14:47 -0600, Derek Martin wrote: > > > sbcglobal.net will fail delivery of the message with the following error: > > > > > > @*sbcglobal.net*: 550 5.7.1 Connections not accepted from > > > servers without a valid s

Re: Use From-address fqdn for Message-ID Generation

2021-11-23 Thread Aaron Poffenberger
On 2021-11-23 14:47 -0600, Derek Martin wrote: > > sbcglobal.net will fail delivery of the message with the following error: > > > > @*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 > > It's just told

Re: Use From-address fqdn for Message-ID Generation

2021-11-23 Thread Derek Martin
On Mon, Nov 22, 2021 at 11:22:33AM -0600, Aaron Poffenberger wrote: > On 2021-11-22 16:48 +, Claus Assmann wrote: > > I'm not sure the problem is really related to "fqdn of the Message-ID", > > could you give a real example: > > sending from the same host using the same addresses but two diffe

Re: Use From-address fqdn for Message-ID Generation

2021-11-22 Thread Patrick Shanahan
* 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-

Re: Use From-address fqdn for Message-ID Generation

2021-11-22 Thread Kevin J. McCarthy
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

Re: Use From-address fqdn for Message-ID Generation

2021-11-22 Thread Aaron Poffenberger
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

Re: Use From-address fqdn for Message-ID Generation

2021-11-22 Thread Patrick Shanahan
* 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

Re: Use From-address fqdn for Message-ID Generation

2021-11-22 Thread Aaron Poffenberger
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

Re: Use From-address fqdn for Message-ID Generation

2021-11-22 Thread Aaron Poffenberger
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

Re: Use From-address fqdn for Message-ID Generation

2021-11-22 Thread Kevin J. McCarthy
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"

Re: Use From-address fqdn for Message-ID Generation

2021-11-22 Thread Aaron Poffenberger
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 "

Re: Use From-address fqdn for Message-ID Generation

2021-11-22 Thread Aaron Poffenberger
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

Re: Use From-address fqdn for Message-ID Generation

2021-11-22 Thread Aaron Poffenberger
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

Re: Use From-address fqdn for Message-ID Generation

2021-11-22 Thread Steffen Nurpmeso
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

Re: Use From-address fqdn for Message-ID Generation

2021-11-22 Thread Aaron Poffenberger
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

Re: Use From-address fqdn for Message-ID Generation

2021-11-22 Thread Kevin J. McCarthy
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.

Re: Use From-address fqdn for Message-ID Generation

2021-11-22 Thread Claus Assmann
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

Re: Use From-address fqdn for Message-ID Generation

2021-11-22 Thread Kevin J. McCarthy
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

Re: Use From-address fqdn for Message-ID Generation

2021-11-22 Thread Aaron Poffenberger
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

Re: Use From-address fqdn for Message-ID Generation

2021-11-22 Thread Will Yardley
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

Re: Use From-address fqdn for Message-ID Generation

2021-11-22 Thread Aaron Poffenberger
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

Re: Use From-address fqdn for Message-ID Generation

2021-11-22 Thread Claus Assmann
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