Hi,
Adrian Zaugg via Exim-users (Fr 01 Jun 2018 02:05:04
CEST):
>
> I try to set tls_certificate and tls_privatekey in remote smtp transport
> in order to instruct exim to present a client certificate on a
> connection made to another server. I get an error saying:
>
> 2018-06-01 00:22:34
Hi Marius
On 01.06.18 15:16, Cyborg via Exim-users wrote:
> Access rights.
This was my first guess and I checked it, as I wrote:
I tried as the user Debian-exim under which Exim runs to cat both files,
that worked. And Exim uses the same files as a server, so it can read them.
Does the code for
Hi Renaud
You can use the service https://www.checktls.com/TestSender
It tells you whether a certificate was presented or not. You need to
send direct to their mx not through your smarthost though.
Regards, Adrian.
On 29.05.18 11:10, Renaud Mertens via Exim-users wrote:
> I'm trying to
Hi Martin
On 01.06.18 04:41, Martin McCormick via Exim-users wrote:
> The last part of this long message is the log of the
> delivery attempt. As you see, I do now log in to the smarthost
> and the only reason for the failure is that the sender name gets
> changed.
>
> The ISP
Adrian Zaugg via Exim-users writes:
> Hi Martin
>
> On Debian you set the outgoing email address map in the file:
>
> /etc/email-addresses
>
> You can add a line like:
> martin: marti...@suddenlink.net
>
> The exim configuration for a simple use case can be made by
>
>
Martin McCormick via Exim-users (Fr 01 Jun 2018 18:54:05
CEST):
>
> /var/log/exim4/mainlog has 166 of it's 305 lines occupied with:
>
> Warning: No server certificate defined; will use a selfsigned one.
> Suggested action: either install a certificate or change tls_advertise_hosts
> option
Hi,
Martin McCormick via Exim-users (Sa 02 Jun 2018 18:33:41
CEST):
>
> I even wrote a little shell script that one runs
> under sudo
>
> #!/bin/sh
> msg=`mailq |awk '{print $3}'`
> if ! test -z $msg;then
> exim4 -d -M $msg
> fi
>
> That's because there are two other lines besides the
