Page 1 of 1

A906 NO FETCH invalid message set -- Inconsistent Error

Posted: Thu Feb 23, 2006 2:11 pm
by will123195
some of my users get many of the following errors in their SWA inbox.

Code: Select all

ERROR:
Scalix Web Access could not correctly parse this message because it is not a valid MIME e-mail message.
Contact the sender and have them fix their mail application (which is sending out the invalid MIME message.)
Mime Error:
A906 NO FETCH invalid message set; nested exception is: com.sun.mail.iap.CommandFailedException: A906 NO FETCH invalid message set
here is the original message


here is some additional information. consider the following turn of events:

1. the user logs in to SWA and notices 12 new messages in her inbox... all of which appear to be error message emails with the above error.

2. she calls me to check out all of these error messages in her inbox, but when i log into her SWA account, there are 12 new messages from different recipients -- nothing appears to be wrong.

3. she logs out and then logs back in to SWA and everything is back to normal.

as far as i know, every few days it happens to a few different users. it seems that SWA is randomly having trouble reading new messages in the inbox)

Posted: Thu Feb 23, 2006 2:13 pm
by will123195
forgot to mention... i'm using 9.4.

where can i find upgrade instructions? thanks.

Posted: Thu Feb 23, 2006 6:39 pm
by ScalixSupport
Documentation is included in the tarball when you download release 10.

Regards,
Don

Posted: Thu Feb 23, 2006 7:40 pm
by mephisto
I have similar issues and no fix for it so far:
http://www.scalix.com/community/viewtopic.php?t=1452

Posted: Fri Feb 24, 2006 6:30 pm
by peteb
This seems to happen if the same user is logged into Scalix more than once. I find that getting them to log out and killing any open processes with their user id fixes the problem.

Pete

Posted: Sat Feb 25, 2006 8:04 am
by florian
Pete,

you're quite right; while Scalix 10 SWA has far better support for users logged in with multiple connections and/or different clients at the same time (previous versions used to display the infamous "null" error in those cases!), there are still limitations due to the fact how we use IMAP for SWA and how it handles those folder change notifications.

We're working on further improving this in a future release.

Cheers,
Florian.