Am 2024-12-25 20:39, schrieb Marc Haber via Exim-users:
Have you tried the init script from the old version with the new
daemon?
I don't see a reason why this shouldn't work.
No, the main priority for me was to have a working system again and
downgrading solved this.
--
## subscription con
Am 26.12.24 um 07:06 schrieb Andreas Metzler via Exim-users:
What seems to be missing here is the systemd side information (journal).
Yes, simply because there was nothing special. Just those lines:
Dec 23 08:56:49 node1.xx systemd[1]: Stopping exim4.service - exim Mail
Transport Agent...
[t
On 2024-12-23 Kai Bojens via Exim-users wrote:
> System:
> - Debian 12
> - Exim 4.98 - rebuild from Debian Backports with ARC enabled
> - MX'er for several domains, forwarding to a seperate Dovecot server
> Action:
> - systemctl restart exim4 / systemctl stop exim4
> Symptom:
> - Restarting o
On Mon, Dec 23, 2024 at 11:37:57AM +0100, Kai Bojens via Exim-users wrote:
> Am 23.12.24 um 11:17 schrieb Jeremy Harris via Exim-users:
>
> > I'd be tending to blame systemd, also. What has it started doing
> > differently?
>
> Debian 11 worked fine without any problems. The problems started wi
Am 23.12.24 um 16:47 schrieb Andrew C Aitchison via Exim-users:
After that are you prepared to replace the 4.96 binary with the
one from 4.98 to confirm that the binary is not at fault ?
Sure, but this will have to wait until next year.
smime.p7s
Description: Kryptografische S/MIME-Signatur
On Mon, 23 Dec 2024, Kai Bojens via Exim-users wrote:
I'll just downgrade everything tomorrow as this will definitely fix the
systemd unit issue.
After that are you prepared to replace the 4.96 binary with the
one from 4.98 to confirm that the binary is not at fault ?
--
Andrew C. Aitchison
Am 23.12.24 um 14:52 schrieb Jeremy Harris via Exim-users:
On 23/12/2024 13:40, Kai Bojens via Exim-users wrote:
2024-12-23 08:57:17 Mail arrives from xyz.outbound.protection.outlook.com and
is accepted
You have a log line for that?
2024-12-23 08:57:17 [2661217] 1tPdIn-000BAIr-2q0S <=
On 23/12/2024 13:40, Kai Bojens via Exim-users wrote:
2024-12-23 08:57:17 Mail arrives from xyz.outbound.protection.outlook.com and
is accepted
You have a log line for that?
--
Cheers,
Jeremy
--
## subscription configuration (requires account):
## https://lists.exim.org/mailman3/postoriu
Am 23.12.24 um 14:18 schrieb Jeremy Harris via Exim-users:
On 23/12/2024 12:41, Kai Bojens via Exim-users wrote:
There's no entry on the receiving server.
Then it was never received, and no mail was lost. So we're good on that front.
I may have chosen my words poorly; the mail is lost inde
On 23/12/2024 12:41, Kai Bojens via Exim-users wrote:
There's no entry on the receiving server.
Then it was never received, and no mail was lost. So we're good on that front.
--
Cheers,
Jeremy
--
## subscription configuration (requires account):
## https://lists.exim.org/mailman3/postoriu
Am 23.12.24 um 13:22 schrieb Jeremy Harris via Exim-users:
Are there any log entries for this message-id?
There's no entry on the receiving server.
Looking at the -H would be interesting. Do the headers imply it was a bounce?
No, it was a normal mail from A to B. Nothing out of the ordina
On 23/12/2024 11:47, Kai Bojens via Exim-users wrote:
that there might be a hanging connection.
A -J is a journal file written during delivery not
during reception. That argues against those files being directly
associated with the incoming connection seen with exiwhat - but could imply
that a
Am 23.12.24 um 11:57 schrieb Jeremy Harris via Exim-users:
Hmm. I have "qq.com" mentally flagged as a poor-quality communicant. It's
not unlikely that it's going unresponsive, and this exim process is waiting
on it. Presumably systemd is waiting on the entire process group, having
successfull
Ahoj,
Dňa Mon, 23 Dec 2024 12:17:03 +0100 Slavko via Exim-users
napísal:
> It includes various Protect*= and Private*= options. IMO you can
> override that unit file (systemd edit ...) and try to disable them to
> find what collides with your settings. From my unit file (as shown by
> systemd ca
Ahoj,
Dňa Mon, 23 Dec 2024 11:37:57 +0100 Kai Bojens via Exim-users
napísal:
> Am 23.12.24 um 11:17 schrieb Jeremy Harris via Exim-users:
>
> > I'd be tending to blame systemd, also. What has it started doing
> > differently?
>
> Debian 11 worked fine without any problems. The problems star
On 23/12/2024 10:37, Kai Bojens via Exim-users wrote:
It took two minutes to restart and exiwhat only showed this in the meantime (I
repeated
the exiwhat several times):
$: exiwhat
2700875 handling TLS incoming connection from xmbghk7.mail.qq.com
[43.163.128.54]
Hmm. I have "qq.com" mentall
Am 23.12.24 um 11:17 schrieb Jeremy Harris via Exim-users:
I'd be tending to blame systemd, also. What has it started doing differently?
Debian 11 worked fine without any problems. The problems started with Debian 12
and the backported version. It is obvious that the systemd files changed and
On 23/12/2024 09:29, Kai Bojens via Exim-users wrote:
Right now my money is on the new Debian systemd unit files and Exim.
I'd be tending to blame systemd, also. What has it started doing differently?
Can it be reverted?
The log lines smell like the effective permissions on the spool area ar
Am 23.12.24 um 10:14 schrieb Andrew C Aitchison via Exim-users:
Is dovecot running when exim shuts down ?
Dovecot is on a different server and is running without interruption.
Right now my money is on the new Debian systemd unit files and Exim.
smime.p7s
Description: Kryptografische S/MIME-Si
On Mon, 23 Dec 2024, Kai Bojens via Exim-users wrote:
System:
- Debian 12
- Exim 4.98 - rebuild from Debian Backports with ARC enabled
- MX'er for several domains, forwarding to a seperate Dovecot
server
Action:
- systemctl restart exim4 / systemctl stop exim4
Symptom:
- Restarting or sto
20 matches
Mail list logo
