Closed chibenwa closed 9 months ago
Log level: INFO
the list below is optional?
remoteIp
userAgent
protocol
we can't get this info in some classes
protocol can alsways be specified even if it's slightly distorded -> eg protocol=mailetcontainer
userAgent yes we can't always. Let's keep it best effort.
remoteIp -> best effet.
Quan concern: user action privacy issue (via logs)? -> Should we have a configuration to enable/disable this log?
user action privacy issue (via logs)?
Audit trail is easy to turn off if unwanted via logback.xml...
LMTP email sent including mimeMessageId, MailId, sender, recipients
If I do not understand wrongly, LMTP email sending shares the SendMailHandler
hook with SMTP.
=> Handled within SMTP message spooled including mailId and mimeMessageId, sender, recipients
.
Maybe need the protocol to be configurable?
If I do not understand wrongly, LMTP email sending shares the SendMailHandler hook with SMTP.
Hmm, likely I was wrong.
LMTP seems not to use a mail queue to send mail and LMTPServer actually does not include SendMailHandler
but uses MailboxDeliverToRecipientHandler
to directly deliver messages to local recipients.
JMAP forward/set including username and forward list
TODO on the TMail side: https://github.com/linagora/tmail-backend/issues/833
Step 1: Audit trail implementation
In james-core add a
AuditTrail
class allowing to log critical user actions accross the application.Usage:
Use SLF4J logger to back this.
Step 2: Use the audit trail where needed