@DustinB3403 Yeah, Exchange 2013 and over. You have to also be on the last 2 Cumulative Updates from Exchange 2013, 2016 or 2019. For 2019 You only can get the updates through Microsoft Volume Licensing.
Yeah, a customer attempted an update from 2016 CU15.1 to CU19, it errored out on the last step, they restored (bad move) and had some mail flow issues for a bit.
I ought to have clarified. DUO MFA comes into play with Outlook for our mailboxes that are in Exchange Online. On-prem mailboxes (the few we have left aren't subject to DUO).
Are those that are left on prem - are they actual users? If so, I'm curious why they can't be migrated?
Eventually all users will be migrated, so, yes, we still have real users on-prem.
This is outside the scope of the original question / scenario, but I've learned a good bit during this process with much of that learning validating a few things I already knew, such as the value of taking the necessary time to plan, and prep the environment for migration (removing unnecessary objects, etc.).
That messages means a lot of things but yeah Whitelist on their Spam Filter end, Adding your IP to your SPF record, check if there is anything on the body of the message triggering the block on their end (i.e. URL or site link).
It is Office 365 with Exchange - I have created all the records that Microsoft wanted me to.
So, just to be clear, this is 100% not on my end, correct?
It shouldn't be on your end, the message is coming from the recipient's end server.
If you add SA to the original licenses - because you know the plan is the keep using Exchange going forward - it will raise the costs noticeably in the beginning, but come renewal time it will make it significantly less. Less enough to be under O365? not likely, hell, even the 5 year plan would be more expensive for onprem vs O365... but it might lower itself over time because of the SA difference.
SA is a scam to get more money. Always has been for the SMB. With negotiated pricing for Enterprise, it is the right thing.
If you're a company that only upgrades once every 10 years - then yeah... SA is a waste of money, but you're already talking about upgrading again in 5 years, so SA could very much make financial sense - show me the numbers before you poo poo it.
e got a strange one... I have a user here whose Emails go from whatever folder they are in to the Deleted Items folder after being read... Sometimes. Sometimes it doesn't happen for several minutes, and other times it happens right away.
The user hasn't been phished that we can tell. No bogus rules in Outlook forwarding things to the deleted items. Check both Web and Outlook 2016.
What am I not looking at that could be causing this?
Does the message trace in Exchange tell you anything? I know that when I had on-prem exchange and barracuda, I had weird issues where the attachment size restrictions being smaller/more restrictive on the Exchange server exhibited this behavior. The barracuda delivered, but Exchange rejected due to policy.
I need some help sorting out the exchange connectors on a server.
We were called in to figure out a spam problem. It's not severe and during our exam, we are trying to check the configuration of Exchange and get mail test tools to be happy.
Right now we are getting: Reverse DNS does not match SMTP Banner from mxtoolbox.
This is a simple MS Exchange setup; One Exchange server on a domain, people connecting with MS outlook from inside the building on the domain and from outside the building using Ms Outlook, and two copiers that can send e-mail.
The issue is all the receive connectors. It's not clear to me which one mxtoolbox is seeing.
A few users are having issues sending out emails. Not everytime, but intermittent. Has anyone experienced this type of issue before? I can use all the help I can get. I would like to know how to release the emails and avoid emails getting stuck again.
In advanced, thank you for your efforts.
Have any of your users been not able to send at all? I am not seeing that right now.
Great question dbeato! Here's the thing, I myself tried to email the same address while monitoring it from Barracuda. Nothing showed up as going out. It's strange cause we received email from the address.