Closed Bug 273915 Opened 20 years ago Closed 20 years ago

on startup there are 3 errors: "imap.web.de is not a imap4 server"

Categories

(Thunderbird :: General, defect)

x86
Windows 2000
defect
Not set
minor

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: firefox-112, Assigned: mscott)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; de-DE; rv:1.7.5) Gecko/20041122 Firefox/1.0
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; de-DE; rv:1.7.5) Gecko/20041122 Firefox/1.0

i own 5 web.de accounts 
on startup of thunderbird 1.0, there appears three times the message box
"imap.web.de is not a imap4 server"

this box DOESN't appear for each account
i wasn't able to locate which account causes this problem. but it is definitely
NOT a problem of the web.de server


Reproducible: Always
Steps to Reproduce:
1. start thunderbird 1.0
2. 
3.

Actual Results:  
the message box "imap.web.de is not a imap4 server" appears
after closing the boxes thunderbird works without probs

Expected Results:  
not shown the boxes :-)

win2000 thunderbird 1.0
adsl
I have just seen this same error with a different configuration.

Running Thunderbird 1.0.2 on OSX 10.4.1, connecting to a single user account on
a Courier-IMAP server using SSL (but on a non-standard port due to firewall
settings):

I get this pop-up error window:  "This mail server is not an IMAP4 mail server."

(and I can't get any mail)

I know that the server is working fine.  I can connect to it using the same
settings on other mail clients such as mutt.

I found the error code on
http://www.mozilla.org/docs/l10n/l10nkits/client/windows/docs/nav40/allxpstr.h

as:

ResDef(MK_MSG_IMAP_SERVER_NOT_IMAP4,                -464,
       "This mail server is not an IMAP4 mail server.")

This is a showstopper for me and means that I cannot use Thunderbird at all.


I tracked this down via

nsImapCore.h and nsImapProtocol.cpp

It turned out to be a misconfigured server returning a malformed CAPABILITY
response.  Fixing the server configuration made the error go away.

so the server was returning illegal syntax? Marking invalid on that understanding.
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.