Re: [exim] QT=... DT=... vs timestamp

On Wed, 05 Oct 2016 10:18:20 -0400 Chris Siebenmann wrote: [ ... ] > Is it possible that cron starts submitting the message the moment the > cron job starts (perhaps because it produces some initial output) and > only finishes submitting it when the cron job finishes some time later? Yes, it

Re: [exim] QT=... DT=... vs timestamp

> On Wed, 5 Oct 2016 10:45:49 +0100 James Gibbard wrote: > > Broken? Nope. QT includes the time spent submitting the message to > > Exim, which ENDS with the first logline, at the start of DT. Look at > > syslog and determine the time that the cron was supposed to start and > > I'd bet it was 4AM.

Re: [exim] QT=... DT=... vs timestamp

On 05/10/16 14:31, Frank Elsner wrote: >> I bet you have a cron job kicking off at 4am that takes that long to >> run. > > Yeah! That's it! Thanks for pointing out my mental deficit. There's an open wishlist entry for a time-to-recieve log element you may want to add your weight to:

Re: [exim] QT=... DT=... vs timestamp

On Wed, 5 Oct 2016 13:08:45 +0100 Jeremy Harris wrote: > On 05/10/16 12:52, Frank Elsner wrote: > > On Wed, 5 Oct 2016 10:45:49 +0100 James Gibbard wrote: > >> Broken? Nope. QT includes the time spent submitting the message to > >> Exim, which ENDS with the first logline, at the start of DT. Look

Re: [exim] QT=... DT=... vs timestamp

On Wed, Oct 05, 2016 at 10:24:09AM +0200, Frank Elsner wrote: > Hello, > > the QT= computation must be broken :-( > > 2016-10-04 04:29:46 1brF1V-0005H0-Gs <= redac...@moltke28.b.shuttle.de U=root > P=local S=600232 T="Cron /usr/local/sbin/Mirror" from >

Re: [exim] QT=... DT=... vs timestamp

On 05/10/16 12:52, Frank Elsner wrote: > On Wed, 5 Oct 2016 10:45:49 +0100 James Gibbard wrote: >> Broken? Nope. QT includes the time spent submitting the message to >> Exim, which ENDS with the first logline, at the start of DT. Look at >> syslog and determine the time that the cron was supposed

Re: [exim] QT=... DT=... vs timestamp

On Wed, 5 Oct 2016 10:45:49 +0100 James Gibbard wrote: > Broken? Nope. QT includes the time spent submitting the message to > Exim, which ENDS with the first logline, at the start of DT. Look at > syslog and determine the time that the cron was supposed to start and > I'd bet it was 4AM. > > Thus

Re: [exim] QT=... DT=... vs timestamp

On Wed, Oct 5, 2016 at 11:52 AM, James Gibbard wrote: > http://www.exim.org/exim-html-current/doc/html/spec_html/ch-log_files.html > > > "queue_time: The amount of time the message has been in the queue on > the local host is logged as QT= on delivery (=>) lines, for >

Re: [exim] QT=... DT=... vs timestamp

http://www.exim.org/exim-html-current/doc/html/spec_html/ch-log_files.html "queue_time: The amount of time the message has been in the queue on the local host is logged as QT= on delivery (=>) lines, for example, QT=3m45s. The clock starts when Exim starts to receive the message, so it includes

Re: [exim] QT=... DT=... vs timestamp

Broken? Nope. QT includes the time spent submitting the message to Exim, which ENDS with the first logline, at the start of DT. Look at syslog and determine the time that the cron was supposed to start and I'd bet it was 4AM. Thus you probably have some issue on your mailserver that means

Re: [exim] QT=... DT=... vs timestamp

On Wed, 5 Oct 2016 10:24:09 +0200 Frank Elsner wrote: > Hello, > > the QT= computation must be broken :-( > > 2016-10-04 04:29:46 1brF1V-0005H0-Gs <= redac...@moltke28.b.shuttle.de U=root > P=local S=600232 T="Cron /usr/local/sbin/Mirror" from >

[exim] QT=... DT=... vs timestamp

Hello, the QT= computation must be broken :-( 2016-10-04 04:29:46 1brF1V-0005H0-Gs <= redac...@moltke28.b.shuttle.de U=root P=local S=600232 T="Cron /usr/local/sbin/Mirror" from for root 2016-10-04 04:29:56 1brF1V-0005H0-Gs =>