samcory
asked on
sbs2008 pop3 connector problems
I have a problem with Exchange refusing to download pop3 connector emails that have a bad header.
I was told this was an unfixable error in the Exchange pop3 connector, since then I have seen this solution, please can you kindly look at it and tell me if it is good ( its the 2nd part that actually allows the bad emails to be downloaded that I am interested in
--------------------------
Problem
If you are using the POP3 Connector on Windows SBS 2008, you may encounter this error in the event log
One or more (5) e-mail messages in the POP3 mailbox account ‘<email address>’ on the POP3 server ‘<server name>’ have invalid header fields. Because of this, the messages cannot be delivered to the Exchange Server mailbox ‘<mailbox>’ in Windows Small Business Server. The messages are still on the POP3 server. To resolve this issue, connect to the POP3 mailbox account, and then manually retrieve or delete the messages.
By default the POP3 connector will stop processing new messages after 5 protocol errors so once this happens, you will not receive any email.
Solution
The quickest and easiest thing to do is to increase the MaxProtocolErrors from 5 to something bigger like 999. You can do this with the following command:
Set-ReceiveConnector -identity ($Env:computername + “\Windows SBS Fax Sharepoint Receive ” + $Env:computername) -MaxProtocolErrors 999
This will allow the remaining messages to be downloaded, but the messages with invalid headers will still not be downloaded. Once you accumulate 999 messages with invalid headers, the problem will still occur.
To fix this you either have to login to your ISP’s mail server and delete the messages manually or figure out why the messages have bad headers. In my case, the problem was that the messages had an invalid Return-Path: header that looked like this:
Return-Path: <MAILER-DAEMON>
I noticed that most of the messages were automated responses such as “out-of-office” replies. The problem is the MAILER-DAEMON is not a valid email address format. Valid email addresses must have an @ sign in them. The workaround I found was to tell Exchange to append the local domain name. Here is the command for that:
Set-ReceiveConnector -Identity ($Env:computername + “\Windows SBS Fax Sharepoint Receive ” + $Env:computername) -DefaultDomain $Env:UserDNSDomain
Once I did that, the POP3 connector was able to download the messages with invalid headers and the errors in the event log went away.
I was told this was an unfixable error in the Exchange pop3 connector, since then I have seen this solution, please can you kindly look at it and tell me if it is good ( its the 2nd part that actually allows the bad emails to be downloaded that I am interested in
--------------------------
Problem
If you are using the POP3 Connector on Windows SBS 2008, you may encounter this error in the event log
One or more (5) e-mail messages in the POP3 mailbox account ‘<email address>’ on the POP3 server ‘<server name>’ have invalid header fields. Because of this, the messages cannot be delivered to the Exchange Server mailbox ‘<mailbox>’ in Windows Small Business Server. The messages are still on the POP3 server. To resolve this issue, connect to the POP3 mailbox account, and then manually retrieve or delete the messages.
By default the POP3 connector will stop processing new messages after 5 protocol errors so once this happens, you will not receive any email.
Solution
The quickest and easiest thing to do is to increase the MaxProtocolErrors from 5 to something bigger like 999. You can do this with the following command:
Set-ReceiveConnector -identity ($Env:computername + “\Windows SBS Fax Sharepoint Receive ” + $Env:computername) -MaxProtocolErrors 999
This will allow the remaining messages to be downloaded, but the messages with invalid headers will still not be downloaded. Once you accumulate 999 messages with invalid headers, the problem will still occur.
To fix this you either have to login to your ISP’s mail server and delete the messages manually or figure out why the messages have bad headers. In my case, the problem was that the messages had an invalid Return-Path: header that looked like this:
Return-Path: <MAILER-DAEMON>
I noticed that most of the messages were automated responses such as “out-of-office” replies. The problem is the MAILER-DAEMON is not a valid email address format. Valid email addresses must have an @ sign in them. The workaround I found was to tell Exchange to append the local domain name. Here is the command for that:
Set-ReceiveConnector -Identity ($Env:computername + “\Windows SBS Fax Sharepoint Receive ” + $Env:computername) -DefaultDomain $Env:UserDNSDomain
Once I did that, the POP3 connector was able to download the messages with invalid headers and the errors in the event log went away.
Gareth Gudger
Not sure on this. What is the need for the POP3 connector? Any reason you are delivering directly to your mail server with MX records?
ASKER
We have 4 offices all using 4 different exchange servers on different local domains but all sharing one email domain. The only way we can split the mail is to have the pop3 connectors downloading the mail for each individual user. This system cannot be changed yet due to budget restrictions..
The solution provided is only for very specific instances. You might try it, but only when the situation is EXACTLY the same, will this solve it.
If the situation doesn't match, the only way is to login to the original POP3 mailbox (either another POP3 client, or webmail), and forward it again (also delete the message, so the errors won't appear again).
If the situation doesn't match, the only way is to login to the original POP3 mailbox (either another POP3 client, or webmail), and forward it again (also delete the message, so the errors won't appear again).
ASKER
I am not the literate with the instructions
If my domain is called "samsdomain.com" and the server is called "samsSBSserver"
Please can you fill in what should be typed in this instruction:
Set-ReceiveConnector -Identity ($Env:computername + “\Windows SBS Fax Sharepoint Receive ” + $Env:computername) -DefaultDomain $Env:UserDNSDomain
thanks
Sam
If my domain is called "samsdomain.com" and the server is called "samsSBSserver"
Please can you fill in what should be typed in this instruction:
Set-ReceiveConnector -Identity ($Env:computername + “\Windows SBS Fax Sharepoint Receive ” + $Env:computername) -DefaultDomain $Env:UserDNSDomain
thanks
Sam
Did you even check if one of the failing POP3 messages contains:
Return-Path: <MAILER-DAEMON>
If not, you're doing it all for nothing. Plus, these are messages sent by yourself, if they're messages from someone else, it still doesn't solve anything.
Return-Path: <MAILER-DAEMON>
If not, you're doing it all for nothing. Plus, these are messages sent by yourself, if they're messages from someone else, it still doesn't solve anything.
ASKER
most of them contain mailer-daemon
Nearly all are automated answerbacks of some sort
Nearly all are automated answerbacks of some sort
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks it seems to work