268599 - Alert: "The current command did not succeed. The mail server responded: invalid mask." because server responds "10 NO Invalid mask"

Status: RESOLVED INVALID

(MailNews Core :: Networking: IMAP, defect)

Description

[rddunlap]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7) Gecko/20040626 Firefox/0.9.1
Build Identifier: version 0.9 (20041103)

Every time that I start Thunderbird (0.8 or 0.9), I get the Alert:
The current command did not succeed.  The mail server responded: invalid mask.

Reproducible: Always
Steps to Reproduce:
1.  start thunderbird  (to an imap server)
2.  get the alert
3.  click OK (to continue)

Actual Results:  
got the alert message then continued to use thunderbird.

Expected Results:  
no Alert, or better message about the condition so that I could do
something about it.

Comment 1

[David :Bienvenu]

that message is coming from your imap server...

if you generate and attach/e-mail me an imap protocol log, I might be able to
tell you more.

http://www.mozilla.org/quality/mailnews/mail-troubleshoot.html#imap

Comment 2

[Mike Cowperthwaite]

*** Bug 268438 has been marked as a duplicate of this bug. ***

Comment 3

[Gary Morrison]

Attachment: This is a log where the server returns invalid mask

Comment 4

[Gary Morrison]

I also had the same problem and attached a log (didn't seem to have one
earlier).  It seems that this occurs when connecting to dovecot servers.

Some more information about is from a dovecot forum can be found at:
http://www.dovecot.org/pipermail/dovecot/2003-May/001469.html

Comment 5

[Neil Parks]

I don't know why this is still "unconfirmed".  There are numerous references on
the Internet.

Example:
http://forum.powweb.com/showthread.php?t=35531

(quote)

2) IMAP Server Error message: Invalid mask.

This appears to only affect IMAP with Mozilla based mail applications like
Thunderbird, Mozilla Mail, and possibly Netscape Mail. This message is because
your mail application issued a command to UW-IMAP that was ignored by the server
for security reasons. Dovecot does not ignore this command and considers it a
security problem. The simplest way to fix this is to delete your imap account
setting for this account, and then set it up again.

(end quote)

Unfortunately the solution isn't quite so simple for me.  I have several IMAP
accounts and I don't know which one is generating the error msg.

Comment 6

[Scott MacGregor]

not a 1.5 blocker. would consider a fix if one appeared.

Comment 7

[Neil Parks]

(In reply to comment #6)
> not a 1.5 blocker. would consider a fix if one appeared.

There just might be one.  I went into the Server Settings/Advanced for all my
IMAP accounts and deleted all the data in all the "namespace" strings on each one.

For each account, one of three things happened after subsequent logins:

#1.  The namespace fields remained empty, OR
#2.  The namespace fields were refilled with the same strings they had before, OR
#3.  The namespace fields were now filled with different strings.

In all cases, my ability to login and read mail was unharmed, and the error msg
went away and has not returned.

Connection, or coincidence?  I don't know.

Comment 8

[David :Bienvenu]

yes, clearing out the namespaces would fix it.

Comment 9

[Neil Parks]

(In reply to comment #8)
> yes, clearing out the namespaces would fix it.

Can this now be promoted from "unconfirmed" to "new" so that it doesn't get
caught by the new auto-expire policy?

Comment 10

[Wayne Mery (:wsmwk)]

Please comment if you still see this problem, or you know it went away.
reporter email address is dead

Comment 11

[Wayne Mery (:wsmwk)]

Neil says he has not seen this recently.

Comment 12

[Wayne Mery (:wsmwk)]

Another reference, from 2005, https://www.redhat.com/archives/rhl-devel-list/2005-May/msg00299.html

But I think we can close this