NoOp wrote:
I was able to reproduce the issue... copied a SM 2.0 from a backup system; first
time I attempted to send I got a password prompt, entered the new smtp password,
worked ok. Then had to reboot for other reasons got the:
Sending of message failed.
The message could not be sent
On 11/29/2009 08:12 PM, NoOp wrote:
...
So it appears that there is something in the 2.0 password routine that
gets stuck when it gets a refused password or error from the isp side.
I'm not sure how to test further.
I was able to reproduce the issue... copied a SM 2.0 from a backup
system;
NoOp wrote:
I'm not sure how to test further.
Make an SMTP log?
http://kb.mozillazine.org/Session_logging_for_mail/news
--
Warning: May contain traces of nuts.
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
NoOp ha scritto:
Ran into an interesting problem today; ATT (my isp) had issues with
their email server today. I opened up SM 2.0 (linux) and found that all
but one account (this one) were working. I couldn't send msgs, couldn't
receive msgs etc. I couldn not even log on to the ATT webmail.
Ran into an interesting problem today; ATT (my isp) had issues with
their email server today. I opened up SM 2.0 (linux) and found that all
but one account (this one) were working. I couldn't send msgs, couldn't
receive msgs etc. I couldn not even log on to the ATT webmail.
So... I bit the bullet
NoOp:
So it appears that there is something in the 2.0 password routine that
gets stuck when it gets a refused password or error from the isp side.
I'm not sure how to test further.
If you could get a log that would be helpful.
https://wiki.mozilla.org/MailNews:Logging
Hartmut
On 11/29/2009 08:35 PM, Hartmut Figge wrote:
NoOp:
So it appears that there is something in the 2.0 password routine that
gets stuck when it gets a refused password or error from the isp side.
I'm not sure how to test further.
If you could get a log that would be helpful.
On 11/29/2009 08:41 PM, NoOp wrote:
On 11/29/2009 08:35 PM, Hartmut Figge wrote:
NoOp:
So it appears that there is something in the 2.0 password routine that
gets stuck when it gets a refused password or error from the isp side.
I'm not sure how to test further.
If you could get a log that
8 matches
Mail list logo