Displaying 5 results from an estimated 5 matches for "t2c82iib027383".
2015 Mar 13
2
Apparent bug in logwatch's reporting of number of email by sendmail
...nged to
make designations in this conversation more intuitive):
Mar 12 04:02:18 srchost sendmail[27151]: t2C82Bjr027151: from=root,
size=2485, class=0, nrcpts=1,
msgid=<201503120802.t2C82Bjr027151 at localhost.localdomain>,
relay=root at localhost
Mar 12 04:02:19 srchost sendmail[27383]: t2C82IiB027383:
from=<root at localhost.localdomain>, size=2756, class=0, nrcpts=1,
msgid=<201503120802.t2C82Bjr027151 at localhost.localdomain>, proto=ESMTP,
daemon=MTA, relay=srchost [127.0.0.1]
Mar 12 04:02:19 srchost sendmail[27151]: t2C82Bjr027151: to=recip at dest,
ctladdr=root (0/0), delay=...
2015 Mar 13
5
Apparent bug in logwatch's reporting of number of email by sendmail
...re intuitive):
>>
>> Mar 12 04:02:18 srchost sendmail[27151]: t2C82Bjr027151: from=root,
>> size=2485, class=0, nrcpts=1,
>> msgid=<201503120802.t2C82Bjr027151 at localhost.localdomain>,
>> relay=root at localhost
>> Mar 12 04:02:19 srchost sendmail[27383]: t2C82IiB027383:
>> from=<root at localhost.localdomain>, size=2756, class=0, nrcpts=1,
>> msgid=<201503120802.t2C82Bjr027151 at localhost.localdomain>,
>> proto=ESMTP, daemon=MTA, relay=srchost [127.0.0.1]
>> Mar 12 04:02:19 srchost sendmail[27151]: t2C82Bjr027151:
>> to=...
2015 Mar 13
0
Apparent bug in logwatch's reporting of number of email by sendmail
...t;
>>> Mar 12 04:02:18 srchost sendmail[27151]: t2C82Bjr027151: from=root,
>>> size=2485, class=0, nrcpts=1,
>>> msgid=<201503120802.t2C82Bjr027151 at localhost.localdomain>,
>>> relay=root at localhost
>>> Mar 12 04:02:19 srchost sendmail[27383]: t2C82IiB027383:
>>> from=<root at localhost.localdomain>, size=2756, class=0, nrcpts=1,
>>> msgid=<201503120802.t2C82Bjr027151 at localhost.localdomain>,
>>> proto=ESMTP, daemon=MTA, relay=srchost [127.0.0.1]
>>> Mar 12 04:02:19 srchost sendmail[27151]: t2C82Bjr0271...
2015 Mar 13
0
Apparent bug in logwatch's reporting of number of email by sendmail
...this conversation more intuitive):
>
> Mar 12 04:02:18 srchost sendmail[27151]: t2C82Bjr027151: from=root,
> size=2485, class=0, nrcpts=1,
> msgid=<201503120802.t2C82Bjr027151 at localhost.localdomain>,
> relay=root at localhost
> Mar 12 04:02:19 srchost sendmail[27383]: t2C82IiB027383:
> from=<root at localhost.localdomain>, size=2756, class=0, nrcpts=1,
> msgid=<201503120802.t2C82Bjr027151 at localhost.localdomain>,
> proto=ESMTP, daemon=MTA, relay=srchost [127.0.0.1]
> Mar 12 04:02:19 srchost sendmail[27151]: t2C82Bjr027151:
> to=recip at dest, c...
2015 Mar 16
0
Apparent bug in logwatch's reporting of number of email by sendmail
...getting that number wrong as well.
>
Based on the day of 'Mar 12', I agree with the bytes transferred.
Logwatch's sendmail component appears to be using the sendmail queue ID
(vs the message ID) as an identifier for a unique message. Using this
identifier, I too count 2 messages (t2C82IiB027383 and t2C82Bjr027151).
Looking at recipients, I also count two: recip at dest and <recip at dest.com>.
What criteria to use as a means of identifying a unique message is
certainly a choice. I can see how some would choose the MUA's message ID
instead. However, that may be more error pro...