On Dec 1, 2006, at 12:35 AM, Göran Krampe wrote:
I think the SMTPClient calls login itself - don't have the image handy - check references to SMTPClient in the Q2* code and see if we don't give it a user/password when we instantiate it.
The basefixes to the image were necessary to get it working though - apparently noone uses SMTP auth but us. :)
Well, when I did senders of #login, SMTPClient wasn't in the list. I added it to Q2MailSender right after the #openOnHost:port: send. Also, the "new" standard port for outgoing mail is 587, so that should probably be another ini file entry; right now it's hard coded to 25.
:-)
regards, Göran
On Dec 1, 2006, at 9:50 AM, Brian Brown wrote:
On Dec 1, 2006, at 12:35 AM, Göran Krampe wrote:
I think the SMTPClient calls login itself - don't have the image handy - check references to SMTPClient in the Q2* code and see if we don't give it a user/password when we instantiate it.
The basefixes to the image were necessary to get it working though - apparently noone uses SMTP auth but us. :)
Well, when I did senders of #login, SMTPClient wasn't in the list. I added it to Q2MailSender right after the #openOnHost:port: send. Also, the "new" standard port for outgoing mail is 587, so that should probably be another ini file entry; right now it's hard coded to 25.
:-)
However; it is called from #ensureConnection on ProtocolClient, but until I added it in Q2MailSender, I just kept getting 550 Not Authorized from the server....
Brian
setools@lists.squeakfoundation.org
-
Brian Brown