On Mon, 2 Feb 2004, Guillermo Llenas wrote:

> 
>     Hi, 
> 
>     I have qpopper running with near over 1500 accounts of e-mail with
> different domains. Works fine, but quite often appear some errors and
> the mbox get corrupted. The only way for the user can check e-mail is
> doing mail -f to the mbox and delete one mail.  Apparently mbox corrupts
> when the user after connecting themselve and checking the mail with
> outlook xp or 2000, and having session opened check again with some
> webmail at the same time.  Similar case is when a user check almoast
> simultaneously over the same mbox, first the error "is busy" and then
> the mbox get corrupted. Is there any way to avoid these.  Any suggestion
> will be very very appreciated.  I have qpopper over Redhat 9, with exim
> and mysql with qpopper-mysql-0.12.patch.
> 

don't use mbox over NFS, unless you got some special locking mechanism 
going on that makes it work right.

--Tony
.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-.
Anthony J. Biacco                            Network Administrator/Engineer
[EMAIL PROTECTED]              http://www.asteroid-b612.org

       "You find magic from your god, and I find magic everywhere" 
.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-.

> The logs in two different machines at the same time.
> 
> Feb  2 17:45:44 fesprueba popper[7515]: (v4.0.5-mysql-0.12) POP login by user 
> "ruben.benayon" at (host106.200.61.143.ifxnw.com.ar) 200.61.143.106 [pop_log.c:244]
> Feb  2 18:05:07 fes11 popper[31687]: ruben.benayon at 
> host106.200.61.143.ifxnw.com.ar (200.61.143.106): -ERR POP EOF or I/O Error 
> [popper.c:847]
> Feb  2 18:05:09 fes11 popper[31687]: I/O error flushing output to client 
> ruben.benayon at host106.200.61.143.ifxnw.com.ar [200.61.143.106]: Operation not 
> permitted (1) [pop_send.c:709]
> Feb  2 18:05:54 fesprueba popper[7515]: ruben.benayon at 
> host106.200.61.143.ifxnw.com.ar (200.61.143.106): -ERR POP EOF or I/O Error 
> [popper.c:847]
> Feb  2 18:05:54 fesprueba popper[7515]: Unable to move /export/poptemp/r/u/[EMAIL 
> PROTECTED] to /export/mail/team.ar.inter.net/r/u/ruben.benayon: No such file or 
> directory (2) [pop_updt.c:766]
> Feb  2 18:05:54 fesprueba popper[7515]: ruben.benayon at 
> host106.200.61.143.ifxnw.com.ar (200.61.143.106): -ERR Error copying messages from 
> temp drop back to mailspool: Stale NFS file handle (116) [pop_updt.c:797]
> Feb  2 18:05:54 fesprueba popper[7515]: ruben.benayon at 
> host106.200.61.143.ifxnw.com.ar (200.61.143.106): -ERR POP mailbox update for 
> ruben.benayon failed! [popper.c:857]
> Feb  2 18:19:12 fesprueba popper[8304]: ruben.benayon at 
> host110.200.61.145.ifxnw.com.ar (200.61.145.110): -ERR [SYS/PERM] Unable to process 
> From lines (envelopes) in /export/mail/team.ar.inter.net/r/u/ruben.benayon; change 
> recognition mode or check for
 corrupted mail drop. [pop_dropcopy.c:863]
> Feb  2 18:20:13 fesprueba popper[8323]: ruben.benayon at 
> host110.200.61.145.ifxnw.com.ar (200.61.145.110): -ERR [SYS/PERM] Unable to process 
> From lines (envelopes) in /export/mail/team.ar.inter.net/r/u/ruben.benayon; change 
> recognition mode or check for
 corrupted mail drop. [pop_dropcopy.c:863]
> Feb  2 18:20:31 fesprueba popper[8328]: ruben.benayon at 
> host110.200.61.145.ifxnw.com.ar (200.61.145.110): -ERR [SYS/PERM] Unable to process 
> From lines (envelopes) in /export/mail/team.ar.inter.net/r/u/ruben.benayon; change 
> recognition mode or check for
 corrupted mail drop. [pop_dropcopy.c:863]
> 
> 
> 
> 
> Guillermo Llenas
> Tecnología
> Inter.net Argentina
> ________________________
> +0054 11 4343-1500
> fax 0054 11 4343-4550
> www.inter.net
> [EMAIL PROTECTED]

-- 
.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-.
Anthony J. Biacco                            Network Administrator/Engineer
[EMAIL PROTECTED]              http://www.asteroid-b612.org

       "You find magic from your god, and I find magic everywhere" 
.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-.

Reply via email to