Exchange 2003 giving occasional NDR's

We have an Exchange 2003 Server awaiting a migration to 2013.
Before we can migrate we need to find out the reason for some occasional mail, sending NDR's to a sender of email. The mail that generates an NDR, will 'leak through' to the recipients with no listed names in the To and no subject.
The funny thing is, in the Exchange tracking log, I can see the mail inbound, accepted and delivery started, but then you see the NDR being send out.
On the protocol logs on the Exchange server I am not seeing any issues.
On the protocol logs on the Edge Server again, I am not seeing any issues.
Not too sure where to go to next, or what to log next to find the issue.
Logs, email headers etc following.
Email header from mail that leaked through and NDR created.
Microsoft Mail Internet Headers Version 2.0
Received: from edge1.ReceiverDomain.com ([ReceiverDomainIP]) by mail.ReceiverDomain.com with Microsoft SMTPSVC(6.0.3790.1830);
Received: from edge1.ReceiverDomain.com ([ReceiverDomainIP]) by mail.ReceiverDomain.com with Microsoft SMTPSVC(6.0.3790.1830);
Tue, 1 Oct 2013 15:59:26 +0100
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
X-WatchGuard-AntiVirus: part scanned. clean action=allow
From: [email protected]
Bcc:
Return-Path: [email protected]
Message-ID: <[email protected]>
X-OriginalArrivalTime: 01 Oct 2013 14:59:26.0825 (UTC) FILETIME=[D2ADBD90:01CEBEB6]
Date: 1 Oct 2013 15:59:26 +0100
Email header from accepted email
Microsoft Mail Internet Headers Version 2.0
Received: from edge1.ReceiverDomain.com ([ReceiverDomainIP]) by mail.ReceiverDomain.com with Microsoft SMTPSVC(6.0.3790.1830);
Tue, 1 Oct 2013 16:01:04 +0100
Received: from SENDERINTMAIL.prod.ds.SenderDomain.com (SenderDomainIP) by
edge1.ReceiverDomain.com (ReceiverDomainIP) with Microsoft SMTP Server (TLS) id
8.1.436.0; Tue, 1 Oct 2013 16:00:58 +0100
Received: from SENDERINT2.prod.ds.SenderDomain.com ([169.254.1.152]) by
SENDERINTMAIL.prod.ds.SenderDomain.com ([169.254.2.131]) with mapi id
14.02.0298.004; Tue, 1 Oct 2013 16:01:00 +0100
From: "Sender, of Email" <[email protected]>
To: "Sender, of Email" <[email protected]>, Receiver1
<[email protected]>, "Receiver2" <[email protected]>
CC: SenderDomainFactsheets <[email protected]>, Receiver3
<[email protected]>, Receiver4<[email protected]>
Subject: RE: Subject line
Thread-Topic: Subject line
Thread-Index: Ac6+lzKxFtHC6ZksQlSoTTK2f8AezQAD2bEQAAFJwVAAARDjsAABYWnAAABGLHAAABXhwA==
Date: Tue, 1 Oct 2013 15:00:59 +0000
Message-ID: <[email protected]rDomain.com>
References: <[email protected]al>
<[email protected]rDomain.com>
<[email protected]al>
<[email protected]rDomain.com>
<[email protected]al>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [SenderIntIP2]
Content-Type: multipart/alternative;
boundary="_000_4C2FB0C9647B0140A70CEEA1B0F99FCA091F15B1LONEXH002PAprod_"
MIME-Version: 1.0
Return-Path: [email protected]
Received-SPF: Pass (edge1.ReceiverDomain.com: domain of [email protected]
designates SenderDomainIP as permitted sender)
receiver=edge1.ReceiverDomain.com; client-ip=SenderDomainIP;
helo=SENDERINTMAIL.prod.ds.SenderDomain.com;
X-WatchGuard-Spam-ID: str=0001.0A0B0204.524AE3AE.00B3,ss=1,re=0.000,fgs=0
X-WatchGuard-Spam-Score: 0, clean; 0, no virus
X-WatchGuard-Mail-Client-IP: 169.254.1.152
X-WatchGuard-Mail-From: [email protected]
X-WatchGuard-Mail-Recipients: [email protected];[email protected];[email protected];[email protected]
X-OriginalArrivalTime: 01 Oct 2013 15:01:04.0215 (UTC) FILETIME=[0CBA4670:01CEBEB7]
--_000_4C2FB0C9647B0140A70CEEA1B0F99FCA091F15B1LONEXH002PAprod_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
X-WatchGuard-AntiVirus: part scanned. clean action=allow
--_000_4C2FB0C9647B0140A70CEEA1B0F99FCA091F15B1LONEXH002PAprod_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
X-WatchGuard-AntiVirus: part scanned. clean action=allow
--_000_4C2FB0C9647B0140A70CEEA1B0F99FCA091F15B1LONEXH002PAprod_--
Exchange 2003 Tracking log
Logs from Edge Server for the emails, both the received email that generated the NDR and the email that was resent and received in full
Timestamp : 01/10/2013 15:46:49
ClientIp : SenderDomainIP
ClientHostname :
ServerIp : ReceiverDomainIP
ServerHostname : edge1
SourceContext : 08D0891A81DE4619;2013-10-01T14:46:48.159Z;0
ConnectorId : edge1\Default internal receive connector EDGE1
Source : SMTP
EventId : RECEIVE
InternalMessageId : 1348948
MessageId : <[email protected]nderDomain.com>
Recipients : {[email protected], [email protected], [email protected], [email protected]}
RecipientStatus : {}
TotalBytes : 48832
RecipientCount : 4
RelatedRecipientAddress :
Reference :
MessageSubject : RE: Subject line
Sender : [email protected]
ReturnPath : [email protected]
MessageInfo : 00A:
Timestamp : 01/10/2013 15:46:49
ClientIp : ReceiverDomainIP
ClientHostname : edge1
ServerIp : 10.0.0.164
ServerHostname :
SourceContext : 08D0891A81DE461A
ConnectorId : sendToExchange2003
Source : SMTP
EventId : SEND
InternalMessageId : 1348948
MessageId : <[email protected]SenderDomain.com>
Recipients : {[email protected], [email protected], [email protected], [email protected]}
RecipientStatus : {250 2.1.5 [email protected] , 250 2.1.5 [email protected] , 250 2.1.5 [email protected] , 250 2.1.5 [email protected] }
TotalBytes : 48832
RecipientCount : 4
RelatedRecipientAddress :
Reference : {, , , }
MessageSubject : RE: Subject line
Sender : [email protected]
ReturnPath : [email protected]
MessageInfo : 01/10/2013 15:46:48
Timestamp : 01/10/2013 15:59:23
ClientIp : SenderDomainIP
ClientHostname :
ServerIp : ReceiverDomainIP
ServerHostname : edge1
SourceContext : 08D0891A81DE4680;2013-10-01T14:59:21.660Z;0
ConnectorId : edge1\Default internal receive connector EDGE1
Source : SMTP
EventId : RECEIVE
InternalMessageId : 1348977
MessageId : <4C2FB0C9647B0140A70CEEA1B0F99FCA091F1592@LON-EXH002P
A.prod.ds.SenderDomain.com>
Recipients : {[email protected], [email protected], [email protected], [email protected]}
RecipientStatus : {}
TotalBytes : 61503
RecipientCount : 4
RelatedRecipientAddress :
Reference :
MessageSubject : RE: Subject line
Sender : [email protected]
ReturnPath : [email protected]
MessageInfo : 00A:
Timestamp : 01/10/2013 15:59:23
ClientIp : ReceiverDomainIP
ClientHostname : edge1
ServerIp : 10.0.0.164
ServerHostname :
SourceContext : 08D0891A81DE4681
ConnectorId : sendToExchange2003
Source : SMTP
EventId : FAIL
InternalMessageId : 1348977
MessageId : <4C2FB0C9647B0140A70CEEA1B0F99FCA091F1592@LON-EXH002P
A.prod.ds.SenderDomain.com>
Recipients : {[email protected], [email protected], [email protected], [email protected]}
RecipientStatus : {503 5.5.2 Need mail command., 503 5.5.2 Need mail command., 503 5.5.2 Need mail command., 503 5.5.2 Need mail command.}
TotalBytes : 61503
RecipientCount : 4
RelatedRecipientAddress :
Reference : {<cdba64fe-f673-439a-afda-136c285acdf4>, <cdba64fe-f6 73-439a-afda-136c285acdf4>, <cdba64fe-f673-439a-afda- 136c285acdf4>, <cdba64fe-f673-439a-afda-136c285acdf4>}
MessageSubject : RE: Subject line
Sender : [email protected]
ReturnPath : [email protected]
MessageInfo :
Timestamp : 01/10/2013 16:00:59
ClientIp : SenderDomainIP
ClientHostname :
ServerIp : ReceiverDomainIP
ServerHostname : edge1
SourceContext : 08D0891A81DE4695;2013-10-01T15:00:57.647Z;0
ConnectorId : edge1\Default internal receive connector EDGE1
Source : SMTP
EventId : RECEIVE
InternalMessageId : 1348985
MessageId : <[email protected]enderDomain.com>
Recipients : {[email protected], [email protected], [email protected], [email protected]}
RecipientStatus : {}
TotalBytes : 62815
RecipientCount : 4
RelatedRecipientAddress :
Reference :
MessageSubject : RE: Subject line
Sender : [email protected]
ReturnPath : [email protected]
MessageInfo : 00A:
Timestamp : 01/10/2013 16:01:01
ClientIp : ReceiverDomainIP
ClientHostname : edge1
ServerIp : 10.0.0.164
ServerHostname :
SourceContext : 08D0891A81DE4697
ConnectorId : sendToExchange2003
Source : SMTP
EventId : SEND
InternalMessageId : 1348985
MessageId : <[email protected]enderDomain.com>
Recipients : {[email protected], [email protected], eg
[email protected], SenderDomainFactsheets@FundAss
ist.com}
RecipientStatus : {250 2.1.5 [email protected] , 250 2.1.5 [email protected] , 250 2.1.5 receiver1@receiverdomain, 250 2.1.5 [email protected] }
TotalBytes : 62815
RecipientCount : 4
RelatedRecipientAddress :
Reference : {, , , }
MessageSubject : RE: Subject line
Sender : [email protected]
ReturnPath : [email protected]
MessageInfo : 01/10/2013 16:00:58
Joe

