MSWgraylist
The Idea and what this do !
The two plug-ins MSWcollect and MSWgraylist is done on a request from a
Mailsweeper administrator there need to collect who his users sends to and when
there comes a reply from the outside sender, then it must bypass the spam
filters, this way it will lower the false positive mails to almost nothing and
save him a lot of time.
Graylist external senders, based on who the
internal user have send mails to and you can use the GUI to Config what things
to match on and how many times the internal user must send a mail to the outside
user before the outside user is gray list and will bypass spam filters
Case ideas for what you can this plug-in to:
| Case 1 | Let external senders bypass the spam filters if the internal user have send
more then 5 mails to the external user before Options set: Email pair is enable and the counter is set to 5 |
| Case 2 | Allow Encrypted mails in from external senders, if the internal user
have send more then a 100 mails to the external user before Options set: Email pair is enable and the counter is set to 100 |
| Case 3 | Allow Encrypted mails in from external senders, if the internal user
have send a Encrypted mail to the external user within 7 days
(This need so extra scripts, but can be done) Options set: Email pair is enable, counter is set to 1 and record delete time is 7 days |
| Case 4 | Bypass spam filters from everyone that the internal users have send
to before Options set: Email single sender is enable and the counter is set to 1 |
| Case 5 | Save incoming mails to a folder for later use when
training the Mailsweeper anti-spam 1.x filter But only save the mails if a internal user have send minimum 25 mails to the external user before Options set: Email pair
is enable and the counter is set to 25 |
| Case 6 | Quentin all mail from external user except for them
the internal users have send a mail to within the last 1 year
Options set: Email pair is enable, counter is set to 1
and record delete time is 1 year |
| Case 7 | Only bypass spam filters for mails there is direct
reply to mails that the internal users have send out
Options set: MessageID and ThreadIndex is enable |
| Case X | Your case, I will like to hear if you use it to of smart
things :-) |
| Windows 2000 Server with SP4 and .Net framework v1.1 |
| Windows 2000 Server with SP4 and .Net framework v1.1 and .Net framework v.1.1 SP1 |
| Windows 2003 Server with .Net framework v1.1 |
| Windows 2003 Server with .Net framework v1.1 and .Net framework v.1.1 SP1 |
| Windows 2003 Server with SP1 and .Net framework v1.1 and .Net framework v.1.1 SP1 |
| Windows XP with SP1 and .Net framework v1.1 |
| Windows XP with SP1 and .Net framework v1.1 and .Net framework v.1.1 SP1 |
| Windows XP with SP2 and .Net framework v1.1 and .Net framework v.1.1 SP1 |
| Mailsweeper 4.2.X |
| Mailsweeper 4.3.X |
| Mailsweeper 5.0.X |
| Mailsweeper 5.1.X |
| MailMarshal 6.0 |
More infomation
There is more docs in the zip file
| File | Date | Platform | Version | Note |
| mswgraylist.1.2006.07.23.zip | 2006-07-23 | Windows / Intel 32 bit | 1.2006.07.23 | |
| mswgraylist.1.2006.02.16.zip | 2006-02-16 | Windows / Intel 32 bit | 1.2006.02.16 | |
| mswgraylist.1.2005.10.23.zip | 2005-10-23 | Windows / Intel 32 bit | 1.2005.10.23 | |
| mswgraylist.1.2005.07.17.zip | 2005-07-17 | Windows / Intel 32 bit | 1.2005.07.17 | |
| Changelog.txt |
Support forum
http://www.tooms.dk/forum/forum.asp?FORUM_ID=4
Screen dumps from the Config GUI
| Add, Delete or Select the cfgID to Config | ![]() |
| Setting up what MSWcollect database to use for this cfgID | ![]() |
| Setup what to match the incoming mails with and what minimum count the match must have before the mail is graylist | ![]() |