CVS: tmda-cgi/htdocs compile.ht,1.8,1.9 compile.html,1.11,1.12 defaults.ht,1.3,1.4 defaults.html,1.3,1.4 surprise.ht,1.10,1.11 surprise.html,1.11,1.12
Gre7g Luterman <[email protected]>
| Newsgroups | gmane.mail.spam.tmda.cvs |
|---|---|
| Message-ID | <[email protected]> |
Update of /cvsroot/tmda/tmda-cgi/htdocs
In directory sc8-pr-cvs1:/tmp/cvs-serv28775/htdocs
Modified Files:
compile.ht compile.html defaults.ht defaults.html surprise.ht
surprise.html
Log Message:
Added a section to the Info on included programs. Display UID/GID info also.
Test for UID 0 when running in no-su and single-user modes.
Added Alan Eldridge and Barry Warsaw to THANKS.
Added docs on international character sets.
Index: compile.ht
===================================================================
RCS file: /cvsroot/tmda/tmda-cgi/htdocs/compile.ht,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- compile.ht 4 May 2003 23:46:06 -0000 1.8
+++ compile.ht 7 May 2003 16:31:54 -0000 1.9
@@ -3,15 +3,15 @@
<h2>Compilation</h2>
<p>Once you have unzipped the source files into the directory where you plan
- to keep tmda-cgi and selected your mode, you will need to compile tmda-cgi.
- Compiling creates a binary executable which gives the program the rights to
- access the files it will need. This also saves certain pieces of information
+ to keep tmda-cgi and selected your mode, you will need to compile tmda-cgi.
+ Compiling creates a binary executable which gives the program the rights to
+ access the files it will need. This also saves certain pieces of information
which it will need accessible before authentication.<p>
<p>You will need to recompile if:</p>
<ul>
<li>you move your configuration files</li>
- <li>you move your supplimental display files (icons, images, and style
+ <li>you move your supplimental display files (icons, images, and style
sheet)</li>
<li>you move your tmda-cgi or TMDA source trees</li>
<li>you change the tmda-cgi mode</li>
@@ -28,22 +28,23 @@
<a href="#Running">Running <tt>configure</tt></a><br>
<a href="#Display"><tt>display</tt> Directory</a><br>
+<a href="#International">International Character Sets</a><br>
<a href="#NoSu">Additional no-su Setup</a><p>
<h3><a name="Running"></a>Running <tt>configure</tt></h3>
-<p>Although <tt>configure</tt> may be run with a large variety of command line
+<p>Although <tt>configure</tt> may be run with a large variety of command line
switches (see <tt><nobr>./configure -h | more</nobr></tt>), I think you'll
- find it far easier to run in interactive mode (by not specifying any
- options). Interactive mode will ask you a series of questions and provide
- "best guess" answers as the defaults. Once you have answered all the
+ find it far easier to run in interactive mode (by not specifying any
+ options). Interactive mode will ask you a series of questions and provide
+ "best guess" answers as the defaults. Once you have answered all the
questions, you'll be all ready to compile and install.</p>
-<p>If you do not know the answer to one of the interactive questions, don't
- panic. Simply hit control-C and the program will save the responses you have
+<p>If you do not know the answer to one of the interactive questions, don't
+ panic. Simply hit control-C and the program will save the responses you have
given. These will be used as the defaults when you re-run <tt>configure</tt>.
-<p>Depending on the mode you have chosen, you may need to be logged in as a
+<p>Depending on the mode you have chosen, you may need to be logged in as a
specific user when you compile tmda-cgi. Consult the following chart:<p>
<table>
@@ -77,44 +78,44 @@
<ol>
<li>The location of your Python interpreter</li>
<li>Where to save the CGI</li>
- <li>The path to TMDA's root directory</li>
- <li>An optional path or "formula" to find the user <tt>config</tt>
+ <li>The path to TMDA's root directory</li>
+ <li>An optional path or "formula" to find the user <tt>config</tt>
files</li>
<li>The <a href="auth.html">authentication mechanism</a> (file / program /
remote)
<li>The web path from the CGI to the <a href="#Display"><tt>display</tt>
- directory</a></li>
+ directory</a></li>
<li>Mode</li>
<li><a href="virtual.html">Virtual user stub and parameters</a></li>
- <li>Real user to use when someone logs in with a virtual e-mail account</li>
- <li>Path and prefix to use for temporary, session files</li>
- <li>How old session files may get before they can be cleaned</li>
- <li>The odds of cleaning up session files</li>
+ <li>Real user to use when someone logs in with a virtual e-mail account</li>
+ <li>Path and prefix to use for temporary, session files</li>
+ <li>How old session files may get before they can be cleaned</li>
+ <li>The odds of cleaning up session files</li>
</ol>
-<p>The <tt>configure</tt> program will provide additional information and
- its best-guess anwers as defaults. Most of these defaults will probably be
- just fine for your system, but check them all carefully before hitting
+<p>The <tt>configure</tt> program will provide additional information and
+ its best-guess anwers as defaults. Most of these defaults will probably be
+ just fine for your system, but check them all carefully before hitting
return.</p>
<h3><a name="Display"></a><tt>display</tt> Directory</h3>
<p>Finally, tmda-cgi requires a variety of visual elements saved in a
- <tt>display</tt> directory (see #6, above). This directory comes with the
- tmda-cgi source and will need to be manually copied or symbolically linked
- (make sure your web server is configured to follow links!) into the
+ <tt>display</tt> directory (see #6, above). This directory comes with the
+ tmda-cgi source and will need to be manually copied or symbolically linked
+ (make sure your web server is configured to follow links!) into the
appropriate web directory.</p>
-<p>Please note that #6 specifies the relative <i>web path</i> from the CGI to
- the <tt>display</tt> directory, which may be different than the actual path.
+<p>Please note that #6 specifies the relative <i>web path</i> from the CGI to
+ the <tt>display</tt> directory, which may be different than the actual path.
For example:</p>
<table border="0" cellspacing="0" cellpadding="0">
- <tr>
+ <tr>
<td width="35"> </td>
<th>Web path</th>
<td width="15"> </td>
<th>Actual path</th>
</tr>
- <tr>
+ <tr>
<td> </td>
<td>http://your.domain/cgi-bin/tmda.cgi</td>
<td> </td>
@@ -127,39 +128,51 @@
<td>/www/tmda/htdocs/display</td>
</tr>
</table>
-<p>In the above example, the actual path from the CGI to the display directory
- is <tt>../htdocs/display/</tt> but the web path is <tt>../display/</tt>. The
- web path (<tt>../display/</tt>) is the one that should be entered in question
+<p>In the above example, the actual path from the CGI to the display directory
+ is <tt>../htdocs/display/</tt> but the web path is <tt>../display/</tt>. The
+ web path (<tt>../display/</tt>) is the one that should be entered in question
#6.</p>
+<h3><a name="International"></a>International Character Sets</h3>
+
+<p>tmda-cgi supports the following international character set:</p>
+
+<blockquote>
+ <a href="http://sourceforge.net/cvs/?group_id=22022">Chinese</a>
+</blockquote>
+
+<p>To be able to use a given character set, you must first install the
+ appropriate codec from the link above. Download and install as per the
+ instructions on the appropriate web page and README files.</p>
+
<h3><a name="NoSu"></a>Additional no-su Setup</h3>
<p>If you compile in no-su mode, you will need to change permissions on any
- existing pending mail and configuration files so that they can be read by the
+ existing pending mail and configuration files so that they can be read by the
CGI. You can either make these files world accessible or group accessible.</p>
-<p>Group accessible is a little more secure than world accessible. World
- accessible files are easily read by accident. Users actually have to take
+<p>Group accessible is a little more secure than world accessible. World
+ accessible files are easily read by accident. Users actually have to take
intentional steps to mess with files in another group.</p>
-<p>We recommend you assign permissions of 660 to files and 2660 to directories
- to make them group accessible. Don't forget to <tt>chgrp</tt> then into the
- appropriate group! Look in your Apache (or other web server) configuration
- file to find out which group you should use. For Apache, this directive will
+<p>We recommend you assign permissions of 660 to files and 2660 to directories
+ to make them group accessible. Don't forget to <tt>chgrp</tt> then into the
+ appropriate group! Look in your Apache (or other web server) configuration
+ file to find out which group you should use. For Apache, this directive will
look like:</p>
<blockquote>
<pre>Group nobody</pre>
</blockquote>
-<p>You will also need to add in code to make sure new e-mails are group
+<p>You will also need to add in code to make sure new e-mails are group
accessible. We recommend adding the following to your <tt>/etc/tmdarc</tt>:
<blockquote>
<pre>os.umask(027)</pre>
</blockquote>
-<p>If you have many users who use tmda-cgi in no-su mode, you may find it
- advantageous to put all of the TMDA files in one central location, such as
- <tt>/var/tmda</tt>. If this sounds appealing, check out the <a
+<p>If you have many users who use tmda-cgi in no-su mode, you may find it
+ advantageous to put all of the TMDA files in one central location, such as
+ <tt>/var/tmda</tt>. If this sounds appealing, check out the <a
href="nosu.html">centralized no-su</a> example.
Index: compile.html
===================================================================
RCS file: /cvsroot/tmda/tmda-cgi/htdocs/compile.html,v
retrieving revision 1.11
retrieving revision 1.12
diff -u -r1.11 -r1.12
--- compile.html 4 May 2003 23:46:06 -0000 1.11
+++ compile.html 7 May 2003 16:31:54 -0000 1.12
@@ -2,7 +2,7 @@
<?xml-stylesheet href="display/styles.css" type="text/css"?>
<html>
<!-- THIS PAGE IS AUTOMATICALLY GENERATED. DO NOT EDIT. -->
-<!-- Sun May 4 18:35:07 2003 -->
+<!-- Wed May 7 01:02:07 2003 -->
<!-- USING HT2HTML 2.1 -->
<!-- SEE http://ht2html.sf.net -->
<!-- User-specified headers:
@@ -84,15 +84,15 @@
<td valign="top" class="body"><h2>Compilation</h2>
<p>Once you have unzipped the source files into the directory where you plan
- to keep tmda-cgi and selected your mode, you will need to compile tmda-cgi.
- Compiling creates a binary executable which gives the program the rights to
- access the files it will need. This also saves certain pieces of information
+ to keep tmda-cgi and selected your mode, you will need to compile tmda-cgi.
+ Compiling creates a binary executable which gives the program the rights to
+ access the files it will need. This also saves certain pieces of information
which it will need accessible before authentication.<p>
<p>You will need to recompile if:</p>
<ul>
<li>you move your configuration files</li>
- <li>you move your supplimental display files (icons, images, and style
+ <li>you move your supplimental display files (icons, images, and style
sheet)</li>
<li>you move your tmda-cgi or TMDA source trees</li>
<li>you change the tmda-cgi mode</li>
@@ -109,22 +109,23 @@
<a href="#Running">Running <tt>configure</tt></a><br>
<a href="#Display"><tt>display</tt> Directory</a><br>
+<a href="#International">International Character Sets</a><br>
<a href="#NoSu">Additional no-su Setup</a><p>
<h3><a name="Running"></a>Running <tt>configure</tt></h3>
-<p>Although <tt>configure</tt> may be run with a large variety of command line
+<p>Although <tt>configure</tt> may be run with a large variety of command line
switches (see <tt><nobr>./configure -h | more</nobr></tt>), I think you'll
- find it far easier to run in interactive mode (by not specifying any
- options). Interactive mode will ask you a series of questions and provide
- "best guess" answers as the defaults. Once you have answered all the
+ find it far easier to run in interactive mode (by not specifying any
+ options). Interactive mode will ask you a series of questions and provide
+ "best guess" answers as the defaults. Once you have answered all the
questions, you'll be all ready to compile and install.</p>
-<p>If you do not know the answer to one of the interactive questions, don't
- panic. Simply hit control-C and the program will save the responses you have
+<p>If you do not know the answer to one of the interactive questions, don't
+ panic. Simply hit control-C and the program will save the responses you have
given. These will be used as the defaults when you re-run <tt>configure</tt>.
-<p>Depending on the mode you have chosen, you may need to be logged in as a
+<p>Depending on the mode you have chosen, you may need to be logged in as a
specific user when you compile tmda-cgi. Consult the following chart:<p>
<table>
@@ -158,44 +159,44 @@
<ol>
<li>The location of your Python interpreter</li>
<li>Where to save the CGI</li>
- <li>The path to TMDA's root directory</li>
- <li>An optional path or "formula" to find the user <tt>config</tt>
+ <li>The path to TMDA's root directory</li>
+ <li>An optional path or "formula" to find the user <tt>config</tt>
files</li>
<li>The <a href="auth.html">authentication mechanism</a> (file / program /
remote)
<li>The web path from the CGI to the <a href="#Display"><tt>display</tt>
- directory</a></li>
+ directory</a></li>
<li>Mode</li>
<li><a href="virtual.html">Virtual user stub and parameters</a></li>
- <li>Real user to use when someone logs in with a virtual e-mail account</li>
- <li>Path and prefix to use for temporary, session files</li>
- <li>How old session files may get before they can be cleaned</li>
- <li>The odds of cleaning up session files</li>
+ <li>Real user to use when someone logs in with a virtual e-mail account</li>
+ <li>Path and prefix to use for temporary, session files</li>
+ <li>How old session files may get before they can be cleaned</li>
+ <li>The odds of cleaning up session files</li>
</ol>
-<p>The <tt>configure</tt> program will provide additional information and
- its best-guess anwers as defaults. Most of these defaults will probably be
- just fine for your system, but check them all carefully before hitting
+<p>The <tt>configure</tt> program will provide additional information and
+ its best-guess anwers as defaults. Most of these defaults will probably be
+ just fine for your system, but check them all carefully before hitting
return.</p>
<h3><a name="Display"></a><tt>display</tt> Directory</h3>
<p>Finally, tmda-cgi requires a variety of visual elements saved in a
- <tt>display</tt> directory (see #6, above). This directory comes with the
- tmda-cgi source and will need to be manually copied or symbolically linked
- (make sure your web server is configured to follow links!) into the
+ <tt>display</tt> directory (see #6, above). This directory comes with the
+ tmda-cgi source and will need to be manually copied or symbolically linked
+ (make sure your web server is configured to follow links!) into the
appropriate web directory.</p>
-<p>Please note that #6 specifies the relative <i>web path</i> from the CGI to
- the <tt>display</tt> directory, which may be different than the actual path.
+<p>Please note that #6 specifies the relative <i>web path</i> from the CGI to
+ the <tt>display</tt> directory, which may be different than the actual path.
For example:</p>
<table border="0" cellspacing="0" cellpadding="0">
- <tr>
+ <tr>
<td width="35"> </td>
<th>Web path</th>
<td width="15"> </td>
<th>Actual path</th>
</tr>
- <tr>
+ <tr>
<td> </td>
<td>http://your.domain/cgi-bin/tmda.cgi</td>
<td> </td>
@@ -208,41 +209,53 @@
<td>/www/tmda/htdocs/display</td>
</tr>
</table>
-<p>In the above example, the actual path from the CGI to the display directory
- is <tt>../htdocs/display/</tt> but the web path is <tt>../display/</tt>. The
- web path (<tt>../display/</tt>) is the one that should be entered in question
+<p>In the above example, the actual path from the CGI to the display directory
+ is <tt>../htdocs/display/</tt> but the web path is <tt>../display/</tt>. The
+ web path (<tt>../display/</tt>) is the one that should be entered in question
#6.</p>
+<h3><a name="International"></a>International Character Sets</h3>
+
+<p>tmda-cgi supports the following international character set:</p>
+
+<blockquote>
+ <a href="http://sourceforge.net/cvs/?group_id=22022">Chinese</a>
+</blockquote>
+
+<p>To be able to use a given character set, you must first install the
+ appropriate codec from the link above. Download and install as per the
+ instructions on the appropriate web page and README files.</p>
+
<h3><a name="NoSu"></a>Additional no-su Setup</h3>
<p>If you compile in no-su mode, you will need to change permissions on any
- existing pending mail and configuration files so that they can be read by the
+ existing pending mail and configuration files so that they can be read by the
CGI. You can either make these files world accessible or group accessible.</p>
-<p>Group accessible is a little more secure than world accessible. World
- accessible files are easily read by accident. Users actually have to take
+<p>Group accessible is a little more secure than world accessible. World
+ accessible files are easily read by accident. Users actually have to take
intentional steps to mess with files in another group.</p>
-<p>We recommend you assign permissions of 660 to files and 2660 to directories
- to make them group accessible. Don't forget to <tt>chgrp</tt> then into the
- appropriate group! Look in your Apache (or other web server) configuration
- file to find out which group you should use. For Apache, this directive will
+<p>We recommend you assign permissions of 660 to files and 2660 to directories
+ to make them group accessible. Don't forget to <tt>chgrp</tt> then into the
+ appropriate group! Look in your Apache (or other web server) configuration
+ file to find out which group you should use. For Apache, this directive will
look like:</p>
<blockquote>
<pre>Group nobody</pre>
</blockquote>
-<p>You will also need to add in code to make sure new e-mails are group
+<p>You will also need to add in code to make sure new e-mails are group
accessible. We recommend adding the following to your <tt>/etc/tmdarc</tt>:
<blockquote>
<pre>os.umask(027)</pre>
</blockquote>
-<p>If you have many users who use tmda-cgi in no-su mode, you may find it
- advantageous to put all of the TMDA files in one central location, such as
- <tt>/var/tmda</tt>. If this sounds appealing, check out the <a
+<p>If you have many users who use tmda-cgi in no-su mode, you may find it
+ advantageous to put all of the TMDA files in one central location, such as
+ <tt>/var/tmda</tt>. If this sounds appealing, check out the <a
href="nosu.html">centralized no-su</a> example.
</td>
<!-- end of body cell -->
Index: defaults.ht
===================================================================
RCS file: /cvsroot/tmda/tmda-cgi/htdocs/defaults.ht,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- defaults.ht 4 May 2003 20:04:22 -0000 1.3
+++ defaults.ht 7 May 2003 16:31:55 -0000 1.4
@@ -35,42 +35,45 @@
</tr>
<tr>
<td><a href="#NoOverrideWhichTar">NoOverride:WhichTar</a></td>
- <td><a href="#GeneralSpamCopAddr">General:SpamCopAddr</a></td>
+ <td><a href="#GeneralCSEncoding">General:CSEncoding</a></td>
</tr>
<tr>
+ <td><a href="#GeneralSpamCopAddr">General:SpamCopAddr</a></td>
<td><a href="#GeneralTheme">General:Theme</a></td>
- <td><a href="#GeneralUseJSConfirm">General:UseJSConfirm</a></td>
</tr>
<tr>
+ <td><a href="#GeneralUseJSConfirm">General:UseJSConfirm</a></td>
<td><a href="#GenAddrExpireNum">GenAddr:ExpireNum</a></td>
- <td><a href="#GenAddrExpireUnit">GenAddr:ExpireUnit</a></td>
</tr>
<tr>
+ <td><a href="#GenAddrExpireUnit">GenAddr:ExpireUnit</a></td>
<td><a href="#GenAddrKeyword">GenAddr:Keyword</a></td>
- <td><a href="#GenAddrSender">GenAddr:Sender</a></td>
</tr>
<tr>
+ <td><a href="#GenAddrSender">GenAddr:Sender</a></td>
<td><a href="#LoginInitPage">Login:InitPage</a></td>
- <td><a href="#PendingListCropDest">PendingList:CropDest</a></td>
</tr>
<tr>
+ <td><a href="#PendingListCropDest">PendingList:CropDest</a></td>
<td><a href="#PendingListCropSender">PendingList:CropSender</a></td>
- <td><a href="#PendingListCropSubject">PendingList:CropSubject</a></td>
</tr>
<tr>
+ <td><a href="#PendingListCropSubject">PendingList:CropSubject</a></td>
<td><a href="#PendingListDateFormat">PendingList:DateFormat</a></td>
- <td><a href="#PendingListPagerSize">PendingList:PagerSize</a></td>
</tr>
<tr>
+ <td><a href="#PendingListPagerSize">PendingList:PagerSize</a></td>
<td><a href="#PendingListShowAddr">PendingList:ShowAddr</a></td>
- <td><a href="#ViewPendingAltPref">ViewPending:AltPref</a></td>
</tr>
<tr>
+ <td><a href="#ViewPendingAltPref">ViewPending:AltPref</a></td>
<td><a href="#ViewPendingAllowTags">ViewPending:AllowTags</a></td>
- <td><a href="#ViewPendingBlockRemove">ViewPending:BlockRemove</a></td>
</tr>
<tr>
+ <td><a href="#ViewPendingBlockRemove">ViewPending:BlockRemove</a></td>
<td><a href="#ViewPendingEmailClass">ViewPending:EmailClass</a></td>
+ </tr>
+ <tr>
<td><a href="#ViewPendingHeaders">ViewPending:Headers</a></td>
</tr>
</table>
@@ -192,7 +195,7 @@
<h4><a name="NoOverrideUninstallInstruct"></a>NoOverride:UninstallInstruct</h4>
<blockquote>
<p>Any special instructions your users will need after uninstalling TMDA. If
- left blank, no special instructions will be given</p>
+ left blank, no special instructions will be given.</p>
<p>Example:
<table class="example">
<tr>
@@ -229,6 +232,24 @@
<blockquote>
<p>Path to <tt>tar</tt> program.</p>
<p>Default: <tt>/bin/tar</tt></p>
+</blockquote>
+
+<h4><a name="GeneralCSEncoding"></a>General:CSEncoding</h4>
+<blockquote>
+ <p>Set the default encoding for all tmda-cgi pages. It's generally safe to
+ leave this one set to the defaults. Internationally encoded e-mails which
+ do not identify their codeset will not render correctly unless this setting
+ matches the content.</p>
+ <p>If many international e-mails are not rendering correctly, try resetting
+ this to match their character set.</p>
+ <p>Example:
+ <table class="example">
+ <tr>
+ <td>[General]<br>
+ CSEncoding = big5</td>
+ </tr>
+ </table>
+ <p>Default: <tt>iso-8859-1</tt></p>
</blockquote>
<h4><a name="GeneralSpamCopAddr"></a>General:SpamCopAddr</h4>
Index: defaults.html
===================================================================
RCS file: /cvsroot/tmda/tmda-cgi/htdocs/defaults.html,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- defaults.html 4 May 2003 20:04:22 -0000 1.3
+++ defaults.html 7 May 2003 16:31:55 -0000 1.4
@@ -2,7 +2,7 @@
<?xml-stylesheet href="display/styles.css" type="text/css"?>
<html>
<!-- THIS PAGE IS AUTOMATICALLY GENERATED. DO NOT EDIT. -->
-<!-- Sun May 4 13:25:32 2003 -->
+<!-- Wed May 7 01:14:14 2003 -->
<!-- USING HT2HTML 2.1 -->
<!-- SEE http://ht2html.sf.net -->
<!-- User-specified headers:
@@ -128,42 +128,45 @@
</tr>
<tr>
<td><a href="#NoOverrideWhichTar">NoOverride:WhichTar</a></td>
- <td><a href="#GeneralSpamCopAddr">General:SpamCopAddr</a></td>
+ <td><a href="#GeneralCSEncoding">General:CSEncoding</a></td>
</tr>
<tr>
+ <td><a href="#GeneralSpamCopAddr">General:SpamCopAddr</a></td>
<td><a href="#GeneralTheme">General:Theme</a></td>
- <td><a href="#GeneralUseJSConfirm">General:UseJSConfirm</a></td>
</tr>
<tr>
+ <td><a href="#GeneralUseJSConfirm">General:UseJSConfirm</a></td>
<td><a href="#GenAddrExpireNum">GenAddr:ExpireNum</a></td>
- <td><a href="#GenAddrExpireUnit">GenAddr:ExpireUnit</a></td>
</tr>
<tr>
+ <td><a href="#GenAddrExpireUnit">GenAddr:ExpireUnit</a></td>
<td><a href="#GenAddrKeyword">GenAddr:Keyword</a></td>
- <td><a href="#GenAddrSender">GenAddr:Sender</a></td>
</tr>
<tr>
+ <td><a href="#GenAddrSender">GenAddr:Sender</a></td>
<td><a href="#LoginInitPage">Login:InitPage</a></td>
- <td><a href="#PendingListCropDest">PendingList:CropDest</a></td>
</tr>
<tr>
+ <td><a href="#PendingListCropDest">PendingList:CropDest</a></td>
<td><a href="#PendingListCropSender">PendingList:CropSender</a></td>
- <td><a href="#PendingListCropSubject">PendingList:CropSubject</a></td>
</tr>
<tr>
+ <td><a href="#PendingListCropSubject">PendingList:CropSubject</a></td>
<td><a href="#PendingListDateFormat">PendingList:DateFormat</a></td>
- <td><a href="#PendingListPagerSize">PendingList:PagerSize</a></td>
</tr>
<tr>
+ <td><a href="#PendingListPagerSize">PendingList:PagerSize</a></td>
<td><a href="#PendingListShowAddr">PendingList:ShowAddr</a></td>
- <td><a href="#ViewPendingAltPref">ViewPending:AltPref</a></td>
</tr>
<tr>
+ <td><a href="#ViewPendingAltPref">ViewPending:AltPref</a></td>
<td><a href="#ViewPendingAllowTags">ViewPending:AllowTags</a></td>
- <td><a href="#ViewPendingBlockRemove">ViewPending:BlockRemove</a></td>
</tr>
<tr>
+ <td><a href="#ViewPendingBlockRemove">ViewPending:BlockRemove</a></td>
<td><a href="#ViewPendingEmailClass">ViewPending:EmailClass</a></td>
+ </tr>
+ <tr>
<td><a href="#ViewPendingHeaders">ViewPending:Headers</a></td>
</tr>
</table>
@@ -285,7 +288,7 @@
<h4><a name="NoOverrideUninstallInstruct"></a>NoOverride:UninstallInstruct</h4>
<blockquote>
<p>Any special instructions your users will need after uninstalling TMDA. If
- left blank, no special instructions will be given</p>
+ left blank, no special instructions will be given.</p>
<p>Example:
<table class="example">
<tr>
@@ -322,6 +325,24 @@
<blockquote>
<p>Path to <tt>tar</tt> program.</p>
<p>Default: <tt>/bin/tar</tt></p>
+</blockquote>
+
+<h4><a name="GeneralCSEncoding"></a>General:CSEncoding</h4>
+<blockquote>
+ <p>Set the default encoding for all tmda-cgi pages. It's generally safe to
+ leave this one set to the defaults. Internationally encoded e-mails which
+ do not identify their codeset will not render correctly unless this setting
+ matches the content.</p>
+ <p>If many international e-mails are not rendering correctly, try resetting
+ this to match their character set.</p>
+ <p>Example:
+ <table class="example">
+ <tr>
+ <td>[General]<br>
+ CSEncoding = big5</td>
+ </tr>
+ </table>
+ <p>Default: <tt>iso-8859-1</tt></p>
</blockquote>
<h4><a name="GeneralSpamCopAddr"></a>General:SpamCopAddr</h4>
Index: surprise.ht
===================================================================
RCS file: /cvsroot/tmda/tmda-cgi/htdocs/surprise.ht,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -r1.10 -r1.11
--- surprise.ht 4 May 2003 23:46:06 -0000 1.10
+++ surprise.ht 7 May 2003 16:31:55 -0000 1.11
@@ -12,7 +12,9 @@
<a href="#Attach">Attachment Anxiety</a><br>
<a href="#WhiteBlack">Whitelist, Blacklist... where are the options?</a><br>
<a href="#Base">Bad Base</a><br>
-<a href="#Install">Install Again?</a></p>
+<a href="#Install">Install Again?</a><br>
+<a href="#NoInstall">Can't Install!</a><br>
+<a href="#International">International Intrigue</a></p>
<h3><a name="Whitelist"></a>Whitelist Woes</h3>
<p>tmda-cgi's whitelist feature does not update the list pointed to by
@@ -48,12 +50,12 @@
<p>We hope to add support for this soon.</p>
<h3><a name="Authentication"></a>Authentication Ailments</h3>
-<p>If no username/password combination lets you log in, your problem may be due
- to a misconfigured authentication method. To aid in finding out precisely
- what is misconfigured, we have added a variety of debugging messages to
+<p>If no username/password combination lets you log in, your problem may be due
+ to a misconfigured authentication method. To aid in finding out precisely
+ what is misconfigured, we have added a variety of debugging messages to
various parts of the authentication code.</p>
-<p>The debugging messages are embedded in comments in the login page. Try
- logging in and when you get the "Wrong password." message, do a "View/Source"
+<p>The debugging messages are embedded in comments in the login page. Try
+ logging in and when you get the "Wrong password." message, do a "View/Source"
of the HTML page. At the top of the page, you should see something like:</p>
<table class="example">
<tr>
@@ -81,40 +83,40 @@
...</td>
</tr>
</table>
-<p>If you do not wish for these messages to be embedded, modify the template
+<p>If you do not wish for these messages to be embedded, modify the template
file <tt>login.html</tt> and remove the <tt>%(ErrMsg)s</tt> string.</p>
-<p>If the messages do not help you get to the root of the problem, refer to the
- instructions on the <a href="contact.html">Contact</a> page to get some
- assistance. Be sure to copy and paste the debug information you are getting,
+<p>If the messages do not help you get to the root of the problem, refer to the
+ instructions on the <a href="contact.html">Contact</a> page to get some
+ assistance. Be sure to copy and paste the debug information you are getting,
to make it easier for the developers to help you.</p>
<h3><a name="Attach"></a>Attachment Anxiety</h3>
<p>tmda-cgi does not let you view the attachments on a pending e-mail.</p>
-<p>If you need one of the attachments in an e-mail, simply release the e-mail
- by clicking on the checkmark button. You can then download the e-mail as if
- the sender had confirmed the message, and view the attachment. Remember,
- tmda-cgi lets you manage your pending messages. It is not a web-based mail
+<p>If you need one of the attachments in an e-mail, simply release the e-mail
+ by clicking on the checkmark button. You can then download the e-mail as if
+ the sender had confirmed the message, and view the attachment. Remember,
+ tmda-cgi lets you manage your pending messages. It is not a web-based mail
client.</p>
<h3><a name="WhiteBlack"></a>Whitelist, Blacklist... where are the options?</h3>
-<p>The screenshots show whitelist and blacklist options, but I don't see
+<p>The screenshots show whitelist and blacklist options, but I don't see
these!</p>
-<p>The whitelist and blacklist options are only available if you have
+<p>The whitelist and blacklist options are only available if you have
configured them in your config file. Try setting <a
href="/config-vars.html#PENDING_WHITELIST_APPEND"><tt>PENDING_WHITELIST_APPEND</tt></a>
and <a
- href="/config-vars.html#PENDING_BLACKLIST_APPEND"><tt>PENDING_BLACKLIST_APPEND</tt></a>.
- The radio buttons and option buttons should appear on the pending list and
+ href="/config-vars.html#PENDING_BLACKLIST_APPEND"><tt>PENDING_BLACKLIST_APPEND</tt></a>.
+ The radio buttons and option buttons should appear on the pending list and
pending e-mail viewer once you do.</p>
<h3><a name="Base"></a>Bad Base</h3>
<p>My <tt>skel</tt> files use <tt>%(Base)s/bin/</tt> to refer to TMDA's
<tt>bin/</tt> directory, but when my users install, the files created point
to the wrong directory.</p>
-<p>The variable <tt>%(Base)s</tt> asssumes you have installed TMDA from source.
- If you installed TMDA from RPM or FreeBSD port, then the assumed relationship
+<p>The variable <tt>%(Base)s</tt> asssumes you have installed TMDA from source.
+ If you installed TMDA from RPM or FreeBSD port, then the assumed relationship
between library files and executables is no longer valid.</p>
-<p>Simply modify the <tt>skel</tt> files, remove <tt>%(Base)s/bin/</tt> and
+<p>Simply modify the <tt>skel</tt> files, remove <tt>%(Base)s/bin/</tt> and
replace it with the correct path to TMDA's executables.</p>
<h3><a name="Install"></a>Install Again?</h3>
@@ -146,9 +148,28 @@
...</td>
</tr>
</table>
-<p>If you do not wish for these messages to be embedded, modify the template
+<p>If you do not wish for these messages to be embedded, modify the template
file <tt>welcome.html</tt> and remove the <tt>%(ErrMsg)s</tt> string.</p>
-<p>If the messages do not help you get to the root of the problem, refer to the
- instructions on the <a href="contact.html">Contact</a> page to get some
- assistance. Be sure to copy and paste the debug information you are getting,
+<p>If the messages do not help you get to the root of the problem, refer to the
+ instructions on the <a href="contact.html">Contact</a> page to get some
+ assistance. Be sure to copy and paste the debug information you are getting,
to make it easier for the developers to help you.</p>
+
+<h3><a name="NoInstall"></a>Can't Install!</h3>
+<p>I've run <tt>configure</tt> and <tt>make</tt>, but <tt>make install</tt>
+ won't work because the user I'm compiling as doesn't have the needed
+ permissions to put a file in the web tree. Can I do <tt>make install</tt> as
+ root?</p>
+<p>No, don't do <tt>make install</tt> as root. That will put the wrong
+ privileges on the binary. If the account you are using doesn't have
+ permission to write to the web tree, then select a different place to save
+ the binary (such as <tt>/tmp/</tt>) when you run <tt>configure</tt>.</p>
+<p>Now run <tt>make</tt> and <tt>make install</tt> as normal and use root to
+ move the file from <tt>/tmp/</tt> (or wherever) into the web tree.</p>
+<p>This will make sure that the binary's UID/GID remain intact.</p>
+
+<h3><a name="International"></a>International Intrigue</h3>
+<p>Instead of Chinese characters in the pending list, the subject lines are
+ showing up as random English characters!</p>
+<p>Did you remember to install the <a href="compile.html#International">Chinese
+ codec</a>? tmda-cgi can't translate Chinese without it.</p>
Index: surprise.html
===================================================================
RCS file: /cvsroot/tmda/tmda-cgi/htdocs/surprise.html,v
retrieving revision 1.11
retrieving revision 1.12
diff -u -r1.11 -r1.12
--- surprise.html 4 May 2003 23:46:06 -0000 1.11
+++ surprise.html 7 May 2003 16:31:55 -0000 1.12
@@ -2,7 +2,7 @@
<?xml-stylesheet href="display/styles.css" type="text/css"?>
<html>
<!-- THIS PAGE IS AUTOMATICALLY GENERATED. DO NOT EDIT. -->
-<!-- Sun May 4 18:44:52 2003 -->
+<!-- Wed May 7 01:02:35 2003 -->
<!-- USING HT2HTML 2.1 -->
<!-- SEE http://ht2html.sf.net -->
<!-- User-specified headers:
@@ -90,7 +90,9 @@
<a href="#Attach">Attachment Anxiety</a><br>
<a href="#WhiteBlack">Whitelist, Blacklist... where are the options?</a><br>
<a href="#Base">Bad Base</a><br>
-<a href="#Install">Install Again?</a></p>
+<a href="#Install">Install Again?</a><br>
+<a href="#NoInstall">Can't Install!</a><br>
+<a href="#International">International Intrigue</a></p>
<h3><a name="Whitelist"></a>Whitelist Woes</h3>
<p>tmda-cgi's whitelist feature does not update the list pointed to by
@@ -126,12 +128,12 @@
<p>We hope to add support for this soon.</p>
<h3><a name="Authentication"></a>Authentication Ailments</h3>
-<p>If no username/password combination lets you log in, your problem may be due
- to a misconfigured authentication method. To aid in finding out precisely
- what is misconfigured, we have added a variety of debugging messages to
+<p>If no username/password combination lets you log in, your problem may be due
+ to a misconfigured authentication method. To aid in finding out precisely
+ what is misconfigured, we have added a variety of debugging messages to
various parts of the authentication code.</p>
-<p>The debugging messages are embedded in comments in the login page. Try
- logging in and when you get the "Wrong password." message, do a "View/Source"
+<p>The debugging messages are embedded in comments in the login page. Try
+ logging in and when you get the "Wrong password." message, do a "View/Source"
of the HTML page. At the top of the page, you should see something like:</p>
<table class="example">
<tr>
@@ -159,40 +161,40 @@
...</td>
</tr>
</table>
-<p>If you do not wish for these messages to be embedded, modify the template
+<p>If you do not wish for these messages to be embedded, modify the template
file <tt>login.html</tt> and remove the <tt>%(ErrMsg)s</tt> string.</p>
-<p>If the messages do not help you get to the root of the problem, refer to the
- instructions on the <a href="contact.html">Contact</a> page to get some
- assistance. Be sure to copy and paste the debug information you are getting,
+<p>If the messages do not help you get to the root of the problem, refer to the
+ instructions on the <a href="contact.html">Contact</a> page to get some
+ assistance. Be sure to copy and paste the debug information you are getting,
to make it easier for the developers to help you.</p>
<h3><a name="Attach"></a>Attachment Anxiety</h3>
<p>tmda-cgi does not let you view the attachments on a pending e-mail.</p>
-<p>If you need one of the attachments in an e-mail, simply release the e-mail
- by clicking on the checkmark button. You can then download the e-mail as if
- the sender had confirmed the message, and view the attachment. Remember,
- tmda-cgi lets you manage your pending messages. It is not a web-based mail
+<p>If you need one of the attachments in an e-mail, simply release the e-mail
+ by clicking on the checkmark button. You can then download the e-mail as if
+ the sender had confirmed the message, and view the attachment. Remember,
+ tmda-cgi lets you manage your pending messages. It is not a web-based mail
client.</p>
<h3><a name="WhiteBlack"></a>Whitelist, Blacklist... where are the options?</h3>
-<p>The screenshots show whitelist and blacklist options, but I don't see
+<p>The screenshots show whitelist and blacklist options, but I don't see
these!</p>
-<p>The whitelist and blacklist options are only available if you have
+<p>The whitelist and blacklist options are only available if you have
configured them in your config file. Try setting <a
href="/config-vars.html#PENDING_WHITELIST_APPEND"><tt>PENDING_WHITELIST_APPEND</tt></a>
and <a
- href="/config-vars.html#PENDING_BLACKLIST_APPEND"><tt>PENDING_BLACKLIST_APPEND</tt></a>.
- The radio buttons and option buttons should appear on the pending list and
+ href="/config-vars.html#PENDING_BLACKLIST_APPEND"><tt>PENDING_BLACKLIST_APPEND</tt></a>.
+ The radio buttons and option buttons should appear on the pending list and
pending e-mail viewer once you do.</p>
<h3><a name="Base"></a>Bad Base</h3>
<p>My <tt>skel</tt> files use <tt>%(Base)s/bin/</tt> to refer to TMDA's
<tt>bin/</tt> directory, but when my users install, the files created point
to the wrong directory.</p>
-<p>The variable <tt>%(Base)s</tt> asssumes you have installed TMDA from source.
- If you installed TMDA from RPM or FreeBSD port, then the assumed relationship
+<p>The variable <tt>%(Base)s</tt> asssumes you have installed TMDA from source.
+ If you installed TMDA from RPM or FreeBSD port, then the assumed relationship
between library files and executables is no longer valid.</p>
-<p>Simply modify the <tt>skel</tt> files, remove <tt>%(Base)s/bin/</tt> and
+<p>Simply modify the <tt>skel</tt> files, remove <tt>%(Base)s/bin/</tt> and
replace it with the correct path to TMDA's executables.</p>
<h3><a name="Install"></a>Install Again?</h3>
@@ -224,12 +226,31 @@
...</td>
</tr>
</table>
-<p>If you do not wish for these messages to be embedded, modify the template
+<p>If you do not wish for these messages to be embedded, modify the template
file <tt>welcome.html</tt> and remove the <tt>%(ErrMsg)s</tt> string.</p>
-<p>If the messages do not help you get to the root of the problem, refer to the
- instructions on the <a href="contact.html">Contact</a> page to get some
- assistance. Be sure to copy and paste the debug information you are getting,
+<p>If the messages do not help you get to the root of the problem, refer to the
+ instructions on the <a href="contact.html">Contact</a> page to get some
+ assistance. Be sure to copy and paste the debug information you are getting,
to make it easier for the developers to help you.</p>
+
+<h3><a name="NoInstall"></a>Can't Install!</h3>
+<p>I've run <tt>configure</tt> and <tt>make</tt>, but <tt>make install</tt>
+ won't work because the user I'm compiling as doesn't have the needed
+ permissions to put a file in the web tree. Can I do <tt>make install</tt> as
+ root?</p>
+<p>No, don't do <tt>make install</tt> as root. That will put the wrong
+ privileges on the binary. If the account you are using doesn't have
+ permission to write to the web tree, then select a different place to save
+ the binary (such as <tt>/tmp/</tt>) when you run <tt>configure</tt>.</p>
+<p>Now run <tt>make</tt> and <tt>make install</tt> as normal and use root to
+ move the file from <tt>/tmp/</tt> (or wherever) into the web tree.</p>
+<p>This will make sure that the binary's UID/GID remain intact.</p>
+
+<h3><a name="International"></a>International Intrigue</h3>
+<p>Instead of Chinese characters in the pending list, the subject lines are
+ showing up as random English characters!</p>
+<p>Did you remember to install the <a href="compile.html#International">Chinese
+ codec</a>? tmda-cgi can't translate Chinese without it.</p>
</td>
<!-- end of body cell -->
</tr><!-- end of sidebar/body row -->
_______________________________________
tmda-cvs mailing list
http://tmda.net/lists/listinfo/tmda-cvs