(In reply to gene smith from comment #7) > I'm now doubting it's the same problem as bug 1577548, but not 100% sure. > My newly set up outlook account definitely reports that it has UIDL capability. But capabilities reported have been known to vary depending on which actual server is accessed, especially for the big providers like microsoft, yahoo and maybe gmail. > Anyhow, looking at the code, it appears that if TB sees an error from the server when trying to do the UIDL command it puts up the error message you reported in comment 0: > ```"The POP3 mail server (outlook.office365.com) does not support UIDL or XTND XLST, which are required to implement the 'Leave on Server', 'Maximum Message Size' or 'Fetch Headers Only' options . To download your mail, turn off these options in the Server Settings for your mail server in the Account Settings window.``` > When this error occurs there is no attempt to fetch the messages by other means. So if the server actually doesn't support UIDL, to get your mail you really do have to switch off those items. So in your case, you only have "Leave on Server" selected so you would need to turn that off to reliably fetch new messages, it seems. > > However, I assume you still want to keep your messages on the server so we need to find out if outlook is really not supporting UIDL. To see what it reports you can set the preference ```mailnews.pop3.loglevel``` to ```Debug``` and look at the log using TB's built-in console. The console can be accessed with ```ctrl-alt-j```. Each time you click the "Get Mail" button or when your 62 minute timer expires a request for new mail will occur and be logged. Then in the console, on each request for new mail, you should see something like this: > ``` > S: +OK The Microsoft Exchange POP3 service is ready. [TQBOADIAUABSADEAMQBDAEEAMAAwADMAMAAuAG4AYQBtAHAAcgBkADEAMQAuAHAAcgBvAGQALgBvAHUAdABsAG8AbwBrAC4AYwBvAG0A] > C: CAPA > S: +OK > TOP > UIDL > SASL PLAIN XOAUTH2 > USER > ``` > If UIDL is not in the list, it will cause the problem you are seeing. > Again, this appears to be intermittent so you need to look at this several times over a fairly long time period and maybe every now and then you will see that UIDL is missing from the list or there is an error getting the response to the "CAPA" command. > > So let me know what your see. > Thanks! I got the following code when requesting to receive new messages: ``` Connecting to pop://outlook.office365.com:995 Connected S: +OK The Microsoft Exchange POP3 service is ready. [QwBQADYAUAAyADgANABDAEEAMAAxADAAMgAuAEIAUgBBAFAAMgA4ADQALgBQAFIATwBEAC4ATwBVAFQATABPAE8ASwAuAEMATwBNAA==] C: CAPA S: +OK TOP UIDL SASL PLAIN XOAUTH2 USER . Possible auth methods: XOAUTH2 Current auth method: XOAUTH2 C: AUTH XOAUTH2 S: + XHRPOST https://login.microsoftonline.com/common/oauth2/v2.0/token [HTTP/2 200 OK 596ms] C: Logging suppressed (it probably contained auth information) S: +OK User successfully authenticated. C: STAT ``` TB found no new messages, even though there are new messages on the server.
Bug 1875633 Comment 9 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
I got the following code when requesting to receive new messages: ``` Connecting to pop://outlook.office365.com:995 Connected S: +OK The Microsoft Exchange POP3 service is ready. [QwBQADYAUAAyADgANABDAEEAMAAxADAAMgAuAEIAUgBBAFAAMgA4ADQALgBQAFIATwBEAC4ATwBVAFQATABPAE8ASwAuAEMATwBNAA==] C: CAPA S: +OK TOP UIDL SASL PLAIN XOAUTH2 USER . Possible auth methods: XOAUTH2 Current auth method: XOAUTH2 C: AUTH XOAUTH2 S: + XHRPOST https://login.microsoftonline.com/common/oauth2/v2.0/token [HTTP/2 200 OK 596ms] C: Logging suppressed (it probably contained auth information) S: +OK User successfully authenticated. C: STAT ``` TB found no new messages, even though there are new messages on the server.