On Tue, 26 Jul 2016 12:07:51 -0700 (PDT), piglet...@gmail.com wrote: >On Tuesday, July 26, 2016 at 2:25:45 PM UTC-4, TCW wrote: >> On Tue, 26 Jul 2016 10:26:00 -0700 (PDT), pigletoid wrote: >> >> >On Tuesday, July 26, 2016 at 12:54:27 PM UTC-4, TCW wrote: >> >> On Tue, 26 Jul 2016 09:29:23 -0700 (PDT), pigletoid wrote: >> >> >> >> >On Tuesday, July 26, 2016 at 9:05:26 AM UTC-4, TCW wrote: >> >> >> On Mon, 25 Jul 2016 20:07:41 -0700 (PDT), pigletoid wrote: >> >> >> >> >> >> >My exchange server was just updated from exchange.XXX.com to >> >> >> >outlook.office365.com. I changed the server settings in SM as >> >> >> >recommended, and the account appears functional. However, it no >> >> >> >longer updates the mail in the inbox. When I press 'Get Messages', I >> >> >> >get the (transient) message on the bottom of 'No new messages on the >> >> >> >server'. I am only able to download new messages by closing down SM >> >> >> >and re-opening it. Then it logs into the account and new messages >> >> >> >will appear. >> >> >> >Any suggestions on how to fix this? >> >> >> > >> >> >> >Thanks. >> >> >> >> >> >> Can you update to SM 2.40 or 2.44 from here: https://goo.gl/9R2c0i >> >> > >> >> >I went back to SM 2.39 because 2.40 kept crashing (once closed, it would >> >> >not re-open). I'll give it a try. >> >> >> >> Cool. If 2.44 plays nicely for you perhaps stick with it. Else I can >> >> point you to a current beta of 2.45 *if* you'd like to try it against >> >> the issue you're having. 2.45 (32-bit) should be out shortly after FF >> >> 48.0 is released an it'll be based off that version. >> >> >> >> I'm on 2.44 myself since early June with zero crashes. >> > >> >Didn't work with 2.40. >> >Tried 2.44- email problem is still there, and my default search provider >> >was switched to DuckDuckGo without permission. >> >Any idea why SM doesn't seem to be able to refresh the inbox except when >> >it's opening up the first time? >> >Thanks for your help. >> >> Hmm, doesn't Exchange use a proprietary protocol (MAPI) to grab mail? >> If the server address is now just pointing elsewhere and the access >> protocol has changed, Seamonkey might be stuck in MAPI protocol land >> and now needs to be rejiggered to adjust to office365.com land which >> is IMAP. >> >> Here's an easy test. Go grab Portable Thunderbird >> (http://goo.gl/ChG1), extract it to desktop, run the setup and >> configure per your environment (outlook.office365.com) and log in. See >> what it configures your settings to be after setup and compare how >> your current email is set up under your Seamonkey profile. I'd imagine >> that aside-by-side analysis will reveal where things are going wrong >> in the setup. > >I loaded up ThunderBird Portable, and set it up manually (didn't configure >automatically). It has the same problem as SM.
What if you do Automatic setup? if you just plug in the same settings that Seamonkey has and it doesn't work, are you surprised? _______________________________________________ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
