THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
| No Format |
|---|
$ ./configure --spooldir /var/lib/qmailscan --qmaildir /var/qmail --bindir /var/qmail/bin \ --qmail-queue-binary /var/qmail/bin/qmail-queue --admin postmaster@example.com --domain example.com \ --notify none --local-domains example1.com,example3.com,some.other.domain.net --silent-viruses auto \ --lang de_DE --debug 1 --unzip 0 --add-dscr-hdrs 0 --archive 1 --redundant no --log-details \ --fix-mime 1 --scanners "verbose_spamassassin" --install 1 |
| Wiki Markup |
|---|
Since qmail allows users to configure their own delivery options via ~/.qmail files, an alternative option, if you have spamd running, is to use \[http://www.gbnet.net/~jrg/qmail/ifspamh/ ifspamh\], which is a spamc wrapper that you can use as a command in any ~/.qmail file. If the message passed to ifspamh is suspected to be spam, it is redelivered to an address specified as the argument to ifspamh (typically an alias which is handled by another .qmail file). Otherwise, the message is usually allowed to be processed by the next line in the .qmail file. In either case, ~/.spamassassin/user_prefs is honored, and ifspamh returns the proper exit codes required of a command; see dot-qmail(8) and qmail-command(8). |
A sample ~/.qmail to test mail to myuserid@myhost with ifspamh, delivering spam to myuserid-spam(@myhost), and feeding non-spam to procmail:
| No Format |
|---|
|/usr/local/bin/ifspamh myuserid-spam
|/var/qmail/bin/preline /usr/local/bin/procmail
|
And a ~/.qmail-spam to handle what gets sent to myuserid-spam:
| No Format |
|---|
/home/myuserid/mail/spambox
|
Integrated into Exim
| Wiki Markup |
|---|
[SpamAssassin] can be integrated into \[http://www.exim.org/ Exim\] in three ways: |
...