Log LMTP/MTA filters events.

Have a great idea for extending Zimbra? Share ideas, ask questions, contribute, and get feedback.
13331stalker
Advanced member
Advanced member
Posts: 131
Joined: Sat Sep 13, 2014 1:55 am

Log LMTP/MTA filters events.

Postby 13331stalker » Mon Feb 20, 2012 8:17 am

Hello Everybody,


When user has created a "Forward To Address" filter and created some rule. I just want to log such filters into database or somewhere if any email get hit by those kind of filters.
Please help me to find a solution.
Thanks.


3244vmahajan
Advanced member
Advanced member
Posts: 138
Joined: Sat Sep 13, 2014 1:00 am

Log LMTP/MTA filters events.

Postby 3244vmahajan » Mon Feb 20, 2012 11:33 pm

Currently an info message "Redirecting message to xxx@yyy.com" is logged in mailbox.log.
13331stalker
Advanced member
Advanced member
Posts: 131
Joined: Sat Sep 13, 2014 1:55 am

Log LMTP/MTA filters events.

Postby 13331stalker » Tue Feb 21, 2012 2:16 am

[quote user="3244vmahajan"]Currently an info message "Redirecting message to xxx@yyy.com" is logged in mailbox.log.[/QUOTE]
I know, but that is not sufficient because it's just says the message has been forwarded to . But doesn't provide any information like message ID etc.
Besides, it is require to parse the logs at some interval. And require to keep track of the the last time the program has checked the logs etc. etc. stuff. Is there any facility which notify me that the filter has been hit and for which account and where the email has been forwarded to?
3244vmahajan
Advanced member
Advanced member
Posts: 138
Joined: Sat Sep 13, 2014 1:00 am

Log LMTP/MTA filters events.

Postby 3244vmahajan » Tue Feb 21, 2012 3:34 am

Feel free to file an enhancement request for this.
13331stalker
Advanced member
Advanced member
Posts: 131
Joined: Sat Sep 13, 2014 1:55 am

Log LMTP/MTA filters events.

Postby 13331stalker » Tue Feb 21, 2012 4:05 am

Alright. Thanks.
10119metux
Advanced member
Advanced member
Posts: 75
Joined: Sat Sep 13, 2014 2:29 am

Log LMTP/MTA filters events.

Postby 10119metux » Wed Feb 29, 2012 5:54 pm

Meanwhile we've fixed this issue by using a special milter.
Our mail_history package consists of three parts:

* milter, running on the MTA nodes

* mailboxd extension

* zimlet

Return to “Developers”

Who is online

Users browsing this forum: No registered users and 4 guests