My exchange server 2003 small business pop connector when pulling email with .dot attachments gets this error. Then the email is lost An error occurred with the connection to the POP3 server (mailbox <myemail@mydomain.com [mail.mydomain.com]>) while downloading the message <id:{BF4BD976-3FB8-4EEC-B090-421F82C97767}>. The error is 10054 (An existing connection was forcibly closed by the remote host. ). All other attachments are fine. If I zip the file it still errors Thanks!

On Wed, 21 Dec 2011 17:10:58 +0000, Jeff_1 wrote: > > >My exchange server 2003 small business pop connector when pulling email with .dot attachments gets this error. Then the email is lost > >An error occurred with the connection to the POP3 server (mailbox <myemail@mydomain.com [mail.mydomain.com]>) while downloading the message <id:{BF4BD976-3FB8-4EEC-B090-421F82C97767}>. The error is 10054 (An existing connection was forcibly closed by the remote host. ). > >All other attachments are fine. If I zip the file it still errors > >Thanks! That POP3 connector is part of SBS, not Exchange. You'll get better help posting this question in the SBS forum(s). --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

Thanks for looking ! I assume you can create pop connectors in any version of exchange. The problem is with the exchange pop connector. Perhaps MS support can look at this and give me there recommendation

I assume you can create pop connectors in any version of exchange. The POP connector is ONLY a part of SBS so it's not possible to create it in any other version. That's why the SBS Forum is the place to ask in. Martina Miskovic - http://www.nic2012.com/

OK learn somthing new every day Thanks!!!!

On Thu, 22 Dec 2011 05:12:15 +0000, Jeff_1 wrote: >Thanks for looking ! I assume you can create pop connectors in any version of exchange. Sure. There are several POP-to-SMTP connectors. None of them are anything more than kludges, though. >The problem is with the exchange pop connector. There's no "POP Connector" supplied with Exchange. The SBS folks have one, but it's a SBS product which is why I directed you to the SBS forum. >Perhaps MS support can look at this and give me there recommendation Maybe, but probably not in this forum! --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

On Thu, 22 Dec 2011 07:18:54 +0000, Jeff_1 wrote: >OK learn somthing new every day Told ya! ;-) --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

The solution was sonicwall firewall was preventing the attachment