|
|
Question : Exchange POP collector not delivering messages from 2nd domain
|
|
Hello all.
Long story short, we have a POP collector and exchange 2003, with one domain. Now we have been asked to setup [email protected], to go to 3 users.
On the 123 reg control panel I have asked for mail sent to [email protected] to be forwarded to [email protected]. Instead I am getting the error below:
There is no delivery information for Microsoft Connector for POP3 Mailboxes to use in routing the message EBC6133FA09}>. Either the message used a blind carbon copy (bcc) or a distribution list when it was delivered to the POP3 account at the ISP or the e-mail domain specified for the global mailbox is incorrect. The message will be delivered to the Exchange mailbox BadMail, as specified in the POP3 Connector Manager. For information about using routing rules to deliver e-mail from a distribution list or global mailboxes, see Help.
-----------
A few things to point out, I have added in the 2nd domain to the recipient policy and I have created [email protected] as an smtp email address for the appropriate user.
The messages are ending up in a bad mail mailbox and I cannot figure out why.
Any help would be much appreciated.
|
Answer : Exchange POP collector not delivering messages from 2nd domain
|
|
The POP3 virtual server has nothing to do with this. The POP3 virtual server is for POP3 clients to collect email from your server.
I think you are going to struggle to get a solution if you must stay with POP3 delivery. The information the POP3 connector uses for email delivery is almost certainly not in the SMTP headers so that it cannot sort the messages.
The native pop3 connector is simply designed to aid the move to SMTP delivery - it is not designed for long term use.
If you really cannot move, then you could try looking at a third party tool, but they will probably have the same problem.
Simon.
|
|
|
|
|