Edge server 2007 to Exchange 2003
2013-11-27T10:00:53.932Z,sendToExchange2003,08D0AFC938C280EE,14,10.11.0.164:56317,10.0.0.164:25,>,MAIL FROM:<[email protected]> SIZE=62314 AUTH=<>,
2013-11-27T10:00:53.948Z,sendToExchange2003,08D0AFC938C280EE,15,10.11.0.164:56317,10.0.0.164:25,<,250 2.1.0 [email protected]...Sender OK,
2013-11-27T10:00:53.948Z,sendToExchange2003,08D0AFC938C280EE,16,10.11.0.164:56317,10.0.0.164:25,>,RCPT TO:<[email protected]>,
2013-11-27T10:00:53.948Z,sendToExchange2003,08D0AFC938C280EE,17,10.11.0.164:56317,10.0.0.164:25,<,250 2.1.5 [email protected] ,
2013-11-27T10:00:53.948Z,sendToExchange2003,08D0AFC938C280EE,18,10.11.0.164:56317,10.0.0.164:25,>,BDAT 61973 LAST,
2013-11-27T10:00:54.197Z,sendToExchange2003,08D0AFC938C280EE,19,10.11.0.164:56317,10.0.0.164:25,<,503 5.5.2 Need mail command.,
2013-11-27T10:00:54.213Z,sendToExchange2003,08D0AFC938C280EE,20,10.11.0.164:56317,10.0.0.164:25,>,QUIT,
2013-11-27T10:00:54.213Z,sendToExchange2003,08D0AFC938C280EE,21,10.11.0.164:56317,10.0.0.164:25,<,221 2.0.0 mail.Receiver.com Service closing transmission channel,
Exchange 2003 Protocol log
2013-11-27 10:01:03 10.11.0.164 edge1.Receiver.com SMTPSVC1 MAIL1 10.0.0.164 0 EHLO +edge1.Receiver.com 250 0 SMTP
2013-11-27 10:01:03 10.11.0.164 edge1.Receiver.com SMTPSVC1 MAIL1 10.0.0.164 0 MAIL +FROM:<[email protected]> 250 0 SMTP
2013-11-27 10:01:03 10.11.0.164 edge1.Receiver.com SMTPSVC1 MAIL1 10.0.0.164 0 RCPT +TO:<[email protected]> 250 0 SMTP
2013-11-27 10:01:03 10.11.0.164 edge1.Receiver.com SMTPSVC1 MAIL1 10.0.0.164 0 BDAT <[email protected]> 250 62 SMTP
2013-11-27 10:01:03 10.11.0.164 edge1.Receiver.com SMTPSVC1 MAIL1 10.0.0.164 0 BDAT +22244 503 0 SMTP
2013-11-27 10:01:03 10.11.0.164 edge1.Receiver.com SMTPSVC1 MAIL1 10.0.0.164 0 QUIT edge1.Receiver.com 240 0 SMTP
Joe

