[Dovecot] rawlog change suggestion
I find the separate .in and .out files rather difficult to work with. I think it would be more useful if the in/out traffic were interleaved with a prefix to indicate direction, and suffix to indicate continuation, as recordio (http://cr.yp.to/ucspi-tcp/recordio.html) does:
<a0002 LIST "" ""
- LIST (\Noselect) ";" "" a0002 OK List completed. <a0003 SELECT "INBOX"
- FLAGS (\Answered \Flagged \Deleted \Seen \Draft)
- OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft \*)] Flags + permitted.
- 18 EXISTS
- 0 RECENT
- OK [UNSEEN 18] First unseen.
- OK [UIDVALIDITY 1055795174] UIDs valid
- OK [UIDNEXT 6741] Predicted next UID a0003 OK [READ-WRITE] Select completed. <a0004 STATUS "incoming.foo" (RECENT)
- STATUS "incoming.foo" (RECENT 397) a0004 OK Status completed. <a0005 NOOP a0005 OK NOOP completed.
Comments?
-- Charlie
On Wednesday, Aug 20, 2003, at 23:47 Europe/Helsinki, Charlie Brady wrote:
I find the separate .in and .out files rather difficult to work with. I think it would be more useful if the in/out traffic were interleaved with a prefix to indicate direction, and suffix to indicate continuation, as recordio (http://cr.yp.to/ucspi-tcp/recordio.html) does:
Depends on usage. I've wanted both.
Comments?
Thanks for reminding that rawlog functionality really doesn't belong to Dovecot. Rawlogging should be a separate binary which is executed by modifying mail_executable setting in config file. Something like:
protocol imap { mail_executable = /usr/local/bin/rawlog /usr/local/libexec/dovecot/imap }
What I'm not sure about is if I should distribute rawlog binary with Dovecot or not :)
On Thu, 21 Aug 2003, Timo Sirainen wrote:
On Wednesday, Aug 20, 2003, at 23:47 Europe/Helsinki, Charlie Brady wrote:
I find the separate .in and .out files rather difficult to work with. I think it would be more useful if the in/out traffic were interleaved with a prefix to indicate direction, and suffix to indicate continuation, as recordio (http://cr.yp.to/ucspi-tcp/recordio.html) does:
Depends on usage. I've wanted both.
You can easily generate the separate logs from a combined logs, but it is a much more difficult problem to combine the two logs to one (and I think you can only do it approximately, and then only if you assume that both client and server implement IMAP correctly).
Comments?
Thanks for reminding that rawlog functionality really doesn't belong to Dovecot. Rawlogging should be a separate binary which is executed by modifying mail_executable setting in config file. Something like:
It suits me to have it built in and available without any sysadmin change, as it makes it easier to collect logs from unsophisticated users/admins.
-- Charlie
participants (2)
-
Charlie Brady
-
Timo Sirainen