> comes into mailbox "cur" folder. It size is about 360-380 bytes maximum.
> When someone tries to check mail mostly in Outlook Express, server
> unexpectedly terminates connection.
> Problem solves when I delete this message from mailbox on server.
>
> The question is: How not to process this kind of messages?

Create a filter. If you are delivering through maildrop, you can put your
filter in maildroprc, and have it effect all messages. We had a bunch of
these, they are spam I think, but it causes outlook to crap out. For me, it
wasn't a problem if outlook was reading imap, but when reading pop, if it
gets stuck on a message, that message remains in the queue for next time.
Our first recommendation to effected users was to switch to imap or set up
imap as a secondary way to clear the bad message. We had some people use
their webmail login for this purpose.

It's definitely outlook that's the problem though - I could bypass the bad
messages with other readers.

Our "bad message" was different though, so our filter would be useless to
you

m/



-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
_______________________________________________
courier-users mailing list
[EMAIL PROTECTED]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users

Reply via email to