571 Message Refused

[Acydman]

I have installed an Exchange 2003 server fully service packed with MS record etc all working correctly. Our current email is POP3, so i set up my own email address on our new server and created an alias on the POP3 account to send the pop mail to the exchange server, but the pop3 accoutn required that my account was deleted before the alias worked.

It worked for about 100 - 200 messages from the pop3 domain and them started kicking out 571, message refused. Mail from any other domain works. My question is:

1. how can I stop exchange refusing the message from the pop3 domain?

We need to migrate about 2000 users from the pop3 to the exchange so we'll have to live with this for about a month and then we'll update tjhe MX record to point the pop3 domain to the exchange server once completed.

THanks

 

[JimWells]

1. What is the other mail MTA software?
2. Can you turn on diagnostic logging for Transport-->NDR and see if an Application event log fires when the mail is returned?

Is the address you're forwarding to Exchange on your E-mail Addresses tab for the AD user object?

 

[Acydman]

I don't know what the other software is at the mail provider but its clara.net. The address is linked to the AD UO.

How do you turn on the diagnostic logging for transport?

 

[JimWells]

It's a tab under the Exchange server's properties in Exchange System Manager.

You can also try Message Tracking under Exchange System Manager tools, if it's turned on. That doesnt always show why the message is refused though.

 

[Acydman]

Hi tried that no joy.

 

[JimWells]

Neither message tracking nor an NDR message in the Application event log on the Exchange server show any details?

 

[Acydman]

Ah

Found this:

A non-delivery report with a status code of 5.3.5 was generated for recipient rfc822;oieiuweiruweoiruwioruweio@1ststop.co.uk (Message-ID <fbfd4ee70706250714j10648d3o95e83f0a5bee3226@mail.gmail.com>).
Causes: A looping condition was detected. (The server is configured to route mail back to itself). If you have multiple SMTP Virtual Servers configured on your Exchange server, make sure they are defined by a unique incoming port and that the outgoing SMTP port configuration is valid to avoid looping between local virtual servers.
Solution: Check the configuration of the virtual serverÆs connectors for loops and ensure each virtual server is defined by a unique incoming port.

For more information, see Help and Support Center at

http://go.microsoft.com/fwlink/events.asp.