logo       
Google Custom Search
    AddThis Social Bookmark Button
-->

CVS: tmda/htdocs config-client.ht,1.30,1.31 config-client.html,1.54,1.55 co: msg#00005

Subject: CVS: tmda/htdocs config-client.ht,1.30,1.31 config-client.html,1.54,1.55 config-filter.ht,1.24,1.25 config-filter.html,1.45,1.46 config-pre.ht,1.17,1.18 config-pre.html,1.39,1.40 config-server.ht,1.25,1.26 config-server.html,1.50,1.51 requirements.ht,1.20,1.21 requirements.html,1.46,1.47
Update of /cvsroot/tmda/tmda/htdocs
In directory sc8-pr-cvs1:/tmp/cvs-serv15059

Modified Files:
        config-client.ht config-client.html config-filter.ht 
        config-filter.html config-pre.ht config-pre.html 
        config-server.ht config-server.html requirements.ht 
        requirements.html 
Log Message:
Fix some typos, and also reorganize the Pre-Configuration page:

- Added a general prerequisites section explaining general
requirements such as extension addresses, and envelope 
information in the form of environment variables.

- Added a "Gripes" subsection under the Sendmail section 
explaining why using TMDA under Sendmail is so much more
difficult than under the other supported MTAs.


Index: config-client.ht
===================================================================
RCS file: /cvsroot/tmda/tmda/htdocs/config-client.ht,v
retrieving revision 1.30
retrieving revision 1.31
diff -u -r1.30 -r1.31
--- config-client.ht    12 Mar 2003 21:12:02 -0000      1.30
+++ config-client.ht    3 Jun 2003 21:31:49 -0000       1.31
@@ -216,7 +216,7 @@
 </ul>
 </ul>
 
-<li>.tmda/config configuration:<br><br>
+<li>~/.tmda/config configuration:<br><br>
 
 Make sure that your <b>crypt_key</b> file is the same
 on both your mail server and your mail client -- they must match.

Index: config-client.html
===================================================================
RCS file: /cvsroot/tmda/tmda/htdocs/config-client.html,v
retrieving revision 1.54
retrieving revision 1.55
diff -u -r1.54 -r1.55
--- config-client.html  18 Apr 2003 22:07:51 -0000      1.54
+++ config-client.html  3 Jun 2003 21:31:49 -0000       1.55
@@ -1,7 +1,7 @@
 <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
 <html>
 <!-- THIS PAGE IS AUTOMATICALLY GENERATED.  DO NOT EDIT. -->
-<!-- Fri Apr 18 17:05:33 2003 -->
+<!-- Tue Jun  3 13:55:13 2003 -->
 <!-- USING HT2HTML 2.0 -->
 <!-- SEE http://ht2html.sf.net -->
 <!-- User-specified headers:
@@ -401,7 +401,7 @@
 </ul>
 </ul>
 
-<li>.tmda/config configuration:<br><br>
+<li>~/.tmda/config configuration:<br><br>
 
 Make sure that your <b>crypt_key</b> file is the same
 on both your mail server and your mail client -- they must match.

Index: config-filter.ht
===================================================================
RCS file: /cvsroot/tmda/tmda/htdocs/config-filter.ht,v
retrieving revision 1.24
retrieving revision 1.25
diff -u -r1.24 -r1.25
--- config-filter.ht    12 Mar 2003 21:12:03 -0000      1.24
+++ config-filter.ht    3 Jun 2003 21:31:49 -0000       1.25
@@ -7,7 +7,7 @@
 disposed of.  For outgoing, it controls how the message is tagged.
 The incoming filter file default is <b>~/.tmda/filters/incoming</b>,
 which can be changed by setting <b>FILTER_INCOMING</b> in your
-<b>tmda/config</b>.  The outgoing filter file default is
+<b>~/.tmda/config</b>.  The outgoing filter file default is
 <b>~/.tmda/filters/outgoing</b>, which can be changed by setting
 <b>FILTER_OUTGOING</b>.  
 <br><br>
@@ -402,7 +402,7 @@
 <br><br>
 
 A variable name is looked up first in the Defaults namespace (all of
-the configuration variables set in Defaults.py or your .tmda/config) and
+the configuration variables set in Defaults.py or your ~/.tmda/config) and
 then in the environment if it was not found in the Defaults
 namespace.  If it is still not found, the parser generates an error
 and the mail is deferred.  Variable names are case-sensitive.

Index: config-filter.html
===================================================================
RCS file: /cvsroot/tmda/tmda/htdocs/config-filter.html,v
retrieving revision 1.45
retrieving revision 1.46
diff -u -r1.45 -r1.46
--- config-filter.html  18 Apr 2003 22:07:51 -0000      1.45
+++ config-filter.html  3 Jun 2003 21:31:49 -0000       1.46
@@ -1,7 +1,7 @@
 <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
 <html>
 <!-- THIS PAGE IS AUTOMATICALLY GENERATED.  DO NOT EDIT. -->
-<!-- Fri Apr 18 17:05:33 2003 -->
+<!-- Tue Jun  3 13:55:13 2003 -->
 <!-- USING HT2HTML 2.0 -->
 <!-- SEE http://ht2html.sf.net -->
 <!-- User-specified headers:
@@ -192,7 +192,7 @@
 disposed of.  For outgoing, it controls how the message is tagged.
 The incoming filter file default is <b>~/.tmda/filters/incoming</b>,
 which can be changed by setting <b>FILTER_INCOMING</b> in your
-<b>tmda/config</b>.  The outgoing filter file default is
+<b>~/.tmda/config</b>.  The outgoing filter file default is
 <b>~/.tmda/filters/outgoing</b>, which can be changed by setting
 <b>FILTER_OUTGOING</b>.  
 <br><br>
@@ -587,7 +587,7 @@
 <br><br>
 
 A variable name is looked up first in the Defaults namespace (all of
-the configuration variables set in Defaults.py or your .tmda/config) and
+the configuration variables set in Defaults.py or your ~/.tmda/config) and
 then in the environment if it was not found in the Defaults
 namespace.  If it is still not found, the parser generates an error
 and the mail is deferred.  Variable names are case-sensitive.

