Emails not arriving internally (Full Version)

All Forums >> [Microsoft Exchange 2003] >> Exchange 2003 SBS



Message

EssCee -> Emails not arriving internally (30.Jan.2007 11:04:07 AM)

Were running SBS 2003. I have one account which when they send an email to another user internally takes about anything from a few hours to a day to deliver. Ive checked the email client settings but not sure what could cause the problem can anyone suggest any ideas please?

Thanks



uemurad -> RE: Emails not arriving internally (30.Jan.2007 11:27:16 AM)

Check Message Tracking to see if you can determine where the delay is happening.



EssCee -> RE: Emails not arriving internally (30.Jan.2007 11:34:20 AM)

I think message tracking was off (couldnt think of a reason why?????) so turned it back on by right clicking the server and selecting enable message tracking Ill report back with the error message if any, in case i cant figure it out.

Thanks

Update:

Even with messag tracking on nothing is listed. Do i need to enable another setting for logging to enable?



uemurad -> RE: Emails not arriving internally (31.Jan.2007 2:42:23 PM)

When you say that nothing is listed, are you saying that the search comes back empty, or that you are getting some sort of message or error?

What are you using for the search parameters?  I'd suggest only entering the sending address, the mailbox server he/she resides on, and a limited time range.  Have that person send a test message to the other, then narrow the time range to make the search faster.



EssCee -> RE: Emails not arriving internally (31.Jan.2007 3:47:28 PM)

quote:

ORIGINAL: uemurad

When you say that nothing is listed, are you saying that the search comes back empty, or that you are getting some sort of message or error?

What are you using for the search parameters?  I'd suggest only entering the sending address, the mailbox server he/she resides on, and a limited time range.  Have that person send a test message to the other, then narrow the time range to make the search faster.


Actually i have message tracking working i think. Everything is normal but when i send an email its not listed in message tracking until its about 30 seconds away from the recepient receiving it. So I send a message from the problem user to another user at 00:00 nothings listed in message tracking. At around (for example) 04:00 its at the server and in message tracking saying its deleivered. Checking the mail box (of the non problematic user) - its there and no error messages. Hope that makes sense.

Thanks



uemurad -> RE: Emails not arriving internally (31.Jan.2007 5:31:37 PM)

Using Message Tracking isn't so much to try to catch the message in flight, but to figure what might be slowing it down.  Wait until the message arrives.  There should be several entries per message indicating what happened to it along the way.  One or more time gaps should be evident when reviewing the information.  It will also be noted if there is a routing issue, as you'll see that other servers appear (unexpectedly) in the list.  Unless you have a lot of traffic, most of the entries should be fairly close together in time.

Does the timestamp MT indicates coincide with when the recipient gets the message?  If not, perhaps you're looking at a client-level issue instead.



EssCee -> RE: Emails not arriving internally (1.Feb.2007 6:08:22 AM)

Hello. MT tracking only shows 1 time i.e. 13:58 for all the events. Even when it was sent 4 hours ago. I also noticed when the message is received it seems to have gone external then come back in (We have a a tag for all external mail that arrives from outside and this internal mail had that tag whenit shoudlnt)

Im thinking of backing up the mails to a pst file. Deleting the account in AD and the mailbox in system manager for exchange. Then recreating the same user and importing the data back in. Would this be recommended?



uemurad -> RE: Emails not arriving internally (1.Feb.2007 9:39:32 AM)

I wouldn't recommend recreating the user.  There are two mysteries here, and recreating the user won't really help either.

First, MT shows that the message was delivered to the mailbox immediately.  The mystery is why doesn't the recipient show it?  If this is fairly easy to reproduce, I'd send a test, then force the recipient's Outlook to check for messages.  You can do this by clicking on Send/Receive, by taking Outlook out of cache mode, or by using Outlook Web.

Second, you say that it appears the message was routed outside and then back in.  You can confirm this by examining the header of one of these messages.  In the recipient's mailbox, right-click on the message in question and select Options.  It will show all the "hops" between sending and receiving system.  For mailboxes on the same server, you should see no server names or IP addresses anywhere in the header.



EssCee -> RE: Emails not arriving internally (1.Feb.2007 11:16:28 AM)

Thanks. Finally figured it. It seems the machine was swapped and had a static IP address and pointing to the wrong domain. Unfortunately the IT admin before me set all PCs with static IPs and noticed same IPs in DNS so changed that and TAADAA.

Thanks for your help, but curiously i checked the headers to see what was there i had:
quote:


Microsoft Mail Internet Headers Version 2.0
X-PMWin-Version: 2.6.1, Antispam-Engine: 2.5.0, Antivirus-Engine: 2.42.3
thread-index: AcdGE27Bds8GyDz0TZGbv2e7AKTehg==
Thread-Topic: testing[Scanned]
X-PMWin-Spam: Gauge=IIIIIIII, Probability=8%, Report='__USER_AGENT, __HAS_MSGID, __SANE_MSGID, __MIME_VERSION, __CT, __CTYPE_CHARSET_QUOTED, __CT_TEXT_PLAIN, __CTE, __RUS_MIME_NO_TEXT, __BODY_MISSING, __MIME_TEXT_ONLY'
Received: from StrangeNAME.ISP.com ([234.123.78.010]) by server.DoMaIn.local with Microsoft SMTPSVC(6.0.3790.0); Thu, 1 Feb 0017 15:12:46 +0000
Received: from [192.168.001.040] (mail.DoMaIn.co.uk [45.678.89.91] (may be forged)) by StrangeNAME.ISP.com with ESMTP id ****; Thu, 1 Feb 0017 13:08:30 GMT
User-Agent: Microsoft-Entourage/10.0.0.1309
Date: Thu, 01 Feb 0017 13:10:14 +0000
Subject: testing[Scanned]
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
Content-Class: urn:content-classes:message
Importance: normal
Priority: normal
From: "PROBLEM_USER" <testMAIL@DoMaIn.co.uk>
To: "USER" <USER@DoMaIn.co.uk>,
Message-ID: <C1E79736.1A18%testMAIL@DoMaIn.co.uk>
MIME-Version: 1.0
Content-Type: text/plain;
charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Return-Path: <testMAIL@DoMaIn.co.uk>
X-OriginalArrivalTime: 01 Feb 0017 15:12:46.0312 (UTC) FILETIME=[6DC87924680:01C74613]


The part that alerts me is "may be forged" - any idea whats that about?. Thanks for all your help



uemurad -> RE: Emails not arriving internally (1.Feb.2007 11:39:58 AM)

Glad to hear you've resolved the issue.

The "may be forged" indicates inconsistent DNS information.  I'd recommend that you send a message to a yahoo.com address (create one if you don't have one).  Yahoo mail has the option to look at the headers (Hotmail didn't the last time I tested).  Make sure that the same thing doesn't appear.  If the message never arrives, I'd confirm by manually testing with Telnet via port 25.  If you really are sending out messages with the private address appended (192.168.x.x), Yahoo may reject your message because reverse DNS will fail.



Page: [1]