Update of /cvsroot/tmda/tmda/htdocs
In directory sc8-pr-cvs1:/tmp/cvs-serv360

Modified Files:
        config-client.ht config-client.html index.ht index.html 
Log Message:
Fix some formatting issues, and also emphasize TMDA's tagged
addresses as a core feature on the index page.


Index: config-client.ht
===================================================================
RCS file: /cvsroot/tmda/tmda/htdocs/config-client.ht,v
retrieving revision 1.27
retrieving revision 1.28
diff -u -r1.27 -r1.28
--- config-client.ht    14 Nov 2002 00:09:53 -0000      1.27
+++ config-client.ht    15 Jan 2003 19:49:24 -0000      1.28
@@ -3,7 +3,7 @@
 
 <h3>TMDA Client Configuration</h3>
 In addition to filtering your incoming e-mail, TMDA can also work with
-your mail client to modify your outgoing address with unique,
+your mail client to send your outgoing messages with unique,
 cryptographically enhanced (tagged) e-mail addresses.  This is done to complement
 the filter's "whitelist" functionality.<br><br>
 
@@ -388,7 +388,8 @@
 
 <blockquote><pre>
 
-alias slrn-dated 'm4 -DTMDADATED=`tmda-address -dn` ~/.slrnrc.m4 > ~/.slrnrc && slrn 
-h newshost'
+alias slrn-dated 'm4 -DTMDADATED=`tmda-address -dn` \
+~/.slrnrc.m4 > ~/.slrnrc && slrn -h newshost'
 
 </pre></blockquote>
 </ol>

Index: config-client.html
===================================================================
RCS file: /cvsroot/tmda/tmda/htdocs/config-client.html,v
retrieving revision 1.45
retrieving revision 1.46
diff -u -r1.45 -r1.46
--- config-client.html  13 Jan 2003 19:27:56 -0000      1.45
+++ config-client.html  15 Jan 2003 19:49:24 -0000      1.46
@@ -1,6 +1,6 @@
 <HTML>
 <!-- THIS PAGE IS AUTOMATICALLY GENERATED.  DO NOT EDIT. -->
-<!-- Mon Jan 13 12:27:25 2003 -->
+<!-- Wed Jan 15 12:47:59 2003 -->
 <!-- USING HT2HTML 1.2 -->
 <!-- SEE http://barry.wooz.org/software/ht2html -->
 <!-- User-specified headers:
@@ -166,7 +166,7 @@
 <TD VALIGN=TOP WIDTH="90%"><BR>
 <h3>TMDA Client Configuration</h3>
 In addition to filtering your incoming e-mail, TMDA can also work with
-your mail client to modify your outgoing address with unique,
+your mail client to send your outgoing messages with unique,
 cryptographically enhanced (tagged) e-mail addresses.  This is done to complement
 the filter's "whitelist" functionality.<br><br>
 
@@ -551,7 +551,8 @@
 
 <blockquote><pre>
 
-alias slrn-dated 'm4 -DTMDADATED=`tmda-address -dn` ~/.slrnrc.m4 > ~/.slrnrc && slrn 
-h newshost'
+alias slrn-dated 'm4 -DTMDADATED=`tmda-address -dn` \
+~/.slrnrc.m4 > ~/.slrnrc && slrn -h newshost'
 
 </pre></blockquote>
 </ol>

Index: index.ht
===================================================================
RCS file: /cvsroot/tmda/tmda/htdocs/index.ht,v
retrieving revision 1.12
retrieving revision 1.13
diff -u -r1.12 -r1.13
--- index.ht    31 Oct 2002 19:30:11 -0000      1.12
+++ index.ht    15 Jan 2003 19:49:24 -0000      1.13
@@ -13,10 +13,15 @@
 and a cryptographically enhanced confirmation system (for unknown, but
 legitimate senders).  TMDA strives to be more effective, yet less
 time-consuming than traditional filters.
+<br><br>
 
+TMDA also supports special-purpose addresses called 
+<a href="config-client.html">"tagged addresses"</a> which increases 
+the transparency of the process for unknown senders by
+allowing them to safely circumvent the whitelist.
 <br><br>
 
-TMDA also acts as a local mail delivery agent, with a flexible 
+TMDA is also a local mail delivery agent, with a flexible 
 <a href="config-filter.html">filtering language</a> that allows fine-grained
 control over how incoming and outgoing mail is delivered and sent.
 <br><br>
@@ -31,11 +36,10 @@
 The way TMDA thwarts incoming junk-mail is simple yet extremely
 effective.  You maintain a "whitelist" of trusted contacts which are
 allowed directly into your mailbox.  Messages from unknown senders are
