Mime Error: A1905

[mephisto]

A colleague gets a bunch of these messages if he logs into SWA:

Code: Select all

FEHLER:
Scalix Web Access konnte diese Nachricht nicht verarbeiten
Mime Fehler:
A1905 NO some of the requested messages no longer exist; nested exception is: com.sun.mail.iap.CommandFailedException: A1905 NO some of the requested messages no longer exist
here is the original message:

No original message attached, however. Those error messages are not shown in Outlook. We're running Scalix 10. The issue is just with one user so far. Any way to further debug this?

[ScalixSupport]

Hi Mephisto,

I suspect something is wrong with the mime content type so it isn't necessarily surprising that Outlook displays the message.

Since SWA access via IMAP what do you see if you use an IMAP client like Thunderbird or, if you are familiar, telneting to port 143 and using command line IMAP commands?

Did you run an omtidyallu -M after your upgrade? This pre-generates the mime messages.

For a single user you can run

omtidyu -u "user name/mailnode" -B -M

Accessing with SWA causes the mime generation but it is better to use omtidyu or omtidyallu.

Regards,
Don

[mephisto]

I started from scratch with Scalix 10, so this shouldn't be an upgrade issue. I ran the omtidyu command and got an output like:

Code: Select all

Priming mailbox for MIME access for 'Peter Smith/mail,ourcompany/CN=Peter Smith'
  InTray: 374 messages
  OutTray: 0 messages
  Folder 'Suchbereich ': 2 items

and so on. This did not help. The next time the user logged in into SWA he had again a bunch of unread error messages with the date and time of the login. Also, the sorting of the message list is shuffled at login.

The IMAP server answeres with "some of the requested messages no longer exist".

This is a serious issue for us. We are planning to order and roll out Scalix on the beginning of march.

[ScalixSupport]

For the user having this problem get his omshowu output. In the output you will see a system login number. In this case...

Code: Select all

omshowu -n "user name"
...
System Login : 60536
...

Then with

Code: Select all

 ps -aef |grep imap

you will see the user's imap sessions i.e.

60536 7804 6099 0 11:45 ? 00:00:00 in.imap41d -d
60536 7805 7804 1 11:45 ? 00:00:00 in.imap41d -d
60536 7816 6099 0 11:45 ? 00:00:00 in.imap41d -d
60536 7817 6099 0 11:45 ? 00:00:00 in.imap41d -d

Have the user log out. Do the ps -aef |grep imap again. Do you still see imap sessions for this user? If so kill them off. Log back on. Resolved?

Thanks,
Don

[mephisto]

I don't know why, but the error does currently not appear. I will provide more info if it does.