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.
Log LMTP/MTA filters events.
-
- Advanced member
- Posts: 131
- Joined: Sat Sep 13, 2014 1:55 am
-
- Advanced member
- Posts: 138
- Joined: Sat Sep 13, 2014 1:00 am
Log LMTP/MTA filters events.
Currently an info message "Redirecting message to xxx@yyy.com" is logged in mailbox.log.
-
- Advanced member
- Posts: 131
- Joined: Sat Sep 13, 2014 1:55 am
Log LMTP/MTA filters events.
[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?
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?
-
- Advanced member
- Posts: 138
- Joined: Sat Sep 13, 2014 1:00 am
Log LMTP/MTA filters events.
Feel free to file an enhancement request for this.
-
- Advanced member
- Posts: 131
- Joined: Sat Sep 13, 2014 1:55 am
Log LMTP/MTA filters events.
Alright. Thanks.
-
- Advanced member
- Posts: 75
- Joined: Sat Sep 13, 2014 2:29 am
Log LMTP/MTA filters events.
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
Our mail_history package consists of three parts:
* milter, running on the MTA nodes
* mailboxd extension
* zimlet