Re: SM 2.0 mailnews Password issues
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 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. Sounds like time to comment in Bugzilla. (Don't forget to check in case a bug has been already been filed under Thunderbird or MailNews Core for this.) -- Warning: May contain traces of nuts. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: SM 2.0 mailnews Password issues
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
Re: SM 2.0 mailnews Password issues
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 https://lists.mozilla.org/listinfo/support-seamonkey
Re: SM 2.0 mailnews Password issues
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. [CUT] 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. Hi, same problem here and I have my own mail server (EIMS 3.3.9). Today I typed a wrong pw, SM 2.0 showed an alert to enter a new pw / retry / cancel. Well, I did type the correct pw, but still the wrong one was sent to my mail server (I saw it in the log). Then I clicked on retry and the good one was sent. Gabriele ps: I'm setting f/u to mozilla.dev.apps.seamonkey only. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
SM 2.0 mailnews Password issues
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 called the tech support. After over nearly 2 hours messing about, I finally got 2nd tier ATT tech support (USA) they reset the password. Tested; I could log in via webmail, I could send receive via SM 2.0. All seemed OK. Then later this evening I noticed that I could receive from this account, but when I tried to send a msg I got: 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. Again, all other email accounts worked just fine (this email addy is a sub account of my main account the other 5 sub accounts were working). I got 2nd tier support on the line again tested with Windows, tested with Opera, tested with another linux machine w/same SM 2.0, tested with 1.1.18; all no go. It wasn't until the 2nd tier got another level to reset the account again that it started working. But... it was only working on a SM 1.1.18 and still not on 2.0. What I found out is that, for whatever reason, the SM 2.0's (on multiple machines) would not work (for this account) *until* I deleted all of the passwords, including the smtp password, and then restart. After that SM 2.0 on all the machines started working again (of course after re-entering the passwords at the revieve send prompts). During the tests I had both 1.1.18 and 2.0 and 2.0pre up on dual machines, including 2.0 on a Win2K virtual machine. It was *only* after I deleted the passwords following the email reset on the isp side that 2.0 would allow me to send again. 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. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: SM 2.0 mailnews Password issues
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 ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: SM 2.0 mailnews Password issues
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. https://wiki.mozilla.org/MailNews:Logging Hartmut Excellent! Thanks for that I'll set one up as I reckon that the ATT/Yahoo radius servers will probably have issues again. Gary ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: SM 2.0 mailnews Password issues
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 would be helpful. https://wiki.mozilla.org/MailNews:Logging Hartmut Excellent! Thanks for that I'll set one up as I reckon that the ATT/Yahoo radius servers will probably have issues again. Gary Works. What I did was modify the seamonkey shell script with: #uncomment for debugging #set -x # keep a log # For bash shell (the default shell on most GNU/Linux systems): export NSPR_LOG_MODULES=smtp:5 export NSPR_LOG_FILE=/home/myusername/SeaMonkey2pre/seamonkey/smtp.log #export NSPR_LOG_MODULES=pop3:5 #export NSPR_LOG_FILE=/home/myusername/SeaMonkey2pre/seamonkey/pop3.log 1. I set the path for where I run SM from in my home folder so that I can easily copy/delete etc rather than having to mess with the /tmp root folder. 2. I added commented out the pop3 variables as those logs get rather large, but can easily uncomment if having pop3 issues. Thanks again Harmut; I'll be prepared next time :-) ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
