ATT'N A.WILLIAMS
Sorry it has been so long since your email but I have not progressed at all. I deleted my Seamonkey mail account and switched to Thunderbird. I couldnt get around Thunderbird's Address/Contacts setup so I created a new Seamonkey mail account. As per before my troubles with Seamonkey mail continue. It still refuses to accept my password. I am at a loss as to whether the upgrade to 2.31 had any influence or not. Until I can get the email account to accept my password I wont be able to see if the double and sometimes triple emails situation has changed. On a slightly different note I was recently searching Microsoft for answers and I came across a statement saying that my problems stemmed from the fact that Seamonkey and/or Mozilla did not trust my ISP Sympatico . I retraced my steps to try to research the statement but couldnt find it a second time. Sympatico is a branch of Bell Canada which is older than dirt so I cant see that as being the problem unless they somehow dont lik e the securities used by them. Any thoughts? From: [email protected] To: [email protected] Subject: RE: Update to SeaMonkey 2.31 caused a "crash" Date: Tue, 16 Dec 2014 12:19:34 -0500 My issues are with the email portion of Seamonkey. About one month ago all of my emails were appearing in duplicate and on occasion in triplicate. After I deleted them I would empty the trash and when I logged back into my mail box some of them had reappeared. I decided to upgrade from 2:30 to 2:31 and at that point I started to receive a new message. My present hurdle is " your password or user name are not correct". I am no longer able to access my mail box. I use windows 7 with 64 bit and my ISP is Sympatico.ca. Any thoughts anyone ? > Date: Tue, 16 Dec 2014 18:01:13 +0100 > From: [email protected] > Subject: Re: Update to SeaMonkey 2.31 caused a "crash" > To: [email protected] > > Gerry Hickman wrote: > > Hi, > > > > When there's a browser update, and you restart SM, it will run the > > updater and then start the browser with a redirect to the release notes. > > This has always worked. > > > > Today, I restarted SM, it ran the updater, but then a SM related dialog > > (which I've never seen) appeared saying there had been a "crash" and did > > I want to report it. I chose "Quit SeaMonkey", and now it seems to work > > normally and reports the version as 2.31... > > > > I had something rather like that on a Win 7 x64 machine a week or so > ago, possibly the day after 2.31 was released. No problems since. > My case was on the initial update. Are you saying yours was as well > (which is what I think you are saying) or that Seamonkey performed the > update process a second time? > _______________________________________________ > [email protected]. > https://lists.mozilla.org/listinfo/support-seamonkey _______________________________________________ support-seamonkey mailing list [email protected] https://lists.mozilla.org/listinfo/support-seamonkey
