On Wed, 2003-01-15 at 22:42, Stephane wrote:
> Amongst the answers to my previous post ("has a large company implemented SA") there
>was a very good idea on success stories with SA... It is true that most of the people
>on the net who would say they were happy with SA and that it worked well for them are
>using it for their private use, or run a server which does mailboxes storage as well
>(POP3/IMAP I would imagine). However I couldn't find any description of a successful
>implementation with a similar setup than ours -- I would guess at least a few other
>companies must follow the same model.
We're a smallish company (500 mailboxes), but we use SpamAssassin and
very good it is too.
> Our infrastructure would look like:
> Internet-->[SA]-->[Mailsweeper]-->[SMTP/Lotus Notes gateway]-->Lotus Notes Mail
>reader on Client PC
We have a similar structure, but for reasons I won't go into we have SA
behind our primary mailservers.
> The goal for us is to tag emails (X-Spam-Flag) in a first step and let the Notes
>client put tagged msgs into a separate folder (only saves time, bandwidth and storage
>are still used).
> In a second step we would like to quarantine all detected spam at the SA server
>level (thus saving also bandwidth and storage).
I quickly read through the replies and I'm not sure if anyone has done
the quarantining bit yet so here goes:
We needed to be able to control what email is processed through SA,
primarily so that if I stuffed up the implementation we didn't lose all
email coming in. I looked at various ways of doing this, but decided to
build a new system using an SMTP store and forward system with some perl
glue in between that controls what domains get their email filtered and
also what emails get quarantined.
The system flags spam at level 7.0, but I quarantine at level 9.0, so
7.0 - 9.0's get passed on to the users and I've let them know how to
filter that in their MTA
Over the past few days I've found what looks like a memory leak in one
of the perl modules I'm using some I'm just in the process of rewriting
the perl glue, but apart from that and a few other hiccups the system
has performed well.
The downside of quarantining is you have to manage that email to ensure
you spot any false positives, but we wanted to do that so that we could
scrub the most objectionable spam from our users email.
I can provide further details if you are interested.
--
Ian MacDougall
***********************************************************************
CONFIDENTIALITY. This e-mail and any attachments are
confidential and may also be privileged. If you are not the
named recipient, please notify the sender immediately and
do not disclose the contents to another person, use it for any
purpose, or store or copy the information in any medium. Any
views expressed in this message are those of the individual
sender, except where the sender specifically states them to
be the views of Pinnacle Insurance Plc.
If you have received this e-mail in error please immediately
notify our Helpdesk on +44 (0) 20 8207 9555.
This footnote also confirms that this email message has been
swept by MIMEsweeper for the presence of computer viruses.
www.mimesweeper.com
**********************************************************************
-------------------------------------------------------
This SF.NET email is sponsored by: Thawte.com
Understand how to protect your customers personal information by implementing
SSL on your Apache Web Server. Click here to get our FREE Thawte Apache
Guide: http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0029en
_______________________________________________
Spamassassin-talk mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
