[courier-users] Further problem about fedora 2 and courier-imap

permalink · #1 (**permalink**) 02-22-2005

This is a multi-part message in MIME format.

------=_NextPart_000_0011_01C518CC.0D7F78E0
Content-Type: text/plain;
charset="big5"
Content-Transfer-Encoding: quoted-printable

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=3D2292: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=3Dmoses,
ip=3D[::ffff:202.82.198.2], top=3D0, retr=3D0

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=3Dmoses,
ip=3D[::ffff:202.82.198.2], top=3D0, retr=3D0, time=3D1

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" <jlee@pbu.edu>
To: <courier-users@lists.sourceforge.net>
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
> --
>
>

------=_NextPart_000_0011_01C518CC.0D7F78E0
Content-Type: text/html;
charset="big5"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Dbig5">
<META content=3D"MSHTML 5.50.4937.800" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV>Dear =
all,</DIV>
<DIV> </DIV>
<DIV>    First of all, thx for the =
reply from=20
Jay Lee. I would like to post this problem again and let see if anyone =
can help=20
me on this after further provide the details information. Thx for anyone =
reading=20
this and i hope that someone can give me some suggestion on =
this.</DIV>
<DIV> </DIV>
<DIV> > That is a very =
old=20
kernel.  It should work, I've not heard of any fs > =
corruption issues=20
in Fedora kernels.  However you are probably vulnerable > to =
a=20
handful of security issues and really should run=20
up2date.     I've two servers encounter the same =
problem.=20
Another one has updated to the newest kernel through up2date, but the =
problem=20
persist. > How are the messages being delivered to the =
folder? =20
Can you give an ls > -alRF before from the top of the =
Maildir?  Are=20
you using ext3 (Fedora Core > default fs) ReiserFS or XFS (must be =

manually chosen at install time) for > the Maildir's=20
filesystem?     I'm using ext3 in maildir's =
filesystem.=20
For those problematic file, it looks like    =20
>>> ?---------  ?=20
?        & nbsp;   =
=20
?        & nbsp;   =
    =20
?        & nbsp;  =20
? 1108808789.M253138P21295V0000000000000307I000 CC688_1.sun,S=3D2292:2,=
    =20
>>> ?---------  ?=20
?        & nbsp; =20
?        & nbsp;   =
  =20
?        & nbsp;  =20
? 1103994827.2207.sun:2,   &nb sp; >>>=20
?---------  ?=20
?        & nbsp;   =
      =20
?        & nbsp;   =
        &n bsp;  =20
? ? 1108533909.28032.sun:2,     when i "ls" =
them. No=20
date, no owner. These file cause the pop3d or imapd unable to read =
the=20
maildir with the following error: Feb 21 09:16:52 sun pop3d: I/O =
error=20
while reading message file cur/1107591456.22770.sun:2,: Is a =
directory Feb=20
21 09:16:52 sun pop3d: I/O error disconnect,=20
user=3Dmoses, ip=3D[::ffff:202.82.198.2], top=3D0, =
retr=3D0 Feb 22 09:57:44=20
sun pop3d: I/O error while reading message =
file cur/1107591456.22770.sun:2,:=20
Is a directory Feb 22 09:57:44 sun pop3d: I/O error disconnect,=20
user=3Dmoses, ip=3D[::ffff:202.82.198.2], top=3D0, retr=3D0,=20
time=3D1     What i can do to these files is to =
move the=20
folder to a dummy directory. Because i cannot do anything with these =
files in=20
console (gives Input/Output Error). If i remove it with "rm -f", the=20
filesystem will crush and it make the server crush as =
well. > Did=20
you rebuild the Courier rpms on each box or use the same ones? =20
Where > did the rpms or manual build come from?  The issue =
may be=20
with the > specific build not the =
source.     I=20
manually compile the courier-imap package (3.0.7) myself =
with "./configure=20
--with-redhat", "make" and "make install". I do the same thing with =
Redhat=20
9.0 and all things work properly.     Yesterday =
night, i=20
tried to install courier-imap-4.0.1. However, as i am using vmailmgr, =
as if=20
the document said, the new authdaemond does not support vmailmgr =
built in=20
authentication function. So i can just upgrade it to=20
3.0.8.     Let me tell you my configuration and =
let see if=20
you can give any further idea.     =
netqmail-1.05 +=20
vmailmgr (vmailmgr-0.96.9) + courier-imap (3.0.7) + squirrelmail=20
(squirrelmail-1.4.3a)     I used courier-imap's =
pop3d and=20
imapd. The situation is, all uses with pop3d (i.e. outlook) work well =
without=20
those "dead" file in mailbox. However, those users using squirrelmail =
(with=20
IMAP) always produce these "dead" file when they check email. The two =
action=20
i found from them is related to move email to another folder by=20
IMAP.     1. check new email: email moved from =
"new" to=20
"cur" folder. and dead file exist in "cur" =
folder.     2.=20
move email: email moved to Trash folder, and dead file exist =
in ".Trash/cur"=20
folder.     I guess that squirrelmail just call =
some IMAP=20
standard protocol to perform the webmail function. So squirrelmail =
should=20
related nothing to file moving action. ----- Original Message=20
----- From: "Jay Lee" <<A =
href=3D"mailto:jlee@pbu.edu"><FONT=20
size=3D3>jlee@pbu.edu</A>> To: <<A =

href=3D"mailto:courier-users@lists.sourceforge.net"><FONT=20
size=3D3>courier-users@lists.sourceforge.net</A>> Sent:=20
Tuesday, February 22, 2005 12:40 AM Subject: Re: [courier-users] Fw: =
Problems=20
in Courier-Imap with fedora 2 OS > Angus Lee said: > =

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

------=_NextPart_000_0011_01C518CC.0D7F78E0--

-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
courier-users mailing list
courier-users@lists.sourceforge.net
Unsubscribe: https://lists.sourceforge.net/lists/.../courier-users

Thread Tools	Search this Thread
Show Printable Version Email this Page	Search this Thread: Advanced Search
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode