How to Setup SpamAssassin in DirectAdmin?

Setting Up SpamAssassin in DirectAdmin

SpamAssassin is a powerful, open-source spam filter that helps reduce unwanted email by analyzing incoming messages and identifying characteristics common to spam. Integrating SpamAssassin with DirectAdmin enhances your server's email filtering capabilities. Below is a comprehensive guide on how to set up SpamAssassin in DirectAdmin.

Prerequisites

Root Access: You need root access to the server to install and configure SpamAssassin.

DirectAdmin Installed: Ensure that DirectAdmin is installed and running on your server.

Backup: It's advisable to back up your configuration files before making changes.

Step 1: Install SpamAssassin

For CentOS/RHEL:

bash

Copy code

yum install spamassassin

For Debian/Ubuntu:

bash

Copy code

apt-get update

apt-get install spamassassin

This command installs SpamAssassin and its dependencies on your server.

Step 2: Enable and Start the SpamAssassin Daemon

The SpamAssassin daemon (spamd) needs to be running for real-time email filtering.

Enable and Start on Systemd Systems:

bash

Copy code

systemctl enable spamassassin

systemctl start spamassassin

For SysVinit Systems:

bash

Copy code

chkconfig spamassassin on

service spamassassin start

Step 3: Integrate SpamAssassin with DirectAdmin

DirectAdmin uses CustomBuild to manage software installations. You'll need to ensure that SpamAssassin is enabled in CustomBuild.

Navigate to the CustomBuild Directory:

bash

Copy code

cd /usr/local/directadmin/custombuild

Update CustomBuild:

bash

Copy code

./build update

Set SpamAssassin to 'yes':

bash

Copy code

./build set spamassassin yes

Compile and Install SpamAssassin:

bash

Copy code

./build spamassassin

This step ensures that SpamAssassin is properly compiled and integrated with DirectAdmin.

Step 4: Configure Exim to Use SpamAssassin

Exim is the default mail transfer agent used by DirectAdmin. You need to configure Exim to pass emails through SpamAssassin.

Rebuild Exim Configuration:

bash

Copy code

./build exim_conf

This command updates the Exim configuration to include SpamAssassin settings.

Step 5: Restart Mail Services

After configuring, restart Exim and SpamAssassin to apply the changes.

bash

Copy code

systemctl restart exim

systemctl restart spamassassin

Step 6: Enable SpamAssassin in DirectAdmin Interface

For Admin Level:

Log into DirectAdmin as Admin.

Navigate to Admin Level > SpamAssassin Setup.

Enable SpamAssassin by checking the appropriate boxes.

Configure global settings like spam threshold, subject tagging, and auto-deletion.

For User Level:

Log into DirectAdmin as a User.

Go to Email Manager > SpamAssassin Setup.

Enable SpamAssassin for your account.

Adjust settings such as:

Spam Threshold Score: Lower scores make filtering more aggressive.

Delete Spam Automatically: Choose whether to delete or move spam.

Subject Tagging: Define how spam emails are labeled.

Blacklists and Whitelists: Add email addresses or domains to block or allow.

Step 7: Configure Per-User Preferences (Optional)

Users can customize their own SpamAssassin settings:

Access User SpamAssassin Configuration:

Navigate to Email Manager > SpamAssassin Setup.

Adjust Preferences:

Score Settings: Adjust the sensitivity of spam detection.

Filter Settings: Specify actions for spam emails.

Custom Rules: Add specific rules for filtering.

Step 8: Test the Configuration

To ensure that SpamAssassin is working correctly:

Send a Test Email: Use the GTUBE test string, which is a standardized text string that should be recognized as spam.

GTUBE String:

markdown

Copy code

XJS*C4JDBQADN1.NSBN3*2IDNEN*GTUBE-STANDARD-ANTI-UBE-TEST-EMAIL*C.34X

Check Email Handling: Verify that the email is flagged or handled according to your SpamAssassin settings.

Additional Tips

Update SpamAssassin Rules Regularly: Keep the rules up-to-date for optimal spam detection.
bash
Copy code
sa-update

systemctl restart spamassassin

Monitor Logs: Check /var/log/maillog or /var/log/exim/mainlog for any errors or issues.

Resource Management: SpamAssassin can be resource-intensive. Ensure your server has adequate memory and CPU resources.

Custom Configurations: Advanced users can edit /etc/mail/spamassassin/local.cf for more granular control.

Troubleshooting

SpamAssassin Not Starting: Check permissions and ensure that the spamd service is enabled.

Emails Not Being Filtered: Confirm that Exim is correctly configured to use SpamAssassin.

High Load: Optimize SpamAssassin rules and consider using spamd with additional parameters to reduce resource usage.