Index: config-pre.ht
===================================================================
RCS file: /cvsroot/tmda/tmda/htdocs/config-pre.ht,v
retrieving revision 1.17
retrieving revision 1.18
diff -u -r1.17 -r1.18
--- config-pre.ht       18 Apr 2003 21:46:26 -0000      1.17
+++ config-pre.ht       3 Jun 2003 21:31:50 -0000       1.18
@@ -2,15 +2,61 @@
 
 <h3>TMDA Pre-Configuration</h3>
 
-You may need to make some system-wide configuration changes to your
-MTA software depending on which one you are running (in order of ease):
-<br><br>
+<h4>MTA Configuration</h4>
 
-[ <A HREF="#qmail">qmail/Courier</a> | <A HREF="#postfix">Postfix</a> | <A 
HREF="#exim">Exim</a>  
+You may need to make some system-wide configuration changes to your
+MTA software depending on which one you are running.  
+First read the <a href="#general">General Prerequisites</a> section,
+and then read the set of instructions corresponding to your MTA:<br>
+[ <A HREF="#qmail">qmail/Courier</a> 
+| <A HREF="#postfix">Postfix</a> | <A HREF="#exim">Exim</a>  
 | <A HREF="#sendmail">Sendmail</a> ]
 <br><br>
 <hr>
 
+<A name="general"><h4>General Prerequisites</h4></a>
+
+<u>Extension Addresses</u><br><br>
+TMDA is heavily based on user "extension addresses" (e.g,
+username+extension@xxxxxxxxxxxxxx), and your MTA must be able
+to understand them.  Some of the supported MTAs do by default,
+others must be configured to do so.<br><br>
+
+The character that separates the username from the extension in an
+extension address is often called the "recipient delimiter".  The most
+popular choices are <code><b>+</b></code> and <code><b>-</b></code>,
+although the <a href="http://tmda.net/faq.cgi?req=all#3.5"; TARGET="Resource 
Window">
+hyphen is recommended</a>.
+TMDA can support any recipient delimiter character though, just make sure you
+use the same character for your <b>RECIPIENT_DELIMITER</b> setting in
+<b>~/.tmda/config</b>.<br><br>
+
+<u>Environment Variables</u><br><br>
+TMDA receives much of its information about the envelope of
+an incoming message from environment variables set by the MTA.  Most
+importantly, <strong>SENDER</strong> (the full envelope sender address),
+<strong>RECIPIENT</strong> (the full envelope recipient address), and
+<strong>EXT</strong> or <strong>EXTENSION</strong> (the recipient
+address extension).  In order to be reliable, TMDA needs these
+<em>real</em> sender and recipient values.  It can't rely on what
+might be in the To: or From: headers.<br><br>
+
+To use TMDA, you must make sure these variables are properly
+set by the time TMDA sees the message.  TMDA expects these variables
+to be in the following format:
+
+<blockquote><pre>
+SENDER=sender@xxxxxxxxxxxxxx
+RECIPIENT=recipient+foo@xxxxxxxxxxxxxx
+EXTENSION=foo
+</blockquote></pre>
+
+That is, just the e-mail address or recipient address extension, with no
+trailing or leading whitespace, or any other extraneous characters.
+As with extension addresses, some MTAs set these variables by default,
+others must be configured to do so.<br><br>
+<hr>
+
 <a name="qmail"><h4>MTA Configuration (qmail and Courier)</h4></a>
 
 No changes need to be made to your configuration in order to use TMDA.
@@ -22,10 +68,9 @@
 <ol>
 
 <li>Enable the <strong>recipient_delimiter</strong> parameter in
-Postfix's <em>main.cf</em> if it isn't already.  The Postfix default is
-<code><b>+</b></code> but <code><b>-</b></code> is an acceptable value as
-well.  Just make sure it matches <b>RECIPIENT_DELIMITER</b> in your
-<b>tmda/config</b>.
+Postfix's <em>main.cf</em> if it isn't already.  Make sure the
+character you choose matches <b>RECIPIENT_DELIMITER</b> in your
+<b>~/.tmda/config</b>.
 
 </ol>
 <hr>
@@ -48,7 +93,6 @@
 It is recommended that you enable this option or become a
 trusted-user, or else the client side of TMDA becomes much less
 functional.
-<br><br>
 </ol>
 
 <h5>DIRECTOR/ROUTER CONFIGURATION</h5>
@@ -56,45 +100,34 @@
 <ol>
 
 <li>
-TMDA is heavily based on user "extension addresses" (e.g,
-username+extension@xxxxxxxxxx), and your Exim must be able
-to understand them.  It doesn't by default.  Both
-<code><b>+</b></code> and <code><b>-</b></code> are an acceptable
-values for the suffix, just make sure it matches
-<b>RECIPIENT_DELIMITER</b> in your <b>tmda/config</b>.
-<br><br>
-
+Exim must be configured to understand extension addresses.
 Add the following lines to both the <b>userforward</b> and 
 the <b>localuser</b> directors if they are not there already:
-<br><br>
 
 <blockquote><pre>
 suffix = -*
 # or "+*" if you prefer "user+suffix" addresses
 suffix_optional
-
 </blockquote></pre>
 
+Make sure the character you choose matches <b>RECIPIENT_DELIMITER</b> in your
+<b>~/.tmda/config</b>.<br><br>
+
 <strong>NOTE:</strong> If you are running Exim version 4.x, 
 use <em>local_part_suffix</em>
 and <em>local_part_suffix_optional</em> instead.
 You also might be interested in 
 <a href="http://mla.libertine.org/tmda-users/2002-11/msg00283.html"; 
TARGET="Resource Window">these</a> 
 Exim 4 specific instructions for a server-wide TMDA setup.
-<br><br>
 </ol>
 
 <h5>TRANSPORTS CONFIGURATION</h5>
 <ol>
 
 <li>
-TMDA receives much of its information about the envelope of
-an incoming message from environment variables set by the MTA.  Most
-importantly, <strong>SENDER</strong> (the full envelope sender address),
-<strong>RECIPIENT</strong> (the full envelope recipient address), and
-<strong>EXT</strong> or <strong>EXTENSION</strong> (the recipient
-address extension).  Exim currently sets only the first, so you
-must set the other two using the <em>environment</em> 
+Exim only sets the <strong>SENDER</strong> environment variable
+by default.  You must configure it to also set <strong>RECIPIENT</strong>
+and <strong>EXTENSION</strong> using the <em>environment</em> 
 pipe option.<br><br>
 
 <li>
@@ -105,7 +138,6 @@
 
 Set <em>return_path_add</em> and <em>environment</em> as follows under
 the <strong>address_pipe</strong> transport:
-<br><br>
 
 <blockquote><pre>
 address_pipe: 
@@ -122,34 +154,46 @@
 
 <a name="sendmail"><h4>MTA Configuration (Sendmail)</h4></a>
 
-TMDA receives much of its information about the envelope of
-an incoming message from environment variables (usually set by the MTA).  Most
-importantly, <strong>SENDER</strong> (the full envelope sender address),
-<strong>RECIPIENT</strong> (the full envelope recipient address), and
-<strong>EXT</strong> or <strong>EXTENSION</strong> (the recipient
-address extension).<br><br>
-
-The main difficulty with using TMDA under Sendmail, is that Sendmail does
-not provide such variables as the other three supported MTAs do.
-In fact, it does not provide any envelope information to commands run
-from a .forward file.  In order to be reliable, TMDA needs these
-<em>real</em> sender and recipient values.  It can't rely on what
-might be in the To: or From: headers.<br><br>
+<u>Gripes</u>
+<ol>
+<li>
+The main difficulty with using TMDA under Sendmail, is that Sendmail
+does not set any of the required environment variables as the other
+supported MTAs do.  In fact, as hard as this is to believe, Sendmail
+does not provide <b>any</b> envelope recipient information to commands run from
+a .forward file.  In today's complex mail environments, full envelope
+information in user-space is essential to support advanced
+applications such as TMDA.  It's not an accident why all the other
+supported MTAs do this; it's a good idea!<br><br>
+
+If you are stuck with
+Sendmail and find this deficiency as troubling as I do, you might
+consider sending a <a href="mailto:sendmail@xxxxxxxxxxxx";>feature request</a> 
+to the Sendmail developers asking
+that the full envelope information be made available to .forward invoked
+programs in the form of environment variables (<strong>SENDER</strong>,
+<strong>RECIPIENT</strong>, and <strong>EXTENSION</strong>).  This
+should be done regardless of whether the Sendmail installation has
+procmail configured as its local mailer or not.<br><br>
 
-So in order to use TMDA, you need some way to obtain the necessary
-envelope information and set the above mentioned environment
-variables.  It matters not how you do this, just as long as these
-variables are properly set by the time TMDA sees the message.  TMDA
-expects these variables to be in the following format:
+<li>
+Sendmail's default recipient delimiter is a plus (<code><b>+</b></code>) 
character, but
+unlike the other supported MTAs, Sendmail doesn't allow the administrator
+to change this default.  You are stick with <code><b>+</b></code> even though
+this presents <a href="http://tmda.net/faq.cgi?req=all#3.5"; TARGET="Resource 
Window">
+problems</a> that other recipient delimiters such as <code><b>-</b></code> 
+do not have.  If you find this inflexibility troubling, consider sending
+a <a href="mailto:sendmail@xxxxxxxxxxxx";>feature request</a> 
+to the Sendmail developers asking that the recipient delimiter be made 
configurable.
 
-<blockquote><pre>
-SENDER=sender@xxxxxxxxxx
-RECIPIENT=recipient@xxxxxxxxxx
-EXTENSION=foo
-</blockquote></pre>
+</ol>
 
-That is, just the e-mail address or recipient address extension, with no
-trailing or leading whitespace, or any other extraneous characters.
+<u>Configuration</u><br><br>
+In order to use TMDA, you need some way to obtain the necessary
+envelope information and set the required environment variables.  It
+matters not how you do this, just as long as these variables are
+properly set by the time TMDA sees the message.  We provide a solution
+below for sites with procmail configured as the local mailer.
 <br><br>
 
 If your Sendmail installation is using <a
@@ -158,18 +202,16 @@
 line argument to procmail, typically introduced by the "-a" flag.
 Your <b>.procmailrc</b> will then be able to construct the environment
 variables from this argument.  The necessary Sendmail configuration
-changes are covered below, and a sample .procmailrc is given in the
-next section.  <br><br>
+changes are covered below, and a sample .procmailrc is given on the
+<a href="config-server.html">Server Configuration</a> page.
 <ol>
 
 <li>Make sure procmail is installed on your server, and then add the
 following rule to your <b>sendmail.mc</b> file if it is not
 already present (most Linux distributions already define this!):
-<br><br>
 
 <blockquote><pre>
 FEATURE(`local_procmail', `/usr/bin/procmail')
-
 </blockquote></pre>
 
 <li>Now run <b>sendmail.mc</b> through <b>m4</b> to produce your new

Index: config-pre.html
===================================================================
RCS file: /cvsroot/tmda/tmda/htdocs/config-pre.html,v
retrieving revision 1.39
retrieving revision 1.40
diff -u -r1.39 -r1.40
--- config-pre.html     18 Apr 2003 22:07:52 -0000      1.39
+++ config-pre.html     3 Jun 2003 21:31:50 -0000       1.40
@@ -1,7 +1,7 @@
 <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
 <html>
 <!-- THIS PAGE IS AUTOMATICALLY GENERATED.  DO NOT EDIT. -->
-<!-- Fri Apr 18 17:05:34 2003 -->
+<!-- Tue Jun  3 15:26:57 2003 -->
 <!-- USING HT2HTML 2.0 -->
 <!-- SEE http://ht2html.sf.net -->
 <!-- User-specified headers:
@@ -187,15 +187,61 @@
 <td valign="top" width="90%" class="body"><br>
 <h3>TMDA Pre-Configuration</h3>
 
-You may need to make some system-wide configuration changes to your
-MTA software depending on which one you are running (in order of ease):
-<br><br>
+<h4>MTA Configuration</h4>
 
-[ <A HREF="#qmail">qmail/Courier</a> | <A HREF="#postfix">Postfix</a> | <A 
HREF="#exim">Exim</a>  
+You may need to make some system-wide configuration changes to your
+MTA software depending on which one you are running.  
+First read the <a href="#general">General Prerequisites</a> section,
+and then read the set of instructions corresponding to your MTA:<br>
+[ <A HREF="#qmail">qmail/Courier</a> 
+| <A HREF="#postfix">Postfix</a> | <A HREF="#exim">Exim</a>  
 | <A HREF="#sendmail">Sendmail</a> ]
 <br><br>
 <hr>
 
+<A name="general"><h4>General Prerequisites</h4></a>
+
+<u>Extension Addresses</u><br><br>
+TMDA is heavily based on user "extension addresses" (e.g,
+username+extension@xxxxxxxxxxxxxx), and your MTA must be able
+to understand them.  Some of the supported MTAs do by default,
+others must be configured to do so.<br><br>
+
+The character that separates the username from the extension in an
+extension address is often called the "recipient delimiter".  The most
+popular choices are <code><b>+</b></code> and <code><b>-</b></code>,
+although the <a href="http://tmda.net/faq.cgi?req=all#3.5"; TARGET="Resource 
Window">
+hyphen is recommended</a>.
+TMDA can support any recipient delimiter character though, just make sure you
+use the same character for your <b>RECIPIENT_DELIMITER</b> setting in
+<b>~/.tmda/config</b>.<br><br>
+
+<u>Environment Variables</u><br><br>
+TMDA receives much of its information about the envelope of
+an incoming message from environment variables set by the MTA.  Most
+importantly, <strong>SENDER</strong> (the full envelope sender address),
+<strong>RECIPIENT</strong> (the full envelope recipient address), and
+<strong>EXT</strong> or <strong>EXTENSION</strong> (the recipient
+address extension).  In order to be reliable, TMDA needs these
+<em>real</em> sender and recipient values.  It can't rely on what
+might be in the To: or From: headers.<br><br>
+
+To use TMDA, you must make sure these variables are properly
+set by the time TMDA sees the message.  TMDA expects these variables
+to be in the following format:
+
+<blockquote><pre>
+SENDER=sender@xxxxxxxxxxxxxx
+RECIPIENT=recipient+foo@xxxxxxxxxxxxxx
+EXTENSION=foo
+</blockquote></pre>
+
+That is, just the e-mail address or recipient address extension, with no
+trailing or leading whitespace, or any other extraneous characters.
+As with extension addresses, some MTAs set these variables by default,
+others must be configured to do so.<br><br>
+<hr>
+
 <a name="qmail"><h4>MTA Configuration (qmail and Courier)</h4></a>
 
 No changes need to be made to your configuration in order to use TMDA.
@@ -207,10 +253,9 @@
 <ol>
 
 <li>Enable the <strong>recipient_delimiter</strong> parameter in
-Postfix's <em>main.cf</em> if it isn't already.  The Postfix default is
-<code><b>+</b></code> but <code><b>-</b></code> is an acceptable value as
-well.  Just make sure it matches <b>RECIPIENT_DELIMITER</b> in your
-<b>tmda/config</b>.
+Postfix's <em>main.cf</em> if it isn't already.  Make sure the
+character you choose matches <b>RECIPIENT_DELIMITER</b> in your
+<b>~/.tmda/config</b>.
 
 </ol>
 <hr>
@@ -233,7 +278,6 @@
 It is recommended that you enable this option or become a
 trusted-user, or else the client side of TMDA becomes much less
 functional.
-<br><br>
 </ol>
 
 <h5>DIRECTOR/ROUTER CONFIGURATION</h5>
@@ -241,45 +285,34 @@
 <ol>
 
 <li>
-TMDA is heavily based on user "extension addresses" (e.g,
-username+extension@xxxxxxxxxx), and your Exim must be able
-to understand them.  It doesn't by default.  Both
-<code><b>+</b></code> and <code><b>-</b></code> are an acceptable
-values for the suffix, just make sure it matches
-<b>RECIPIENT_DELIMITER</b> in your <b>tmda/config</b>.
-<br><br>
-
+Exim must be configured to understand extension addresses.
 Add the following lines to both the <b>userforward</b> and 
 the <b>localuser</b> directors if they are not there already:
-<br><br>
 
 <blockquote><pre>
 suffix = -*
 # or "+*" if you prefer "user+suffix" addresses
 suffix_optional
-
 </blockquote></pre>
 
+Make sure the character you choose matches <b>RECIPIENT_DELIMITER</b> in your
+<b>~/.tmda/config</b>.<br><br>
+
 <strong>NOTE:</strong> If you are running Exim version 4.x, 
 use <em>local_part_suffix</em>
 and <em>local_part_suffix_optional</em> instead.
 You also might be interested in 
 <a href="http://mla.libertine.org/tmda-users/2002-11/msg00283.html"; 
TARGET="Resource Window">these</a> 
 Exim 4 specific instructions for a server-wide TMDA setup.
-<br><br>
 </ol>
 
 <h5>TRANSPORTS CONFIGURATION</h5>
 <ol>
 
 <li>
-TMDA receives much of its information about the envelope of
-an incoming message from environment variables set by the MTA.  Most
-importantly, <strong>SENDER</strong> (the full envelope sender address),
-<strong>RECIPIENT</strong> (the full envelope recipient address), and
-<strong>EXT</strong> or <strong>EXTENSION</strong> (the recipient
-address extension).  Exim currently sets only the first, so you
-must set the other two using the <em>environment</em> 
+Exim only sets the <strong>SENDER</strong> environment variable
+by default.  You must configure it to also set <strong>RECIPIENT</strong>
+and <strong>EXTENSION</strong> using the <em>environment</em> 
 pipe option.<br><br>
 
 <li>
@@ -290,7 +323,6 @@
 
 Set <em>return_path_add</em> and <em>environment</em> as follows under
 the <strong>address_pipe</strong> transport:
-<br><br>
 
 <blockquote><pre>
 address_pipe: 
@@ -307,34 +339,46 @@
 
 <a name="sendmail"><h4>MTA Configuration (Sendmail)</h4></a>
 
-TMDA receives much of its information about the envelope of
-an incoming message from environment variables (usually set by the MTA).  Most
-importantly, <strong>SENDER</strong> (the full envelope sender address),
-<strong>RECIPIENT</strong> (the full envelope recipient address), and
-<strong>EXT</strong> or <strong>EXTENSION</strong> (the recipient
-address extension).<br><br>
-
-The main difficulty with using TMDA under Sendmail, is that Sendmail does
-not provide such variables as the other three supported MTAs do.
-In fact, it does not provide any envelope information to commands run
-from a .forward file.  In order to be reliable, TMDA needs these
-<em>real</em> sender and recipient values.  It can't rely on what
-might be in the To: or From: headers.<br><br>
+<u>Gripes</u>
+<ol>
+<li>
+The main difficulty with using TMDA under Sendmail, is that Sendmail
+does not set any of the required environment variables as the other
+supported MTAs do.  In fact, as hard as this is to believe, Sendmail
+does not provide <b>any</b> envelope recipient information to commands run from
+a .forward file.  In today's complex mail environments, full envelope
+information in user-space is essential to support advanced
+applications such as TMDA.  It's not an accident why all the other
+supported MTAs do this; it's a good idea!<br><br>
+
+If you are stuck with
+Sendmail and find this deficiency as troubling as I do, you might
+consider sending a <a href="mailto:sendmail@xxxxxxxxxxxx";>feature request</a> 
+to the Sendmail developers asking
+that the full envelope information be made available to .forward invoked
+programs in the form of environment variables (<strong>SENDER</strong>,
+<strong>RECIPIENT</strong>, and <strong>EXTENSION</strong>).  This
+should be done regardless of whether the Sendmail installation has
+procmail configured as its local mailer or not.<br><br>
 
-So in order to use TMDA, you need some way to obtain the necessary
-envelope information and set the above mentioned environment
-variables.  It matters not how you do this, just as long as these
-variables are properly set by the time TMDA sees the message.  TMDA
-expects these variables to be in the following format:
+<li>
+Sendmail's default recipient delimiter is a plus (<code><b>+</b></code>) 
character, but
+unlike the other supported MTAs, Sendmail doesn't allow the administrator
+to change this default.  You are stick with <code><b>+</b></code> even though
+this presents <a href="http://tmda.net/faq.cgi?req=all#3.5"; TARGET="Resource 
Window">
+problems</a> that other recipient delimiters such as <code><b>-</b></code> 
+do not have.  If you find this inflexibility troubling, consider sending
+a <a href="mailto:sendmail@xxxxxxxxxxxx";>feature request</a> 
+to the Sendmail developers asking that the recipient delimiter be made 
configurable.
 
-<blockquote><pre>
-SENDER=sender@xxxxxxxxxx
-RECIPIENT=recipient@xxxxxxxxxx
-EXTENSION=foo
-</blockquote></pre>
+</ol>
 
-That is, just the e-mail address or recipient address extension, with no
-trailing or leading whitespace, or any other extraneous characters.
+<u>Configuration</u><br><br>
+In order to use TMDA, you need some way to obtain the necessary
+envelope information and set the required environment variables.  It
+matters not how you do this, just as long as these variables are
+properly set by the time TMDA sees the message.  We provide a solution
+below for sites with procmail configured as the local mailer.
 <br><br>
 
 If your Sendmail installation is using <a
@@ -343,18 +387,16 @@
 line argument to procmail, typically introduced by the "-a" flag.
 Your <b>.procmailrc</b> will then be able to construct the environment
 variables from this argument.  The necessary Sendmail configuration
-changes are covered below, and a sample .procmailrc is given in the
-next section.  <br><br>
+changes are covered below, and a sample .procmailrc is given on the
+<a href="config-server.html">Server Configuration</a> page.
 <ol>
 
 <li>Make sure procmail is installed on your server, and then add the
 following rule to your <b>sendmail.mc</b> file if it is not
 already present (most Linux distributions already define this!):
-<br><br>
 
 <blockquote><pre>
 FEATURE(`local_procmail', `/usr/bin/procmail')
-
 </blockquote></pre>
 
 <li>Now run <b>sendmail.mc</b> through <b>m4</b> to produce your new

Index: config-server.ht
===================================================================
RCS file: /cvsroot/tmda/tmda/htdocs/config-server.ht,v
retrieving revision 1.25
retrieving revision 1.26
diff -u -r1.25 -r1.26
--- config-server.ht    12 Mar 2003 21:12:06 -0000      1.25
+++ config-server.ht    3 Jun 2003 21:31:50 -0000       1.26
@@ -37,7 +37,7 @@
 filter file, the incoming message will require confirmation.  The
 lines in your filter make exceptions to that rule.  You can also
 change the default by setting <strong>ACTION_INCOMING</strong> in your
-.tmda/config.  <br><br>
+~/.tmda/config.  <br><br>
 
 The most common use for the incoming filter is to create both a 
 "whitelist" (see the FAQ) to allow your trusted contacts

Index: config-server.html
===================================================================
RCS file: /cvsroot/tmda/tmda/htdocs/config-server.html,v
retrieving revision 1.50
retrieving revision 1.51
diff -u -r1.50 -r1.51
--- config-server.html  18 Apr 2003 22:07:52 -0000      1.50
+++ config-server.html  3 Jun 2003 21:31:50 -0000       1.51
@@ -1,7 +1,7 @@
 <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
 <html>
 <!-- THIS PAGE IS AUTOMATICALLY GENERATED.  DO NOT EDIT. -->
-<!-- Fri Apr 18 17:05:34 2003 -->
+<!-- Tue Jun  3 13:55:13 2003 -->
 <!-- USING HT2HTML 2.0 -->
 <!-- SEE http://ht2html.sf.net -->
 <!-- User-specified headers:
@@ -222,7 +222,7 @@
 filter file, the incoming message will require confirmation.  The
 lines in your filter make exceptions to that rule.  You can also
 change the default by setting <strong>ACTION_INCOMING</strong> in your
-.tmda/config.  <br><br>
+~/.tmda/config.  <br><br>
 
 The most common use for the incoming filter is to create both a 
 "whitelist" (see the FAQ) to allow your trusted contacts

Index: requirements.ht
===================================================================
RCS file: /cvsroot/tmda/tmda/htdocs/requirements.ht,v
retrieving revision 1.20
retrieving revision 1.21
diff -u -r1.20 -r1.21
--- requirements.ht     28 Apr 2003 02:57:11 -0000      1.20
+++ requirements.ht     3 Jun 2003 21:31:50 -0000       1.21
@@ -14,8 +14,8 @@
 
 <br><br>
 
-<li>TMDA currently runs only on UNIX-like systems, such as GNU/Linux,
-Solaris, *BSD, etc.  It should also work on Mac OS X but not earlier
+<li>TMDA currently runs only on UNIX-based systems, such as GNU/Linux,
+Solaris, *BSD, etc.  It also works on Mac OS X, but not earlier
 versions of Mac OS.  TMDA does not currently run on 
 <a href="http://tmda.net/faq.cgi?req=all#1.3"; TARGET="Resource 
Window">Microsoft Windows</a>.
 
@@ -27,7 +27,7 @@
 <br><br>
 
 <li>If you decide to give TMDA a whirl, make sure you have the necessary
-prerequisite software installed first.
+prerequisite software installed first.<br>
 
 <ol>
 
@@ -39,13 +39,11 @@
 <strong>python2</strong> at your shell's command line:
 
 <blockquote><pre>
-
 % python
-Python 2.2.2 (#1, Oct 17 2002, 03:12:45) 
-[GCC 2.95.4 20020320 [FreeBSD]] on freebsd4
+Python 2.2.3 (#1, 06/02/03, 12:58:43) 
+[GCC Apple cpp-precomp 6.14] on darwin
 Type "help", "copyright", "credits" or "license" for more information.
 >>> ^D
-
 </pre></blockquote>
 
 <li>An SMTP server (a.k.a. mail transport agent or MTA) for mail reception.

Index: requirements.html
===================================================================
RCS file: /cvsroot/tmda/tmda/htdocs/requirements.html,v
retrieving revision 1.46
retrieving revision 1.47
diff -u -r1.46 -r1.47
--- requirements.html   28 Apr 2003 02:57:11 -0000      1.46
+++ requirements.html   3 Jun 2003 21:31:50 -0000       1.47
@@ -1,185 +1,190 @@
-<HTML>
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html>
 <!-- THIS PAGE IS AUTOMATICALLY GENERATED.  DO NOT EDIT. -->
-<!-- Sun Apr 27 20:56:20 2003 -->
-<!-- USING HT2HTML 1.2 -->
-<!-- SEE http://barry.wooz.org/software/ht2html -->
+<!-- Tue Jun  3 13:48:00 2003 -->
+<!-- USING HT2HTML 2.0 -->
+<!-- SEE http://ht2html.sf.net -->
 <!-- User-specified headers:
 Title: TMDA Requirements
 
 -->
 
-<HEAD>
-<TITLE>TMDA Requirements</TITLE>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff" TEXT="#000000"
-      TOPMARGIN="0" LEFTMARGIN="0" MARGINWIDTH="0" MARGINHEIGHT="0"
-      LINK="#0000bb"  VLINK="#551a8b"
-      ALINK="#ff0000">
+<head>
+<title>TMDA Requirements</title>
+<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
+<meta name="generator" content="HT2HTML/2.0">
+<style type="text/css">
+body { margin: 0px; }
+</style>
+</head>
+<body bgcolor="#ffffff" text="#000000"
+      marginwidth="0" marginheight="0"
+      link="#0000bb"  vlink="#551a8b"
+      alink="#ff0000">
 <!-- start of page table -->
-<TABLE WIDTH="100%" BORDER=0 CELLSPACING=0 CELLPADDING=0>
+<table width="100%" border="0" cellspacing="0" cellpadding="0">
 <!-- start of banner row -->
-<TR>
+<tr>
 <!-- start of corner cells -->
-<TD WIDTH=150 VALIGN=CENTER BGCOLOR="#afeeee">
+<td width="150" valign="middle" bgcolor="#afeeee" class="corner">
 <center><font size="+2"
-        >&gt;&gt;&gt;&nbsp;TMDA&nbsp</font></center> </TD>
-<TD WIDTH=15 BGCOLOR="#cccccc">&nbsp;&nbsp;</TD><!--spacer-->
+        >&gt;&gt;&gt;&nbsp;TMDA&nbsp</font></center> </td>
+<td width="15" bgcolor="#cccccc">&nbsp;&nbsp;</td><!--spacer-->
 <!-- end of corner cells -->
 <!-- start of banner -->
-<TD WIDTH="90%" BGCOLOR="#cccccc">
+<td width="90%" bgcolor="#cccccc" class="banner">
 <!-- start of site links table -->
-<TABLE WIDTH="100%" BORDER=0
+<table width="100%" border="0"
 CELLSPACING=0 CELLPADDING=0
-       COLS=4 ROWS=1 BGCOLOR="#ffffff">
-<TR>
-    <TD BGCOLOR="#cccccc">
+       bgcolor="#ffffff">
+<tr>
+    <td bgcolor="#cccccc">
 <a href="./index.html">TMDA Homepage</a><br>[    <a 
href="http://www.au.tmda.net/";>AU</a> |    <a 
href="http://www.us.tmda.net/";>US</a>     mirror ]
-    </TD>
-    <TD BGCOLOR="#cccccc">
+    </td>
+    <td bgcolor="#cccccc">
 <a href="http://sourceforge.net/projects/tmda";>TMDA @ SourceForge</a>
-    </TD>
-    <TD BGCOLOR="#cccccc">
-&nbsp;&nbsp;</TD>
-    <TD BGCOLOR="#cccccc">
-&nbsp;&nbsp;</TD>
-</TR>
-</TABLE><!-- end of site links table -->
-
-</TD><!-- end of banner -->
-</TR><!-- end of banner row -->
-<TR><!-- start of sidebar/body row -->
+    </td>
+    <td bgcolor="#cccccc">
+&nbsp;&nbsp;</td>
+    <td bgcolor="#cccccc">
+&nbsp;&nbsp;</td>
+</tr>
+</table><!-- end of site links table -->
+
+</td><!-- end of banner -->
+</tr><!-- end of banner row -->
+<tr><!-- start of sidebar/body row -->
 <!-- start of sidebar cells -->
-<TD WIDTH=150 VALIGN=TOP BGCOLOR="#cccccc">
+<td width="150" valign="top" bgcolor="#cccccc" class="sidebar">
 <!-- start of sidebar table -->
-<TABLE WIDTH="100%" BORDER=0 CELLSPACING=0 CELLPADDING=3
-       BGCOLOR="#ffffff">
-<TR><TD BGCOLOR="#191970"><B><FONT COLOR="#ffffff">
+<table width="100%" border="0" cellspacing="0" cellpadding="3"
+       bgcolor="#ffffff">
+<tr><td bgcolor="#191970"><b><font color="#ffffff">
 Overview
-</FONT></B></TD></TR>
-<TR><TD BGCOLOR="#cccccc">
-<A HREF="index.html">Introduction</A>
-</TD></TR>
-<TR><TD BGCOLOR="#cccccc">
-<A HREF="history.html">History</A>
-</TD></TR>
-<TR><TD BGCOLOR="#cccccc">
-<A HREF="features.html">Features</A>
-</TD></TR>
-<TR><TD BGCOLOR="#cccccc">
-<A HREF="results.html">Results &amp; Testimonials</A>
-</TD></TR>
-<TR><TD BGCOLOR="#cccccc">
-<A HREF="inuse.html">TMDA In Use</A>
-</TD></TR>
-<TR><TD BGCOLOR="#cccccc">
-<A HREF="press.html">Press Coverage</A><!-- -*- html -*- -->
-</TD></TR>
-<TR><TD BGCOLOR="#cccccc">&nbsp;
-<TR><TD BGCOLOR="#191970"><B><FONT COLOR="#ffffff">
+</font></b></td></tr>
+<tr><td bgcolor="#cccccc">
+<a href="index.html">Introduction</a>
+</td></tr>
+<tr><td bgcolor="#cccccc">
+<a href="history.html">History</a>
+</td></tr>
+<tr><td bgcolor="#cccccc">
+<a href="features.html">Features</a>
+</td></tr>
+<tr><td bgcolor="#cccccc">
+<a href="results.html">Results &amp; Testimonials</a>
+</td></tr>
+<tr><td bgcolor="#cccccc">
+<a href="inuse.html">TMDA In Use</a>
+</td></tr>
+<tr><td bgcolor="#cccccc">
+<a href="press.html">Press Coverage</a><!-- -*- html -*- -->
+</td></tr>
+<tr><td bgcolor="#cccccc">&nbsp;
+<tr><td bgcolor="#191970"><b><font color="#ffffff">
 Install
-</FONT></B></TD></TR>
-<TR><TD BGCOLOR="#cccccc">
+</font></b></td></tr>
+<tr><td bgcolor="#cccccc">
 <b>Requirements</b>
-</TD></TR>
-<TR><TD BGCOLOR="#cccccc">
-<A HREF="download.html">Download</A>
-</TD></TR>
-<TR><TD BGCOLOR="#cccccc">
-<A HREF="install.html">Installation</A>
-</TD></TR>
-<TR><TD BGCOLOR="#cccccc">&nbsp;
-<TR><TD BGCOLOR="#191970"><B><FONT COLOR="#ffffff">
+</td></tr>
+<tr><td bgcolor="#cccccc">
+<a href="download.html">Download</a>
+</td></tr>
+<tr><td bgcolor="#cccccc">
+<a href="install.html">Installation</a>
+</td></tr>
+<tr><td bgcolor="#cccccc">&nbsp;
+<tr><td bgcolor="#191970"><b><font color="#ffffff">
 Configuration
-</FONT></B></TD></TR>
-<TR><TD BGCOLOR="#cccccc">
-<A HREF="config.html">Overview</A>
-</TD></TR>
-<TR><TD BGCOLOR="#cccccc">
-<A HREF="config-pre.html">Pre-Configuration</A>
-</TD></TR>
-<TR><TD BGCOLOR="#cccccc">
-<A HREF="config-server.html">Server Configuration</A>
-</TD></TR>
-<TR><TD BGCOLOR="#cccccc">
-<A HREF="config-client.html">Client Configuration</A>
-</TD></TR>
-<TR><TD BGCOLOR="#cccccc">
-<A HREF="config-vars.html">Configuration Variables</A>
-</TD></TR>
-<TR><TD BGCOLOR="#cccccc">
-<A HREF="config-filter.html">Filter Specification</A>
-</TD></TR>
-<TR><TD BGCOLOR="#cccccc">
-<A HREF="filter-sources.html">Filter Sources</A>
-</TD></TR>
-<TR><TD BGCOLOR="#cccccc">&nbsp;
-<TR><TD BGCOLOR="#191970"><B><FONT COLOR="#ffffff">
+</font></b></td></tr>
+<tr><td bgcolor="#cccccc">
+<a href="config.html">Overview</a>
+</td></tr>
+<tr><td bgcolor="#cccccc">
+<a href="config-pre.html">Pre-Configuration</a>
+</td></tr>
+<tr><td bgcolor="#cccccc">
+<a href="config-server.html">Server Configuration</a>
+</td></tr>
+<tr><td bgcolor="#cccccc">
+<a href="config-client.html">Client Configuration</a>
+</td></tr>
+<tr><td bgcolor="#cccccc">
+<a href="config-vars.html">Configuration Variables</a>
+</td></tr>
+<tr><td bgcolor="#cccccc">
+<a href="config-filter.html">Filter Specification</a>
+</td></tr>
+<tr><td bgcolor="#cccccc">
+<a href="filter-sources.html">Filter Sources</a>
+</td></tr>
+<tr><td bgcolor="#cccccc">&nbsp;
+<tr><td bgcolor="#191970"><b><font color="#ffffff">
 HOWTOs
-</FONT></B></TD></TR>
-<TR><TD BGCOLOR="#cccccc">
-<A HREF="howtos.html">Overview</A>
-</TD></TR>
-<TR><TD BGCOLOR="#cccccc">
-<A HREF="howto-template.html">Templates</A>
-</TD></TR>
-<TR><TD BGCOLOR="#cccccc">
-<A HREF="tmda-ofmipd.html">tmda-ofmipd</A>
-</TD></TR>
-<TR><TD BGCOLOR="#cccccc">
-<A HREF="tmda-vdomains.html">Virtual Domains</A>
-</TD></TR>
-<TR><TD BGCOLOR="#cccccc">
+</font></b></td></tr>
+<tr><td bgcolor="#cccccc">
+<a href="howtos.html">Overview</a>
+</td></tr>
+<tr><td bgcolor="#cccccc">
+<a href="howto-template.html">Templates</a>
+</td></tr>
+<tr><td bgcolor="#cccccc">
+<a href="tmda-ofmipd.html">tmda-ofmipd</a>
+</td></tr>
+<tr><td bgcolor="#cccccc">
+<a href="tmda-vdomains.html">Virtual Domains</a>
+</td></tr>
+<tr><td bgcolor="#cccccc">
 <a href="tmda-cgi/index.html" TARGET="Resource Window">tmda-cgi</a>
-</TD></TR>
-<TR><TD BGCOLOR="#cccccc">&nbsp;
-<TR><TD BGCOLOR="#191970"><B><FONT COLOR="#ffffff">
+</td></tr>
+<tr><td bgcolor="#cccccc">&nbsp;
+<tr><td bgcolor="#191970"><b><font color="#ffffff">
 Support
-</FONT></B></TD></TR>
-<TR><TD BGCOLOR="#cccccc">
-<A HREF="trouble.html">Troubleshooting</A>
-</TD></TR>
-<TR><TD BGCOLOR="#cccccc">
+</font></b></td></tr>
+<tr><td bgcolor="#cccccc">
+<a href="trouble.html">Troubleshooting</a>
+</td></tr>
+<tr><td bgcolor="#cccccc">
 <a href="http://tmda.net/faq.cgi"; TARGET="Resource Window">FAQ</a>
-</TD></TR>
-<TR><TD BGCOLOR="#cccccc">
-<A HREF="bugs.html">Bugs &amp; Patches</A>
-</TD></TR>
-<TR><TD BGCOLOR="#cccccc">
+</td></tr>
+<tr><td bgcolor="#cccccc">
+<a href="bugs.html">Bugs &amp; Patches</a>
+</td></tr>
+<tr><td bgcolor="#cccccc">
 <a href="http://tmda.net/lists/listinfo/"; TARGET="Resource Window">Mailing 
Lists</a>
-</TD></TR>
-<TR><TD BGCOLOR="#cccccc">
+</td></tr>
+<tr><td bgcolor="#cccccc">
 <a href="http://mla.libertine.org/"; TARGET="Resource Window">List Archive</a> 
-</TD></TR>
-<TR><TD BGCOLOR="#cccccc">
-<A HREF="support-commercial.html">Commercial Support</A>
-</TD></TR>
-<TR><TD BGCOLOR="#cccccc">
-<A HREF="resources.html">External Resources</A>
-</TD></TR>
-<TR><TD BGCOLOR="#cccccc">
-<A HREF="mirrors.html">Mirrors</A>
-</TD></TR>
-<TR><TD BGCOLOR="#cccccc">&nbsp;
-<TR><TD BGCOLOR="#191970"><B><FONT COLOR="#ffffff">
+</td></tr>
+<tr><td bgcolor="#cccccc">
+<a href="support-commercial.html">Commercial Support</a>
+</td></tr>
+<tr><td bgcolor="#cccccc">
+<a href="resources.html">External Resources</a>
+</td></tr>
+<tr><td bgcolor="#cccccc">
+<a href="mirrors.html">Mirrors</a>
+</td></tr>
+<tr><td bgcolor="#cccccc">&nbsp;
+<tr><td bgcolor="#191970"><b><font color="#ffffff">
 Author
-</FONT></B></TD></TR>
-<TR><TD BGCOLOR="#cccccc">
-<A HREF="mailto:jason@xxxxxxxxxxxx";>Jason R. Mastaler</A>
-</TD></TR>
-<TR><TD BGCOLOR="#cccccc">
+</font></b></td></tr>
+<tr><td bgcolor="#cccccc">
+<a href="mailto:jason@xxxxxxxxxxxx";>Jason R. Mastaler</a>
+</td></tr>
+<tr><td bgcolor="#cccccc">
 &nbsp;
-</TD></TR>
-<TR><TD BGCOLOR="#cccccc">
+</td></tr>
+<tr><td bgcolor="#cccccc">
 &copy; 2001-2003
-</TD></TR>
-</TABLE><!-- end of sidebar table -->
+</td></tr>
+</table><!-- end of sidebar table -->
 
-</TD>
-<TD WIDTH=15>&nbsp;&nbsp;</TD><!--spacer-->
+</td>
+<td width="15">&nbsp;&nbsp;</td><!--spacer-->
 <!-- end of sidebar cell -->
 <!-- start of body cell -->
-<TD VALIGN=TOP WIDTH="90%"><BR>
+<td valign="top" width="90%" class="body"><br>
 <h3>TMDA Requirements</h3>
 
 <li>TMDA is designed to 
@@ -194,8 +199,8 @@
 
 <br><br>
 
-<li>TMDA currently runs only on UNIX-like systems, such as GNU/Linux,
-Solaris, *BSD, etc.  It should also work on Mac OS X but not earlier
+<li>TMDA currently runs only on UNIX-based systems, such as GNU/Linux,
+Solaris, *BSD, etc.  It also works on Mac OS X, but not earlier
 versions of Mac OS.  TMDA does not currently run on 
 <a href="http://tmda.net/faq.cgi?req=all#1.3"; TARGET="Resource 
Window">Microsoft Windows</a>.
 
@@ -207,7 +212,7 @@
 <br><br>
 
 <li>If you decide to give TMDA a whirl, make sure you have the necessary
-prerequisite software installed first.
+prerequisite software installed first.<br>
 
 <ol>
 
@@ -219,13 +224,11 @@
 <strong>python2</strong> at your shell's command line:
 
 <blockquote><pre>
-
 % python
-Python 2.2.2 (#1, Oct 17 2002, 03:12:45) 
-[GCC 2.95.4 20020320 [FreeBSD]] on freebsd4
+Python 2.2.3 (#1, 06/02/03, 12:58:43) 
+[GCC Apple cpp-precomp 6.14] on darwin
 Type "help", "copyright", "credits" or "license" for more information.
 >>> ^D
-
 </pre></blockquote>
 
 <li>An SMTP server (a.k.a. mail transport agent or MTA) for mail reception.
@@ -242,7 +245,7 @@
 your MTA.
 
 </ol>
-</TD><!-- end of body cell -->
-</TR><!-- end of sidebar/body row -->
-</TABLE><!-- end of page table -->
-</BODY></HTML>
+</td><!-- end of body cell -->
+</tr><!-- end of sidebar/body row -->
+</table><!-- end of page table -->
+</body></html>

_______________________________________
tmda-cvs mailing list
http://tmda.net/lists/listinfo/tmda-cvs



<Prev in Thread] Current Thread [Next in Thread>