First, I would like to say that I appreciate Viktor's contributions here.
Comparisons with and information about how Postfix handles various issues
are, IMNSHO, highly relevant.
On Tue, Jul 30, 2024 at 2:38 PM Viktor Dukhovni via Exim-users <
exim-users@lists.exim.org> wrote:
>
>
> FWIW, my take
On 2024-07-30 Viktor Dukhovni via Exim-users wrote:
[...]
> I get the impressionexpect that most exim-users list readers find my
> occasional posts on TLS in SMTP more useful than not.
[...]
FWIW I do [find them useful].
cu Andreas
--
`What a good friend you are to him, Dr. Maturin. His other f
On 2024-07-30 Viktor Dukhovni via Exim-users wrote:
[...]
> I get the impressionexpect that most exim-users list readers find my
> occasional posts on TLS in SMTP more useful than not.
[...]
FWIW I do.
cu Andreas
--
`What a good friend you are to him, Dr. Maturin. His other friends are
so grate
On Tue, Jul 30, 2024 at 01:17:00PM +0100, Jeremy Harris via Exim-users wrote:
> On 30/07/2024 12:52, Andrew C Aitchison via Exim-users wrote:
> > *If* I extended the config to allow admins to set the OpenSSL option
> > SSL_OP_IGNORE_UNEXPECTED_EOF (and an equivalent gnutls option if I can
> > find
On 30/07/2024 12:52, Andrew C Aitchison via Exim-users wrote:
*If* I extended the config to allow admins to set the OpenSSL option
SSL_OP_IGNORE_UNEXPECTED_EOF (and an equivalent gnutls option if I can
find one) which ignores this detection, would you accept it into the
exim code base ?
Probabl
On Mon, Jul 29, 2024 at 09:44:17AM +0100, Bernard Quatermass via Exim-users
wrote:
> > Exim really should be updated to ignore OpenSSL's truncation
> > detection, I don't recall whether that even already happened and the
> > OP is running an older version?
>
> I rather think postfix is the codeb
On Mon, 29 Jul 2024, Bernard Quatermass via Exim-users wrote:
On 29/07/2024 03:18, Viktor Dukhovni via Exim-users wrote:
On Sun, Jul 28, 2024 at 05:56:33PM +0100, Jeremy Harris via Exim-users
wrote:
BUT in the log, I get the following message:
H=gmail-smtp-in.l.google.com [142.251.16.2
On 29/07/2024 03:18, Viktor Dukhovni via Exim-users wrote:
On Sun, Jul 28, 2024 at 05:56:33PM +0100, Jeremy Harris via Exim-users wrote:
BUT in the log, I get the following message:
H=gmail-smtp-in.l.google.com [142.251.16.26] TLS error on
connection (recv): The TLS connection was no
On Mon, Jul 29, 2024 at 10:26 AM Francois Sauterey via Exim-users <
exim-users@lists.exim.org> wrote:
> Le 28/07/2024 à 18:56, Jeremy Harris via Exim-users a écrit :
> > On 28/07/2024 17:31, Francois Sauterey via Exim-users wrote:
> >> if I write to francois.saute...@gmail.com, the message arrives
On Mon, Jul 29, 2024 at 09:25:21AM +0200, Francois Sauterey via Exim-users
wrote:
> The response was :
>
> TLS Negotiation failed: FAILED_PRECONDITION: starttls error (71):
> 54099363978240:error:1410:SSL
> routines:OPENSSL_internal:SSLV3_ALERT_HANDSHAKE_FAILURE:third_party/openssl/boringss
Am 29.07.24 um 09:25 schrieb Francois Sauterey via Exim-users:
Well, my @gmail.com messages are coming in, so let's not talk about it
anymore, even if my logs are polluted.
But that doesn't solve my REAL problem: I can't receive messages from
@gmail.com!
So I'm reposting the message I got in
> From: Francois Sauterey
> the TLS part of my configuration:
> tls_require_ciphers = "SECURE256"
Did you try to comment out this line and restart Exim?
> From: Thomas Krichel
> It's a significant pollutant of logs.
My logs aren't polluted like that. I have in transport:
driver = smtp
ho
On 29/07/2024 08:25, Francois Sauterey via Exim-users wrote:
Well, my @gmail.com messages are coming in, so let's not talk about it anymore,
even if my logs are polluted.
But that doesn't solve my REAL problem: I can't receive messages from
@gmail.com!
Those two lines seem to be in conflict
Le 28/07/2024 à 18:56, Jeremy Harris via Exim-users a écrit :
On 28/07/2024 17:31, Francois Sauterey via Exim-users wrote:
if I write to francois.saute...@gmail.com, the message arrives,
So, that's good.
Well, my @gmail.com messages are coming in, so let's not talk about it
anymore, even if
Dňa 29. júla 2024 5:39:34 UTC používateľ Viktor Dukhovni via Exim-users
napísal:
>On Mon, Jul 29, 2024 at 03:24:35AM +, Thomas Krichel via Exim-users wrote:
>> root@tagol~# grep -c 'The TLS connection was non-properly terminated'
>> /var/log/exim4/mainlog.1
>> 645
>
>Perhaps, in that case,
On Mon, Jul 29, 2024 at 03:24:35AM +, Thomas Krichel via Exim-users wrote:
> > Exim really should be updated to ignore OpenSSL's truncation detection,
> > I don't recall whether that even already happened and the OP is running
> > an older version?
>
> root@tagol~# exim --version | head -1
>
Viktor Dukhovni via Exim-users writes
> Exim really should be updated to ignore OpenSSL's truncation detection,
> I don't recall whether that even already happened and the OP is running
> an older version?
In my case
root@tagol~# exim --version | head -1
Exim version 4.98 #2 built 11-Jul-202
On Sun, Jul 28, 2024 at 05:56:33PM +0100, Jeremy Harris via Exim-users wrote:
> > BUT in the log, I get the following message:
> >
> > H=gmail-smtp-in.l.google.com [142.251.16.26] TLS error on
> > connection (recv): The TLS connection was non-properly terminated.
>
> Google is violating stan
On 28/07/2024 17:31, Francois Sauterey via Exim-users wrote:
if I write to francois.saute...@gmail.com, the message arrives,
So, that's good.
BUT in the log, I get the following message:
H=gmail-smtp-in.l.google.com [142.251.16.26] TLS error on connection (recv):
The TLS connection was no
19 matches
Mail list logo