-.\" $Id: t-prot.1,v 1.136 2009/12/20 21:38:41 jochen Exp $
+.\" $Id: t-prot.1,v 1.144 2010/01/08 11:08:50 jochen Exp $
.\"
-.TH T-PROT "1" "August 2009" "T-PROT"
+.TH T-PROT "1" "January 2010" "T-PROT"
.SH NAME
t-prot \- TOFU Protection - Display Filter for RFC 2822 messages
.SH SYNOPSIS
is the reason for not using standard CPAN modules for handling
messages).
.PP
-For easy usage, you can download a file to be included in your ~/.muttrc:
-.I http://www.escape.de/users/tolot/mutt/t\-prot/muttrc.t\-prot
-.br
-And here is an example S-Lang macro to use t-prot from within slrn:
-.I http://www.escape.de/users/tolot/mutt/t\-prot/t\-prot.sl
+For easy usage, you can include the file muttrc.t\-prot in your
+~/.muttrc. Also coming with the t-prot package is the example S-Lang
+macro t\-prot.sl for using t-prot from within slrn.
.SH OPTIONS
.TP
.BR "\-A" =DIRECTORY
.IR ratio [=n]
.br
If the quoting ratio is n or more, the message is rejected. Must be
-between 0 and 1, or else it is entirely disabled.
+between 0 and 1, or else it is entirely disabled. Default is 0.75
+(i.e., three quarters are quoted).
.TP
.B "\-d, \-\-debug"
"debug":
.BR "\-\-max\-lines" =x
Maximum number of lines a message may count (with headers). If the message
is longer than x lines, the message will not be processed but printed
-unmodified.
+unmodified. Exit status will be EX_DATAERR except when called with -Mmutt.
.TP
.BR "\-o" =FILE
"output file":
All of the documentation and software included in the t-prot releases
is copyrighted by Jochen Striepe (except when explicitly stated otherwise).
.PP
-Copyright \(co 2001-2009 Jochen Striepe. All rights reserved.
+Copyright \(co 2001-2010 Jochen Striepe. All rights reserved.
.PP
Redistribution and use, with or without modification, are permitted
provided that the following conditions are met:
There is a problem when mutt gives a PGP verified or even a multipart
message to t-prot: The information where the PGP encrypted/signed data
or even attachments begin and end is plainly embedded in the text, not
-really cleanly recognizeable for t-prot. The problem should be worked
+really cleanly recognizable for t-prot. The problem should be worked
around by now, please send a bug report if it does not work for you.
.SH "REPORTING BUGS"
Please note that t-prot development happens on