l

Let's close this until it fails again, at least now failures should be greatly reduced as incremental_vacuum does not happen on read connection immediately after account creation.

> Why is postfix only emitting a ticket every second time an issue? Because session resumption does not work every second time.

In Postfix 3.8.6 file `src/tls/tls_server.c` there is this code: ``` ticketable = (*var_tls_tkt_cipher && scache_timeout > 0 && !(off & SSL_OP_NO_TICKET)); ... if (ticketable) { #if OPENSSL_VERSION_PREREQ(3,0) SSL_CTX_set_tlsext_ticket_key_evp_cb(server_ctx, ticket_cb); #else...

The message has already been edited, when you read GH emails you only get the first version.

There is a test `test_cleartext_incoming_mailer_daemon` checking that incoming messages can be accepted. But we don't have an example of quota exceeded message and there are reports that they are not...

Legacy Python test `tests/test_1_online.py::test_resend_message` got broken by this. Resent message is not recognized as duplicate anymore because outer timestamp of just received message is compared to the timestamp of the...

This has now broken the test added in c14f45a8f5523c14c2b567c745dd5980387c5207

We will have to use something less suspicious than unix epoch, GMX is unhappy: https://github.com/chatmail/core/issues/6878#issuecomment-2923262681

I have updated this PR to not send 1970 as the date. Should be good enough for review/merging now.

So now the date looks like this `Date: Sun, 15 Jun 2025 15:06:40 +0000`. You convert it and get: ``` date -d 'Sun, 15 Jun 2025 15:06:40 +0000' +%s 1750000000...