On Sun, Sep 22, 2019 at 03:07:54PM +0200, benoit wrote:
> I change my cert_file parameter to fullchain.pem. So now I don't have
> error for server:
>
> Sep 22 15:00:25 jolly postfix/smtpd[15774]: connect from unknown[192.168.5.1]
> Sep 22 15:00:25 jolly postfix/smtpd[15774]: Anonymous TLS connection
> established from unknown[192.168.5.1]: TLSv1.2 with cipher
> ECDHE-RSA-CHACHA20-POLY1305 (256/256 bits)
Looks like the TLS handshake completes.
> Sep 22 15:00:33 jolly postfix/smtpd[15774]: lost connection after EHLO
> from unknown[192.168.5.1]
> Sep 22 15:00:33 jolly postfix/smtpd[15774]: disconnect from
> unknown[192.168.5.1] ehlo=2 starttls=1 commands=3
As also evidenced by the second (post-TLS) "EHLO".
> But my client can't connect . the client is my android phone
But the client gives up immediately after seeing the server's EHLO
response. Probably, it does not like the SASL AUTH mechanisms
offered, or AUTH is not offered at all. Perhaps the phone is
connecting to port 25.
See my reply
http://postfix.1071664.n5.nabble.com/Question-getting-Mail-app-working-with-PostFix-SMTP-td102381.html#a102823
to:
http://postfix.1071664.n5.nabble.com/Question-getting-Mail-app-working-with-PostFix-SMTP-tp102381p102822.html
and if you're still unable to resolve the problem after ensuring
that the client is using port 587 (submission), in your next post
include:
1. "postconf -nf" output (as-is, no rewrapping of lines)
2. "postconf -Mf" output (as-is, no rewrapping of lines)
3. Relevant enties from the log file.
--
Viktor.
