Update of /cvsroot/tmda/tmda/htdocs
In directory usw-pr-cvs1:/tmp/cvs-serv9060/htdocs
Modified Files:
config-vars.ht config-vars.html filter-sources.ht
filter-sources.html
Log Message:
Add support for the ``X-Primary-Address'' header in order to
help users of challenge/response systems like TMDA interact more
seamlessly.
Previously, when TMDA users interacted, there was no way for the user
to specify which address he prefers be "whitelisted" after he
successfully confirmed his first message. This problem was
exacerbated by use of 'dated' addresses, since you'd have to confirm
each of your messages over and over until the recipient stepped in and
manually added a "wildcard" entry for you.
We now support a header called ``X-Primary-Address'' which allows the
user to specify the address he prefers be whitelisted. A general name
was chosen for this header to encourage other C/R systems to adopt it.
The take advantage of this feature, you should configure your MUA to
add an X-Primary-Address: address field to your outgoing message. e.g,
X-Primary-Address: [EMAIL PROTECTED]
If you use tmda-sendmail or tmda-ofmipd to send your outgoing mail,
you can do this with an `ADDED_HEADERS_CLIENT' entry in your
~/.tmda/config.
Now, if an incoming message contains an ``X-Primary-Address'' header,
TMDA will CONFIRM_APPEND that address instead of the Return-Path address
when the message is confirmed.
TMDA will also check the address in ``X-Primary-Address'' against
FILTER_INCOMING along with the envelope sender, From and Reply-To.
To limit the potential for abuse where a sender would specify an
external address to get it whitelisted, TMDA will only honor
``X-Primary-Address'' if the address looks sufficiently similar to the
envelope sender address. If not, TMDA falls back on using the envelope
sender address instead. The necessary degree of closeness can be tuned
by setting the PRIMARY_ADDRESS_MATCH variable. The default setting is
to accept if the domains of the addresses match. This should be
flexible enough to cover most users while still greatly limiting
potential abuse.
Overall, this mechanism should reduce the amount of thinking and
planning ahead you need to do when sending mail to a new correspondent
who may or may not use a C/R system.
Thanks to Gre7g Luterman for this idea.
Index: config-vars.ht
===================================================================
RCS file: /cvsroot/tmda/tmda/htdocs/config-vars.ht,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- config-vars.ht 9 Nov 2002 00:56:31 -0000 1.8
+++ config-vars.ht 13 Nov 2002 01:56:54 -0000 1.9
@@ -139,62 +139,64 @@
</tr>
<tr>
<td><a href="#PENDING_WHITELIST_APPEND">PENDING_WHITELIST_APPEND</a></td>
-<td><a href="#PURGED_HEADERS">PURGED_HEADERS</a></td>
+<td><a href="#PRIMARY_ADDRESS_MATCH">PRIMARY_ADDRESS_MATCH</a></td>
</tr>
<tr>
+<td><a href="#PURGED_HEADERS">PURGED_HEADERS</a></td>
<td><a href="#RECIPIENT_DELIMITER">RECIPIENT_DELIMITER</a></td>
-<td><a href="#RECIPIENT_HEADER">RECIPIENT_HEADER</a></td>
</tr>
<tr>
+<td><a href="#RECIPIENT_HEADER">RECIPIENT_HEADER</a></td>
<td><a href="#RESPONSE_DIR">RESPONSE_DIR</a></td>
-<td><a href="#SENDER_TEMPLATE_VARS">SENDER_TEMPLATE_VARS</a></td>
</tr>
<tr>
+<td><a href="#SENDER_TEMPLATE_VARS">SENDER_TEMPLATE_VARS</a></td>
<td><a href="#SENDMAIL_PROGRAM">SENDMAIL_PROGRAM</a></td>
-<td><a href="#SMTPAUTH_PASSWORD">SMTPAUTH_PASSWORD</a></td>
</tr>
<tr>
+<td><a href="#SMTPAUTH_PASSWORD">SMTPAUTH_PASSWORD</a></td>
<td><a href="#SMTPAUTH_USERNAME">SMTPAUTH_USERNAME</a></td>
-<td><a href="#SMTPHOST">SMTPHOST</a></td>
</tr>
<tr>
+<td><a href="#SMTPHOST">SMTPHOST</a></td>
<td><a href="#SMTPSSL">SMTPSSL</a></td>
-<td><a href="#SMTPSSL_CERTFILE">SMTPSSL_CERTFILE</a></td>
</tr>
<tr>
+<td><a href="#SMTPSSL_CERTFILE">SMTPSSL_CERTFILE</a></td>
<td><a href="#SMTPSSL_KEYFILE">SMTPSSL_KEYFILE</a></td>
-<td><a
href="#SMTP_MAX_SESSIONS_PER_CONNECTION">SMTP_MAX_SESSIONS_PER_CONNECTION</a></td>
</tr>
<tr>
+<td><a
+href="#SMTP_MAX_SESSIONS_PER_CONNECTION">SMTP_MAX_SESSIONS_PER_CONNECTION</a></td>
<td><a href="#SUMMARY_HEADERS">SUMMARY_HEADERS</a></td>
-<td><a href="#TAGS_CONFIRM">TAGS_CONFIRM</a></td>
</tr>
<tr>
+<td><a href="#TAGS_CONFIRM">TAGS_CONFIRM</a></td>
<td><a href="#TAGS_DATED">TAGS_DATED</a></td>
-<td><a href="#TAGS_KEYWORD">TAGS_KEYWORD</a></td>
</tr>
<tr>
+<td><a href="#TAGS_KEYWORD">TAGS_KEYWORD</a></td>
<td><a href="#TAGS_SENDER">TAGS_SENDER</a></td>
-<td><a href="#TEMPLATE_DIR">TEMPLATE_DIR</a></td>
</tr>
<tr>
+<td><a href="#TEMPLATE_DIR">TEMPLATE_DIR</a></td>
<td><a href="#TEMPLATE_DIR_MATCH_SENDER">TEMPLATE_DIR_MATCH_SENDER</a></td>
-<td><a href="#TEMPLATE_EMAIL_HEADERS">TEMPLATE_EMAIL_HEADERS</a></td>
</tr>
<tr>
+<td><a href="#TEMPLATE_EMAIL_HEADERS">TEMPLATE_EMAIL_HEADERS</a></td>
<td><a href="#TEMPLATE_ENCODED_HEADERS">TEMPLATE_ENCODED_HEADERS</a></td>
-<td><a href="#TERSE_SUMMARY_HEADERS">TERSE_SUMMARY_HEADERS</a></td>
</tr>
<tr>
+<td><a href="#TERSE_SUMMARY_HEADERS">TERSE_SUMMARY_HEADERS</a></td>
<td><a href="#TIMEOUT">TIMEOUT</a></td>
-<td><a href="#USERNAME">USERNAME</a></td>
</tr>
<tr>
+<td><a href="#USERNAME">USERNAME</a></td>
<td><a href="#USEVIRTUALDOMAINS">USEVIRTUALDOMAINS</a></td>
-<td><a href="#VIRTUALDOMAINS">VIRTUALDOMAINS</a></td>
</tr>
<tr>
+<td><a href="#VIRTUALDOMAINS">VIRTUALDOMAINS</a></td>
<td><a href="#X_TMDA_IN_SUBJECT">X_TMDA_IN_SUBJECT</a></td>
+</tr>
</table>
<dl>
@@ -996,6 +998,43 @@
<code>PENDING_WHITELIST_APPEND = "/full/path/to/whitelist"</code>
<br><br>
No default
+<dt><hr>
+<a name="PRIMARY_ADDRESS_MATCH"><h4>PRIMARY_ADDRESS_MATCH</h4></a>
+<dd>
+An integer which controls how closely the address in the
+``X-Primary-Address'' header of an incoming messages must match the
+envelope sender address before it's honored.
+<br><br>
+If the match is close enough, this address will be used for
+CONFIRM_APPEND instead of the envelope sender, and also added to the
+list of addresses checked against FILTER_INCOMING.
+<br><br>
+This option is available to limit cases of abuse where a sender
+attempts to "whitelist" an address not his own by using an external
+address in an ``X-Primary-Address'' header.
+<br><br>
+Available options:
+<br><br>
+0 - Never a match. Equivalent to disabling X-Primary-Address recognition.
+<br><br>
+1 - Identical addresses match. e.g, [EMAIL PROTECTED] and
[EMAIL PROTECTED]
+<br><br>
+2 - Usernames and hostnames must match. e.g, [EMAIL PROTECTED] and
[EMAIL PROTECTED]
+<br><br>
+3 - Usernames and domains must match. e.g, [EMAIL PROTECTED] and
[EMAIL PROTECTED]
+<br><br>
+4 - Hostnames must match. e.g, [EMAIL PROTECTED] and
[EMAIL PROTECTED]
+<br><br>
+5 - Domains must match. e.g, [EMAIL PROTECTED] and
[EMAIL PROTECTED]
+<br><br>
+6 - Always a match. e.g, [EMAIL PROTECTED] and [EMAIL PROTECTED]
+<br><br>
+Default is 5
<dt><hr>
<a name="PURGED_HEADERS"><h4>PURGED_HEADERS</h4></a>
<dd>
Index: config-vars.html
===================================================================
RCS file: /cvsroot/tmda/tmda/htdocs/config-vars.html,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -r1.10 -r1.11
--- config-vars.html 9 Nov 2002 00:56:31 -0000 1.10
+++ config-vars.html 13 Nov 2002 01:56:54 -0000 1.11
@@ -1,6 +1,6 @@
<HTML>
<!-- THIS PAGE IS AUTOMATICALLY GENERATED. DO NOT EDIT. -->
-<!-- Fri Nov 8 17:54:10 2002 -->
+<!-- Tue Nov 12 17:47:17 2002 -->
<!-- USING HT2HTML 1.2 -->
<!-- SEE http://barry.wooz.org/software/ht2html -->
<!-- User-specified headers:
@@ -301,62 +301,64 @@
</tr>
<tr>
<td><a href="#PENDING_WHITELIST_APPEND">PENDING_WHITELIST_APPEND</a></td>
-<td><a href="#PURGED_HEADERS">PURGED_HEADERS</a></td>
+<td><a href="#PRIMARY_ADDRESS_MATCH">PRIMARY_ADDRESS_MATCH</a></td>
</tr>
<tr>
+<td><a href="#PURGED_HEADERS">PURGED_HEADERS</a></td>
<td><a href="#RECIPIENT_DELIMITER">RECIPIENT_DELIMITER</a></td>
-<td><a href="#RECIPIENT_HEADER">RECIPIENT_HEADER</a></td>
</tr>
<tr>
+<td><a href="#RECIPIENT_HEADER">RECIPIENT_HEADER</a></td>
<td><a href="#RESPONSE_DIR">RESPONSE_DIR</a></td>
-<td><a href="#SENDER_TEMPLATE_VARS">SENDER_TEMPLATE_VARS</a></td>
</tr>
<tr>
+<td><a href="#SENDER_TEMPLATE_VARS">SENDER_TEMPLATE_VARS</a></td>
<td><a href="#SENDMAIL_PROGRAM">SENDMAIL_PROGRAM</a></td>
-<td><a href="#SMTPAUTH_PASSWORD">SMTPAUTH_PASSWORD</a></td>
</tr>
<tr>
+<td><a href="#SMTPAUTH_PASSWORD">SMTPAUTH_PASSWORD</a></td>
<td><a href="#SMTPAUTH_USERNAME">SMTPAUTH_USERNAME</a></td>
-<td><a href="#SMTPHOST">SMTPHOST</a></td>
</tr>
<tr>
+<td><a href="#SMTPHOST">SMTPHOST</a></td>
<td><a href="#SMTPSSL">SMTPSSL</a></td>
-<td><a href="#SMTPSSL_CERTFILE">SMTPSSL_CERTFILE</a></td>
</tr>
<tr>
+<td><a href="#SMTPSSL_CERTFILE">SMTPSSL_CERTFILE</a></td>
<td><a href="#SMTPSSL_KEYFILE">SMTPSSL_KEYFILE</a></td>
-<td><a
href="#SMTP_MAX_SESSIONS_PER_CONNECTION">SMTP_MAX_SESSIONS_PER_CONNECTION</a></td>
</tr>
<tr>
+<td><a
+href="#SMTP_MAX_SESSIONS_PER_CONNECTION">SMTP_MAX_SESSIONS_PER_CONNECTION</a></td>
<td><a href="#SUMMARY_HEADERS">SUMMARY_HEADERS</a></td>
-<td><a href="#TAGS_CONFIRM">TAGS_CONFIRM</a></td>
</tr>
<tr>
+<td><a href="#TAGS_CONFIRM">TAGS_CONFIRM</a></td>
<td><a href="#TAGS_DATED">TAGS_DATED</a></td>
-<td><a href="#TAGS_KEYWORD">TAGS_KEYWORD</a></td>
</tr>
<tr>
+<td><a href="#TAGS_KEYWORD">TAGS_KEYWORD</a></td>
<td><a href="#TAGS_SENDER">TAGS_SENDER</a></td>
-<td><a href="#TEMPLATE_DIR">TEMPLATE_DIR</a></td>
</tr>
<tr>
+<td><a href="#TEMPLATE_DIR">TEMPLATE_DIR</a></td>
<td><a href="#TEMPLATE_DIR_MATCH_SENDER">TEMPLATE_DIR_MATCH_SENDER</a></td>
-<td><a href="#TEMPLATE_EMAIL_HEADERS">TEMPLATE_EMAIL_HEADERS</a></td>
</tr>
<tr>
+<td><a href="#TEMPLATE_EMAIL_HEADERS">TEMPLATE_EMAIL_HEADERS</a></td>
<td><a href="#TEMPLATE_ENCODED_HEADERS">TEMPLATE_ENCODED_HEADERS</a></td>
-<td><a href="#TERSE_SUMMARY_HEADERS">TERSE_SUMMARY_HEADERS</a></td>
</tr>
<tr>
+<td><a href="#TERSE_SUMMARY_HEADERS">TERSE_SUMMARY_HEADERS</a></td>
<td><a href="#TIMEOUT">TIMEOUT</a></td>
-<td><a href="#USERNAME">USERNAME</a></td>
</tr>
<tr>
+<td><a href="#USERNAME">USERNAME</a></td>
<td><a href="#USEVIRTUALDOMAINS">USEVIRTUALDOMAINS</a></td>
-<td><a href="#VIRTUALDOMAINS">VIRTUALDOMAINS</a></td>
</tr>
<tr>
+<td><a href="#VIRTUALDOMAINS">VIRTUALDOMAINS</a></td>
<td><a href="#X_TMDA_IN_SUBJECT">X_TMDA_IN_SUBJECT</a></td>
+</tr>
</table>
<dl>
@@ -1158,6 +1160,43 @@
<code>PENDING_WHITELIST_APPEND = "/full/path/to/whitelist"</code>
<br><br>
No default
+<dt><hr>
+<a name="PRIMARY_ADDRESS_MATCH"><h4>PRIMARY_ADDRESS_MATCH</h4></a>
+<dd>
+An integer which controls how closely the address in the
+``X-Primary-Address'' header of an incoming messages must match the
+envelope sender address before it's honored.
+<br><br>
+If the match is close enough, this address will be used for
+CONFIRM_APPEND instead of the envelope sender, and also added to the
+list of addresses checked against FILTER_INCOMING.
+<br><br>
+This option is available to limit cases of abuse where a sender
+attempts to "whitelist" an address not his own by using an external
+address in an ``X-Primary-Address'' header.
+<br><br>
+Available options:
+<br><br>
+0 - Never a match. Equivalent to disabling X-Primary-Address recognition.
+<br><br>
+1 - Identical addresses match. e.g, [EMAIL PROTECTED] and
[EMAIL PROTECTED]
+<br><br>
+2 - Usernames and hostnames must match. e.g, [EMAIL PROTECTED] and
[EMAIL PROTECTED]
+<br><br>
+3 - Usernames and domains must match. e.g, [EMAIL PROTECTED] and
[EMAIL PROTECTED]
+<br><br>
+4 - Hostnames must match. e.g, [EMAIL PROTECTED] and
[EMAIL PROTECTED]
+<br><br>
+5 - Domains must match. e.g, [EMAIL PROTECTED] and
[EMAIL PROTECTED]
+<br><br>
+6 - Always a match. e.g, [EMAIL PROTECTED] and [EMAIL PROTECTED]
+<br><br>
+Default is 5
<dt><hr>
<a name="PURGED_HEADERS"><h4>PURGED_HEADERS</h4></a>
<dd>
Index: filter-sources.ht
===================================================================
RCS file: /cvsroot/tmda/tmda/htdocs/filter-sources.ht,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- filter-sources.ht 18 Aug 2002 22:52:43 -0000 1.1
+++ filter-sources.ht 13 Nov 2002 01:56:54 -0000 1.2
@@ -14,6 +14,19 @@
filter files.
<br><br>
+<strong>NOTE:</strong> <br>
+
+In order to find a match, the <code>from-*</code> sources examine the
+envelope sender address, any addresses in the From header field (not the UNIX
+mbox separator From_), any addresses in the Reply-To header field, and
+the address in the X-Primary-Address header field if the
+<a href="config-vars.html#PRIMARY_ADDRESS_MATCH">PRIMARY_ADDRESS_MATCH</a>
+setting can be satisfied.
+<br><br>
+The <code>to-*</code> sources examine the envelope recipient address but
+<i>not</i> the To header field, which is often bogus in spam email.
+<br><br>
+
<dl>
<dt>
<code>
@@ -29,18 +42,6 @@
<br><br>
-The <code>from</code> source examines the envelope sender, any
-addresses in the From header field (not the UNIX mbox separator From_)
-and any addresses in the Reply-To header field in order to find a
-match.
-
-<br><br>
-
-The <code>to</code> source examines the envelope recipient but
-<i>not</i> the To header field, which is often bogus in spam email.
-
-<br><br>
-
<dt>
<code>
from-file [ <a href="#autoflags">-autocdb</a> |
@@ -77,17 +78,6 @@
<br><br>
-The <code>from-file</code> source examines the envelope sender, any
-addresses in the From header field (not the UNIX mbox separator From_)
-and any addresses in the Reply-To header field in order to find a
-match.
-
-<br><br>
-
-The <code>to-file</code> source examines the envelope recipient but
-<i>not</i> the To header field, which is often bogus in spam email.
-
-<br><br>
<dt>
<code>
@@ -112,18 +102,6 @@
<br><br>
-The <code>from-cdb</code> source examines the envelope sender, any
-addresses in the From header field (not the UNIX mbox separator From_)
-and any addresses in the Reply-To header field in order to find a
-match.
-
-<br><br>
-
-The <code>to-cdb</code> source examines the envelope recipient but
-<i>not</i> the To header field, which is often bogus in spam email.
-
-<br><br>
-
<dt>
<code>
from-dbm [ -optional ] <a href="#db_file"><database.db></a><br>
@@ -147,17 +125,6 @@
<br><br>
-The <code>from-dbm</code> source examines the envelope sender, any
-addresses in the From header field (not the UNIX mbox separator From_)
-and any addresses in the Reply-To header field in order to find a
-match.
-
-<br><br>
-
-The <code>to-dbm</code> source examines the envelope recipient but
-<i>not</i> the To header field, which is often bogus in spam email.
-
-<br><br>
<dt>
<code>
@@ -182,17 +149,6 @@
<br><br>
-The <code>from-ezmlm</code> source examines the envelope sender, any
-addresses in the From header field (not the UNIX mbox separator From_)
-and any addresses in the Reply-To header field in order to find a
-match.
-
-<br><br>
-
-The <code>to-ezmlm</code> source examines the envelope recipient but
-<i>not</i> the To header field, which is often bogus in spam email.
-
-<br><br>
<dt>
<code>
@@ -210,7 +166,7 @@
<br><br>
The <code>-mailman</code> sources require you to specify an
-`attribute' to search. Use the <code>-attr=<attribute></code> flag to
+`attribute' to search. Use the <code>-attr=attribute</code> flag to
specify the name of an attribute contained in the database. For
example, `members' (subscriber addresses), `digest_members' (digest
subscriber addresses), or `owner' (list owner's address).
@@ -221,18 +177,6 @@
file is not an error. If the file should exist, don't specify this
flag; the parser will log an error and will defer the mail so that you
have a chance to fix the problem.
-
-<br><br>
-
-The <code>from-mailman</code> source examines the envelope sender, any
-addresses in the From header field (not the UNIX mbox separator From_)
-and any addresses in the Reply-To header field in order to find a
-match.
-
-<br><br>
-
-The <code>to-mailman</code> source examines the envelope recipient but
-<i>not</i> the To header field, which is often bogus in spam email.
<br><br>
Index: filter-sources.html
===================================================================
RCS file: /cvsroot/tmda/tmda/htdocs/filter-sources.html,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- filter-sources.html 25 Oct 2002 02:01:46 -0000 1.4
+++ filter-sources.html 13 Nov 2002 01:56:54 -0000 1.5
@@ -1,6 +1,6 @@
<HTML>
<!-- THIS PAGE IS AUTOMATICALLY GENERATED. DO NOT EDIT. -->
-<!-- Thu Oct 24 19:59:44 2002 -->
+<!-- Tue Nov 12 18:23:49 2002 -->
<!-- USING HT2HTML 1.2 -->
<!-- SEE http://barry.wooz.org/software/ht2html -->
<!-- User-specified headers:
@@ -176,6 +176,19 @@
filter files.
<br><br>
+<strong>NOTE:</strong> <br>
+
+In order to find a match, the <code>from-*</code> sources examine the
+envelope sender address, any addresses in the From header field (not the UNIX
+mbox separator From_), any addresses in the Reply-To header field, and
+the address in the X-Primary-Address header field if the
+<a href="config-vars.html#PRIMARY_ADDRESS_MATCH">PRIMARY_ADDRESS_MATCH</a>
+setting can be satisfied.
+<br><br>
+The <code>to-*</code> sources examine the envelope recipient address but
+<i>not</i> the To header field, which is often bogus in spam email.
+<br><br>
+
<dl>
<dt>
<code>
@@ -191,18 +204,6 @@
<br><br>
-The <code>from</code> source examines the envelope sender, any
-addresses in the From header field (not the UNIX mbox separator From_)
-and any addresses in the Reply-To header field in order to find a
-match.
-
-<br><br>
-
-The <code>to</code> source examines the envelope recipient but
-<i>not</i> the To header field, which is often bogus in spam email.
-
-<br><br>
-
<dt>
<code>
from-file [ <a href="#autoflags">-autocdb</a> |
@@ -239,17 +240,6 @@
<br><br>
-The <code>from-file</code> source examines the envelope sender, any
-addresses in the From header field (not the UNIX mbox separator From_)
-and any addresses in the Reply-To header field in order to find a
-match.
-
-<br><br>
-
-The <code>to-file</code> source examines the envelope recipient but
-<i>not</i> the To header field, which is often bogus in spam email.
-
-<br><br>
<dt>
<code>
@@ -274,18 +264,6 @@
<br><br>
-The <code>from-cdb</code> source examines the envelope sender, any
-addresses in the From header field (not the UNIX mbox separator From_)
-and any addresses in the Reply-To header field in order to find a
-match.
-
-<br><br>
-
-The <code>to-cdb</code> source examines the envelope recipient but
-<i>not</i> the To header field, which is often bogus in spam email.
-
-<br><br>
-
<dt>
<code>
from-dbm [ -optional ] <a href="#db_file"><database.db></a><br>
@@ -309,17 +287,6 @@
<br><br>
-The <code>from-dbm</code> source examines the envelope sender, any
-addresses in the From header field (not the UNIX mbox separator From_)
-and any addresses in the Reply-To header field in order to find a
-match.
-
-<br><br>
-
-The <code>to-dbm</code> source examines the envelope recipient but
-<i>not</i> the To header field, which is often bogus in spam email.
-
-<br><br>
<dt>
<code>
@@ -344,17 +311,6 @@
<br><br>
-The <code>from-ezmlm</code> source examines the envelope sender, any
-addresses in the From header field (not the UNIX mbox separator From_)
-and any addresses in the Reply-To header field in order to find a
-match.
-
-<br><br>
-
-The <code>to-ezmlm</code> source examines the envelope recipient but
-<i>not</i> the To header field, which is often bogus in spam email.
-
-<br><br>
<dt>
<code>
@@ -372,7 +328,7 @@
<br><br>
The <code>-mailman</code> sources require you to specify an
-`attribute' to search. Use the <code>-attr=<attribute></code> flag to
+`attribute' to search. Use the <code>-attr=attribute</code> flag to
specify the name of an attribute contained in the database. For
example, `members' (subscriber addresses), `digest_members' (digest
subscriber addresses), or `owner' (list owner's address).
@@ -383,18 +339,6 @@
file is not an error. If the file should exist, don't specify this
flag; the parser will log an error and will defer the mail so that you
have a chance to fix the problem.
-
-<br><br>
-
-The <code>from-mailman</code> source examines the envelope sender, any
-addresses in the From header field (not the UNIX mbox separator From_)
-and any addresses in the Reply-To header field in order to find a
-match.
-
-<br><br>
-
-The <code>to-mailman</code> source examines the envelope recipient but
-<i>not</i> the To header field, which is often bogus in spam email.
<br><br>
_______________________________________
tmda-cvs mailing list
http://tmda.net/lists/listinfo/tmda-cvs
