Re: [exim] option -MCd

2020-07-01 Thread Jeremy Harris via Exim-users
On 01/07/2020 15:27, Marc Haber via Exim-users wrote: >> An experiment of a short suspend, and waiting for longer than that, >> would be of interest - assuming the issue can be created on demand. > > You mean like > > - reboot (start exim daemon here) > - suspend for like a minute > -

Re: [exim] option -MCd

2020-07-01 Thread Marc Haber via Exim-users
On Tue, 30 Jun 2020 20:17:55 +0100, Jeremy Harris via Exim-users wrote: >On 30/06/2020 16:01, Marc Haber via Exim-users wrote: >> Is this the possible cause of the issue showing up on at least three >> Debian systems since we upgraded to exim 4.94? > >It does sound plausible that it is related. >

Re: [exim] option -MCd

2020-06-30 Thread Jeremy Harris via Exim-users
On 30/06/2020 16:01, Marc Haber via Exim-users wrote: > A contributor on the bug report says: > |I am pretty sure that the problem is caused by the commit > 6906c131d1d07d07831f8fbabae6290a3cba6ca3 > |(Use a monotonic clock, if available, for ID generation).

Re: [exim] option -MCd

2020-06-30 Thread Jeremy Harris via Exim-users
On 30/06/2020 16:01, Marc Haber via Exim-users wrote: > Is this the possible cause of the issue showing up on at least three > Debian systems since we upgraded to exim 4.94? It does sound plausible that it is related. How was the message given exim - command-line or smtp? Was it first given to

Re: [exim] option -MCd

2020-06-30 Thread Marc Haber via Exim-users
On Fri, 19 Jun 2020 10:04:09 +0100, Jeremy Harris via Exim-users wrote: >Exim uses the system time as part of generating unique identifiers. >To do that it waits, if needed, for the granularity of the time >it is using for that purpose. That should be something in the >millisecond range. To end

Re: [exim] option -MCd

2020-06-19 Thread Frank Elsner via Exim-users
On Fri, 19 Jun 2020 10:04:09 +0100 Jeremy Harris via Exim-users wrote: > On 19/06/2020 09:48, Frank Elsner via Exim-users wrote: > > Ok, it is not a repro of the initial case. > > But it is not nomal as it delays the massege. > > > > But can you explain this please > > > > 22937 tick

Re: [exim] option -MCd

2020-06-19 Thread Jeremy Harris via Exim-users
On 19/06/2020 09:48, Frank Elsner via Exim-users wrote: > Ok, it is not a repro of the initial case. > But it is not nomal as it delays the massege. > > But can you explain this please > > 22937 tick check: 1592491915.156500 1592491548.933500 > 22937 waiting 366.223500 sec Exim

Re: [exim] option -MCd

2020-06-19 Thread Frank Elsner via Exim-users
On Thu, 18 Jun 2020 17:02:40 +0100 Jeremy Harris via Exim-users wrote: > On 18/06/2020 15:58, Frank Elsner via Exim-users wrote: > > I could reproduce the problem with exim-4.94 which occures after the system > > came up after suspend: > > > > 22937 Process 22937 is handling incoming connection

Re: [exim] option -MCd

2020-06-18 Thread Jeremy Harris via Exim-users
On 18/06/2020 15:58, Frank Elsner via Exim-users wrote: > I could reproduce the problem with exim-4.94 which occures after the system > came up after suspend: > > 22937 Process 22937 is handling incoming connection from [127.0.0.1] [...] There's no exec there at all. In what way is it a repro?

Re: [exim] option -MCd

2020-06-18 Thread Frank Elsner via Exim-users
On Wed, 17 Jun 2020 22:51:41 +0200 Frank Elsner via Exim-users wrote: > On Wed, 17 Jun 2020 11:08:58 +0100 Jeremy Harris via Exim-users wrote: > > On 17/06/2020 10:56, Frank Elsner via Exim-users wrote: > > >>> 264381 exec /usr/exim/bin/exim -d=0xf7795cfd -MCd > > >>> daemon-accept-delivery -Mc

Re: [exim] option -MCd

2020-06-17 Thread Frank Elsner via Exim-users
On Wed, 17 Jun 2020 11:08:58 +0100 Jeremy Harris via Exim-users wrote: > On 17/06/2020 10:56, Frank Elsner via Exim-users wrote: > >>> 264381 exec /usr/exim/bin/exim -d=0xf7795cfd -MCd daemon-accept-delivery > >>> -Mc 1jiZUo-0016mC-CU > > >> Is there no other mention of process 264381 (or

Re: [exim] option -MCd

2020-06-17 Thread Jeremy Harris via Exim-users
On 17/06/2020 10:56, Frank Elsner via Exim-users wrote: >>> 264381 exec /usr/exim/bin/exim -d=0xf7795cfd -MCd daemon-accept-delivery >>> -Mc 1jiZUo-0016mC-CU >> Is there no other mention of process 264381 (or whatever the process >> doing the exec is)? > > Coming back to the still unsolved

Re: [exim] option -MCd

2020-06-17 Thread Frank Elsner via Exim-users
On Tue, 9 Jun 2020 09:55:31 +0100 Jeremy Harris via Exim-users wrote: > On 09/06/2020 09:30, Frank Elsner via Exim-users wrote: > > my exim-4.94 has problems. Message coming in via TCP doesn't get delivered. > > The debug output is > > > > 264380 SMTP>> 221 siffux.fritz.box closing connection > >

Re: [exim] option -MCd

2020-06-09 Thread Jeremy Harris via Exim-users
On 09/06/2020 09:30, Frank Elsner via Exim-users wrote: > my exim-4.94 has problems. Message coming in via TCP doesn't get delivered. > The debug output is > > 264380 SMTP>> 221 siffux.fritz.box closing connection > 264380 LOG: smtp_connection MAIN > 264380 SMTP connection from

[exim] option -MCd

2020-06-09 Thread Frank Elsner via Exim-users
Hello, my exim-4.94 has problems. Message coming in via TCP doesn't get delivered. The debug output is 264380 SMTP>> 221 siffux.fritz.box closing connection 264380 LOG: smtp_connection MAIN 264380 SMTP connection from (siffux.fritz.box) [::1] closed by QUIT 264381 exec /usr/exim/bin/exim