830215 - Unable to load mail : Security Content Error

Status: RESOLVED WORKSFORME

(MailNews Core :: Networking: IMAP, defect)

Description

[akash.delhite]

User Agent: Mozilla/5.0 (Windows NT 6.1; rv:10.0.2) Gecko/20100101 Firefox/10.0.2
Build ID: 20120215223356

Steps to reproduce:

Downloaded Thunderbird 17.0.2 for Windows 7 32 bit. 
Installed it, and linked it to my GMAIL account.


Actual results:

After downloading 1263 mails out of 4882, the process just stopped.
Seeing error console lists the following error :

Security Error: Content at moz-nullprincipal:{5adf91dd-f84d-4899-a996-3f7822023a3e} may not load or link to imap://[e-mail]:993/fetch%3EUID%3E/INBOX%3E35282?header=filter&emitter=js&part=1.2&filename=test11.JPG.


Expected results:

This error should not have occured, and if security policies make it appear then should be a option to turn it off. Basically the mail download process should not stop.

Comment 1

[Atul Jangra [:atuljangra]]

I am not able to detect what is causing the problem here. :-/
Reporter, Can you reproduce the problem? If yes, then an IMAP log would be a good treat for us :-)
More information on how you can get IMAP log : https://wiki.mozilla.org/MailNews:Logging

Comment 2

[akash.delhite]

@Atul : I am able to reproduce this.

I am trying to take the logs as suggested in wiki, but i get the blank file created.

set NSPR_LOG_MODULES=imap:5
set NSPR_LOG_FILE=%USERPROFILE%\Desktop\imap.log
"%ProgramFiles%\Mozilla Thunderbird\thunderbird.exe"

Let me know how can i tell more info on this.

Comment 3

[Atul Jangra [:atuljangra]]

Hey Akash,
Did you run the batch files with administrative priviledges?

Comment 4

[:Hb]

A very similar error message shows up with a POP3 account in Seamonkey 2.31 under Windows 7 on a local mail account with lagging response. This very slow response may have other reasons, perhaps a broken mailbox file or else. The ID is here: moz-nullprincipal:{5271de4f-9ee6-44af-9774-47ab8333307f}

Comment 5

[Wayne Mery (:wsmwk)]

Do you still see this issue when using a current version?

Comment 6

[:Hb]

I don't get the error with the ID moz-nullprincipal:{5271de4f-9ee6-44af-9774-47ab8333307f} any more. The initial error for this bug report was never an issue here, too.

Comment 7

[Wayne Mery (:wsmwk)]

I do not totally understand comment 6. But I'll take as you no longer see this original issues.