Thanks again for your help. I found out that thunderbird, etc was
ignoring the SSL/TLS AUTH "requirement" and sending the data over the
TLS without authentication (since it was on the local network, it would
send successfully). The android was not as forgiving since it always was
on the remote
Yeah, I you're right. The auth login I was seen was for putting the sent
email into dovecot's sent folder, NOT for logging into the smtp server.
So SASL is needed for TLS, but not for plain text. I'll go back to the
drawing board with enabling SASL.
Sorry, been dealing with sendmail, haven't u
OK, perhaps I don't understand. I am not using saslauthd at all. It's
not even installed.
Why do other clients (e.g.: Thunderbird, Apple Mail) work and do an
authentication just fine over TLS (breaking RFC I guess because it's
still not advertised as per debug_peer logging)?
However, if I c
On 26 Jun 2016, at 17:17, E M Recio wrote:
> smtpd_sasl_auth_enable = no
That's your problem right there...
Bill,
Thanks for the feedback. I will update the configuration to use port
587, disabling SMTP AUTH on 25 completely, as soon as I get this working
at all. As per the debug documentation, attached is the skimmed down
output from the commands in the documentation.
Postconf -n and postconf -Mf
On 26 Jun 2016, at 15:55, E M Recio wrote:
So I have TLS and AUTH working just fine in almost every email client
that I use. I have confirmed that it's encrypted, and authenticating
correctly, so my settings are OK (for those two things used together).
The problem I am having is when enabling
So I have TLS and AUTH working just fine in almost every email client
that I use. I have confirmed that it's encrypted, and authenticating
correctly, so my settings are OK (for those two things used together).
The problem I am having is when enabling the following feature:
smtpd_tls_auth_only
