On Tue, 7 Jan 2025, Gandalf Corvotempesta via Exim-users wrote:
There is also a side issue: smtp auth is not used even after adding
the remote host (and also tried with IP and "*") and it's user/pass in
/etc/exim4/passwd.client
From `man exim4_passwd_client` on Ubuntu:
/etc/exim4/passwd.client
contains account and password data for SMTP authentication
when exim is authenticating as a client to some remote server.
The file should contain lines of the form
target.mail.server.example:login-user-name:password which will
cause exim to use login-user-name and password when sending
messages to a server with the canonical host name
** target.mail.server.example. Please note that this does not
** configure the mail server to send to (this is determined in
** Debconf), but only creates the correlation between host name and
authentication credentials to avoid exposing passwords to the
wrong host.
Did you use Debconf ?
Il giorno mar 7 gen 2025 alle ore 12:09 Gandalf Corvotempesta
<gandalf.corvotempe...@gmail.com> ha scritto:
Hi all.
I have an exim used as receiver (relaying to a dovecot LMTP) and as
smarthost client (for vacation messages and so on).
As receiver, SSL/TLS works as expected, with no issue at all
(certificated from google ca/letsencrypt)
As client, the smarthost server deny the email due to "A TLS fatal
alert has been received: Certificate is bad" but the certificate is
good, as i'm able to relay email to this server using TLS
I've set hosts_require_tls = my.smarthost.server forcing the use of
TLS, the smarthost is set as my.smarthost.server::587
Any clue on why this is happening?
--
Andrew C. Aitchison Kendal, UK
and...@aitchison.me.uk
--
## subscription configuration (requires account):
## https://lists.exim.org/mailman3/postorius/lists/exim-users.lists.exim.org/
## unsubscribe (doesn't require an account):
## exim-users-unsubscr...@lists.exim.org
## Exim details at http://www.exim.org/
## Please use the Wiki with this list - http://wiki.exim.org/
