Feature Request Module Identification
|
Logged in as: Guest
|
|
Users viewing this topic:
none
|
|
Login  | |
|
Feature Request Module Identification - 17.Sep.2008 9:26:24 AM
|
|
|
mharri
Posts: 40
Joined: 15.Nov.2006
Status: offline
|
As a feature request, I would like to see Mail Essentials be able to tag each blocked email with a tag identifying which module blocked it.
For instance, if a particular email is blocked due to header checking there should be a way to identify which module did it.
If an individual sets a particular module to dump into a spam folder, they can then later go back to help identify which module is grabbing legitimate emails more easily. This should be a feature that you can either turn on and off based on the particular module. Thank you.
|
|
|
|
|
RE: Feature Request Module Identification - 17.Sep.2008 9:29:44 AM
|
|
|
Michael Alexieff
Posts: 80
Joined: 8.Sep.2008
Status: offline
|
What actions are you taking when GFI MailEssentials finds a piece of spam?
_____________________________
Regards,
Michael Alexieff - Technical Support Representative
GFI Software - www.gfi.com
|
|
|
|
|
RE: Feature Request Module Identification - 17.Sep.2008 9:35:27 AM
|
|
|
mharri
Posts: 40
Joined: 15.Nov.2006
Status: offline
|
Currently I have most modules set to delete. However we are sometimes getting false positives that I have found when I direct a module to dump into a folder.
The problem then becomes identifying which module is grabbing the legitimate items. I thought by having a tag option built into Mail Essentials that it would help to identify which module is grabbing the legitimate email. I could either turn it off, dial it down or continue to monitor the traffic being captured by that particular module. Thanks.
|
|
|
|
|
RE: Feature Request Module Identification - 17.Sep.2008 9:44:37 AM
|
|
|
Michael Alexieff
Posts: 80
Joined: 8.Sep.2008
Status: offline
|
There is a registry entry you can change that when moved specified folder in the inbox that it will tag the reason why it was moved there. Check out the following Knowledge base article on how to enable this, http://kbase.gfi.com/showarticle.asp?id=KBID001892
_____________________________
Regards,
Michael Alexieff - Technical Support Representative
GFI Software - www.gfi.com
|
|
|
|
|
RE: Feature Request Module Identification - 17.Sep.2008 12:32:53 PM
|
|
|
SoCal_HEMIHead
Posts: 18
Joined: 14.Aug.2008
Status: offline
|
You can also search the log files for each module to locate the blocked message. That's what I do.
|
|
|
|
|
RE: Feature Request Module Identification - 19.Sep.2008 8:56:23 AM
|
|
|
joestern
Posts: 238
Joined: 18.Sep.2003
From: Philadelphia, PA
Status: offline
|
Another thing that makes spam-reason diagnosis easier is to use separate logs for each antispam component. Emails removed by the DNS blacklist module go in the DNSBlacklist.log file, Emails embargoed by the Bayesian filter go in Bayesian.log, etc.
I use Agent Ransack to search the logs directory for the affected mail, and it will check all the logs at once.
- Joe
|
|
|
|
|
RE: Feature Request Module Identification - 19.Sep.2008 1:37:20 PM
|
|
|
vizeroth
Posts: 7
Joined: 1.Aug.2008
Status: offline
|
It should also be noted that you can move the individual log files to create archives, and ME just generates a new file in place of the old one (alternatively you could rename the log file, but I move them to an archive folder and add the date range of the logs they contain to the filename). If you do this often enough (or schedule a task to do it for you), the log files should be at a pretty reasonable size, depending on the number of messages you catch in a particular filter in a given period of time.
|
|
|
|
 New Messages |
 No New Messages |
 Hot Topic w/ New Messages |
 Hot Topic w/o New Messages |
 Locked w/ New Messages |
 Locked w/o New Messages |
|
 Post New Thread
Reply to Message
Post New Poll
Submit Vote
Delete My Own Post
Delete My Own Thread
Rate Posts |
|
|
Printable Version
