• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1446
  • Last Modified:

There was a SMTP communication problem with the recipient's email server

All outgoing emails fail with:
Your message did not reach some or all of the intended recipients.

      Subject:      test
      Sent:      03/08/2007 12:26

The following recipient(s) could not be reached:

      user@domain.com on 03/08/2007 12:26
            There was a SMTP communication problem with the recipient's email server.  Please contact your system administrator.
            <craftynotions.com #5.5.0 smtp;550-e1636700.demon.co.uk (craftynotions.com) [83.105.91.89] is currently not>

Stopped working about a week ago. No idea what changed. Incoming email ok. Can send using Outlook Express to mail.craftynotions.com (same mail server) so domain host seems ok.
I've rummaged around on EE re similar messages and looked at some solutions, but no luck. ESM Recipient Policies show @craftynotions.com, not .local.
The isp say it is not a reverse dns problem. FQDN is set to our domain, craftynotions.com. They are sure it is a exchange problem at our end.

Help much appreciated!
 
0
DSL8159
Asked:
DSL8159
1 Solution
 
SembeeCommented:
Is Demon Internet your ISP?
If so you have my deepest sympathy.

Anyway, the server you are sending your email out through is rejecting your message. If that server is not Demon's server then you need to adjust the SMTP Connector to authenticate when sending email.
ESM, Connectors. Right click on the SBS SMTP Connector and choose properties.
Click on the tab Advanced and then Outbound Security. Enter the username and password required by the operator of the server you send email through in to the box. Apply/OK out.

The reason it works in Outlook Express is that you have probably configured it with an account that checks POP3 first. Most ISP email servers will then allow you to send if you check your email first. Exchange cannot do that.

Simon.
0
 
davidwainwrightCommented:
If the incoming mail is being directed to 62.149.36.116 (where your A & MX records are pointing) could this not be a result of the origin IP not matching the domain of the return address (83.105.91.89)? Have you changed anything on the public IP side of things?

Dave
0

Featured Post

Free Tool: ZipGrep

ZipGrep is a utility that can list and search zip (.war, .ear, .jar, etc) archives for text patterns, without the need to extract the archive's contents.

One of a set of tools we're offering as a way to say thank you for being a part of the community.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now