EDGE 2019 Server - Unable to relay recipient in non-accepted domain
we are in the middle of a side by side upgrade of our on-prem Exchange servers from 2016 to 2019. The mailbox server and the hybrid server have both been successful with their 2016 counterparts readying to decommission. But each time i attempt to put the Exchange 2019 EDGE server in play, email from Exchange Online mailboxes is bounced back with "550 5.7.54 SMTP; Unable to relay recipient in non-accepted domain" no matter what destination. The process followed is: 1. remove Edge subscription from Exchange 2016 Edge and answer yes to remove synced objects 2. remove Edge subscription from on-prem Hybrid server 3. create new Edge subscription on the 2019 Edge server to create the xml file 4. copy xml file to Hybrid and create new Edge subscription on-prem. Hybrid will be the sync server for Edge. 5. Run Hybrid Configuration Wizard on the Exchange Hybrid server with the option checked for Central Mail Transport (requirement by the mail gateway keepers, not my first choice) On the surface, everything looks as it should, the Edge sync shows Success for status, the new connectors are there for Edge and O365 to on-prem and vice-versa. We can send email from external and on-prem mailboxes up to our users in the cloud on Exchange Online without issues. But any email, whether to arccorp.com (our primary domain) or to any other domain is bounced back within a few seconds. Same procedure is followed to fail back to the Exchange 2016 Edge server. And email starts to flow again in both directions. What am i missing here???
OWA via Exchange 2019 Edge
Hello Everybody, I'm upgrading from Exchange 2013 to Exchange 2019. I followed those steps: - Install two new Mailboxes servers in Co-existance with the old Exch 2013 servers. - Configure my new DAG - Move all mailboxes to the new servers. At this stade, all is working fine. I have an exchange 2013 CAS server in my DMZ that I want to replace with a new Exch 2019 Server Edge. To do, I followed the steps bellow: - Install the new Edge role server - Install a new certificate - Subscribe the edge server in my new mailbox server. When I configured my Firewall to route all HTTPS (OWA) flow to the new Edge server, I got a blank page instead of the OWA login page. I tried to test a direct access to https://myedgeserver.mydomain.com/owa to see if it can works, same result. The OWA requests are proxied by the Edge Server? How to verify it? I'm doining something wrong? Need your help after 2 days googling a solution. Regards.
mail queue disaster recovery on Edge Transport
Hi Guys I've an interesting question regarding the mail.que in an edge transport server. Recently was tasked to recover some mail stuck in the mail.que on one of the edge transport servers from a domain that i do not access to. Following instructions from: Change the location of the queue database | Microsoft Docs I extracted the following files: • Mail.que • Trn.chk • Trn.log • Trntmp.log • Trn nnn.log • Trnres00001.jrs • Trnres00002.jrs I then booted up my own dummy edge transport server on my own domain. However, even though when i run the cmdlet, get-queue i only receive the submission queue with no messages. There are no other queues. I am confident that the mail.que has been mounted correctly and that the transport exchange service is reading from it. Also double checked to confirm that the mail.que database is not corrupted. I have the following questions: 1. Can i view the mail.que from another domain if i mount it in my own domain? 2. Does the transport edge server have be connected to an internal mail server in order to show the queues? 3. Does my dummy transport edge server have to be the exact same CU version? Could this be the cause of the queues nit showing up? Thanks Edward
