Am 03.08.2011 12:32 schrieb Murray S. Kucherawy:
> I'm starting to plan the work that will go into v2.5.0.
Murray,
I suggest improved logging.
I run opendkim on separate boxes, not on the mta. Multiple MTAs access opendkim
via TCP/IP.
In this case the logging not only looks boring, but important information is now splitt
accross multiple maillogs on different hosts.
Aug 31 14:00:33 dkimbox opendkim[6992]: 63E282C4D: mail.ietf.org [2001:1890:123a::1:1e] not internal
Aug 31 14:00:33 dkimbox opendkim[6992]: 63E282C4D: not authenticated
Aug 31 14:00:38 dkimbox opendkim[6992]: 63E282C4D: DKIM verification successful
Aug 31 14:00:39 dkimbox opendkim[6992]: 63E282C4D: DKIM reputation: 0
Aug 31 16:00:24 dkimbox opendkim[6992]: 777602C4D: no MTA name match
Aug 31 16:00:24 dkimbox opendkim[6992]: 777602C4D: mail.ietf.org [2001:1890:123a::1:1e] not internal
Aug 31 16:00:24 dkimbox opendkim[6992]: 777602C4D: not authenticated
Aug 31 16:00:27 dkimbox opendkim[6992]: 777602C4D: DKIM verification successful
Aug 31 16:00:28 dkimbox opendkim[6992]: 777602C4D: DKIM reputation: 0
Aug 31 17:39:28 dkimbox opendkim[6992]: 4CB5F2C4D: no MTA name match
Aug 31 17:39:28 dkimbox opendkim[6992]: 4CB5F2C4D: mail.ietf.org [2001:1890:123a::1:1e] not internal
Aug 31 17:39:28 dkimbox opendkim[6992]: 4CB5F2C4D: not authenticated
Aug 31 17:39:33 dkimbox opendkim[6992]: 4CB5F2C4D: message has signatures from ietf.org, sonnection.nl
Aug 31 17:39:33 dkimbox opendkim[6992]: 4CB5F2C4D: s=ietf1 d=ietf.org SSL error:04077068:rsa routines:RSA_verify:bad signature
Aug 31 17:39:33 dkimbox opendkim[6992]: 4CB5F2C4D: key retrieval failed (s=ietf1, d=ietf.org): 'ietf1._domainkey.ietf.org' query timed out
Aug 31 18:00:59 dkimbox opendkim[6992]: BCE932C4D: no MTA name match
Aug 31 18:00:59 dkimbox opendkim[6992]: BCE932C4D: mail.ietf.org [2001:1890:123a::1:1e] not internal
Aug 31 18:00:59 dkimbox opendkim[6992]: BCE932C4D: not authenticated
Aug 31 18:00:59 dkimbox opendkim[6992]: BCE932C4D: DKIM verification successful
Aug 31 18:01:00 dkimbox opendkim[6992]: BCE932C4D: DKIM reputation: 0
Aug 31 18:51:23 dkimbox opendkim[6992]: 915682C4D: no MTA name match
Aug 31 18:51:23 dkimbox opendkim[6992]: 915682C4D: liszt.debian.org [82.195.75.100] not internal
Aug 31 18:51:23 dkimbox opendkim[6992]: 915682C4D: not authenticated
Aug 31 18:51:24 dkimbox opendkim[6992]: 915682C4D: no signature data
unanswered Questions:
- which MTA asked vor verifieng mails ?
- who was sender and receiver ?
- what was the milteraction ?
I like to see only one line per mail containing all informations.
Aug 31 19:00:01 dkimbox opendkim[1234]: MTA=mx01, Queue-ID=BC1A82B65, from=<$from>, to=<$to1,$to2,...$ton>, client=remotemta[192.0.2.25], internal=0, authenticated=0, dkim=<pass|fail|...>, dkim-rep=$score,action=pass|reject|discard, ...
Yes, the lines looks ugly but if the fields are arranged in a common way, the logs are easy parsable by scripts.
Maybe one line of logging could contain many if not all information, a statsline also contain. This would be easy to code,
becaus stats it already implemented and focussed on one line !?
Also it would make searching in the logs much easier.
Andreas
--
########################################################################
#
# Andreas Schulze
# https://andreasschulze.de
#
# GnuPG Key-ID: A7DBA67F, https://andreasschulze.de/sca.asc
# GnuPG Fingerprint: 14C1 39A8 CE6D 6BE0 28C6 5652 03B5 6793 A7DB A67F
#
# $Id: .signature,v 1.3 2007-12-27 21:13:36 sca Exp $
########################################################################
Received on Wed Aug 31 2011 - 17:37:29 PST