Hi,
I am not yet completely happy with the logging behavior of the lmtp. It
logs informative messages like 'lmtp: Info: Connection closed' or 'lmtp:
Info: Disconnected for inactivity'. Hm, which server was connected to
the lmtp? Who was disconnected for inactivity?
I think it would be useful if the lmtp would also log new connections.
For example:
a) TCP connections:
lmtp: Info: Connection: rip=10.1.2.3, lip=10.1.2.5, cid=1255555555.12345
b) Socket connections:
lmtp: Info: Connection: via socket, cid=1255555777.10452
rip:
There may be multiple SMTP servers in front the IMAP server(s)
lip:
The lmpt may listen to more than one address
cid:
The 'connection ID', consists of the current unix time and the pid
of the lmtp process. (Or some other values in some other format)
The cid should be used in the 'saved' messages. So the delivering MTA
would see something like '250 2.0.0 OK: 1255555555.12345 Saved',
instead of a message like '250 2.0.0 <[email protected]> Saved'.
The lmtp should also write the cid to the log. For example:
'lmtp(jdoe): Info: msgid=123, cid=1255555555.12345: saved mail to INBOX'
(or discarded because of a matching sieve rule).
With this connection ID it would be possible to trace the route which
the e-mail has taken.
Regards,
Pascal
--
The trapper recommends today: [email protected]
