1000087 - Thunderbird Fedora x86_64 release not connecting to IMAP server (Suspect DNS issue)

Status: RESOLVED WORKSFORME

(Thunderbird :: Untriaged, defect)

Description

[reachprak]

User Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/34.0.1847.116 Safari/537.36

Steps to reproduce:

Switched to a Intel-i7 process. Loaded Fedora 19 x86_64 version. Thunderbird does not connect to IMAP server. Changed DNS to IP address. Works intermittently.

Linux Fedora 19 version: 
Linux nirvana-new.cdotb.ernet.in 3.9.5-301.fc19.x86_64 #1 SMP Tue Jun 11 19:39:38 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux

Thunderbird 24.4.0 that came with the release.



Actual results:

Thunderbird did not connect to the IMAP server. Keeps trying to download INBOX and never stops.


Expected results:

Thunderbird should have smoothly connected to the IMAP server and downloaded mails.

Comment 1

[WADA:World Anti-bad-Duping Agency]

See bug 402793 comment #28, and get NSPR log and check log.
> Win example : SET NSPR_LOG_MODULES=timestamp,nsHostResolver:5,imap:5,pop3:5,nntp:5,smtp:5
> if Socket level log is needed, add ",nsSocketTransport:5".
Because log volume is usually large, get minimum log.
 1. create new Tb's profile, start Tb with the new profile,
    disable Global Search and Indexer, mail.server.default.offline_download = false, restart.
 2. define one relevant mail account only, disable any automatic actions:
    new mail check, automatic delete, ....
    If POP3, check "Leve Messages on Server", check "Fetch headers only".
    auto-sync is disabled by offline_download = false.
 3. restart Tb with required logging enabled.

Comment 2

[Wayne Mery (:wsmwk)]

reachprak, please supply the requested information...

(In reply to WADA from comment #1)
> See bug 402793 comment #28, and get NSPR log and check log.
> > Win example : SET NSPR_LOG_MODULES=timestamp,nsHostResolver:5,imap:5,pop3:5,nntp:5,smtp:5
> > if Socket level log is needed, add ",nsSocketTransport:5".
> Because log volume is usually large, get minimum log.
>  1. create new Tb's profile, start Tb with the new profile,
>     disable Global Search and Indexer, mail.server.default.offline_download
> = false, restart.
>  2. define one relevant mail account only, disable any automatic actions:
>     new mail check, automatic delete, ....
>     If POP3, check "Leve Messages on Server", check "Fetch headers only".
>     auto-sync is disabled by offline_download = false.
>  3. restart Tb with required logging enabled.

Comment 3

[reachprak]

Thunderbird is now able to connect to the IMAP server.

I set this parameter "network.dns.diableipv6" to true after reading this somewhere. Not sure whether it was this that solved the problem. Also, I had a large amount of mail on the IMAP servers (Multiple GB). It could be that thunderbird new installation was downloading the whole thing.

I cannot afford to delete the current working configuration. Will have to replicate this in a new account and get back. Will try and confirm in a day or two.

Comment 4

[Wayne Mery (:wsmwk)]

(In reply to reachprak from comment #3)
> Thunderbird is now able to connect to the IMAP server.
> 
> I set this parameter "network.dns.diableipv6" to true after reading this
> somewhere. Not sure whether it was this that solved the problem. Also, I had
> a large amount of mail on the IMAP servers (Multiple GB). It could be that
> thunderbird new installation was downloading the whole thing.
> 
> I cannot afford to delete the current working configuration. Will have to
> replicate this in a new account and get back. Will try and confirm in a day
> or two.

What were your findings?
How about with version 31?

Comment 5

[reachprak]

Current version of thunderbird = 31.2.0
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0

I tried the following:

1. Set "network.dns.disableIPv6" = true. Restart thunderbird.
  - Connecting to IMAP server properly. I am able to read INBOX and subfolders.
  - Mail sending via a different SMTP server OK. Mail copied to "Sent" folder using IMAP OK.

2. Changed "network.dns.disableIPv6" = false. Restart thunderbird.
  - Same behaviour as above.

Tried steps 1 & 2 thrice. Same result.

Able to use without any problem. Either the problem was fixed or my observation of the problem was wrong.

Comment 6

[Wayne Mery (:wsmwk)]

Thanks for the update