Hello there,
i'm stuck with a problem, in that when users that have their mailbox on a Ex2K3 server sends an e-mail to an Ex5.5 recipient an NDR is generated at once.
My current environment:
[ul]
[li]One Site and one Exchange 5.5 organization[/li]
[li]no foreign charakters or dots in server name, site name etc.[/li]
[li]the first Ex2K3 Server was joined into the Ex5.5 organization[/li][/ul]
I am able to send e-mails to external users, and they are able to reply. Also, Ex5.5 users are able to mail Ex2K3 Users.
The error being written into the application eventlog looks like this
After searching numerous articles, i finally found an article which describes just this problem You receive a non-delivery report after you send an e-mail message to an Exchange 5.5 recipient.
The article mentions three reasons why this behavior may occur, and execpt for "There is a dot (.) in the server name of the Exchange 5.5 server where the mailbox of the recipient is located" they all apply.
The workarounds mentioned are not really helpful, because
[ol]
[li]If i could move all the mailboxes from Ex5.5 to a different Ex5.5 i would have done so. Different constraints apply so this is no option.[/li]
[li]Move all mailboxes from the Ex5.5 server to a Ex2K3 Server - well, this is what we intent to do, but this is going to take time and that's why we have this problem.[/li]
[li]Remove the Ex2K3 Server and reinstall it into another administrative group - also choosing to create another organization which is named exactly the same as the existing one - well..[/li]
[/ol]
Has any one out there experienced the same?
Of course, I did test this migration scenario in my testing environment first, without any problems. Why did Murphy need to "visit" me in my live environment????
Cheers
Knutern
i'm stuck with a problem, in that when users that have their mailbox on a Ex2K3 server sends an e-mail to an Ex5.5 recipient an NDR is generated at once.
My current environment:
[ul]
[li]One Site and one Exchange 5.5 organization[/li]
[li]no foreign charakters or dots in server name, site name etc.[/li]
[li]the first Ex2K3 Server was joined into the Ex5.5 organization[/li][/ul]
I am able to send e-mails to external users, and they are able to reply. Also, Ex5.5 users are able to mail Ex2K3 Users.
The error being written into the application eventlog looks like this
After searching numerous articles, i finally found an article which describes just this problem You receive a non-delivery report after you send an e-mail message to an Exchange 5.5 recipient.
The article mentions three reasons why this behavior may occur, and execpt for "There is a dot (.) in the server name of the Exchange 5.5 server where the mailbox of the recipient is located" they all apply.
The workarounds mentioned are not really helpful, because
[ol]
[li]If i could move all the mailboxes from Ex5.5 to a different Ex5.5 i would have done so. Different constraints apply so this is no option.[/li]
[li]Move all mailboxes from the Ex5.5 server to a Ex2K3 Server - well, this is what we intent to do, but this is going to take time and that's why we have this problem.[/li]
[li]Remove the Ex2K3 Server and reinstall it into another administrative group - also choosing to create another organization which is named exactly the same as the existing one - well..[/li]
[/ol]
Has any one out there experienced the same?
Of course, I did test this migration scenario in my testing environment first, without any problems. Why did Murphy need to "visit" me in my live environment????
Cheers
Knutern
