516914 - Shredder hangs on several imap operations, like copying message to Sent and Drafts folders.

Status: RESOLVED INVALID

(MailNews Core :: Networking: IMAP, defect)

Description

[Sergey Fukanchik]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; ru; rv:1.9.1.2) Gecko/20090729 Firefox/3.5.2 (.NET CLR 3.5.30729)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.4pre) Gecko/20090915 Shredder/3.0b4pre

All messages that i send through imap server on mail.ru service make sending dialog hang wating for message to be copied somewhere. Another problem - if i write message during some time it tries to save draft but can never finish this operation too. Probably there is no folders with such name. Probably these folders have russian names, i don't know and do not know how to debug that.

I'm not sure who is responsible for this problem - imap server or shredder, but i bet it's too early to use imap in mail client by default. Or just check capabilities and server responses on various operations before offering imap.someserver.com to user of shredder. It may be better to still use pop protocol.


Reproducible: Always

Steps to Reproduce:
0. Register account on mail.ru free mail service. Create this account in Shredder.
1. Create new message. Fill address, subject, body;
2. Press "Send";
3. "Sending Messages" dialog never closes. It writes: "Status: Copying message to Sent folder...
Actual Results:  
Sending dialog hangs and never closes.

Expected Results:  
Dialog should just send message and close as soon as possible.

Comment 1

[Ludovic Hirlimann [:Usul]]

Serge could you provide us imap,timestamp logs ? see https://wiki.mozilla.org/MailNews:Logging for instructions on how to get it.

Comment 2

[Sergey Fukanchik]

Attachment: Log when sending never ends

It was made with such .bat file.

set NSPR_LOG_MODULES=imap:5,timestamp
set NSPR_LOG_FILE=C:\imap.log
"C:\Program Files\Shredder\thunderbird.exe"

I created message and sent it. Then i waited for some time.

Comment 3

[Ludovic Hirlimann [:Usul]]

2009-08-16 10:33:51.371000 UTC - 1372[436c040]: 4433800:imap.mail.ru:A:CreateNewLineFromSocket: * BYE Internal login failure. Error report written to server log.

You might want to contact the technical support of mail.ru as the issue seems to be on their server - point them to this bug.

Comment 4

[Sergey Fukanchik]

If there is some kind of error, 
why don't notify user and close dialog?

Comment 5

[WADA:World Anti-bad-Duping Agency]

(In reply to comment #4)
> If there is some kind of error, 
> why don't notify user and close dialog?

IMAP log says;
> 2009-08-16 10:33:50.830000 UTC (snip) 2 OK Logged in.
> 2009-08-16 10:33:50.830000 UTC (snip) 3 namespace
> 2009-08-16 10:33:50.830000 UTC (snip) * BYE Internal login failure. Error report written to server log.
> 
2009-08-16 10:33:50.840000 UTC (snip) 4 lsub "" "*"
IMAP protocol defines response code to a command as next.
> http://tools.ietf.org/html/rfc3501#section-2.2.2
> OK (indicating success), NO (indicating failure),
> or BAD (indicating a protocol error such as unrecognized command or command syntax error)
It's apparent server side RFC violation(bug of server, or incorrect setup).

Even though invalid * BYE to 3 namespace, Tb doesn't notify user about RFC violation of your IMAP server, and Tb sends 4 lsub "" "*".
As you say, I also think It's not so good behaviour for you. And, as you say, I also think Tb should notify user about server's RFC violation.
However, some servers(not so small number) return unsolisite response for older IMAP command which is inavliad for currently active command, or return wrong response to a command. If this kind of invalid response is reported to user and if Tb stops to communicate with server, users of the some servers(not so small number) can't use the IMAP server, and error notification is very annoying. I think "ignoring such invalid response" and "no error notification to user for such error" in this case is a result of quirks for such server's wrong behaviour.

Comment 6

[Wayne Mery (:wsmwk)]

sounds like INVALID, and there are already bugs about improving error feedback.