[courier-users] Corrupted Mailbox Problems (456,

This is a discussion on [courier-users] Corrupted Mailbox Problems (456, within the Courier-Imap forums, part of the Mail Servers and Related category; This email contains a review of a problem I had on one of our courier email servers that is running ...


Go Back   Usenet Forums > Mail Servers and Related > Courier-Imap

FAQ Members List Calendar Search Today's Posts Mark Forums Read
  #1 (permalink)  
Old 06-21-2007
Charles Uchu Strader
 
Posts: n/a
Default [courier-users] Corrupted Mailbox Problems (456,

This email contains a review of a problem I had on one of our courier
email servers that is running courier version 0.52.1.

I resolved the issue, but trying to understand what might have caused it
in the first place. Below I have gone through my resolution, any
thoughts or ideas about the cause would be appreciated.

....

Review of issue and fix.

1) Incoming email to a valid address (realuser@planet-save.com) was all
getting temporary errors such as below

Jun 21 10:38:27 emailserver1 courierlocal: maildrop: Unable to create a
dot-lock.
Jun 21 10:40:38 emailserver1 courieresmtpd: 456 Address temporary
unavailable.

2) All permissions, quota, etc were fine for this mailbox and logging in
via POP3 or IMAP was fine

3) Removed the mailbox from the server entirely, added it back in and
the problem still existed.

4) Removed it again and tried sending, now the error was:

Jun 21 11:44:47 emailserver1 courieresmtpd: 556 Address unavailable.

Since the mailbox no longer existed my expectation was it should have
been getting a "550 User unknown" error.

4) I issued cancelmsg on the four msgs in the mailq for this user. One
of them continued to be in mailq for another 45 minutes so investigated
further.

5) I checked in the mail spool directories manually and found the
following that contained references to this mailbox:

- 3 files in ./msgs/ (I deleted these)
- 1 file in ./msgq/ (I deleted it)
- 22 files in ./track/ (I edited those files to remove the lines
referencing the mailbox)

6) I created the mailbox again after verifying nothing in mailq any
longer and nothing in any of the spool directories. The problem was now
solved and delivery is fine.

....

Questions:

So what could have caused the original problem?

Was the mailq for this user corrupted somehow? What are possibilities
for causing corruption?

Are there any tools for situations like this to purge any information in
the spool directories besides cancelmsg? I know it would not follow RFC
for delivery failure notification, but that method did not work in this
situation.

What do the /track/ files do?

Thanks,

charles uchu strader



-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
courier-users mailing list
courier-users@lists.sourceforge.net
Unsubscribe: https://lists.sourceforge.net/lists/.../courier-users
Reply With Quote
Reply
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are Off
[IMG] code is Off
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On



All times are GMT +1. The time now is 06:34 PM.


Powered by vBulletin® Version 3.7.3
Copyright ©2000 - 2008, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO 3.0.0