Dear all,
 
    First of all, thx for the reply from Jay Lee. I would like to post this problem again and let see if anyone can help me on this after further provide the details information. Thx for anyone reading this and i hope that someone can give me some suggestion on this.
 

> That is a very old kernel.  It should work, I've not heard of any fs
> corruption issues in Fedora kernels.  However you are probably vulnerable
> to a handful of security issues and really should run up2date.

    I've two servers encounter the same problem. Another one has updated to
the newest kernel through up2date, but the problem persist.

> How are the messages being delivered to the folder?  Can you give an ls
> -alRF before from the top of the Maildir?  Are you using ext3 (Fedora Core
> default fs) ReiserFS or XFS (must be manually chosen at install time) for
> the Maildir's filesystem?

    I'm using ext3 in maildir's filesystem. For those problematic file, it
looks like

    >>> ?---------  ? ?             ?                 ?            ?
1108808789.M253138P21295V0000000000000307I000CC688_1.sun,S=2292:2,

    >>> ?---------  ? ?           ?               ?            ?
1103994827.2207.sun:2,

    >>> ?---------  ? ?                   ?                        ?
? 1108533909.28032.sun:2,

    when i "ls" them. No date, no owner. These file cause the pop3d or imapd
unable to read the maildir with the following error:

Feb 21 09:16:52 sun pop3d: I/O error while reading message file
cur/1107591456.22770.sun:2,: Is a directory
Feb 21 09:16:52 sun pop3d: I/O error disconnect, user=moses,
ip=[::ffff:202.82.198.2], top=0, retr=0

Feb 22 09:57:44 sun pop3d: I/O error while reading message file
cur/1107591456.22770.sun:2,: Is a directory
Feb 22 09:57:44 sun pop3d: I/O error disconnect, user=moses,
ip=[::ffff:202.82.198.2], top=0, retr=0, time=1

    What i can do to these files is to move the folder to a dummy directory.
Because i cannot do anything with these files in console (gives Input/Output
Error). If i remove it with "rm -f", the filesystem will crush and it make
the server crush as well.

> Did you rebuild the Courier rpms on each box or use the same ones?  Where
> did the rpms or manual build come from?  The issue may be with the
> specific build not the source.

    I manually compile the courier-imap package (3.0.7) myself with
"./configure --with-redhat", "make" and "make install". I do the same thing
with Redhat 9.0 and all things work properly.

    Yesterday night, i tried to install courier-imap-4.0.1. However, as i am
using vmailmgr, as if the document said, the new authdaemond does not
support vmailmgr built in authentication function. So i can just upgrade it
to 3.0.8.

    Let me tell you my configuration and let see if you can give any further
idea.

    netqmail-1.05 + vmailmgr (vmailmgr-0.96.9) + courier-imap (3.0.7) +
squirrelmail (squirrelmail-1.4.3a)

    I used courier-imap's pop3d and imapd. The situation is, all uses with
pop3d (i.e. outlook) work well without those "dead" file in mailbox.
However, those users using squirrelmail (with IMAP) always produce these
"dead" file when they check email. The two action i found from them is
related to move email to another folder by IMAP.

    1. check new email: email moved from "new" to "cur" folder. and dead
file exist in "cur" folder.
    2. move email: email moved to Trash folder, and dead file exist in
".Trash/cur" folder.

    I guess that squirrelmail just call some IMAP standard protocol to
perform the webmail function. So squirrelmail should related nothing to file
moving action.

----- Original Message -----
From: "Jay Lee" <
[EMAIL PROTECTED]>
To: <
[email protected]>
Sent: Tuesday, February 22, 2005 12:40 AM
Subject: Re: [courier-users] Fw: Problems in Courier-Imap with fedora 2 OS


> Angus Lee said:
> >     I'm not sure this is the right place to post this message, but i
> > really want to seek for help.
>
> Technically IMAP specific issues should go to courier-imap but anyone who
> uses Courier-MTA is likely using IMAP also.
>
> >     I'm using courier-imap-3.0.7 with fedora core 2 (2.6.5-1.358smp).
>
> That is a very old kernel.  It should work, I've not heard of any fs
> corruption issues in Fedora kernels.  However you are probably vulnerable
> to a handful of security issues and really should run up2date.
>
> >     For two servers with this config, i found that when user check email
> > through webmail (squirrel mail), the email should move from "new" user
> > folder to "cur" user folder. However, some "dead" file will be
> > generated inside the "cur" folder. When i "ls" that file,
> > "Input/Output Error" will be generated in console.
>
> How are the messages being delivered to the folder?  Can you give an ls
> -alRF before from the top of the Maildir?  Are you using ext3 (Fedora Core
> default fs) ReiserFS or XFS (must be manually chosen at install time) for
> the Maildir's filesystem?
>
> >     I'm quite sure that it is the problem related to this courier-imap
> > release and this linux kernel, by prove by two different hardware
> > config servers. I searched through web and have no solution.
>
> Did you rebuild the Courier rpms on each box or use the same ones?  Where
> did the rpms or manual build come from?  The issue may be with the
> specific build not the source.
>
> First upgrade your kernel as well as any other packages up2date shows need
> updates.  Then make sure your running the latest stable version of Courier
> (0.48.2).  Rebuild the rpms on each box seperately.  Others are running
> Courier on FC2 without issue.
>
> >     Can anyone help me on this? or is that the related issue has been
> > fixed in newer courier-imap release?
>
> You didn't say what version of Courier your running so we can't really
> say, upgrade to the latest.
>
> Jay
> --
> Jay Lee
> Network / Systems Administrator
> Information Technology Dept.
> Philadelphia Biblical University
> --
>
>

Reply via email to