MSL problem -item MIME structure not produced -see error log

[les]

environment = scalix 11.3.0 U1

a user has some 4800+ messages in inbox.

When access via SWA the following error pops up on screen.....

"Failed to display messages for folder INBOX. The browser received some data but was unable to display it. Click Send/receive to try again".

and swa only shows a small percentage of the 4800+ messages. I.e. once it hits the problem it basically stops there and then.

in the fatal log i get....

ERROR IMAP Server Da(IMAP Server Pr) Thu Feb 14 01:23:29 2008
[OM.UI 2203] MSL problem - item MIME structure not produced - see error log
File Name: /var/opt/scalix/ls/s/data/000006h/002bigr
User Name: Joe Blow / lates/CN=Joe Blow
Pid of logging process: 19373
Current errno value: 1

The file DOES NOT exist on the system!!!!!


in the imap-<hostname> log file i only see the following errors....

20529 00:28:48.798 CMD: A363 FETCH 4459 (BODY[HEADER.FIELDS (X-Scalix-Class)])
20529 00:28:48.802 RSP: A363 NO some of the requested messages no longer exist
20529 00:28:48.802 CMD: A364 FETCH 4459 (ENVELOPE INTERNALDATE RFC822.SIZE)
20529 00:28:48.806 RSP: A364 NO some of the requested messages no longer exist

22527 01:05:15.289 CMD: A361 FETCH 4458 (BODY[HEADER.FIELDS (X-Scalix-Class)])
22527 01:05:15.293 RSP: A361 NO some of the requested messages no longer exist
22527 01:05:15.293 CMD: A362 FETCH 4458 (ENVELOPE INTERNALDATE RFC822.SIZE)
22527 01:05:15.297 RSP: A362 NO some of the requested messages no longer exist


I have troubleshooted extensively.

omcheck = ran and fixed.

omscan has been run over the user in full fix mode.

imap-cache contents in the user directory have been reset.

omtidyu -M has been run to regenerate mime.

Clearly there is a problem with a reference to a file that doesn't exist or is corrupt.

How can i clean this up for the user so SWA works fully again?

[Valerion]

I found the best way is to try and isolate the email. Move all mails to another folder using another client (Outlook works well, usually). See if the second folder has the same issue in SWA. If so, move the emails back to the INBOX in groups, checking if the issue re-appears.

Time-consuming, I know

[les]

I found the best way is to try and isolate the email. Move all mails to another folder using another client (Outlook works well, usually). See if the second folder has the same issue in SWA. If so, move the emails back to the INBOX in groups, checking if the issue re-appears.

Time-consuming, I know :(

yeah....that would be ok if there were not 4886 emails in the inbox......

[deyjvu]

Two other possibilites:

1 Turn on imap logging with the script from Wiki Diag/imap-logs - test it on a small account first to seeif the log reports what messages are being opened and indentifies them clearly.

2 sxmboxexp will allow you to export just one folder and not the whole mailbox. You could export it to a test server and see if the problem is resolved by the export/import.

I'd also suggest that they cleanup their Intray as well. The inbox isn't intended to be the place to hold messages. If they had this 'intray' on their desk they'd disappear behind it. This is from an ex-mail server administrator :-)

[les]

Two other possibilites:

1 Turn on imap logging with the script from Wiki Diag/imap-logs - test it on a small account first to seeif the log reports what messages are being opened and indentifies them clearly.

2 sxmboxexp will allow you to export just one folder and not the whole mailbox. You could export it to a test server and see if the problem is resolved by the export/import.

I'd also suggest that they cleanup their Intray as well. The inbox isn't intended to be the place to hold messages. If they had this 'intray' on their desk they'd disappear behind it. This is from an ex-mail server administrator :-)

Thanks, i'll try that.

[les]

Two other possibilites:

1 Turn on imap logging with the script from Wiki Diag/imap-logs - test it on a small account first to seeif the log reports what messages are being opened and indentifies them clearly.

2 sxmboxexp will allow you to export just one folder and not the whole mailbox. You could export it to a test server and see if the problem is resolved by the export/import.

I'd also suggest that they cleanup their Intray as well. The inbox isn't intended to be the place to hold messages. If they had this 'intray' on their desk they'd disappear behind it. This is from an ex-mail server administrator :-)

Thanks, i'll try that.

Its been a while....i have fixed my issues. It end up happening to two different clients. The common thread, or so it seems......

Both use multiple ways to access an account via imap (blackberry, swa, scalix mobile client) and both have large inboxes (1gb+ and 3000+ messages) with subfolders.

Here's a quick and dirty run through of what i did....

1. disable mail coming in, Service Router and Local Delivery.
because i wanted a clean backup.
2. run sxmboxexp (including subfolders)
3. use omtidyu to purge all messages in the inbox for the user.
WARNING - this will also clean subfolders aswell. Hence when you export include subfolders.
4. reimport inbox and subfolders back into the users account.

This cleared all issues with imap for both clients.

There should be an easier way though to track which message, or reference is at fault.

Caveat: there appears a bug with sxmboximp. When importing folders, if that folder already exists it duplicates in your folder list with the same name. This happens for swa and outlook.
I'll file a bug for that as i don't think it should do that.