-held in a pending queue until they respond to a confirmation request
+held in a pending queue until they respond to a one-time confirmation request
 sent by TMDA.  Once they respond to the confirmation, their original
-message is deemed legitimate and is delivered to you.  Updating your
-whitelist insures they won't have to confirm future messages.  TMDA
-can even be configured to automatically whitelist confirmed senders.
+message is deemed legitimate and is delivered to you.  TMDA then adds
+their address to your whitelist so they won't have to confirm future messages.
 To see what the confirmation process looks like, 
 <a href="mailto:[EMAIL PROTECTED]";>send me a test message</a>,
 and then reply to the confirmation request.
@@ -43,11 +47,12 @@
 
 This methodology has the advantage of being very selective about what
 it allows in, while at the same time permitting legitimate, but
-previously unknown senders to reach you.  TMDA also has several
-techniques (See the <a href="config-client.html">Client
-Configuration</a> section) that allow senders to circumvent the
-whitelist, which greatly reduces the number of legitimate senders who are
-burdened with a confirmation request (only ~6% in my case).
+previously unknown senders to reach you.  
+<br><br>
+
+Optional use of TMDA's <a href="config-client.html">tagged addresses</a> 
+will greatly reduce the number of unknown senders who are actually sent a 
+confirmation request (only ~6% in my case).
 <br><br>
 </ul>
 

Index: index.html
===================================================================
RCS file: /cvsroot/tmda/tmda/htdocs/index.html,v
retrieving revision 1.30
retrieving revision 1.31
diff -u -r1.30 -r1.31
--- index.html  13 Jan 2003 19:28:09 -0000      1.30
+++ index.html  15 Jan 2003 19:49:24 -0000      1.31
@@ -1,6 +1,6 @@
 <HTML>
 <!-- THIS PAGE IS AUTOMATICALLY GENERATED.  DO NOT EDIT. -->
-<!-- Mon Jan 13 12:27:26 2003 -->
+<!-- Wed Jan 15 12:41:47 2003 -->
 <!-- USING HT2HTML 1.2 -->
 <!-- SEE http://barry.wooz.org/software/ht2html -->
 <!-- User-specified headers:
@@ -151,10 +151,15 @@
 and a cryptographically enhanced confirmation system (for unknown, but
 legitimate senders).  TMDA strives to be more effective, yet less
 time-consuming than traditional filters.
+<br><br>
 
+TMDA also supports special-purpose addresses called 
+<a href="config-client.html">"tagged addresses"</a> which increases 
+the transparency of the process for unknown senders by
+allowing them to safely circumvent the whitelist.
 <br><br>
 
-TMDA also acts as a local mail delivery agent, with a flexible 
+TMDA is also a local mail delivery agent, with a flexible 
 <a href="config-filter.html">filtering language</a> that allows fine-grained
 control over how incoming and outgoing mail is delivered and sent.
 <br><br>
@@ -169,11 +174,10 @@
 The way TMDA thwarts incoming junk-mail is simple yet extremely
 effective.  You maintain a "whitelist" of trusted contacts which are
 allowed directly into your mailbox.  Messages from unknown senders are
-held in a pending queue until they respond to a confirmation request
+held in a pending queue until they respond to a one-time confirmation request
 sent by TMDA.  Once they respond to the confirmation, their original
-message is deemed legitimate and is delivered to you.  Updating your
-whitelist insures they won't have to confirm future messages.  TMDA
-can even be configured to automatically whitelist confirmed senders.
+message is deemed legitimate and is delivered to you.  TMDA then adds
+their address to your whitelist so they won't have to confirm future messages.
 To see what the confirmation process looks like, 
 <a href="mailto:[EMAIL PROTECTED]";>send me a test message</a>,
 and then reply to the confirmation request.
@@ -181,11 +185,12 @@
 
 This methodology has the advantage of being very selective about what
 it allows in, while at the same time permitting legitimate, but
-previously unknown senders to reach you.  TMDA also has several
-techniques (See the <a href="config-client.html">Client
-Configuration</a> section) that allow senders to circumvent the
-whitelist, which greatly reduces the number of legitimate senders who are
-burdened with a confirmation request (only ~6% in my case).
+previously unknown senders to reach you.  
+<br><br>
+
+Optional use of TMDA's <a href="config-client.html">tagged addresses</a> 
+will greatly reduce the number of unknown senders who are actually sent a 
+confirmation request (only ~6% in my case).
 <br><br>
 </ul>
 

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

Reply via email to