Hello Frank,

On 2013-03-30 22:31, Frank Ellebrecht wrote:

May I make two suggestion/feature requests? Here is the first one, I'll
leave the second one for an upcoming message.

Almost every action in the web UI is logged to the audit log. Would it
be possible and make sense to add another log for basic piler actions,
for instance generate entries when an email is archived, a message is
rejected because of the Spam/Virus filter settings, a message is purged
because of a retention rule and so on?

well, all these actions are logged to the maillog file.

Probably it's already possible to get this information from the MySQL
database, but access from the UI would be nice. From my point of view
such a log should contain
  - the date the log entry was created,
  - message details (from, to, subject),
  - the kind of action taken (archived, deleted, rejected, purged,
recognized as spam, virus infected, ...)
- some additional information (archiving rule no. XXX triggered, Spam
probability = 99 per cent, ...).

The reason I ask is that I am obliged by German law to archive all mails
that are possibly related to my business. If I decide to not archive a
message, I should be able to explain the reason and that it wasn't
related to my business and thus not worth archiving.

I see your point.

At the moment, when for instance ClamAV rejects a message or I have a
(no) archiving rule for Spam, it's only displayed on the status monitor
page. There is no way (at least from the web UI) to find out which
message wasn't archived and why.

What do you think? Would such a log be useful?

Possible. The archived messages already searchable in the gui for the auditor user(s). However creating a separate table for every incoming email would basically duplicate the metadata table, so you can expect another huge table.

How long would you keep this data? Which do you prefer: inserting the corresponding records on the fly to the database right after processing, or post processing of the maillog file via a perl/php/... script? Is it enough to records these data for emails received by the piler daemon or you want them for imported
emails too?


Janos

Reply via email to