ASSP Success Stories
From ASSPSMTP
Return to Documentation Home
ASSP Success Stories
This is a place where we get to tell how ASSP has worked for us. If you have a success story, send it to the link below, or post here it yourself.
2003-Nov-19 4:06pm jhanna
Tesimonials
'There are more Success Stories found under Testimonials'
ASSP + Exchange = 99.86% success with no false positives.
I don't know if everyone is having this kind of success, but I use Exchange and Outlook 2003 (which has additional SPAM fighting capabilities). Between Oct 1 & 15, my company has received 182,055 e-mails. This team of products has provided us with a 99.86% spam kill rate. False positives...0, zero, zilch, nada, nothing. Since we don't have Outlook 2003 completely rolled out, this number is anticipated to improve another .1%. Also, SPAM average has decreased by 2% since we implemented it in September. I'm not sure what caused this. jasont80 ( Jason Thompson ) 2003-11-19 23:58
From the Slovak Republic
Few months ago I wrote you about some bugs in assp. Last month I have returned to assp project to see what' s the progress. I was really surprised and I' ve desided to try assp in production environment of our small company. Now it is one month of my testing and assp really solve our spam problems. I have only one!! spam reported. (But some good mail was lost in the beggining and version 1.0.6 has crashed two times.) So I want to tell you big thank for this good job. See you. Patrik.
Nonprofit & Exchange -- 100,000 spams per week no more.
OUR SUCCESS STORY I am an IT consultant. A week ago I installed ASSP at a 25 employee non-profit corporation. BEFORE implementation of ASSP everyone was getting about 300 spams/day (over 100,000 spams/week for the domain). Now we are almost spam free!!! The success we are enjoying is absolutely amazing. I had tried two expensive commercial products “McAfee SpamKiller for Microsoft Exchange” and “Symantec Mail Security for Microsoft Exchange 4.0” with very little success. ASSP beats the pants off them – it’s easy to setup, has very powerful features, detects spam very well and I love the price! All of the staff have reported that they are saving 30 minutes per day because they do not need to delete spam. On behalf of 25 very happy people THANK YOU, THANK YOU, THANK YOU to John and everyone else who has helped to make this tool possible. OUR SOFTWARE ENVIRONMENT We use Exchange 2000 so our configuration is: Internet -> ASSP -> exchange 2000 -> Outlook Client Our server runs Windows XP Corp Edition. We are using ActivePerl with Win32::Daemon – everything was installed exactly as per the directions on the ASSP website. I also installed Norton AntiVirus Corporate Edition 8.0 and WinConnect Server XP so that I can manage the server from home. OUR HARDWARE ENVIRONMENT & STATS We are running it on an old Pentium II, 300 MHz with 256MB of RAM. CPU utilization is about 4%. During the f irst week of operation: - about 100,000 spams were rejected - about 6,000 good email messages were passed through to our exchange server. - About 600 relay attempts were rejected. - “netstat” reports that we received 700,000,000 bytes and sent 300,000,000 bytes (this works out to 2,000 bytes/second) - 100% uptime was enjoyed -grenfell
Win2k3/ASSP + Win2k3/Exchange2k3
Successfully running ASSP on a Windows Server 2003 box in our DMZ proxying to an Windows Server 2003 box with Exchange 2003 running on it. We have roughly 60 users, process about 1k e-mails per day, and it have been working great so far. 2004-Mar-23 6:51pm darcher
ASSP+Postfix+Relaying to internal SMTP Servers: Perfect SPAM Hit Rate
About a week ago, we've changed to a new setup, using ASSP on a Mail Relay (we're a SME, ~50 users local+roadwarriors, 1500 mails/day, about 80% Spam). Spam detection rate is wonderful (>99.8%), we have at most 3 undetected Spams a day. We especially like the auto-whitelisting of outgoing mails, the spambuckets, the non-processing rule for non-whitelisting of auto-replies, and the email interface for submitting Spam, Ham and Manual Whitelisting. Wonderful piece of software! Especially those users who have the same email address for almost 10 years enjoy a completely new experience, when they look at their Inbox now... We used to run sendmail+spamassassin (via procmail), and then relay the mails to two internal servers. Spamassassin's hit rate was rather limited, and several users kept tweaking their custom spamassassin rules, to catch up with the latest spam characteristics. We are now running ASSP in front of postfix, which then - depending on user's account - relays mails to a sendmail/POP system, or an Exchange clone (HP Openmail) for Outlook/MAPI client access (all Linux based except for MUA). We are still running in TestMode, until the whitelist has grown some more. I can highly recommend ASSP to anybody who is suffering from SPAM. 2004-Jul-29 10:27pm daniel
Non-profit: ASSP on Redhat 9 + MS Exchange on W2K
I am a part time systems administrator at a non-profit organization in Baltimore
Maryland. The organization uses Microsoft's Exchange for their e-mail and has
23 employees who collectively receive >500 spam messages each day in their outlook
mailboxes. This number was slowly increasing until we could no longer stand it.
Something needed to be done!
Because I am a great believer in open source software, I try to use open source
solutions wherever I can. ASSP is one of these choices, and I haven't regret it
so far. I also try to keep things as simple as possible to keep things easily
managable and maintainable.
Our network topology roughly looks like this:
(Internet)----[Firewall]--+----[W2KServer]
+----[W2KWorkstation]
+----[W2KWorkstation]
...
+----[W2KWorkstation]
The firewall is a pentium III 999 Mhz with 256 MB RAM running Redhat Linux 9.
The firewalling is done by IPTables version 1.2.7. SMTP is the only type of
inbound traffic the firewall accepts on its WAN connection.
I have installed ASSP on the firewall as well. It listens for incoming SMPT
messages on port 25, and relays all sollicited messages to port 25 on the W2K
Server. On that W2K Server, Exchange is configured to relay all outgoing e-mail
to port 25 on the firewall. This makes our SMTP chain look like this:
Internet <--> Firewall:25 <--> W2KServer:25 <--> W2KWorkstation
It all works like a dream. ASSP effectively blocks all those annoying spam
messages, saving people numerous minutes per day. Way to go!
It does take quite some effort and time to get ASSP to "know" the organisation.
Informing and instructing the workstation users about ASSP is crucial in order
to make ASSP work! Tell the users how to whitelist their e-mail addressbooks.
Tell them how they can send spam reports.
ASSP lacks one feature that I would really (I mean: really really) like to see
in the future:
The ability to send or copy all unsollicited messages for valid recipients to
that recipients "spambox".
I have created a crude Perl script myself to do this. It basically goes through
all files in the spam directory, and copies messages that are less old than 1
hour (this is configurable) and were sent to a valid recipient (= valid e-mail
account) to that recipients personal spam directory. This directory is mapped
(through Samba) to the S: drive on the workstation the recipient happens to be
logged on to. I have added a line to the firewall's cron table to run this script
every hour.
Now, the users can personally go through their spam and verify that it actually
is spam, and send non-spam messages in a notspam report to ASSP. This takes
them about 15 minutes per week. It saves me an incredible amount of work,
and does not require me to open private messages to check if it is spam or not.
The same script can also delete files. I use that feature to automatically
clean-up spam files older than 90 days once a month.
It's all realized with open source technology. Life is good!
Thanks a million ASSP creators!
Mark Nankman
See more Success Stories found under Testimonials
Return to Documentation Home
These icons link to social bookmarking sites where readers can share and discover new web pages.
