885236 - imap client problem when trying to retrieve messages from the server after undergoing successful authorization

Status: RESOLVED INCOMPLETE

(MailNews Core :: Networking: IMAP, defect)

Description

[sergey]

User Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:21.0) Gecko/20100101 Firefox/21.0 (Beta/Release)
Build ID: 20130511120803

Steps to reproduce:

add an entry in the program,
[e-mail]
pass: test
then I enter the password is sending registration information, and receive messages and folders available on the server does not, in this case the server runs without key problems, and authorization for logs also runs successfully, loop occurs on the stage, get a list of folders and the contents of those folders.

Lie to the server and the client is attached.


Метка времени: 20.06.2013 11:49:27
Ошибка: 
Источник: resource:///modules/errUtils.js
Строка: 96
------------------------
Метка времени: 20.06.2013 11:49:27
Ошибка: 
Источник: resource:///modules/errUtils.js
Строка: 35
--------------------------
Метка времени: 20.06.2013 11:49:30
Ошибка: Not Found
Источник: resource:///modules/errUtils.js
Строка: 96
------------------------------
Метка времени: 20.06.2013 11:49:30
Ошибка: Not Found
Источник: resource:///modules/errUtils.js
Строка: 35
---------------------------------
Метка времени: 20.06.2013 11:49:33
Ошибка: MX lookup would be no different from domain
Источник: resource:///modules/errUtils.js
Строка: 96
---------------------------------
Метка времени: 20.06.2013 11:49:33
Ошибка: MX lookup would be no different from domain
Источник: resource:///modules/errUtils.js
Строка: 35
--------------------------------
Put the beta version of mozila thunderbird 24.0a1 problems even more.

Time stamp: 19.06.2013 22:59:56
Warning: Unknown property «box-sizing». Lost ad.
Source:
Line 14, character 22
Source:
box-sizing: border-box;
-----------------------------
Time stamp: 19.06.2013 22:59:56
Warning: Unknown property «-moz-border-radius». Lost ad.
Source:
String 135, symbol 25
Source:
-moz-border-radius: 5px;
------------------------------
Time stamp: 19.06.2013 22:59:56
Warning: Unknown property «-moz-border-radius». Lost ad.
Source:
String 168, symbol 25
Source:
-moz-border-radius: 5px 5px 0 0;
---------------------------------------
Time stamp: 19.06.2013 21:29:26
Warning: Container for XUL element comprises _moz_generated_content_before inline-descendant # text, which leads to the fact that all of its descendants are wrapped in a block.
Source: chrome :/ / messenger / content / messenger.xul
Line: 0
-------------------------------
Tried to re-create the database mySQL, thought base crumbled, it turned all the rules, all of the backup restore and restore messages through synchronization utility.

here is the log e-mail client:
Time stamp: 19.06.2013 5:45:51
Warning: Unknown property «box-sizing». Lost ad.
Source:
Line: 15

Time stamp: 19.06.2013 5:45:51
Warning: Unknown property «-moz-border-radius». Lost ad.
Source:
Line: 136

Time stamp: 19.06.2013 5:45:51
Warning: Unknown property «-moz-border-radius». Lost ad.
Source:
Line: 169

before the client logs:
Time stamp: 19.06.2013 5:31:42
Warning: Error in parsing value «padding-bottom». Lost ad.
Source: chrome :/ / messenger / skin / messenger.css
Line: 401
Time stamp: 19.06.2013 5:31:44
Warning: Container for XUL element comprises _moz_generated_content_before inline-descendant # text, which leads to the fact that all of its descendants are wrapped in a block.
Source: chrome :/ / global / content / bindings / toolbar.xml
Line: 276
Time stamp: 19.06.2013 5:31:44
Warning: Container for XUL element comprises _moz_generated_content_before inline-descendant # text, which leads to the fact that all of its descendants are wrapped in a block.
Source: chrome :/ / global / content / bindings / toolbar.xml
Line: 276
Time stamp: 19.06.2013 5:31:44
Warning: Container for XUL element comprises _moz_generated_content_before inline-descendant # text, which leads to the fact that all of its descendants are wrapped in a block.
Source: chrome :/ / global / content / bindings / toolbar.xml
Line: 276
Time stamp: 19.06.2013 5:31:45
Warning: The use of Mutation Events is obsolete. Instead, use the MutationObserver.
Source: chrome :/ / messenger/content/msgMail3PaneWindow.js
Line: 944
Time stamp: 19.06.2013 5:31:46
Warning: Unknown property «box-sizing». Lost ad.
Source:
Line: 15
Time stamp: 19.06.2013 5:31:46
Warning: Unknown property «-moz-border-radius». Lost ad.
Source:
Line: 136
Time stamp: 19.06.2013 5:31:46
Warning: Unknown property «-moz-border-radius». Lost ad.
Source:
Line: 169
End of errors
----------------------

