I seem to remember that there is a bug in the current SecureMailHost
implementation where it will always try the secure version, and only
attempt the non-encrypted communication if it can't any secure server. So
if it finds that the server says that it accepts encrypted logins, it will
never attempt the unencrypted version, even if the encrypted version fails
(as long as it exists).
My memory on this is very hazy, though — but might be something to look
into. :)
— Alexander
On Wed, 06 Jun 2007 11:43:22 -0700, Mike Inglis
<[EMAIL PROTECTED]> wrote:
I am the sysadmin.
The authentication on that email server is set to "Login" and never uses
SSL
or port 443.
As I took my time (again) and considered every possibility, I changed the
authentication method on the email server to CRAM-MD5 -
challenge-response.
And it worked.
Then I toggled the TLS on/off in the ZMI Mailhost pref and it works in
both
cases.
Hmm...
Mike.
Reinout van Rees wrote:
Mike Inglis wrote:
Jun 6 00:06:33 moderndesktop postfix/smtpd[5162]: connect from
unknown[206.248.146.233]
Jun 6 00:06:35 moderndesktop postfix/smtpd[5162]: lost connection
after
AUTH from unknown[206.248.146.233]
Jun 6 00:06:35 moderndesktop postfix/smtpd[5162]: disconnect from
unknown[206.248.146.233]
I learned that UGFzc3dvcmQ6 is Base64 for AUTH (?). Not sure what I can
do
with that bit of info :-)
Is Python doing the email? What else would you try?
AUTH... Perhaps the mailserver only accepts secure/encrypted
connections (the smtp equivalent of https) and wants you to authenticate
or so? Can you ask your sysadmin?
Reinout
--
Reinout van Rees - Programmer at http://zestsoftware.nl/
http://vanrees.org/weblog/
mailto:[EMAIL PROTECTED]
"White space, the opposite of black hole?" -- Joris slob
--
Alexander Limi · http://limi.net
_______________________________________________
Setup mailing list
[email protected]
http://lists.plone.org/mailman/listinfo/setup
