Re: SBS2008 / Exchange with POP3 Connector / Invalid Header Fields
- From: "Ed Crowley [MVP]" <curspice@xxxxxxxxxx>
- Date: Wed, 12 Aug 2009 20:10:12 -0700
If you open a support ticket with PSS you'll likely find out about that.
--
Ed Crowley MVP
"There are seldom good technological solutions to behavioral problems."
..
"Pitti" <pitti@xxxxxxxxxxxxxxx> wrote in message news:%23qq8OX2GKHA.4316@xxxxxxxxxxxxxxxxxxxxxxx
Hello Brad,
I am glad to hear, that you are in same situation, or maybe I shouldn't be glad, because we are both in trouble with this POP Connector case.
I have been using POP Connector since SBS 2003, and there haven't never been this big problem, some little problems and always solved with very small amount work. Usually the fault have been found in Antivirus-product.
I really hope that there is still someone who has "the power and knowledge solve or repair this".
Maybe someone in Microsoft?
Jani
Brad wrote:I have been reading this thread with interest since we are in the same situation.
I am a consultant focusing on small businesses. These businesses generally have no IT support in house and use my company for support as needed. Sometimes we see the client once/month, sometimes once/week, sometimes only as needed.
We find that supporting both exchange and groupwise using a pop connector is fairly durable for this size client, since it will allow, as has been said, an emergency method to view and respond to emails if something goes wrong in the email system.
In a perfect world, with support staff on site, email direct to exchange and groupwise is preferable with a postini or some other backup service storing your emails in case of an outage. But, in this client set, that does not work. It could be several days before a diagnosis is found and a fix is actually implemented in some of these clients. It can be a day or two before they even notify us if there is an outage of some sort in their email.
To get back to the problem at hand. We have SBS 2008 w/ exchange 2007 using the POP connector and have the same problem with "malformed" emails not being received and then clogging up the email pathway for our users. Increasing the error threshold only delays the problem and makes it more laborious to clean out the POP accounts. Outlook, Eudora, Thunderbird, Outlook Express can all read these emails. Why can't exchange/Pop connector allow these emails to be read?
There is obviously a bug or configuration error that should be fixed to allow this to work properly.
Any ideas are welcome. More people telling us that the pop connector is the wrong to go are not much help.
Thanks for listening.
Brad
"Pitti" wrote:
First, sorry about long delay in my reply.
Anyway, I can't use those solutions.
But thanks very much your opinions, and solution-possibilities.
I just hope, that Microsoft will repair this, or will give some possibillity to change behavioir about POP Connector / Exchange / SBS2008.
Thanks, Lanwench and Duncan
.
- References:
- Prev by Date: Re: SBS2008 / Exchange with POP3 Connector / Invalid Header Fields
- Next by Date: OWA Quite Working - Both Internal/External
- Previous by thread: Re: SBS2008 / Exchange with POP3 Connector / Invalid Header Fields
- Next by thread: HT server communication
- Index(es):
Relevant Pages
|