log server
вот логи сервака
"IMAPD" 4076 4 "2013-06-18 23:00:21.390" "109.74.*.*" "SENT: * OK IMAPrev1"
"IMAPD" 3748 4 "2013-06-18 23:00:21.490" "109.74.*.*" "RECEIVED: 1 capability"
"IMAPD" 3748 4 "2013-06-18 23:00:21.491" "109.74.*.*" "SENT: * CAPABILITY IMAP4 IMAP4rev1 CHILDREN IDLE QUOTA SORT ACL NAMESPACE RIGHTS=texk[nl]1 OK CAPABILITY completed"
"IMAPD" 3608 4 "2013-06-18 23:00:21.521" "109.74.*.*" "RECEIVED: 3 login "sergey-x@******.pro" ***"
"IMAPD" 3608 4 "2013-06-18 23:00:23.086" "109.74.*.*" "SENT: 3 OK LOGIN completed"
"IMAPD" 3300 4 "2013-06-18 23:00:23.117" "109.74.*.*" "RECEIVED: 4 namespace"
"IMAPD" 3300 4 "2013-06-18 23:00:23.118" "109.74.*.*" "SENT: * NAMESPACE (("" ".")) NIL (("#Publi"
"DEBUG" 3916 "2013-06-18 23:01:16.280" "No messages to index."

http://forum.mozilla-russia.org/viewtop ... 43#p616643


Actual results:

I can not get a list of folders from the server after a successful authentication protocol imap and messages respectively, and available on a server
played on versions 24.0a1 (16.06.13), and the latest release of 17.0.6


Expected results:

to happen correctly to get a list of folders on the server and the contents of these folders in the form of messages, but it does not happen, because on stage after a successful login email client loops and authorizes indefinitely.

Comment 1

[sergey]

outlook 2007 прекрасно обрабатывает почту на сервере так что это бага именно почтового клиента от mozilla...

2007 outlook perfectly handles mail on the server so that it is a bug that is the mail client from mozilla ...

Comment 2

[Alexander L. Slovesnik]

