On Wednesday 19 November 2003 08:58, Jeff Breidenbach wrote:
> Well, it's not quite that bad. I can't computationally afford to put
> SpamAssassin on the existing primary server.
I am running a Celeron 1200 with 256 MB RAM and a single IDE disk. The machine
is running Suse Linux 8.1 with sendmail, to which I added
spamassassin-milter, spamassassin and milter-sender.
The usage stats are at
http://vvv.koehntopp.de/rrd
The system is not handling overly much mail, up to 8000 messages a day, but
the load is close to 0 as well
(http://vvv.koehntopp.de/rrd/index.php?scale=1+day&data=allmail,
http://vvv.koehntopp.de/rrd/index.php?scale=1+day&data=load)
The key problems when setting up this machine were a) using a milter for
spamassassin. I am using spamassassin-milter (available from
http://www.runestig.com/osp.html) to drive my spamassassin process, and I am
using milter-sender before that
(http://www.snert.com/Software/milter-sender/). Milter-sender does exim-style
sender verification before accepting a message. That is, the sender of a
message must have a working reverse lookup, and the primary mx for the
senders domain must be able to accept an error message ("MAIL FROM: <>") for
the presumed senders address ("RCPT TO: <senders address [EMAIL PROTECTED] domain
here>" must not 5xx out). This cuts out a lot of spam before it even hits the
SpamAssassin.
Kristian
_______________________________________________
Gossip mailing list
[EMAIL PROTECTED]
http://www.mail-archive.com/cgi-bin/mailman/listinfo/gossip