Similar Messages

Exchange 2003 -2010 cross forest (NDR 5.4.6)

Hi.
Have: Exchange 2003+2010 in source forest. Exchange 2010 in target forest.
Successful migrate mailbox to target forest (in source forest this mailbox convert to mailuser).
When try send e-mail to this mailbox (it`s in target forest) from Exchange 2003 mailbox get this:
A configuration error in the e-mail system caused the message to bounce between two servers or to be forwarded between two recipients.
If send from Exchange 2010 (source/target) - all mail ok.
If delete this mailuser (in source forest) - all set to ok.
x500?
Please, help.
Thanks.

Hi,
In the error event, 5.4.6 means "Routing loop detected" (RFC1893).
This issue occurs if the source Exchange organization is authoritative for the target domain. Because the source Exchange organization is responsible for mail delivery to target, the categorizer tries to find locally a recipient for
that message. The categorizer does not succeed, and then you receive the NDR.
More details in the following KB:
You receive an NDR with a 5.4.6 status code when you send a message to a specific domain in Exchange
http://support.microsoft.com/kb/324732/en-us
Hope it is the solution.
Thanks
Mavis
Mavis Huang
TechNet Community Support

Exchange 2003 SMTP resolves to incorrect MX record for Outbound emails

Starting October 2007, we have encountered numerous incidents where users complaint that they can not send emails to randomly with Relayed Denied error.
First we thought the problem is with the receipient servers, but after reviewing the SMTP log intensively, I have noticed that the SMTP service on Exchange Server 2003 SP2 tries to send out emails to wrong IP Addresses (instead of sending out to listed IP of MX record, it tries to send to primary domain IP address).
To test further, we have changed the DNS server of the Exchange Server to public DNS service provided by the ISPs and still received same result.
If the user tries to send the email again (from the bounced back message), it some times goes through.
Has anyone know what the problem is?
Have checked the server configuration, DNS configuration, ran all updates, and yet still same result. Is one of the Microsoft Updates causing this issue?

Here is the official explanation i got from MS, sounds like it is doing what they expect it to do.
Problem Description
When Exchange 2003 sends e-mail to the Internet using DNS to resolve external domain names a DNS query is done for the remote domain's MX records. In the event that the initial MX query returns a "server failure", Exchange 2003 will fall back to a DNS A record query. If this query is, in turn, successful and there is an A record for the domain in question that happens to be listening on port 25, Exchange will make a connection to that server. However, if this server does not relay, or accept e-mail for the intended domain a NDR will be generated with a 5.7.1, or
5.5.0 error message.
There are several domains that have A records that point to IP addresses that accept connections on port 25, but do not relay for the same name space:
Eg: Mindspring.com; Earthlink.net
Resolution
Resolve the DNS resolution problems that are causing occasional MX record failures.
Examples:
1. The Exchange server has multiple default gateways set on a multi-homed server.
This is not a recommended configuration and can cause a number of unexpected network problems. If the internal DNS server the internal NIC points to cannot resolve external DNS queries, this problem can occur.
Action: remove the default gateway from one of the NICs.
This doesn’t applies to us, as we don’t use Internal DNS
2. If the Exchange server points to multiple DNS servers on TCP/IP properties, or on the SMTP Virtual Server properties, verify that each of these DNS servers will return MX records properly. If one of the DNS servers does not return DNS records consistently, rectify this problem.
Action: remove this DNS server from the external DNS tab.
Workaround:
Bypass DNS by creating a SMTP connector with address space of <domain.com> and forward to smart host as the IP address the MX/A points to.
Exchange Query Explained
1. If Exchange finds the MX record(s) for a remote domain (through DNS query) it will not fall back to an A record query in the event the MX record (more precisely, the A record the MX record points to) is temporarily not responding on port 25. Instead, Exchange will try another MX record if one exists. If no other MX records exist and none are responding on port 25, the queue will go into a retry state for this remote domain. When that retry state has expired, Exchange will again attempt to resolve MX records for this domain, and so on.
2. Exchange will fall back to an A record query for the remote domain in the event that no MX record can be found. This is not to say that the MX record does not exist - only that when Exchange issued a DNS query for the remote domain the DNS response was "server failure", which basically means no MX was found. So, the MX record may indeed exist, but Exchange simply could not find it through DNS resolution.
3. Exchange then queries the A record and this happens to return a result. If the A record is listening on port 25, but does not accept mail for <domain.com> then we will get the NDR with 550 5.7.1 unable to relay (or some variation of this NDR error code) when Exchange connects and attempts to send the e-mail.
So, the intermittent nature of the problem is caused by a failure to find the MX record and a success in finding A record. This can happen for a variety of reasons, but it boils down to flakey DNS resolution.
For example:
a. A bad DNS server listed as a forwader on the DNS server.
b. A bad DNS server on the TCP/IP properties.
c. A bad DNS server on the SMTP VS (external DNS servers)
d. Multiple default gateways on Exchange (ie. multiple NICs on different networks, each NIC having a default GW)
A netmon on Exchange will show the failed MX lookup and successful A record lookup; however, it may not be conclusive unless the "bad" DNS server is listed in the netmon trace. For example, if Exchange points to internal DNS server(s) for name resolution and these DNS servers service these DNS queries by Exchange, you may need a netmon on the DNS server(s) as well to determine which DNS server/Forwarder/etc is at fault.
Regards,
Shahul Hameed Dasthagir
Support Engineer | Enterprise Communications Support

Cannot Move Mailbox from Exchange 2003 to Exchange 2007

Hello,
I am migrating exchange 2003 to Exchange 2007 and have moved almost all the mailboxes without any issue, but there are some mailboxes which are not being moved since they are giving me the below error.
Error:
Error was found for John Doe ([email protected]) because: Error occurred in the step: Opening source mailbox. Failed to open mailbox with error: ClassFactory cannot supply requested class, error code: -1056749262
Initially I found that the account was disabled from Active
Directory so enabled it but and also replicated the active Directory but still the problem is there, its not hidden in the GAL aswell.
http://www.arabitpro.com

Thanks everybody .. I have solved the problem myself.
To resolve this issue I had to give the account "SELF" permissions for "Associated external account". If the user does not have these
permissions to its own account it is unable to set the msExchMasterAccountSID attribute for the disabled account causing the error. By setting this permission on the disabled account, it allows it to mark the msExchMasterAccountSID attribute.
To do this follow this procedure:
1. In the Active Directory Users and Computers snap-in, on the View menu, click Advanced Features.
2. In the Exchange Advanced properties of the disabled user object that owns the mailbox, click Mailbox Rights, and then search the list of accounts for one
that has the Associated External Account permission.
4. If no account has this permission, grant the SELF account Associated External Account and Full Mailbox Access permissions.
https://support.microsoft.com/kb/278966?wa=wsignin1.0
http://www.arabitpro.com

Exchange 2003 Permissions Error when attempting to forward emails

Server 2003 R2 (fully patched as of 11/2013) running Exchange 2003 SP2 (Built 7638.x2) on ESXi 4.1; WinXP clients and Server 2003 Terminal Servers running Outlook 2003; Domain and Forest are running at 2008 Functional Levels.
Occasionally, some users are receiving this error message: "You do not have sufficient permission to perform this operation on this object. See the folder contact or your system administrator" intermittently when attempting
to 1) forward email both to and from senders/recipients inside and outside the domain, 2) When attempting to modify the subject of a previously received email (I didn't know you could do that), 3) When attempting to open received attachments.
There is no discernible pattern to the users or the original senders of the emails.
Most of the results I've found when searching relate to NTFS permissions or a ReadOnly propery on items in the users's profile folder, or sending on behalf of another user - these either do not apply or have been verified as not the cause.
During the initial rash of problems when there was a problem with an attachment and we absolutely needed it, I was able to connect to OWA using a special administrative account with access to the mailbox, open the attachment and log out. Once I had
done so with this account, the end user was able to open the attachment on their own without a warning.
Changes made to the environment prior to this issue that may be related (nobody remembers when exactly this started, so I can't state that it definitively happened after this change):
All servers were virtualized on ESXi 4.1 in late 2011; subsequently converted and migrated to Hyper-V Server 2012 in early 2013 (with the exception of the Exchange and SQL servers).
All 2003/R2 domain controllers demoted and removed; DFL/FFL raised to 2008; SYSVOL replication was migrated from FRS to DFS-R.
Troubleshooting steps:
Exchange server and affected client computers have been restarted several times; the various exchange services have been restarted; permissions on the mailboxes and AD objects have been verified; event logs are generally clean with the exception of ActiveSync
errors for a single user not currently affected by forwarding emails, there are no other errors reported.
Per recommendations on another forum, I had enabled several diagnostic logs in the diagnostic logging tab of the server. Unfortunately not much was found in the Application log even after filtering out the basics. There were occasional errors
referencing User A failed to modify an item in User B's mailbox because access was denied; however, I was unable to correlate these errors to any reported incidence of the above message.
I created a new mailbox database on the same server and migrated all the mailboxes to the new database, there was no change; users immediately began seeing these errors.
Over a holiday weekend, I then spun up a new Win 2003 R2 server, with a fresh installation of Server 2003 R2 (also fully patched through 11/2013) running the same version of Exchange 2003 SP2 this time running as a virtual guest on Hyper-V Server 2012.
I migrated all mailboxes from the original mail server to the new mail server and it appeared that the problem was remedied; however, it has slowly started up again and is starting to become more frequent.
I'm really at my wits end with this problem and would like to get it resolved before we purchase and install our new Exchange Server later this year.

Updates
Users have reported that they can forward the email from OWA; even after doing so, they are unable to forward from Outlook. So either my previous notes on the issue were wrong, or this is just more of the "intermittent" nature of the problem.
I will have to investigate what logging options are available to me at the Outlook client level - any thoughts on that subject are also welcome.
Users have now reported that a previous (rarely used) workaround (the administrative account opening the email in OWA) no longer enables them to view attachments or forward emails in Outlook.
I'm still adjusting the various diagnostic logging settings to see if I can spot an event which corresponds to a reported occurrence. The most unusual warning reported is the following:
Source:MSExchangeIS Mailbox Store
Category: Access Control
Event ID: 1029
[email protected] failed an operation because the user did not have the following access rights:
'Delete' 'Read Property' 'Write Property' 'Create Message' 'View Item' 'Create Subfolder' 'Write Security Descriptor' 'Write Owner' 'Read Security Descriptor' 'Contact'
The distinguished name of the owning mailbox is /O=DOMAIN/OU=FIRST ADMINISTRATIVE GROUP/CN=RECIPIENTS/CN=USER_B. The folder ID is in the data section of this event.
However odd these occasional warnings are, they do not appears to correlate to the reported permissions issue. Everytime I've seen one of these events, I've inquired with "user_A" to see if they've recently seen the popup and in each case they have
not.

Account Lockout issue between Apple devices and Exchange 2003

I have been having an ongoing issue for a couple of months with a few different users Apple devices locking out their accounts in AD when they try to authenticate to ActiveSync. This doesn't happen every time they authenticate, it seems to be random,
while the rest of the time they have access to their email. It might occasionally happen with an Android, but not on a repetitive basis like this.
Primarily this has been four different iPads, running different versions of iOS, and an iPhone running the latest release of iOS 7. Other iPhones and iPads function without having the problem, including iPhones on iOS 7.
The user accounts in question are set to never have their passwords expire, but again, they aren't the only users that are set like this, and those other users, even with Apple devices are not having the same problem.
I used NetWrix to trace out the source machine, which is my Exchange 2003 server and times, and I've checked the W3SVC1 log file, and come up with the following as an example with identification details masked:
<internal IP>, <Domain\Username>, 4/30/2014, 8:10:04, W3SVC1, <ServerName>, <internal IP>, 15, 329, 3367926, 200, 0, GET, /exchange-oma/<[email protected]>/NON_IPM_SUBTREE/Microsoft-Server-ActiveSync/iPad/ApplV50462*****/eb53cd5d5b9fcf40****************-20ef44,
As I was typing this, the owner of the iPad from the log file above came by my desk, so I asked a couple more questions. He's never had another iPad, it's a gen 1, and he's never updated the iOS on it. I know one of the other iPads in question
has the most up to date iOS, and the other one is brand new, replacing one that was broken, but the owner of that one had the same issue on a 3 year old iOS.
There is nothing special about the user accounts, no special privileges or restrictions.
Has anyone encountered this before? Exchange 2003, Server 2003 in a 2008 domain. Promotion to the 2008 domain was 2 years ago.

Hi Brian,
I am so sorry for the delay.
Do you have any progress by now?
Since there are lots of devices which use user accounts to log on, failed logon attempts on these devices could be the cause for account lockout.
If this issue persists, I suggest you refer to these troubleshooting articles below:
Troubleshooting account lockout the PSS way
http://blogs.technet.com/b/instan/archive/2009/09/01/troubleshooting-account-lockout-the-pss-way.aspx
Troubleshooting Account Lockout
http://technet.microsoft.com/en-us/library/cc773155(v=WS.10).aspx
In addition, you can also get efficient support at Active Sync forum below:
http://social.technet.microsoft.com/Forums/exchange/en-US/home?forum=exchangesvrmobilitylegacy
Best Regards,
Amy

Exchange 2003 to Exchange 2010 migration steps

HI ,
I have migrated windows 2003 to windows 2008.Its successfully migrated.
Second phase i have a plan to migrate exchange 2003 to exchange 2010.
My current setup
windows 2008 64bit (DC)
exchange 2003 sp2
1
Bring the Exchange organization to Exchange Native Mode.
2
Upgrade all Exchange Servers to Exchange Server 2003 Service Pack 2.
3
Bring the AD forest and domains to Windows Server 2003 Functional (or higher) levels.
4
Upgrade at least one Global Catalog domain controller in each AD site that will house Exchange Server
to Windows Server 2003 SP2 or greater.
5
Prepare a Windows Server 2008 (RTM or R2) x64 edition server for the first Exchange 2010 server.
6
Install the AD LDIFDE tools on the new Exchange 2010 server (to upgrade the schema).
7
Install any necessary prerequisites (WWW for CAS server role).
8
Run setup on the Exchange 2010 server, upgrade the schema, and prepare the forest and domains. (Setup runs all in one step or separate
at the command line.)
9
Install CAS server role servers and configure per 2010 design. Validate functionality.
10
Transfer OWA, ActiveSync, and Outlook Anywhere traffic to new CAS servers.
11
Install Hub Transport role and configure per 2010 design.
12
Transfer inbound and outbound mail traffic to the HT servers.
13
Install mailbox servers and configure Databases (DAG if needed).
14
Create public folder replicas on Exchange 2010 servers using pfmigrate.wsf script, AddReplicaToPFRecursive.ps1, or Exchange 2010
Public Folder tool.
15
Move mailboxes to Exchange Server 2010 using Move Mailbox Wizard or Power Shell.
16
Rehome the Offline Address Book (OAB) generation server to Exchange Server 2010.
17
1Rehome the public folder hierarchy on the new Exchange Server 2010 admin group.
18
Transfer all Public Folder Replicas to Exchange Server 2010 Public folder store(s).
19
Delete Public and Private Information Stores from Exchange 2003 server(s).
20
Delete Routing Group Connectors to Exchange Server 2003.
21
Delete Recipient Update Service agreements using ADS Edit.
22
Uninstall all Exchange 2003 servers.
This is my plan to migrate.But i have a doubt in installing exchange 2010 in this scenario.
Is it necessary to use
Setup.com /PrepareLegacyExchangePermissions,
Please help me what excactly i have to do

I think that <a href="http://www.micronobal.com/blog/2014/5/1/exchange-server-migration-to-the-cloud-ensure-a-seamless-transition" title="Exchange Server Migrations">Exchange Server
Migration</a> is a very delicate project and to be taken very seriously as it is a detailed work as well. You are giving us some great tips.
Some Articles I would like to share as well:
<a href="http://www.micronobal.com/blog/2014/5/1/exchange-server-migration-to-the-cloud-ensure-a-seamless-transition" title="Exchange Server Migration to the Cloud - Seamless Transition.">
Exchange Server Migration to the Cloud</a>
It takes a lot of time and effort to get it right. Thank you for helping
Here some information about services for migrations
<a href="http://www.micronobal.com/business/cloud/advancedtechnologyservices" title="Migrate your email to the cloud.">Business Email migration</a>

Case of the Missing User Exchange 2003 - Exchange 2010 Migration issue

Hey All,
I am in the middle migrating from Exchange 2003 to Exchange 2013 by way of Exchange 2010 and going through the final parts of my Exchange 2010 portion of the migration I found that one of the users on Exchange 2003 is not showing up in the EMC to migrate.
In EPS I can find the user with Get-User username but I cannot get the mailbox or kick off the mailbox move from EPS giving me the error of "Object could not be found" It is a valid user with a valid user mailbox and I can log into the
mailbox in OWA for Exchange 2003. Any thoughts as to why the user's mailbox is not showing in EMC or that I can't get it to move via PS?
Thanks,
Joe

Hello,
Come back and mark the replies as answers if they help and unmark them if they provide no help.
I'm marking the reply as answer as there has been no update for a couple of days.
If you come back to find it doesn't work for you, please reply to us and unmark the answer.
Cara Chen
TechNet Community Support

Namespace for Exchange 2003 == 2010 == 2013 Migration

Hi
Hope someone can help. I am working on an Exchange 2003 to 2010 migration, which will then quickly move onto a 2010 to 2013 migration and need some clarification on the namespaces to use. I am aware that if I do not do this right at the 2003
to 2010 migration, this will cause a headache at the 2010 to 2013 migration.
Some background:
2003 Functional Level Domain - 2 x 2008 DC's
Currently users are on a 2003 exchange cluster with a mix of RPC (internal users) and RPC over HTTP connections (roaming users)
We will be installing Exchange 2010 on a single server, with CAS, HUB and Mailbox roles and no load balancer, as we will be moving quickly to 2013.
We have two Kemp load balancers ready for Exchange 2013.
Exchange 2010 is installed on a single server (exh2010.domain.local) and configured with an CAS array name (exh-cas.domain.local) which is resolvable internally only.
Currently we have multiple smtp namespaces e.g. @company.com, @company2.com.
Our main website etc is www.company.com
Our public facing services are at https://service.mycompany.com
Our 2003 RPC address is https://webmail.mycompany.com
I understand that the 2010 RPC CAS array name should be separated from the Outlook Anywhere (RPC over HTTPS) address so that when 2013 takes over the HTTPS address, the RPC connections are not broken.
Two Questions:
Do we have to use the HTTPS same namespace for 2013 as we do in 2010? Its just I would want to test the Kemp load balancers before making them live (slow careful transition), and giving them a different namespace, e.g.
https://mail.mycompany.com would allow a migration, rather then a cutover.
Can we use the *.mycompany.com address rather then the company.com address, even though we have no SMTP addresses at mycompany.com? Can autodiscover still work?
Thanks in advance for any guidance
Cheers
Steve

1. No, but you can. Exchange 2013 will proxy all services for Exchange 2010, so if you set up everything right, you should be able to simply swing the name from Exchange 2010 to 2013.
2. Your web services can be published with any domain as long as the hostname is in the certificate. Only Autodiscover needs to match the e-mail domain(s). So in your example, you could publish OWA, ECP, ActiveSync, Web Services and OAB
at owa.mycompany.com. You would need autodiscover.company.com, autodiscover.company2.com, etc., but if you don't have e-mail addresses with mycompany.com, you don't need autodiscover.mycompany.com. If all users have a company.com e-mail address,
the you only need autodiscover.company.com as long as users know to enter that e-mail address when configuring profiles on PCs or devices. If you're going to have to have Autodiscover for multiple domains, then you might consider using an SRV record
instead because it can greatly simplify your certificate requirements.
Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Exchange 2003 to 2010 migration mailflow issue

Hello,
I have a server 2003 w/ exchange 2003 that we are upgrading to 2010 to support Outlook 2013.
So we installed a windows 2008 server and exchange 2010. We followed a guide to help with the different steps and didn't have problem or error until now.
So what we have right now, is exchange 2003 with still ALL mailboxes.
Replications of folders is done.
Policies are updated.
The firewall is forwarding port 25 to the new exchange 2010 server:
Emails are coming in fine.
Internal emails are also perfectly fine (from internal user to internal users).
the only thing that is giving us trouble is the emails coming out. None of them are going out and they are getting "stuck" in the "routing group connector" on the 2003 machine.
The 2010 exchange has a simple send connector set SMTP/* with this server as source. The 2003 exchange only had the exch2003-exch2010 connector.
Because emails were kind of accumulating (80+) I decided to take the send connector on the 2010 exchange out. and added back a send connector on the 2003 exchange. This kind of "fixed" it as now all emails are going just fine. It also fixed
the queue as part of it got liberated when I added the 2003 send connector.
I still have 25 emails stuck in this "routing group connector" that I'd like to take care of.
We are obviously not done with the migration and this coexistence phase as actual mailboxes still need to be moved.
So I'd like to take care of this queue in the routing group connector as well as continue the process of being able to receive and send from the 2010 machine only. then I would continue the migration process.
FYI, the 2003-2010 connector was created using power shell on the 2010 machine. I am not using any smarthost.
and the error message (in the queue) I get is: "unable to bind to the destination server in DNS"
FYI, my 2003 server is called "SERVER1" and the 2010 server is "SERVER2", they're on the same local domain company.local.
FYI (not sure if that's relevant), the server1 exchange has a different certificate (different domain name) than the new server (server2) as our web host finally allowed us to use subdomains. not trying to confuse anyone but I am really stuck there and maybe
this is related: certificate for the exchange 2003 machine: www.company-mail.com (only 1) and certificates for the exchange 2010 are: mail.company.com / autodiscover.company.com (and a legacy.company.com we may not need since the actual coexistence phase will/should
be short).
any idea what's wrong here?

I added back the send connector on the 2010 exchange. everything still works fine since I still have the send connector on the 2003. However...
I connected through telnet to server2 (the exchange 2010) and was able to mail internally. however I couldn't send mail externally, it gives me a "cannot relay" error when I enter my rcpt to:... command.
I am guessing that this may be the reason why the queue is not emptying itself through that send connector.
Anything else I could try to test my "send connector" on the 2010 exchange?

Exchange 2003 users are unable to send attachments larger then 8 MB to Exchange 2010 users on the same LAN

I am migrating from Exchange 2003 to Exchange 2010.
Users who are still on Exchange 2003 cannot send attachments any larger than around 8MB to Exchange 2010 users on the same LAN.
Users on Exchange 2010 can send large attachments to fellow Exchange 2010 users without issue.
I do not have any quota restrictions on Exchange 2010.
Had a look at the Exchange 2003 Connector but could not see any reference to attachement restrictions.
Has anyone come across this?

Here is a note of the NDR:-
Your message did not reach some or all of the intended recipients.
Subject:
The following recipient(s) cannot be reached:
Tracey xxxxxx on 01/12/2014 13:27
This message is larger than the current system limit or the recipient's mailbox is full.
Create a shorter message body or remove attachments and try sending it again.
<mail.xxxxxxxxx.com #5.2.3 smtp;450 5.2.3 Msg Size greater than allowed by Remote Host>

Remove a domain from Exchange 2003, now other domains cannot send to the old domain error 5.1.1

We have a single Exchange 2003 server. We have multiple mail domains on the server, but are slowly moving to a hosted email solution. I moved the first domain, I will call it
domainABC, to our hosted solution. I have removed all exchange mailboxes from the users, and deselected the domain from Recipient Policies. I then ran the policy.
Whenever I send an email to anyone on Domain ABC from any other domain on the Exchange server, I get the 5.1.1 message. I am not sure what to do next - any help would be appreciated...
Brian

Hi Brian,
Could you post the detail information for the NDR message?
When you migrate all the users to the host email server, did you change mx record point to the new server?
You also can use this tool to help you check for the inbound email test (for Domain ABC).
Exchange Remote Connectivity Analyzer
https://www.testexchangeconnectivity.com/
Thanks,
Evan Liu
TechNet Subscriber Support in forum
If you have any feedback on our support, please contact
[email protected]
Evan Liu
TechNet Community Support

Exchange 2003 and Mac Mail

I have set up a work email account in Mac Mail using IMAP (the mail is stored on an internal server - Exchange 2003).
An issue has come to light where when I send messages with large attachments they DON'T go into sent items in Mail or into the exchange server. I should say that occasionally they do go into sent but more often they do not.
If I send messages with no or a small attachments then it DOES go into the sent items on both the Mac and the exchange server.
Can someone please help with this one?
Many thanks
Adrian

I have exchange 2003 at school(and outlook web access from internet) and I am trying to get it to show up directly into the mail part of my mac book.... I am not a techie, obviously, but when I try to add the account, I had been using Exchange instead of IMAP and POP.... The exchange process didn't work so then I actually did try IMAP and POP, but maybe the incoming outgoing server should be different than what I am putting in.... I can receive outlook (school email, contacts, etc) on my samsung blackjack so I thought there wouldn't be much to it, but obviously I am doing something wrong and I should just talk to my school

No-reply mailbox in Exchange 2003

You basically want a sending only account.
So create one on exchange or have your system that is generating these emails send from [email protected], add a disclaimer to emails from this address stating this is unmanaged, and at your spam/filter/gateway have it accept then drop the message - if someone does reply, they will think it got delivered, but in fact your server would take it then delete it.
It in effect would be 'an unmanaged mailbox' no one would ever see any replies sent to this address.

Hi..
We need to set up a mechanism for a system to send no-reply mail through our exchange 2003 server. I saw a post on having the exchange server simple do a NDR. However, I did not understand what that meant.
1- Do I need to make a mailbox in exchange in order for the exchange server to forward the system generated emails out?2- If, in fact, I do need a mailbox, how do I keep the account from filling up the sent file associated with the user? If it collects, it will waste disk space and eventually lock the prevent the user (system) from sending due to server mailbox size restrictions.
The account will rarely, if ever, be accessed by a person (so no way to archive /drop old sent messages.)
I would like some scheme that would allow someone (if needed) to go into the account and look back a month or so and see what was sent out, but it is...
This topic first appeared in the Spiceworks Community

Any ideas for how to sync to Exchange 2003 - contacts and calendar

Hi
I am still searching for a mechanism to give me the sync solution I want, which is as follows:
At work I have a PC running Outlook 2003 via an Exchange Server 2003 setup.
At home I have an iMac running Snow Leopard
In the middle I have an iPhone 3G
I want to sync Calendar and Contacts across all three machines.
I want to sync work email between the Exchange server and the iphone, but do NOT need this to sync on my iMac at home
That's it.
At the moment I can sync email, calendars and contacts successfully between the Exchange server and iPhone, using the over-the-air Exchange Sync on the iPhone. But sadly my iMac will not sync contacts and calendars to the exchange server 2003 as Snow Leopard only supports exchange 2007.
Ironically (because I don't need this bit to work) I have managed to get my iMac to sync with my Exchange server EMAIL, by selecting the Exchange IMAP option when setting up the mail account on my iMac (as opposed to the Exchange 2007 option). However, I cannot get iCal or Address book to sync with Exchange 2003, regardless of the options I select when setting up the new accounts in Address book or iCal. I guess these just do not work with Exchange 2003
I know that I cannot use mobileme as a solution, as you cannot have two over-the-air syncs going on, and I need to maintain my iphone link to the exchange server via activesync
I also know that using itunes to sync via the cable will not work, as this creates separate contacts and calendar files on the iphone and so does not provide the syncing solution I seek.
I have tried using google to act as the middle man between my iMac and Exchange server data - getting the iMac to sync to Google Calandar and Google Address Book, and then using a third party piece of software called gsyncit to sync from google to the .ost outlook file on my PC workstation. This works some of the time, but keeps crashing and leaving me with multiple duplicates to have to sort out - much too much hard work on a regular basis.
So I still do not have a solution. Unfortunately upgrading to Exchange server 2007 is not a solution.....
Any new ideas out there
Thanks

I don't think there will be a solution to this. Exchange 2003 just isn't supported.

Exchange 2003 giving occasional NDR's

Similar Messages

Maybe you are looking for