Sorry that i'm new to this maillist, and i'm not sure i understand the posting policy. Sorry for the direct reply. Is it the right way to send email back to the list with Forward and send to receiver "[email protected]" ?
> Now we're getting somewhere. > > Troubleshooting method #26 : process of elimination... > Does the problem occur for IMAP access that does *not* include squirrelmail? > (you said "mainly through squirrelmail" - we need to know *specifically* - > we're looking for a computer problem here, not a paint color... :-) > > Also, the read and delete operations in IMAP are different (I think) when > passed to the OS. Are you *sure* both scenarios cause the problem? > > Likewise, can you consistently reproduce the problem (relating to the > above)? If so, how? In my server config, i used courier-imap's pop3d and imapd for client to check email from Outlook and Webmail. To narrow down, i found that both check email method produce these dead file. (i.e. pop3d and imapd also produce this error ) Maybe my "delete" word is misleading. The "delete" i said is the action in webmail, where actually is moving the email from Inbox to Trash, but not really delete the mail file. I cannot reproduce the error myself. because i cannot read these dead file. So, maybe special character within the mail file cause the error? i dunno. And i can't find a way to figure it out. My server mainly user is Chinese, with charset zh-TW and zh-CN. There're lots of email with chinese title and content. And i guess courier-imap should handle locale quite well. My server have about 200 virtual domain and around 1500 mail account. About 1 dead file produced within few days, in different virtual domain and different user ( i.e. different folder in filesystem ). As i found that all these dead file exist in "cur" mail folder, and only imap will move the mail file to these folder (with both pop3d and imapd), this is the reason i think that courier-imap have problem with my existing filesystem. > Are you doing "stock" FC2 installs? Have you used rpm "--force"? As we've > mentioned, something is seriously borked with these servers, and only > something *unusual* would get them to this point. I used fedora core 2 disk with default server installation for a new harddisk partitioning and formatting in ext3. And run up2date to update all packages. My existing kernel is 2.6.5-1.358. I know that i should update to the newest kernel. However, i cannot reboot the server for kernel upgrade now because these dead email file will certainly make the bootup filesystem check fail and the worse case is corrupt that partition. I guess that somebody else should use this default FC2 kernel as well with no filesystem related problem. I searched the ChangeLog in FC2 between this old kernel and most updated kernel and no such filesystem related bug fixes. (maybe i was wrong) I'm not trying to say that i rejected the possibility for the source of problem from this kernel. I'd like to know if someone tell me that "yes, this kernel version is buggy and will produce corrupted file at ext3 filesystem in some manner", so i can simply format this server, update kernel, re-install anything and done. But seems that the problem is not that exact. I know that i should try to upgrade kernel version, but are there any possible solution besides this? I think that this is my last last step if i really can't find solution. For these dead email file, i cannot find any I/O related error in syslog. And I'm quite certain that this is not a hardware failure. Again, thx for anyone reading this and i hope that i can solve this problem asap. ----- Original Message ----- From: "Jerry Amundson" <[EMAIL PROTECTED]> To: <[email protected]> Sent: Wednesday, February 23, 2005 10:39 AM Subject: [courier-users] Re: Further problem about fedora 2 and courier-imap > [ *Again*, please do not Reply - *post* to the list! ] > > [ And as long as I'm being critical, *please* don't top-post... ] > > On Tue February 22 2005 7:49 pm, Angus Lee wrote: > > I also want to find the source of problem. "What generate these dead > > files" > > > > From observation, only the users with IMAP have those dead file. mainly > > through squirrelmail webmail, when they move the mail to different mail > > folder. ( e.g. read new email moves the mail from "new" to "cur" or > > delete the email move from "cur" to ".Trash/cur" folder. ) > > Now we're getting somewhere. > > Troubleshooting method #26 : process of elimination... > Does the problem occur for IMAP access that does *not* include squirrelmail? > (you said "mainly through squirrelmail" - we need to know *specifically* - > we're looking for a computer problem here, not a paint color... :-) > > Also, the read and delete operations in IMAP are different (I think) when > passed to the OS. Are you *sure* both scenarios cause the problem? > > Likewise, can you consistently reproduce the problem (relating to the > above)? If so, how? > > > So, i suspect it's related to Fedora 2 and courier-imap (as from my post > > title) and seek for thelp in this maillist. > > That's well and fine that you've narrowed it down to one of those two. But, > based on historical data, the problem is *neither* of those two. FC2 is > quite stable, and from what I can recall, was a Courier development > platform for several months. > > > I still have no solution yet, as no one encountered similar problem > > before, but happens to me for every fedora 2 + qmail + courier-imap. > > > > i guess it's not qmail problem because it's not qmail's responsibility to > > deliver email to mailbox ( i used vmailmgr, and vmailmgr never produce > > these dead file in "new" folder ) > > > > any more idea? > > Are you doing "stock" FC2 installs? Have you used rpm "--force"? As we've > mentioned, something is seriously borked with these servers, and only > something *unusual* would get them to this point. > > jerry > > > > ------------------------------------------------------- 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 [email protected] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
