The Penguinlinux.com Blog

The following table describes the most commonly-used configuration
options for SpamAssassin as of version 2.20 (more options exist in
version 2.41, which includes all the options listed below). All these
options may be applied system-wide by placing them in the file
/software/spamassassin/config/local.cf or to an
individual’s incoming mail by placing them in the
.spamassassin/user_prefs file under the mail recipient’s
home directory.

Continua”UNDERSTANDING SETTINGS WITH SPAM ASSASSIN”

HOW TO DELETE FILES OLDER THAN CERTAIN DAYS.

Try this

find . -name “*.log” -mtime +15 -exec rm {} \;

this is the command I had to type.

[mmaldonado@Jefferson cur]$ find -mtime +1 -exec rm {} \;

##############################################################################
Continua”HOW TO USE FIND TO DELETE FILES”

This HOWTO is intended to be a “quick and dirty” guide to
getting qmail, an excellent MTA
(Mail Transport Agent) written by Dan Bernstein, up and running with a
minimum of hassle.

Continua”QMAIL HOWTO”

To move your qmail user files from one server to another you should follow these steps:
Continua”How do you move a queue to another server?”

Here are some tips I found for qmail that might come in handy sometime.
Continua”VARIOUS QMAIL TIPS”

This article shows in a step-by-step fashion, how to install and configure the Apache 1.3.x Web server in order to mitigate or avoid successful break-in when new vulnerabilities in this software are found.

Functionality

Before we start securing Apache, we must specify what functionality we expect from the server. Variety of Apache’s use makes it difficult to write a universal procedure to secure the server in every case. That’s why in this article we’ll base on the following functionality:
Continua”Securing Apache: Step-by-Step”

Use cronolog to Rotate Your Web Server Log Files.
Continua”Learning about Cronolog”

Trying to find a way to rotate the logs on this server.
Let’s try to find a way to do that automatically.
Continua”Rotating Apache Logs”

Filtering Spam and Viruses with Maildrop + capability for messages to be Nuked

–

What it does:

This setup allows you to filter Spam and Viruses. Users can also configure a “Nuke” threshold. Messages that score a higher spam score than the user’s configured threshold can be automatically deleted. This cuts down on the amount of flagarant spam that users must sort through (if you simply move all spam to another folder, users still have to sort through it regularly). Users who get tons of junkmail can configure a threshold and cut down on the amount of Spam they must sort through at the risk of a few lost false positives (explain in to them and give them the choice, many are ok with some lost legit mail if it significantly cuts down the spam). Default settings simply mark messages with a score of 15 or higher with a subject of [NUKED-SPAM]. Users can change the action performed (mark_subject (default), delete, do_nothing) and the nuke score (15 stars is default and minimum).
Continua”Spam Assassin With Maildrop and Clamassassin”

1. Setting up Site-Wide Bayesian FilteringIn local.cf, tell SpamAssassin where to find the Bayesian database files:

bayes_path /etc/mail/spamassassin/bayes

This tells the system that the Bayesian filter database files will be /etc/mail/spamassassin/bayes_msgcount, _seen and _toks. Feel free to move it wherever you want.

Now start feeding the Bayesian filter spam and ham messages. Tell sa-learn to use /etc/mail/spamassassin as the configuration directory (i.e. where to find the bayes_msgcount, _seen and _toks files):

sa-learn –spam -C /etc/mail/spamassassin –showdots –dir /path/to/directory/full/of/spam/msgs
sa-learn –ham -C /etc/mail/spamassassin –showdots –dir /path/to/directory/full/of/ham/msgs

See SiteWideBayesFeedback for more tips on getting an entire site to feed back spam and ham messages into the Bayesian filter. Just use -C to make sure that the correct database files are used.

Also restart spamd if you’re running it already so that it will re-read local.cf and enable the Bayes filter:

ps axo %p%a | awk ‘/spamd/ { print $1 }’
spamd -x -q -d -L -u nobody

(your spamd options may be different than mine)

You may experience difficulties with permissions. Make sure you chmod your bayes files to readable/writable by your user group.

If you are running spamd in setuid mode (setuid’s to the user who ran spamc), you will probably need to set bayes_file_mode in local.cf. Otherwise, the bayes file permissions will default to 0700 when the first caller causes updates, and subsequent callers will lack the permissions to open these file.

In local.cf (your setttings may vary):

bayes_file_mode 0770

See Mail::SpamAssassin::Conf(3) for details.
Continua”Site wide Bayesian Filtering Spamassassin”