james-server-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Peter M. Goldstein" <peter_m_goldst...@yahoo.com>
Subject RE: Easy protocol logging
Date Tue, 03 Dec 2002 18:22:53 GMT


> I thought I read something on this list awhile ago where someone had
> it
> dead-easy to log all of the wire comms on a socket. This would be very
> helpful to see what was going on, now that I've started connecting
> clients to James.
> I'm thinking of a SocketManager/ConnectionManager implementation that
> returns
> a logging socket, so that the logging code doesn't need to be in the
> actual
> protocol server at all.
> Has anyone tried something like this? Or does someone feel like coding
> up
> while I sleep?  :)

Uh, this is not a particularly good idea.

It would introduce regressions - most notably reintroducing the security
holes where passwords were recorded in log files.  Currently the logging
infrastructures for each protocol server are designed to record in the
log all command/replies with the exception of password data and message

Implementing the same logging method as the other protocol services on
IMAP is relatively trivial.


To unsubscribe, e-mail:   <mailto:james-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:james-dev-help@jakarta.apache.org>

View raw message