On 2021-10-13 Heiko Schlittermann wrote:
> Andreas Metzler via Exim-users (Di 12 Okt 2021 18:24:02
> CEST):
>> thank you, afaict MTA-STS is fine now. Could you also fix the TLS
>> certificate? The MX record points to hummus.exim.org but the
>> certificate is only for mx.exim.org without SAN
Laura Williamson via Exim-users (Mi 13 Okt 2021 12:31:36
CEST):
> just got this back
>
> The response was:
> The certificate is not valid according to the STS policy
What about caching? The relevant files look good for me, and at least
one MTA-STS validator is happy with exim.org
Andreas Metzler via Exim-users (Di 12 Okt 2021 18:24:02
CEST):
> Hello Heiko,
>
> thank you, afaict MTA-STS is fine now. Could you also fix the TLS
> certificate? The MX record points to hummus.exim.org but the
> certificate is only for mx.exim.org without SAN for hummus.
We generated a cert
On Sun, Oct 10, 2021 at 1:29 PM Jeremy Harris via Exim-users <
exim-users@exim.org> wrote:
> On 09/10/2021 23:25, Oliver Heesakkers via Exim-users wrote:
> > I've done some more testing and have been reliably able to reproduce the
> problem. The problem always occurs (in my test setup) when I
Hi
it happened on several servers all with less than 100mb emails (some as
small as 1mb or less) no high traffic, no swapping on disk so not a
running out of memory problem, exim -M msg-id replicates problem (tried
many times with messages in queue), moving back to 4.94.2 and problem
On Tue, Oct 12, 2021 at 12:09 PM Cyborg via Exim-users
wrote:
>
> This is a forward from:
>
> Laura Williamson
>
>
> Delivery incomplete
>
> There was a temporary problem while delivering your message to
> *exim-users@exim.org*. Gmail will retry for 47 more hours. You'll be
> notified if
just got this back
The response was:
The certificate is not valid according to the STS policy
Den 12/10/2021 kl. 17:24 skrev Andreas Metzler via Exim-users:
On 2021-10-12 Heiko Schlittermann via Exim-users wrote:
I'm working on it, it may be caused by the migration of the Exim main
site
