If you can spare a box, put *nix on it, and use it as a gateway to your Exchange server. You can put ASSP or Maia Mailguard on it, and that will protect your Exchange from all sorts of things. Maia is a user-friendly set of programs that incorporate SpamAssassin, and provide the user with a set of web pages to manage their spam/ham.
If the SQL database containing addresses for a whitelist is important, and you wish to use a *nix email gateway, a scheduled job that dumps those email addresses to a text file can SCP'ed to the *nix box for incorporation in the config files. Or, I'm sure, there are ways to set up a pull of data from SQL to the *nix box via ODBC, or something like that. Kurt On Wed, Aug 6, 2008 at 11:52 AM, Jacob <[EMAIL PROTECTED]> wrote: > After searching around, I figured SpamAssassin may be my best solution. > > I found other sites that discuss SpamAssassin with SQL > http://wiki.apache.org/spamassassin/UsingSQL > > I will take some time to figure this out, but if the price is right (free) > it will probably make the big boss man happy! :) > > -----Original Message----- > From: Troy Meyer [mailto:[EMAIL PROTECTED] > Sent: Wednesday, August 06, 2008 11:45 AM > To: NT System Admin Issues > Subject: RE: challenge/response SQL based white list > > Jacob, > > Its been a while since I used Spam Assassin in my former life, but its crazy > feature rich if you have time. > > http://spamassassin.apache.org/full/3.0.x/dist/doc/Mail_SpamAssassin_SQLBase > dAddrList.html > > I wonder if you could use that to create an auto-whitelist for all users and > then if the email doesn't pass that you can flag and quarantine, or bump up > the spam rating for client identification (or do a challenge response which > I despise). > > It probably will take a decent amount of thought, but having Spam Assassin > on your edge does give you a lot of ammo in your arsenal, its just a matter > of finding the goods. > > > -Troy > > > -----Original Message----- > From: Jacob [mailto:[EMAIL PROTECTED] > Sent: Wednesday, August 06, 2008 11:39 AM > To: NT System Admin Issues > Subject: RE: challenge/response SQL based white list > > C/R is not necessary... it could even flag an email update the subject with > something like "Not a Customer" or "Possible Spam". Or, even forward it to > another email address. > > For myself, I use spambytes for Outlook and it works about 95% of the time. > > But for the powers above me.. does not use Outlook (and won't move to > Outlook or any other email client) and wants something down at the server > end without the need for the user (himself) to mess with. > > The mail server we use has spamassassin built in. If I could figure out how > to configuration the local.cf to read the SQL table, I could possibly work. > I have been playing with this for the last hour. > > The problem we have is that most built in spam filters won't work for us. > If you happen to look at the domain of my email address (NSFW), quite a few > emails will be rejected. > > -----Original Message----- > From: Kurt Buff [mailto:[EMAIL PROTECTED] > Sent: Wednesday, August 06, 2008 11:02 AM > To: NT System Admin Issues > Subject: Re: challenge/response SQL based white list > > On Wed, Aug 6, 2008 at 9:40 AM, Jacob <[EMAIL PROTECTED]> wrote: >> We are looking at different solution for spam protection. > > OK > >> What we are looking for a solution that can challenge/response an incoming >> email based on a white list that is SQL database based. > > Don't do it. For the love of all things sacred - spare your users and > their correspondents the pain and aggravation. C/R systems should all > be called Hoover - they all suck badly. > >> Anybody have any suggestions they have uses/tried for white list >> centralization? > > Yes - don't do it. Get something that the users can manage themselves, > like Maia Mailguard, or ASSP, or something like that. You can have > whitelists in those, and blacklists (which are much less useful than > you might think), but either of those are infinitely superior to a C/R > system, and are much better for all concerned. Also, don't use > catchall addresses, and make sure that your system refuses mail for > invalid recipients. Lastly, if you can, publish SPF records in DNS. > > Kurt > > ~ Upgrade to Next Generation Antispam/Antivirus with Ninja! ~ > ~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm> ~ > > > ~ Upgrade to Next Generation Antispam/Antivirus with Ninja! ~ > ~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm> ~ > > ~ Upgrade to Next Generation Antispam/Antivirus with Ninja! ~ > ~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm> ~ > > > ~ Upgrade to Next Generation Antispam/Antivirus with Ninja! ~ > ~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm> ~ > ~ Upgrade to Next Generation Antispam/Antivirus with Ninja! ~ ~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm> ~
