Why exactly was it caught as spam?
|
Logged in as: Guest
|
|
Users viewing this topic:
none
|
|
Login  | |
|
Why exactly was it caught as spam? - 26.Sep.2008 10:51:31 AM
|
|
|
nachtmsk
Posts: 2
Joined: 26.Sep.2008
Status: offline
|
Hi,
I'm evaluating MailEssentials.
Is there a way for me to tell with each individual message, why it was classified as spam or HAM for that matter.
I'm used to working with Spamassassin. SA will re-write the header with information as to which rules were triggered and also what Baysian rating that particular piece of email received.
I ask this because I'd like an easy way to determine why a message was received as spam -- easier then looking through the message and figuring out which keyword or phrase might have triggered it being marked as spam.
Also, if there is a particular message marked as spam, is there a shortcut for me to re-input that message into my PICKUP folder and have it completely bypass all spam filters? (Currently I have spam being saved in a central folder on the server and not going to users boxes).
Thanks!
Mike
|
|
|
|
|
RE: Why exactly was it caught as spam? - 26.Sep.2008 11:41:47 AM
|
|
|
RSP
Posts: 450
Joined: 31.Oct.2006
From: UK
Status: offline
|
This might help: http://kbase.gfi.com/showarticle.asp?id=KBID001892
Alternatively, enable logging on all the modules and look through the log files.
Another file that is useful is ase_action.gfi_log.txt in the debuglogs folder, but you may need to enable debugging first in the registry
|
|
|
|
|
RE: Why exactly was it caught as spam? - 26.Sep.2008 12:00:19 PM
|
|
|
nachtmsk
Posts: 2
Joined: 26.Sep.2008
Status: offline
|
Thanks RSP. That information is very useful.
I'm curious, have you enabled the registry change mentioned in that KB article?
Are there any downsides? Does the re-write of the header slow the server up?
Thanks again,
Mike
|
|
|
|
|
RE: Why exactly was it caught as spam? - 26.Sep.2008 12:04:34 PM
|
|
|
RSP
Posts: 450
Joined: 31.Oct.2006
From: UK
Status: offline
|
I do not require that change as I tag spam and use the rules wizard on most installations.
Run IISRESET after making the change for it to become effective.
I don't think it will change the load on the server, incidentally.
Debugging will add load though, but the main concern I have with that is disk space!
< Message edited by RSP -- 26.Sep.2008 12:06:02 PM >
|
|
|
|
 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
