Hi there we have a issue with a server whereby the management shell/console can no longer access the server after making some changes.
As well as this prior we had emails from btyahoo stuck in the queue not sending out.
For the purpose of this question we have used fake dns names
The external name is mail.example.co.uk
The local name is tragic.example.local
Due to emails stuck in the queue we ran DNS report
We had DNS issue saying the SMTP greeting was malformed and didnt match the PTR of your mail server.
The greeting was “220 tragic.example.local Microsoft….”
We understood the greeting is generated from the “receive connectors within Exchange. They all said “TRAGIC” so a collegue changed them to “mail.example.co.uk”.
To achieve they had to remove from the Authentication tab “Exchange Server Authentication”, as on reading this is only required if you have other Exchange servers talking to each other something this server does not currently have.
Upon changing this emails were still stuck in the queue so this may have been red herring
On hovering over each queue there is a “last error message”
421 4.7.1 [TS03] All messages from (server fake ip example 99.999.9.999) will be permanently deferred; Retrying will NOT succeed.
If you go onto Yahoo’s webpage here; http://help.yahoo.com/kb/index?page=content&y=PROD_MAIL_ML&locale=en_US&id=SLN3436&impressions=true
it explains the problem.
This article provides reasons why you could receive a delivery failure message containing the error "421 4.7.1 [TS03]" and "messages from x.x.x.x. permanently deferred" when sending email messages to Yahoo! from an third-party service.
My collegue then rebooted the server and exchange service didnt come back up properly the service wouldnt start. Setting to manual allowed the service to then start. The store was mounted and we can confirm email flow is working to and from the server except for the Yahoo issue.
But we now cannot access the exchange management console or shell.
Would the above connector change cause this?
We have run a exchange management troubleshooter which says
[tragic.example.local] connecting to remote server failed (this is local server to this command!) with the following error message: The client cannot connect to any exchange server in the current site.
The http binding has been removed from the default web site, exchange powershell needs to be configured so that the IP addess is All unassigned the port is 80 and the host name is ..... (we checked and IIS looks to have default site all unassigned to port 80) it offers to resolve/reconned we tried this but it didnt resolve the issue.
Can you please assist with restoring connection to EMC EMS?
Can you please assist with preventing yahoo messages in queue?