DSpam RELAY - Revision history

Ledhed: /* Configuring DSPAM as a seamless front-end relay using Postfix */

2009-07-27T22:58:20Z

‎Configuring DSPAM as a seamless front-end relay using Postfix

Ledhed: /* Step 7: Configure user aliases for dspam_virtual_uids */

2009-07-27T22:57:18Z

‎Step 7: Configure user aliases for dspam_virtual_uids

Ledhed: /* GLOBAL DATABASES */

2009-07-27T22:57:04Z

‎GLOBAL DATABASES

Ledhed: /* ALIASES */

2009-07-27T22:56:41Z

‎ALIASES

Ledhed: /* GLOBAL DATABASES */

2009-07-27T22:56:33Z

‎GLOBAL DATABASES

Ledhed: /* Configuring DSPAM as a seamless front-end relay using Postfix */

2009-07-27T22:56:15Z

‎Configuring DSPAM as a seamless front-end relay using Postfix

Ledhed: /* ALIASES */

2009-07-27T22:23:08Z

‎ALIASES

Ledhed: /* GLOBAL DATABASES */

2009-07-27T22:22:59Z

‎GLOBAL DATABASES

Ledhed at 22:22, 27 July 2009

2009-07-27T22:22:07Z

Ledhed at 22:20, 27 July 2009

2009-07-27T22:20:02Z

@@ Line 17: / Line 17: @@
 .1.12 to avoid some nasty bugs in MySQL which affect DSPAM).
+<br>
-−
 === Step 1: Configure, compile and install Postfix with MySQL support ===
 -----
@@ Line 30: / Line 29: @@
   make && make install
+<br>
-−
 === Step 2: Configure, compile  and install DSPAM with daemon + mysql support ===
 -----
@@ Line 51: / Line 49: @@
                   --enable-daemon
+<br>
-−
 === Step 3: Install DSPAM MySQL Objects (With a twist) ===
 -----
@@ Line 60: / Line 57: @@
 addresses with the same uid, which is how DSPAM recognizes users.
+<br>
-−
 === Step 4: Configure DSPAM to receive LMTP and delivery SMTP ===
 -----
@@ Line 82: / Line 78: @@
 needs to retrain the message. I'll explain how to set this up in a bit.
+<br>
-−
 === Step 5: Configure Postfix to use DSPAM + virtual UIDs table ===
 -----
@@ Line 106: / Line 101: @@
   additiona_conditions =
+<br>
-−
 === Step 6: Add a localStore preference for each user ===
 -----
@@ Line 125: / Line 119: @@
 will be stored in $DSPAM_HOME/data/1
+<br>
-−
 === Step 7: Configure user aliases for dspam_virtual_uids ===
 -----

@@ Line 149: / Line 149: @@
 You might want to run with verbose debug to test and ensure everything is
 working properly.
 == GLOBAL DATABASES ==

@@ Line 152: / Line 152: @@
 == GLOBAL DATABASES ==
 -----
-If you're thinking about going with a global database, I strongly recommend
+If you're thinking about going with a global database, I strongly recommend using merged groups + toe instead of a single global group. To do this, just follow the README directions for setting one up and leave everything the way it is. If, however, you insist on a single global group, you'll need to make one change to dspam.conf to accomodate this configuration. Add --user [globaluser] to your ServerParameters property. This will cause all mail to be processed using this user, but will still deliver using the recipient information.
 using merged groups + toe instead of a single global group. To do this, just
-follow the README directions for setting one up and leave everything the way
+<br>
 it is. If, however, you insist on a single global group, you'll need to make
 one change to dspam.conf to accomodate this configuration. Add
 --user [globaluser] to your ServerParameters property. This will cause all
 mail to be processed using this user, but will still deliver using the
 recipient information.
 == ALIASES ==

@@ Line 162: / Line 162: @@
 == ALIASES ==
+-----
 If you have some aliases, you'll need to also set them up on your relay
 so that DSPAM can process the individual users. To do this, add the

@@ Line 151: / Line 151: @@
 == GLOBAL DATABASES ==
+-----
 If you're thinking about going with a global database, I strongly recommend
 using merged groups + toe instead of a single global group. To do this, just

@@ Line 1: / Line 1: @@
 == Configuring DSPAM as a seamless front-end relay using Postfix ==
+-----
 This HOWTO explains how to set up DSPAM as a front-end relay.  Using this
 configuration, you can point your MX records to the DSPAM server and
@@ Line 20: / Line 20: @@
 === Step 1: Configure, compile and install Postfix with MySQL support ===
+-----
 To do this, you'll need to init a set of makefiles including the path to your
 MySQL includes and libraries...
@@ Line 33: / Line 33: @@
 === Step 2: Configure, compile  and install DSPAM with daemon + mysql support ===
+-----
 You'll need the following options:
 * MySQL
@@ Line 54: / Line 54: @@
 === Step 3: Install DSPAM MySQL Objects (With a twist) ===
+-----
 Create the MySQL objects as outlined in the mysql DSPAM doc, but use the
 virtual_user_aliases.sql script instead of virtual-users.sql script to create
@@ Line 63: / Line 63: @@
 === Step 4: Configure DSPAM to receive LMTP and delivery SMTP ===
+-----
 We're going to configure postfix to connect to DSPAM via LMTP using a domain
 socket. The following configuration properties should be set in dspam.conf:
@@ Line 85: / Line 85: @@
 === Step 5: Configure Postfix to use DSPAM + virtual UIDs table ===
+-----
 The following is a sample configuration that will tell postfix to use DSPAM
 as its virtual transport (passing all mail to DSPAM via LMTP) and to use the
@@ Line 109: / Line 109: @@
 === Step 6: Add a localStore preference for each user ===
+-----
 The localStore preference defines the web directory name for each user (for
 the WebUI). Since users might have multiple email addresses, you want to avoid
@@ Line 128: / Line 128: @@
 === Step 7: Configure user aliases for dspam_virtual_uids ===
+-----
 Postfix is now set up to do a lookup in dspam_virtual_uids. It _must_ find a
 valid address in this table in order to accept the message. What you'll need
@@ Line 149: / Line 149: @@
 You might want to run with verbose debug to test and ensure everything is
 working properly.
 == GLOBAL DATABASES ==

← Older revision		Revision as of 22:20, 27 July 2009
Line 181:		Line 181:

	<br>		<br>
		+	[[Category:DSpam]]