On May 7, 5:14 am, Daniel <[email protected]> wrote: > Ed wrote: > > > -------- Original Message -------- > > Subject: Re:SeaMonkey2.0.14 Security Update > > Date: Sun, 1 May 2011 11:30:08 -0700 (PDT) > > From: blurosemarie1 <[email protected]> > > To: Edmund <[email protected]> > > > On Apr 28, 7:28 pm, Edmund <[email protected]> wrote: > >> As part of Mozilla's ongoing stability and security update process, > >>SeaMonkey2.0.14 is now available for Windows, Mac, and Linux as a free > >> download fromwww.seamonkey-project.org. > > >> We strongly recommend that allSeaMonkeyand old suite users upgrade to > >> this latest release. If you already haveSeaMonkey2.0, you will receive > >> an automated update notification within 24 to 48 hours. This update can > >> also be applied manually by selecting "Check for Updates..." from the > >> Help menu. > >> Edmund > > Edmund, > > Since this update fromSeaMonkeyour Mac OS X "OUTGOING"mail > > does not WORK! We need help trying to get this fix, but have had no > > success from anyone and/or they pass it to another business saying it > > is "not their doing". > > EXAMPLE: Since our server is Comcast they said they will not help with > > our problem since it started when we updated with "SeaMonkey" and it > > must be a problem/bug from them and they need to correct. > > We finally were able to get the "Incoming"mailto work, but the > > "Outgoing" still has this problem with the "SMTP" and sometimes a > > "KeyChain password" prompts up... We have used the same password/s for > > a long time and haven't changed anything since this problem. > > Are there other "SeaMonkey" users having this problem since the new > > update? Can you or someone who is very tech savvy help us. Our email > > is our main source for communication, bill paying, document saving, > > etc.... > > > ****Oh, by the way... I am writing and "sending" this email from my > > MacBook using our Router from our Mac OS X that is having the > > problem.. Since this MacBook works, we copied exactly my settings for > >mail(port,SMTP,server..etc.) with no success... > > > Please Help. > > Sincerely Blurosemarie1 > > Blurosemarie1, in your last paragraph, you mention that you use a > Router!! Is it possible that this router does not know whatSeaMonkey > 2.0.14 is, so is blocking it's send function. > > It's possible that your router knew thatSeaMonkey2.0.13 was o.k. to > send emails, because you had told your router it was o.k., but no-one > has told the router it's o.k. forSeaMonkey2.0.14 to send. > > Try to tell your router that SM 2.0.14 is o.k.!! > > Daniel
The Router is for use of my Macbook laptop in another room. The laptop works fine for "outgoing" mail. so, that tells me the Router is fine. The reason for this is: I didn't not allow for "SeaMonkey's" Sercurity update, but on the Main computer my husband allowed the update and that when the whole problem started of "outgoing" mail on the "Main" computer not working at all. The "Main" computer is hooked up directly to a cable from Comcast. Thanks anyway for you suggestion. Blurosemarie :-) _______________________________________________ support-seamonkey mailing list [email protected] https://lists.mozilla.org/listinfo/support-seamonkey
