Lets have some fun with PMX...
File Tracing
One of PMX's functions is to scan files... Its a bit of a mixed blessing but the file scanner really doesn’’’’t care what the file is or what its called.. it will search the file and identify it by its true file type.. This can be somewhat tricky when it comes to false positives .. sometimes your wondering .. why did that file trigger the suspect rule?
So here’’’’s what you do ...
su - pmx6
password
pmx-list-true-filetypes -v filename.doc
this will take your test file and inject it directly into PMX's file scanner, the verbose setting will output exactly what file type was found so you can modify your suspect list and allow the file.
Message Tracing
Another very useful toy included with PMX is the ability to literally stuff a message into it and follow that message from start to finish..
Lets assemble a test message
Open the message, goto the header options and copy out all of the headers.. then paste them into your touch file below.. after that do the same thing with the message body..
once you have the entire message
su - pmx6
password
touch test.txt
vi test.txt
insert message headers
insert message body
:wq!
Then:
pmx-policy inject test.txt --relay 188.88.89.87 --to your@email.com --dry-run -verbose -v -v -v
(options)
-- relay if you want you can use internal address 10 192.168 172 .. etc.. or any external ip
--dry-run don’’’’t include if you want to deliver the message
-verbose enable wordy responses
-v the level of verbose logging.
I’’’’m kind of lazy in this regard so I would also include a | grep -i true to the command... or you can scroll up and see any rule that tested true.
This is very useful to:
follow the message path and rule set.
see if the relays are correct
get an exact spam score
generate a spam report
nailing down policy hits
This thread was automatically locked due to age.
