DSpam INTEGRATION - Revision history

Ledhed: /* INTEGRATION */

2009-07-27T23:22:58Z

‎INTEGRATION

Ledhed: /* INTEGRATION OVERVIEW */

2009-06-12T19:19:22Z

‎INTEGRATION OVERVIEW

Ledhed: /* INTEGRATION OVERVIEW */

2009-06-12T19:18:51Z

‎INTEGRATION OVERVIEW

Ledhed: /* INTEGRATION OVERVIEW */

2009-06-12T19:18:24Z

‎INTEGRATION OVERVIEW

Ledhed: /* MTA SPECIFIC INTEGRATION */

2009-06-12T19:16:26Z

‎MTA SPECIFIC INTEGRATION

Ledhed: /* MTA SPECIFIC INTEGRATION */

2009-06-12T19:15:19Z

‎MTA SPECIFIC INTEGRATION

Ledhed: /* INTEGRATION OVERVIEW */

2009-06-12T19:14:19Z

‎INTEGRATION OVERVIEW

Ledhed: /* MTA SPECIFIC INTEGRATION */

2009-06-12T18:08:24Z

‎MTA SPECIFIC INTEGRATION

Ledhed at 17:58, 12 June 2009

2009-06-12T17:58:24Z

Ledhed: /* Mail Server Integration Overview */

2009-06-12T17:35:23Z

‎Mail Server Integration Overview

@@ Line 1: / Line 1: @@
 == INTEGRATION ==
+-----
 === INTEGRATION OVERVIEW ===
+-----
 As previously mentioned, there are three popular ways to implement DSPAM:
@@ Line 35: / Line 36: @@
   /bin/mail -d bob
 === ALIASES ===
+-----
 There are essentially two different ways a user might train DSPAM. The first is by using the Web UI, which allows them to retrain via the "History" tab. This works quite well, as users must visit the Web UI occasionally to review their quarantine anyway (and reverse any false positives). We'll discuss this shortly in section 1.1.8.
@@ Line 50: / Line 52: @@
 Because DSPAM learns each user's specific email behavior, it's necessary to identify the user in order to program their specific filtering database. This can be done in one of three ways:
+<br>
-−
 ==== The Simple Way ====
@@ Line 71: / Line 72: @@
 The 'root' user represents any active dspam user. It is necessary to supply a username on the commandline or DSPAM will bail on an error, however the user will be changed internally once the signature is read.
+<br>
-−
 ==== The Kind-of-Simple Way ====
@@ Line 88: / Line 88: @@
+<br>
 ==== The Old Way (A.K.A. The Hard Way) ====
@@ Line 107: / Line 107: @@
 You might be wondering if a user can forward a spam to another user's address, or whether a spammer can forward a spam to another user's notspam address. The answer is "no". The key to all mail-based retraining is the signature embedded in each email. The signature is stored with each user's own user id, and so not only does the incoming message have to bear a valid signature, but it also has to be stored on the system with the correct user id. This prevents any kind of alias abuse.
+<br>
 === MTA SPECIFIC INTEGRATION ===
@@ Line 120: / Line 120: @@
 *[[DSpam_POP3FILTER|POP3 Filter]]
+<br>
-−
 [[Category:DSpam]]

← Older revision		Revision as of 19:19, 12 June 2009
Line 9:		Line 9:
	'''As a delivery proxy'''		'''As a delivery proxy'''

−	The default approach integrates DSPAM directly with the mail server and filters spam as mail comes in. Please see the appropriate instructions in the [[#MTA_SPECIFIC_INTEGRATION]] section or the files in doc/ pertaining to your MTA.	+	The default approach integrates DSPAM directly with the mail server and filters spam as mail comes in. Please see the appropriate instructions in the [[#MTA_SPECIFIC_INTEGRATION\|MTA Specific Integration]] section or the files in doc/ pertaining to your MTA.

← Older revision		Revision as of 19:18, 12 June 2009
Line 9:		Line 9:
	'''As a delivery proxy'''		'''As a delivery proxy'''

−	The default approach integrates DSPAM directly with the mail server and filters spam as mail comes in. Please see the appropriate instructions in the [[#~~MTA Specific~~]] section or the files in doc/ pertaining to your MTA.	+	The default approach integrates DSPAM directly with the mail server and filters spam as mail comes in. Please see the appropriate instructions in the [[#MTA_SPECIFIC_INTEGRATION]] section or the files in doc/ pertaining to your MTA.

← Older revision		Revision as of 19:18, 12 June 2009
Line 9:		Line 9:
	'''As a delivery proxy'''		'''As a delivery proxy'''

−	The default approach integrates DSPAM directly with the mail server and filters spam as mail comes in. Please see the appropriate instructions in doc/ pertaining to your MTA.	+	The default approach integrates DSPAM directly with the mail server and filters spam as mail comes in. Please see the appropriate instructions in the [[#MTA Specific]] section or the files in doc/ pertaining to your MTA.

@@ Line 117: / Line 117: @@
 *[[DSpam_DBMAIL_INTEGRATION|DBMail]]
 *[[DSpam_EXCHANGE_INTEGRATION|Exchange]]
-[[DSpam_RELAY|INTEGRATION/Relay]]
+*[[DSpam_RELAY|Relay]]
-*[[DSpam_POP3FILTER|INTEGRATION/POP3 Filter]]
+*[[DSpam_POP3FILTER|POP3 Filter]]
 [[Category:DSpam]]

@@ Line 15: / Line 15: @@
 '''As a POP3 proxy'''
-This alternative approach implements a POP3 proxy where users connect to the proxy to check their email, and email is filtered when being downloaded.  The POP3 proxy is a much easier approach, as it requires much less integration work with the mail server (and is ideal for implementing DSPAM on Exchange, etcetera). Please see the file doc/pop3filter.txt.
+This alternative approach implements a POP3 proxy where users connect to the proxy to check their email, and email is filtered when being downloaded.  The POP3 proxy is a much easier approach, as it requires much less integration work with the mail server (and is ideal for implementing DSPAM on Exchange, etcetera). Please see the [[DSpam_POP3FILTER|INTEGRATION/POP3 Filter]] section or the file doc/pop3filter.txt.
@@ Line 21: / Line 21: @@
 '''As an SMTP Relay'''
-DSPAM can be configured as an SMTP relay, a.k.a appliance. You can set it up to sit in front of your real mail server and then point your MX records at it. DSPAM will then pass along the good mail to your real SMTP server. See doc/relay.txt for more information. The example provided uses Postfix and MySQL.
+DSPAM can be configured as an SMTP relay, a.k.a appliance. You can set it up to sit in front of your real mail server and then point your MX records at it. DSPAM will then pass along the good mail to your real SMTP server. See the [[DSpam_RELAY|INTEGRATION/Relay]] section or doc/relay.txt for more information. The example provided uses Postfix and MySQL.

@@ Line 115: / Line 115: @@
 *[[DSpam_SENDMAIL_INTEGRATION|Sendmail]]
 *[[DSpam_QMAIL_INTEGRATION|QMail]]
 *[[DSpam_EXCHANGE_INTEGRATION|Exchange]]
 [[Category:DSpam]]