On 10/22/2013 01:56 AM, Neil wrote: > NoOp wrote: > >>Thanks for taking the time to have a look Neil. I still have it in the same >>state & will leave it like that for a few more hours. I have 3 other pop3 >>accounts that use the same pop servers & they aren't having issues. >> >> > What you can try is a complete hack to reset the server's flags. Note: > this procedure does not work if you are using the Global Inbox. > > 1. Select the failing account or one of its folders > 2. Open the Error Console from the mail window > 3. Evaluate the following text > > top.opener.msgWindow.openFolder.server.nsIPop3IncomingServer.pop3CapabilityFlags > |= 0x30; >
Neil, Finally caught the error & copy & pasted the above into the error console & clicked 'Evaluate' Got this response: Timestamp: 11/14/2013 03:32:42 PM Error: TypeError: top.opener.msgWindow.openFolder.server.nsIPop3IncomingServer is undefined Source File: javascript:%20top.opener.msgWindow.openFolder.server.nsIPop3IncomingServer.pop3CapabilityFlags%20%20%20%20%20%20%20|=%200x30; Line: 1 _______________________________________________ support-seamonkey mailing list [email protected] https://lists.mozilla.org/listinfo/support-seamonkey
