On Mon, 2007-02-05 at 17:14 +0100, Michelle Konzack wrote: > > Try again without swap (swapoff -a)? > > Oh my Swap is a dedicated Harddisk of 18 GByte (U160) > But removeing the 8 GByte swap kill more then the imapd.
I know you're following a suggestion, but doesn't it seem natural that if your out-of-memory killer is killing off imapd, then decreasing swap will cause more applications to die off. Have you checked your memory use with "free" and "top"? > BUT, if I connect via IMAP, mutt moves first ALL MESSAGES from "new" > to "cur" and then list the mailbox. Now if I disconnect, and reconnect > it does not more detect the messages as new, since they are moved to > "cur". I must select the mailbox manualy and then I see the NEW messages. > > Now I have the question: > > Ist this a BUG from MUTT or COURIER? Technically, imapd moves the messages from new to cur. It also doesn't notify the client that it's done so. A message's read status is not indicated by its being in the "new" folder. There's also no reason for mutt to show you the correct number of unread messages during an IMAP session, and not on subsequent sessions. If your description is accurate, then it would probably indicate flaws in mutt. ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier. Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ courier-users mailing list [email protected] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
