-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 1/30/2014 8:18 AM, Dennis Putnam wrote: > On 1/30/2014 9:10 AM, li...@rhsoft.net wrote: >> >> Am 30.01.2014 15:00, schrieb Dennis Putnam: >>> I changed the loglevel to 1. I am not sure where or what I >>> am supposed to see but the normal maillog contained nothing >>> different. >> lines like while connect to the destination >> >> Jan 27 19:16:17 mail postfix/smtp[14368]: Trusted TLS >> connection established to >> gmail-smtp-in.l.google.com[173.194.70.27]:25: TLSv1.2 with >> cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits) >> >> > I changed the level to 2. I am not seeing what you suggest but > there is one additional line initializing TLS engine. Here is > the output: >
... useless debug output deleted > > To repeat my previous question, is there no way to force a > login regardless of the EHLO responses? > No, there is no way to force a login if the server doesn't offer AUTH. Even if you did force it, it's highly unlikely the server would accept it, and it wouldn't be safe since you're not encrypting your connection -- no encryption is the root of the problem. Your TLS is screwed up. Show "postconf -n" output. -- Noel Jones -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (MingW32) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJS6mL7AAoJEJGRUHb5Oh6g8RkIAM8/lqnHhYtqKTCBTJ1XkVcu VIe9MAyE4aJaomLcyt0wlYfUDvyv2ZmGdFDZa2uzYXnmBlTxPECb02ONkxMkUjFL PzbeRaSk5Dr+kEN+26fH6WqpdOK1OggSPKsT1oao7FVkl0JwNPZ5+6iOurcOK2iF XkUq9YA86iZuO9jTpoDx1rWJ8e6H8GqHfvoqIe1ewYM+HB0bAlkULTPXVdlqJyy8 QNCrFABkkxHh2xrGWWKt1a6h4SMwwbWno7Gi04eHiQPTX3Po1c8aju7UPYV0H/vh 76tZMOi3snZzwVpguK7AJBmncub+YcaWt5EH9WhZKmTLukv42XhUqLIhbvnN6/Q= =cdKg -----END PGP SIGNATURE-----
