I have a small Exchange environment, 10 PCs running Outlook 2007, 3 Droid phones, 2 iPhones and a couple Ipod touches. I came in this morning to the realization that external recipients are not getting mail from us. There are no errors or kickbacks, the mail just disappears. Here's the weird part, the Apple devices connect via EAS, and are able to send no problem, recipient gets the message. The Android devices and all Outlook users (EXCEPT ONE!) are able to send, but the recipient never gets the mail, its like its sent to nowhere. OWA gives the same result as Outlook.
Message tracking in Exchange Console shows the messages going out.
My SMTP logs show exactly the same result for a message that wasn't delivered, as one that was by that one user that is able to send.
All mail to internal users works properly.
EDIT: There is only ONE user that can send, and this is through Outlook or OWA. To clarify,
User1 cannot send with Outlook or OWA, or his Droid using EAS to my gmail address, but can connect his iTouch to EAS and it sends fine.
User2 can send to my gmail account using Outlook, OWA (from any computer) or his iTouch. This is the ONLY user not experiencing any issues
I cannot send to my gmail account using Outlook or OWA, but my iPhone works using EAS
Here is the SMTP log of an undelivered mail:
Tue, 19 Oct 2010 13:40:38 -0400", EHLO mail.domain.com,
250-cm-omr9 says EHLO to our.external.ip.address:34152,
250-8BITMIME,
250-PIPELINING,
250-AUTH=CRAM-MD5 LOGIN PLAIN,
250-AUTH CRAM-MD5 LOGIN PLAIN,
250 ENHANCEDSTATUSCODES,
AUTH LOGIN,
235 Authed. Go on.,
63,sending message
MAIL FROM:[email protected],
RCPT TO:[email protected],
RCPT TO:[email protected],
250 MAIL FROM accepted,
250 RCPT TO accepted,
250 RCPT TO accepted,
DATA,
"354 continue. finished with ""\r\n.\r\n""",
250 OK 5C/1B-10393-618DDBC4,
QUIT,
221 cm-omr9 closing connection,
Here is the SMTP log of a delivered mail:
220 cm-omr4 ESMTP ecelerity 2.2.2.41 r(31179/31189) Tue, 19 Oct 2010 13:42:18 -0400",
EHLO mail.domain.com,
250-cm-omr4 says EHLO to mail.domain.com:5524,
250-PIPELINING,
250-ENHANCEDSTATUSCODES,
250-8BITMIME,
250-AUTH=CRAM-MD5 LOGIN PLAIN,
250 AUTH CRAM-MD5 LOGIN PLAIN,
AUTH LOGIN,
235 Authed. Go on.,
65,sending message
MAIL FROM
RCPT TO:[email protected],
250 MAIL FROM accepted,
250 RCPT TO accepted,
DATA,
354 continue. finished with ""\r\n.\r\n""",
250 OK F9/15-07570-A78DDBC4,
QUIT,
221 cm-omr4 closing connection,
.220 cm-omr5 ESMTP ecelerity 2.2.2.41 r(31179/31189)
Try creating a new smtp sendmail connector, make sure namespace is * and its internet based delivery. see if you can right click disable for the existing one after the new one is setup and then try delivery.
I'd first suggest trying to send from OWA if the delivery works then at least this is a for sure way to bypass and client side issues and narrow it down to a server side problem.
Have you checked to make sure you are not on any block lists? mxtoolbox.com/SuperTool.aspx
Are you forwarding your email to a smart host or spam filtering device or service that requires authentication, because that's what it looks like to me. My initial suggestion would be to remove the smart host and\or spam filtering device or service from your configuration, configure the server to use DNS to deliver email, and test again. If email is successfully delivered then you know the problem is the smart host and\or spam filtering device or service (which is my guess). If it doesn't work then you've narrowed the problem down to your server.
The log entries show that the email was delivered to and accepted by the servers\devices cm-omr9 and cm-omr4, so that's where the problem lies, from my perspective.