Marisa Ciceran wrote:
I booted up my Toshiba L500 laptop this morning to SeaMonkey which
promptly updated itself to version 2.0.12. I can no longer send out mails.
The error message I get every time is that the ISP mail server (Verizon)
has timed out, so I called my ISP, Verizon. I spent nearly an hour on
the telephone with technical support who went through all the obvious
configurations and found nothing obviously wrong. Not to leave me
stranded, they had me open and configure an older version of MS Outlook
that is on my system that I have never used just to find out if the
problem would be repeated there, but instead we proved that the
malfunction was not at the ISP server end, but due to some malfunction
in the updated SeaMonkey.
I have already uninstalled and reinstalled SeaMonkey 2.0.12 several
times to no avail. Meanwhile, my desktop PC - mwhich updated SeaMonkey a
day or two ago - has experience no such problem and appears to otherwise
be functioning normally.
Has anyone else experience an outgoing mail problem like this? I have
never had such a problem before, and have no idea how to fix it. Any clues?
Thanks.
Marisa
I have found the cause of the problem: Avast! Free Antivirus Mail Shield
settings. I will explain how I fixed it, but cannot interpret what it
means technically. I do not know how the "corruption" occurred during
the upgrade of SeaMonkey to v. 2.0.12. The areas where I did the repair
are , since
I went to the Avast Mail Shield menu window where I had previously
ticked the options to scan both incoming and outgoing mails. I then
opened the "expert settings" and saw that all three options there were
ticked - inbound mail (POP3, IMAP4), outbound mail (SMTP) and newsgroups
(NNTP). I then went to the "SSL accounts" submenu and found that my ISP,
verizon.net along with several others, but had the option "none" in the
encryption column.
I went back and unticked the option to scan outgoing mails and went to
see if my mails would now go through - and they did. I then re-ticked
the outgoing scan option and went to look at the SSL accounts submenu
again. The encryption option now was changed to "SSL", and all is
restored in SeaMonkey mails in the newly updated version.
I don't know if I could have avoided the steps I mentioned in my last
paragraph and instead changed the "none" to "SSL" on the verizon.net
line manually to achieve the same results. I leave that assessment to
the experts here.
Marisa
_______________________________________________
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey
