DSpam QMAIL INTEGRATION - Revision history

Ledhed at 19:04, 12 June 2009

2009-06-12T19:04:44Z

Ledhed at 19:04, 12 June 2009

2009-06-12T19:04:06Z

Ledhed at 19:03, 12 June 2009

2009-06-12T19:03:35Z

Ledhed: /* USER-LEVEL INTEGRATION */

2009-06-12T19:00:40Z

‎USER-LEVEL INTEGRATION

Ledhed: Created page with '[http://www.qmail.org/ qmail] is designed with a modular system architecture, so there are a couple of places to add dspam to such a system. VPopmail extends the base qmail deli...'

2009-06-12T18:59:44Z

Created page with '[http://www.qmail.org/ qmail] is designed with a modular system architecture, so there are a couple of places to add dspam to such a system. VPopmail extends the base qmail deli...'

New page

[http://www.qmail.org/ qmail] is designed with a modular system architecture, so there are a couple of places to add dspam to such a system. VPopmail extends the base qmail delivery process to handle virtual domains and users, which can reside in several different user databases. Whether you want to add dspam at the virtual domain level or user level largely determines the best way to add it to your system.

== USER-LEVEL INTEGRATION ==

If you are only configuring dspam for a small percentage of your users, this is the best method. Configure dspam to use a standalone local delivery agent like safecat (if you already use procmail or maildrop as an LDA, you should call dspam from those tools directly).

First, create a small script called maildir_mod in /usr/local/bin...
#!/bin/sh
VPOPDOMAINS="/home/vpopmail/domains"
if [[ "$2" = "-d" ]]; then
user=`eval echo $3 | cut -f 1 -d "@"`
domain=`eval echo $3 | cut -f 2 -d "@"`
cd $VPOPDOMAINS/"$domain"/"$user"
fi
/usr/local/bin/safecat "$1"/tmp "$1"/new 1>/dev/null

''NOTE:''

Be sure to configure VPOPDOMAINS to point to the path for your virtual domain directories

Now configure DSPAM:
./configure \
--with-dspam-owner=vpopmail \
--with-dspam-group=vchkpw \
--with-delivery-agent="/usr/local/bin/maildir_mod Maildir -d %u" \
# Your arguments

Next, create a .qmail file in the directory for the user with a line to call dspam, like this:
| /usr/local/bin/dspam --deliver=innocent --user $EXT@$USER

The two environment variables $EXT and $USER are created by the qmail-local program which begins the local delivery process.

== DOMAIN-LEVEL INTEGRATION ==

If you're adding dspam for all users in a domain, you can add dspam directly inline with the vpopmail LDA: vdelivermail. In this mode, you don't need to configure dspam to use a custom LDA, nor do you need to add a .qmail file for all users. Instead, you replace the existing line to the .qmail-default file at the virtual domain level, like this:
| /usr/local/bin/dspam --deliver=innocent --user $EXT@$USER --stdout | /home/vpopmail/bin/vdelivermail '' bounce-no-mailbox

In essence, you just add the call to dspam (with the appropiate options including --stdout) to the front of the existing line which vadddomain creates when you add a domain.

← Older revision		Revision as of 19:04, 12 June 2009
Line 1:		Line 1:
		+	__FORCETOC__
		+
	[http://www.qmail.org/ qmail] is designed with a modular system architecture, so there are a couple of places to add dspam to such a system. VPopmail extends the base qmail delivery process to handle virtual domains and users, which can reside in several different user databases. Whether you want to add dspam at the virtual domain level or user level largely determines the best way to add it to your system.		[http://www.qmail.org/ qmail] is designed with a modular system architecture, so there are a couple of places to add dspam to such a system. VPopmail extends the base qmail delivery process to handle virtual domains and users, which can reside in several different user databases. Whether you want to add dspam at the virtual domain level or user level largely determines the best way to add it to your system.

← Older revision		Revision as of 19:04, 12 June 2009
Line 44:		Line 44:

	In essence, you just add the call to dspam (with the appropiate options including --stdout) to the front of the existing line which vadddomain creates when you add a domain.		In essence, you just add the call to dspam (with the appropiate options including --stdout) to the front of the existing line which vadddomain creates when you add a domain.
		+
		+
		+
		+	[[Category:DSpam]]

@@ Line 8: / Line 8: @@
 First, create a small script called 'maildir_mod' in /usr/local/bin...
   #!/bin/sh
   VPOPDOMAINS="/home/vpopmail/domains"
@@ Line 16: / Line 17: @@
   fi
   /usr/local/bin/safecat "$1"/tmp "$1"/new 1>/dev/null
 ''NOTE:''

@@ Line 7: / Line 7: @@
 If you are only configuring dspam for a small percentage of your users, this is the best method. Configure dspam to use a standalone local delivery agent like safecat (if you already use procmail or maildrop as an LDA, you should call dspam from those tools directly).
-First, create a small script called maildir_mod in /usr/local/bin...
+First, create a small script called 'maildir_mod' in /usr/local/bin...
   #!/bin/sh
   VPOPDOMAINS="/home/vpopmail/domains"
@@ Line 19: / Line 19: @@
 ''NOTE:''
-Be sure to configure VPOPDOMAINS to point to the path for your virtual domain directories
+Be sure to configure ''VPOPDOMAINS'' to point to the path for your virtual domain directories
@@ Line 34: / Line 34: @@
-The two environment variables $EXT and $USER are created by the qmail-local program which begins the local delivery process.
+The two environment variables ''$EXT'' and ''$USER'' are created by the qmail-local program which begins the local delivery process.
-−
-−
 == DOMAIN-LEVEL INTEGRATION ==