(In reply to sergey from comment #1)
> outlook 2007 прекрасно обрабатывает почту на сервере так что это бага именно
> почтового клиента от mozilla...
> 
> 2007 outlook perfectly handles mail on the server so that it is a bug that
> is the mail client from mozilla ...

Can you turn on logging in thunderbird and attach log to this bug?
See https://wiki.mozilla.org/MailNews:Logging#Generating_a_Protocol_Log for instructions.

Comment 3

[sergey]

(In reply to Alexander L. Slovesnik from comment #2)
> (In reply to sergey from comment #1)
> > outlook 2007 прекрасно обрабатывает почту на сервере так что это бага именно
> > почтового клиента от mozilla...
> > 
> > 2007 outlook perfectly handles mail on the server so that it is a bug that
> > is the mail client from mozilla ...
> 
> Can you turn on logging in thunderbird and attach log to this bug?
> See https://wiki.mozilla.org/MailNews:Logging#Generating_a_Protocol_Log for
> instructions.
2636[6dc6cd0]: ImapThreadMainLoop entering [this=8748800]
0[220f140]: 8748800:allservice.pro:NA:SetupWithUrl: clearing IMAP_CONNECTION_IS_OPEN
2636[6dc6cd0]: 8748800:allservice.pro:NA:ProcessCurrentURL: entering
2636[6dc6cd0]: 8748800:allservice.pro:NA:ProcessCurrentURL:imap://[e-mail]:143/select%3E%5EINBOX:  = currentUrl
4112[6dc7210]: ImapThreadMainLoop entering [this=78e0800]
0[220f140]: 78e0800:allservice.pro:NA:SetupWithUrl: clearing IMAP_CONNECTION_IS_OPEN
4112[6dc7210]: 78e0800:allservice.pro:NA:ProcessCurrentURL: entering
4112[6dc7210]: 78e0800:allservice.pro:NA:ProcessCurrentURL:imap://[e-mail]:143/select%3E%5EINBOX:  = currentUrl
2636[6dc6cd0]: ReadNextLine [stream=6b87748 nb=15 needmore=0]
2636[6dc6cd0]: 8748800:allservice.pro:NA:CreateNewLineFromSocket: * OK IMAPrev1

4112[6dc7210]: ReadNextLine [stream=87295c8 nb=15 needmore=0]
4112[6dc7210]: 78e0800:allservice.pro:NA:CreateNewLineFromSocket: * OK IMAPrev1

2636[6dc6cd0]: 8748800:allservice.pro:NA:SendData: 1 capability

4112[6dc7210]: 78e0800:allservice.pro:NA:SendData: 1 capability

2636[6dc6cd0]: ReadNextLine [stream=6b87748 nb=81 needmore=0]
2636[6dc6cd0]: 8748800:allservice.pro:NA:CreateNewLineFromSocket: * CAPABILITY IMAP4 IMAP4rev1 CHILDREN IDLE QUOTA SORT ACL NAMESPACE RIGHTS=texk

2636[6dc6cd0]: ReadNextLine [stream=6b87748 nb=27 needmore=0]
2636[6dc6cd0]: 8748800:allservice.pro:NA:CreateNewLineFromSocket: 1 OK CAPABILITY completed

2636[6dc6cd0]: try to log in
2636[6dc6cd0]: IMAP auth: server caps 0xC0335, pref 0x0, failed 0x1006, avail caps 0x0
2636[6dc6cd0]: (GSSAPI = 0x1000000, CRAM = 0x0, NTLM = 0x20000, MSN =  0x0, PLAIN = 0x100000, LOGIN = 0x0, old-style IMAP login = 0x200000)auth external IMAP login = 0x0
2636[6dc6cd0]: trying auth method 0x4
4112[6dc7210]: ReadNextLine [stream=87295c8 nb=81 needmore=0]
4112[6dc7210]: 78e0800:allservice.pro:NA:CreateNewLineFromSocket: * CAPABILITY IMAP4 IMAP4rev1 CHILDREN IDLE QUOTA SORT ACL NAMESPACE RIGHTS=texk

4112[6dc7210]: ReadNextLine [stream=87295c8 nb=27 needmore=0]
4112[6dc7210]: 78e0800:allservice.pro:NA:CreateNewLineFromSocket: 1 OK CAPABILITY completed

4112[6dc7210]: try to log in
4112[6dc7210]: IMAP auth: server caps 0xC0335, pref 0x0, failed 0x1006, avail caps 0x0
4112[6dc7210]: (GSSAPI = 0x1000000, CRAM = 0x0, NTLM = 0x20000, MSN =  0x0, PLAIN = 0x100000, LOGIN = 0x0, old-style IMAP login = 0x200000)auth external IMAP login = 0x0
4112[6dc7210]: trying auth method 0x4
2636[6dc6cd0]: got new password
2636[6dc6cd0]: IMAP: trying auth method 0x4
2636[6dc6cd0]: old-style auth
2636[6dc6cd0]: 8748800:allservice.pro:NA:SendData: Logging suppressed for this command (it probably contained authentication information)
2636[6dc6cd0]: ReadNextLine [stream=6b87748 nb=22 needmore=0]
2636[6dc6cd0]: 8748800:allservice.pro:NA:CreateNewLineFromSocket: 3 OK LOGIN completed

2636[6dc6cd0]: login succeeded
2636[6dc6cd0]: 8748800:allservice.pro:A:SendData: 4 namespace

4112[6dc7210]: got new password
4112[6dc7210]: IMAP: trying auth method 0x4
4112[6dc7210]: old-style auth
4112[6dc7210]: 78e0800:allservice.pro:NA:SendData: Logging suppressed for this command (it probably contained authentication information)
4112[6dc7210]: ReadNextLine [stream=87295c8 nb=22 needmore=0]
4112[6dc7210]: 78e0800:allservice.pro:NA:CreateNewLineFromSocket: 3 OK LOGIN completed

4112[6dc7210]: login succeeded
4112[6dc7210]: 78e0800:allservice.pro:A:SendData: 4 namespace

0[220f140]: proposed url = INBOX folder for connection  has To Wait = TRUE can run = FALSE
0[220f140]: queuing url:imap://[e-mail]@allservice.pro:143/folderstatus>^INBOX
0[220f140]: considering playing queued url:imap://[e-mail]@allservice.pro:143/folderstatus>^INBOX
0[220f140]: creating protocol instance to play queued url:imap://[e-mail]@allservice.pro:143/folderstatus>^INBOX
0[220f140]: proposed url = INBOX folder for connection  has To Wait = TRUE can run = FALSE
0[220f140]: failed creating protocol instance to play queued url:imap://[e-mail]@allservice.pro:143/folderstatus>^INBOX
2636[6dc6cd0]: ReadNextLine [stream=6b87748 nb=0 needmore=1]
4112[6dc7210]: ReadNextLine [stream=87295c8 nb=0 needmore=1]
2636[6dc6cd0]: 8748800:allservice.pro:A:CreateNewLineFromSocket: clearing IMAP_CONNECTION_IS_OPEN - rv = 80004004
4112[6dc7210]: 78e0800:allservice.pro:A:CreateNewLineFromSocket: clearing IMAP_CONNECTION_IS_OPEN - rv = 80004004
2636[6dc6cd0]: 8748800:allservice.pro:A:TellThreadToDie: close socket connection
4112[6dc7210]: 78e0800:allservice.pro:A:TellThreadToDie: close socket connection
2636[6dc6cd0]: 8748800:allservice.pro:A:CreateNewLineFromSocket: (null)
4112[6dc7210]: 78e0800:allservice.pro:A:CreateNewLineFromSocket: (null)
4112[6dc7210]: 78e0800:allservice.pro:A:ProcessCurrentURL: aborting queued urls
2636[6dc6cd0]: 8748800:allservice.pro:A:ProcessCurrentURL: aborting queued urls
4112[6dc7210]: ImapThreadMainLoop leaving [this=78e0800]
2636[6dc6cd0]: ImapThreadMainLoop leaving [this=8748800]

Comment 4

[Alexander L. Slovesnik]

This log reminds me log from Bug 817008. Have you tried to change IMAP port from 143/STARTTLS to 993/SSL? According to Bug 817008 comment 6 it could help.

Comment 5

[Alexander L. Slovesnik]

Moving to correct component.

Comment 6

[sergey]

honored proposed bugs, it's not because Koma-Mail e-mail that has been taken, and shows only some of the messages says that he can not get them and offers to delete or skip, emergency exits often, but this is because He did not do a tasting 8 64-bit,
In turn, the assembly hmail server-a are tested for compliance with standards and principle is reasonably robust,

ie the Problem is in the client, and to the extent that the lient-mail, can not read can not say exactly, but presumably corrupted messages (neproindeksirovannye letter), just if it does, and the Problem lies in the very servrnoy part, then I'll get in touch with the developer server to resolve the error.

But I still think that the bug is in the mail client from mozilla, because Until then, everything worked fine, no I can not imagine that after the fall of the server kakieto messages in the index server to stop reading, but a customer of priority; such reports shall in any sluche handle and simple or no-show or suggest to remove, as it makes the Koma-Mail and receive new messages, and show already on the client side, just right now it turns out that I generally can not see any old or new messages.

And yet such a moment and e-mail client such as mailboxes that the client from mozilla, reflected in the unified inbox folder or a feature of a client or a server bug pokak Know ...

Comment 7

[WADA:World Anti-bad-Duping Agency]

To bug opener:

When did your problem start to occur with your IMAP server/account?
After upgrade of Tb? Or this is your first use of Tb?

About IMAP log.
No log for response to "4 namespace" is seen in log data pasted by you. Does your server correctly return responses to all IMAP command passed to your IMAP server from Tb? Or it means you edited log data?

Following is a log line in server side log you pasted.
> "IMAPD" 3300 4 "2013-06-18 23:00:23.118" "109.74.*.*" "SENT: * NAMESPACE (("" ".")) NIL (("#Publi"
Is this entire data of response which your server returned to Tb?

What is shown as namespace setting/data at Server Settings/Advanced? 

"Getting log" is for trouble shooting. Get minimum log, please.
1. Disable any automatic IMAP server access.
   (disable automatic new mail check at Server Settings)
2. To disable pararell access to server, max cached connections = 1
   (Serveer Settings, Advanced)
3. Select account instead of Inbox at folder pane, and terminate Tb,
   in order to disable automatic open of Inbox upon restart of Tb.
4. Enable IMAP logging, restart Tb, and click Inbox at folder pane.
   => Tb tries to access server, and tries to open Inbox
5, Terminate Tb, keep backup of log.
   Edit log file by text editor, and remove excess or irrelevant log,
   for example, log of access to other servers,
   with keeping required log for problem determinatin of this bug.
5. *Attach* minimum log file to this bug instead of pasting long data
   to bug.

Following is seen in pasted log.
> 0[220f140]: queuing url:imap://[e-mail]@allservice.pro:143/folderstatus>^INBOX
This indicates Tb tries to open "^INBOX"(or tries to issue status) instead of "INBOX". 
This kind of excess "^" is seen in bug 697789, bug 720911.
These are actual bugs of Tb. However, trigger is not-so-well server side set up. For example, even though namespace is not needed, excess namespace setting is kept. If excess namespace setting in IMAP server package is removed by careful customization, such bug won't occur even if Tb's bug exists.
Does your server well configured?

Comment 8

[Wayne Mery (:wsmwk)]

sergey, please see and reply to questions in comment 7. Thanks

Comment 9

[Phoenix]

Resolved per whiteboard