>>Where I'm completely lost is how this ties to Sniffer and what the
"XYNTService.ini" file is supposed to be. I don't have any such file?
You can run the utility at the command line with no options to get a reminder of command line
options. You can tell DRGOutflow.exe where to find message files (i=<path>), where the
files should eventually go (o=<path>), how long to delay them (d=<minutes>)
You can start this at the command line, minimize the window, and let it run. If
you really want not to do that then run it in a service wrapper like
XYNTService or similar.
When you want it to stop, go into it's command line window and hit Ctrl-C
"break" -- it will get the message and will let you know it's received the
SIGINT (interrupt) signal. After a minute or so it will
quit.
---
How it works:
About once per minute it does a directory scan of the messages in it's input directory. It collects
all of the messages that have been there long enough. It looks at the modified timestamp on the
.hdr or q*.smd files to figure this out. The messages are scanned and delivered at a
"reasonable" pace so that DRGOutflow doesn't overload the system. It "takes it's
time" so that the rescans can easily be interleaved with the other work on the system.
Essentially it tries to take a whole minute to scan all of the eligible messages so that on the
next minute it can start fresh. The more messages it has to process the faster it will do the
work... but if it can relax then it will.
David
On 11/14/2014 6:15 PM, Andy Schmidt wrote:
Hi David,
Thanks for sharing that. I'm trying to wrap my head around how the "flow".
A message comes into Declude, is not whitelisted, passes by the Sniffer tests,
etc. and at the VERY end runs into the Gauntlet filter. If it has a weight of
20, it's considered already spammy enough to not even bother and it's left
alone.
If it has the word "GAUNTLET" in the header (presumingly set by the utility?), then this
is assumed to be the "second" pass for that message and it's left alone.
Otherwise (after a few other exemptions), if it matches certain criteria, the "Gauntlet"
filter will register as having been triggered, and the message will be moved into the
"Gauntlet" subfolder.
That part I think I understand.
Now, presumingly the DRGOutflow.exe is the one that will periodically scan the Gauntlet
subfolder for messages old enough, possibly set a "Gauntlet" X-Header, and move
those back into one of the other Declude process folders where it will be rescanned?
How am I doing thus far?
Where I'm completely lost is how this ties to Sniffer and what the
"XYNTService.ini" file is supposed to be. I don't have any such file? It's
sounds like you are somehow having the Sniffer service launch Gauntlet - instead of just
configuring DRGOutflow.exe as its own Windows service?
I couldn't quite gather/surmise the answers to those questions from your
instructions.
Best Regards,
Andy
-----Original Message-----
From: [email protected] [mailto:[email protected]] On
Behalf Of David Barker
Sent: Friday, November 14, 2014 2:00 PM
To: [email protected]
Subject: [MBF] Gauntlet 2.0 Release for SM & IM
Hi Folks,
The Gauntlet 2.0 is available.
Instructions
http://mailsbestfriend.com/downloads/docs/Gauntlet_2.0_Instructions.pdf
Utility http://mailsbestfriend.com/downloads/Scripts/DRGOutflow.exe
Filter http://mailsbestfriend.com/downloads/Filters/GAUNTLET.txt
--
David Barker
Mail’s Best Friend
Email : [email protected]
Web : www.mailsbestfriend.com
Office : 866.919.2075
Mobile : 978.518.6461
#############################################################
This message is sent to you because you are subscribed to
the mailing list <[email protected]>.
To unsubscribe, E-mail to: <[email protected]>
To switch to the DIGEST mode, E-mail to <[email protected]>
To switch to the INDEX mode, E-mail to <[email protected]>
Send administrative queries to <[email protected]>
