No SMTP server defined. Use real server address instead of 127.0.0.1 in your account
we have a single windows sbs2011 running exchange and windows 10 pro clients running outlook2007.
everything was running ok, but today, for some reason, for certain email contacts (not all), we receive a bounce back stating :-
No SMTP server defined. Use real server address instead of 127.0.0.1 in your account
I did research this and noticed an article relating to avast cloudcare, so we disabled the core shields on both the client and mail server, along with our vamsoft ORF antispam, but we still get the same error.
Can anyone advise how we go about resolving this?
Any advice much appreciated.
Thanks.
everything was running ok, but today, for some reason, for certain email contacts (not all), we receive a bounce back stating :-
No SMTP server defined. Use real server address instead of 127.0.0.1 in your account
I did research this and noticed an article relating to avast cloudcare, so we disabled the core shields on both the client and mail server, along with our vamsoft ORF antispam, but we still get the same error.
Can anyone advise how we go about resolving this?
Any advice much appreciated.
Thanks.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
core shields are what avast cloudcare calls their anti virus services.
I did disable them but it did not seem to make any difference.
I did not restart outlook after closing down the shields though, or restart the workstation. Would I need to do that?
I am not sure where to check whether outlook is using 127.0.0.1 or localhost? Thought that was the same thing? Can you advise where I would find this?
Many thanks.
I did disable them but it did not seem to make any difference.
I did not restart outlook after closing down the shields though, or restart the workstation. Would I need to do that?
I am not sure where to check whether outlook is using 127.0.0.1 or localhost? Thought that was the same thing? Can you advise where I would find this?
Many thanks.
Regarding the certificate error, please check whether it is present or not in the past.
did you change the certificate recently?
The default receive connector of Exchange 2010 should not use any TLS certificate as it is not used for client submission.
run this
Get-ReceiveConnector | fl *
and post the output
did you change the certificate recently?
The default receive connector of Exchange 2010 should not use any TLS certificate as it is not used for client submission.
run this
Get-ReceiveConnector | fl *
and post the output
ASKER
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
it was indeed the cloudcare antivirus on our server. We had to remove both the webshield and mail shield modules from our server, restart and it resolved the issue.
many thanks to all
many thanks to all
Glad you solved!
Re the connectors, the receive connector inspection is unrelated to 127.0.0.1 issue but it is usually related to the certificates issue (that you can ignore because, anyway, the name referred in the eventvwr log entry is the private one).
Ciao!
Re the connectors, the receive connector inspection is unrelated to 127.0.0.1 issue but it is usually related to the certificates issue (that you can ignore because, anyway, the name referred in the eventvwr log entry is the private one).
Ciao!
ASKER
The client has confirmed that when they reply to an email from the problem destination, it goes through ok.
I also noticed the following event on the server application event log :-
Not sure whether this is even related, but thought I would include it.
Thanks.