On Wed, 20 Oct 1999 [EMAIL PROTECTED] wrote:
> Unfortunately, I disagree. We have 3 options here:
> - Leave _all_ message contents unspecified
> - Specify _some_ message contents
> - Specify _all_ message contents
Although it would be impossible to specify everything, we could allow a
machine-readable string to be sent together with the log message. The
format of the string depends on facility and version number. For example:
19991021 122030 9 1 "25344 1 HELO localhost" "smtpd[25344]: < HELO
localhost"
19991021 122030 9 1 "25344 2 200 G'day" "smtpd[25344]: > 200 G'day"
19991021 122030 8 1 "25344 3 1 localhost" "smtpd[25344]: Remote identified
itself as 'localhost'"
[...]
Would be parseable into human readable logs:
mail.debug:
21-Oct-1999 12:20:30 smtpd[25344]: < HELO localhost
21-Oct-1999 12:20:30 smtpd[25344]: > 200 G'day
mail.info:
21-Oct-1999 12:20:30 smtpd[25344]: Remote identified itself as 'localhost'
And, additionally, you could save the machine-readable parts and, for
example, put the session back together with a tool that understands that
in version 1 of the "mail" facility's log message format
- class 1 means received data
- class 2 means sent data
- class 3 means e.g. internal state changes, where
- code 1 means that the peer has identified itself
etc.
Additionally, if you have a park of mail servers, some sort of "plugin"
could watch out for problems and report them to the sysop. This would
require formats to be defined for every facility, doing so is "beyond the
scope of this document".
Simon
PGP public key available from ftp://phobos.fs.tum.de/pub/pgp/geier.asc
Fingerprint: 10 62 F6 F5 C0 5D 9E D8 47 05 1B 8A 22 E5 4E C1
