No solution here yet. I suspect you're correct in your conjecture about the source of the issue. Looking at the smptd source tree on CVS, I see no recent code changes that would explain the regression. I'm going to try upgrading OpenBSD snapshots later today.
On Tue, Mar 14, 2023 at 9:42 AM John Batteen <j...@batteen.com> wrote: > Has no one else experienced this? Scott, did you ever find a resolution? > For me it's only on a relay box mailing status reports so I put a special > rule in smtpd.conf to send it straight to the IP of the other box on the > network, so not a huge deal, but eventually I will have to upgrade my real > mail server from 7.2 to 7.3 and I can't have my mail stop working so I'm > curious to track down the real cause here. DNS resolution works fine for > everything else on the machine. I notice that OpenSMTPD is 7.0.0 on both > boxes so I'm actually inclined to think the changes may have been on the > OpenBSD side of things and I might take this to misc@ or tech@ if we > don't get anywhere here. > > Thanks for your time everyone. I sincerely appreciate all the work > everyone has put into these products, and they create a great deal of value > for me in my life. Best wishes to all. > > John > On 3/12/23 11:54, Scott Vanderbilt wrote: > > Just upgraded snapshots from OpenBSD 7.2-current (GENERIC.MP) #1047 to > OpenBSD 7.3-beta (GENERIC.MP) #1100. So, smtpd version is OpenSMTPD > 7.0.0. > > All of a sudden I'm getting MX resolution errors that were not occurring > immediately prior to the upgrade, e.g. > > Mar 10 11:56:20 callistino smtpd[81842]: smtp-out: Failed to resolve MX > for [relay:gmail.com,smtp]: Temporary failure in MX lookup > Mar 10 11:56:20 callistino smtpd[81842]: 0000000000000000 mta delivery > evpid=32d4773f133f952b from=<i...@datagenius.com> <i...@datagenius.com> > to=<datagen...@gmail.com> <datagen...@gmail.com> rcpt=<-> source="-" > relay="gmail.com" delay=6m40s result="TempFail" stat="Temporary failure > in MX lookup" > > There have been no smtpd configuration changes, smtpd.conf is same as > just prior to the snapshot upgrade. > > Host name resolution using the dig and host all seem to work fine, so it > doesn't seem to be a connectivity issue. > > Can anyone kindly give me some pointers on how to troubleshoot this issue? > > Many thanks in advance. > >
