Not as far as I know... we havent seen this issue.

We have had 2 scenarios in a month.

sounds like the issue we are experiencing, I opened a ticket and am not impressed with how they are handling it. Disable "Reverse DNS" and tell me if your situation improves

Question would be whether this is a smartermail issue or an intermittent failure / timeout in the infrastructure level? Unless one has a decent repro case that is brutally hard to nail down.

I have been having issues with this in build 8629. I have filed a ticket with ST support a month ago and they did identify an issue, so they escalated it to development to get a fix. I was notified today that the fix is included in the next Beta build for the next .NET release, which I was also told could be in Beta for the next 2-3 months. Not really happy about the fact they won't have a fix from the sounds of it in this version.

I can tell you looking at example emails, SPF, DMARC and ReverseDNS are all experiencing false positves. My first guess is a slow lookup that SM assumes it failed and scores it as such. I can't confirm that but it's the only thing that makes sense. Changing DNS in the SM interface didn't help all that much either.

So it seems either install the Beta on your production server or tough it out for the next several months before the Beta is released as a production build. Not too keen on running a Beta build on my production server and possibly introduce other issues.

These SPF issues are the reason we've been holding back on some overdue upgrades as well. Was really hoping this would be in the next update even if it's the only fix!

"I've been informed that our next big update of SmarterMail uses an entirely new DNS client, and we have not been able to replicate these issues on that build."

Riley French

SmarterTools 

Ron, we were able to approach DNS very differently because of .NET 7 and it works incredibly well.

The BETA is available now!

Jay, I found out who told you 2 to 3 months and Zach has repented.  His manager already talked to him about that before I reached out to the team.  The BETA will be about six weeks.  Hope you give it a try, lot of good stuff in there!

Tim I was told in response to a ticket I had open on this that it could be 2-3 months by the tech on the ticket. I was not taking that as the end all be all timeframe and I'm not trying to get anyone in trouble here. With the beta, I may have to run it on my production server, is this recommended?

Also having rDNS issues, specific to Gmail. We've adjusted our SMTP blocking and SPAM scoring as a workaround until the new .NET version of SM becomes available.

We're also noticing some Reverse DNS Lookup failures and "SPF Fail" occurrences. This is using the current Build 8664 (Sep 21, 2023) and causes messages to get rejected or put in the Spam folder.

Right. We're on Build 8664 (Sep 21, 2023) as well.

Also getting rDNS and SPF Lookup errors. Seems isolated to messages from outlook.com / Microsoft 365 users.

We have a number of support tickets open on this.

We've disabled SMTP Blocking for rDNS and SPF currently as a workaround. 

Anyone else have workarounds for this? Other than update to the BETA?

Odd that it's just starting now out of the blue. We've been on Build 8664 for a month now.

Flush your dns cache every 15 mins.... it will solve it as well

We received another report of this with Gmail. Do you guys have a general idea of when the new version will be available? This year?

We will be out of BETA in a few weeks.

Thank you Tim. Much appreciated. 

Not really complaining, but this occurred again with Reverse DNS again today.

96.102.200.9

resqmta-h1p-028591.sys.comcast.net

Looking forward to the fix.

Tim, how is the timeline look for out of BETA. Perhaps this week?