On Wed, Oct 20, 2021 at 03:24:12PM -0400, fp145 wrote:
> I use evolution as my mail client on the laptop.
Are you using TLS? Either port 587 with STARTTLS, or port 465 with
"implicit TLS" (some MUAs confuse things by calling this "SSL", and
reserve "TLS" for "STARTTLS").
> Oct 20 21:16:57 libertyfp postfix/smtpd[175562]: connect from
> 87.sub-174-212-171.myvzw.com[174.212.171.87]
> Oct 20 21:16:59 libertyfp postfix/smtpd[175562]: F0DEF3FFFD:
> client=87.sub-174-212-171.myvzw.com[174.212.171.87], sasl_method=LOGIN,
> sasl_username=fp...@libertyfp.org
I don't see logging of a TLS session establishment there, and you really
should be encrypting sessions that transmit passwords.
> Oct 20 20:07:49 libertyfp postfix/smtpd[174025]: warning: hostname
> ip245.tervelnet.com does not resolve to address 87.246.7.245
> Oct 20 20:07:49 libertyfp postfix/smtpd[174025]: connect from
> unknown[87.246.7.245]
> Oct 20 20:07:51 libertyfp postfix/smtpd[174025]: warning:
> unknown[87.246.7.245]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Perhaps your Evolution client is doing reverse resolution on the server
IP address before deciding which password to send to the server in
question? [ That would be a really bad idea, use a better MUA if that's
the case. ]
The issue is surely on the client end, and the reason Exim succeeds may
have more to do with how the particular IP addresses resolve over the
VPN, than the software runnign on the server.
When the VPN is up find out what IP addresses both servers resolve to,
and what those IP addresses back to (PTR records).
You're probably searching for clues on the wrong side of the VPN.
Troubleshoot the client, not the server.
--
Viktor.
