Our Smartermail instance is hosted in our office, but we also have a mail server in our production environment that sends out emails as some of the email accounts that exist in Smartermail. For this example, I will use support@testcompany.com. This account exists in our smartermail instance but when users perform a password reset in our application, our application sends out a password reset mail through our production mail server with the same account. Support@testcompany.com is also used to send out various other system alerts from production as well.

It seems that since I updated smartermail from 15.x to 7242, employees have not been consistently receiving emails from support@testcompany.com. Often times employees don't receive emails from that address at all. Other times, they receive dozens of emails from that address all at once usually hours after they are expected to come.

In Smartermail, I have done everything I've can to ensure that support@testcompany.com and the mail server it is coming from is whitelisted:

-IP of the mail server is in the SMTP whitelist

-The IP is in the IP bypass list with spam filtering and greylisting disabled

-testcompany.com is in the trusted domains list

-support@testcompany.com is in the trusted email address list

-support@testcompany.com is not in an internal blocked senders list

-the mail server is not IDS blocked

-greylisting is disabled

-I can see traffic from the production mail server being allowed on our office firewall

-the emails that do come through show that the email is a trusted sender and spam filtering was skipped on them

I am not really seeing anything in the SMTP logs indicating emails from support@testcompany.com or the production mail server are being blocked. Is there anywhere else that I may have missed?