What is the problem ? pop3

[Lee Tae-kyung]

Hello,
ux17202 has many mail users.
The below error messages don't happen to all mail users.
I want to know what is wrong.
Please help me^^;


Thanks many in advance.


******** Error messages ******************
Jun 26 11:21:18 ux17202 popper[3135]: kang at ux17201 (61.73.58.135): -ERR POP EOF or I/O Error
Jun 26 11:21:18 ux17202 popper[3135]: Stats: kang 0 0 19 936835 ux17201 61.73.58.135
Jun 26 11:21:18 ux17202 popper[3135]: I/O error flushing output to client kang at ux17201 [61.73.58.135]: Broken pipe ()

[benoit Bruckert]

HI,
Broken pipe is typically a network error.
If just a few users have this kind of troubles, you could check the client side.
I.E. :
If the clients concerned are in a specific network (remote users, firewall between them and the server, connected through an extended network, connected to a fully collision hub, connected to a separate switch...).
To test it, you could try to create the account on a client where you have no trouble and see if you have still these messages.
If it's better, then you have the confirmation about network/client (OS/software) trouble...
You can also check some timeout config on the pop3 client, try another kind of client..

THis is just suggestion, not a solution, but I hope that help..

regards
Benoit
_________________
"Fruit: l'??ge mur de l'homme s'apparente ?? celui des poires. Dans les deux cas, c'est la queue qui l??che." SIM

[Angus Crome]

It's been a long time since I used pop, but I remember similar errors. We would get truncated messages delivered to multiple people. Every one of them would get Broken pipe errors and not be able to download their mail. Originally, we would view the mail file and remove the offending mail, but that got to be long and tedious. We ended up loading an IMAP server and viewing their mail file from that. We could usually determine what the offending file was immediately and remove it using IMAP.
Finally, we just moved everyone to IMAP and let them deal with it.

[Steven E. Protter]

Maybe you have too many users and are out of band width.

That would cause this problem.

Perhaps look at some performance data and see what it tells you.

Attaching a peformance data collection script.

SEP

[Shannon Petry · Accepted solution]

Most of the time these problems are caused by 1 of 2 things.

1. Corrupt mail box.

Load a local client and view mail box, make sure client supports attachments, etc...

If this fails, then you need to fix the mailbox. The easiest way to do this is with IMAP.

2. Large mailboxes cause timeouts when being retrieved.

You can restrict user mail box sizes, or... you can change your client.

I would highly recommend for several reasons that you go to an IMAP configuration. Washington University IMAP for example includes IMAP(pop4), POP3, POP2, and POP. As long as the daemons are configured into /etc/inetd.conf then you can use any of the above mentioned protocols.


What makes IMAP so nice? Imap can store files off the mail spool directory. Mail files can be created and delted, as well as backed up relatively eaily from the same mail server.

Imap reads header information, and content only when requested, where POP reads the whole mailbox in 1 shot and downloads it.

Hope it helps.
Shannon