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; 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 because the connection to SMTP server smtp.att.yahoo.com was lost in the middle of the transaction. Try again or contact your network administrator. msg. Looking at the log shows: -1215547552[b7511060]: SMTP Connecting to: smtp.att.yahoo.com -1215547552[b7511060]: SMTP entering state: 0 -1215547552[b7511060]: SMTP Response: 220 smtp107.sbc.mail.gq1.yahoo.com ESMTP -1215547552[b7511060]: SMTP entering state: 14 -1215547552[b7511060]: SMTP Send: EHLO [192.168.4.100] -1215547552[b7511060]: SMTP entering state: 0 -1215547552[b7511060]: SMTP Response: 250-smtp107.sbc.mail.gq1.yahoo.com -1215547552[b7511060]: SMTP entering state: 0 -1215547552[b7511060]: SMTP Response: 250-AUTH LOGIN PLAIN XYMCOOKIE -1215547552[b7511060]: SMTP entering state: 0 -1215547552[b7511060]: SMTP Response: 250-PIPELINING -1215547552[b7511060]: SMTP entering state: 0 -1215547552[b7511060]: SMTP Response: 250 8BITMIME -1215547552[b7511060]: SMTP entering state: 4 -1215547552[b7511060]: SMTP entering state: 21 -1215547552[b7511060]: SMTP entering state: 16 -1215547552[b7511060]: Logging suppressed for this command (it probably contained authentication information) -1215547552[b7511060]: SMTP entering state: 0 -1215547552[b7511060]: SMTP Response: 530 Access denied -1215547552[b7511060]: SMTP entering state: 18 -1215547552[b7511060]: SMTP entering state: 21 -1215547552[b7511060]: SMTP entering state: 15 -1215547552[b7511060]: SMTP Send: AUTH LOGIN -1215547552[b7511060]: SMTP connection dropped after 147 total bytes read So I took a look at the Password manager and find that the old password is still listed. Only deleating all the pw's associated with the account & closing/restarting SM fixed the problem. _______________________________________________ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
