folders.
The filtering is quite sophisticated, as it is done using real Perl
-substitution (s//) commands.
+matching (m//) commands.
=cut
=item $HOME/.mincspam
-If this file exists, minc will include it with the expectation that it
+If this file exists, B<minc> will include it with the expectation that it
will define a B<is_spam> function. This function takes a message
filename as an argument and returns 1 if the message is spam, else 0.
-If this file does not exist, minc will define a simple function that
+If this file does not exist, B<minc> will define a simple function that
always returns 0.
-One of minc's global variables is available to the user-defined
+One of B<minc>'s global variables is available to the user-defined
is_spam function: $run. This boolean should be honored; is_spam
should only take real action (i.e. removing or creating files, running
external programs, etc.) if $run is non-zero.
=item `mhpath +`/logs/minc.log
-Where minc logs what it does, unless in -n mode.
+Where B<minc> logs what it does, unless in -n mode.
=item `mhpath +`/logs/dryrun.log
-Where minc logs what it would do; used in -n mode.
-
-=back
+Where B<minc> logs what it would do; used in -n mode.
=item `mhpath +`/.minc.context
-minc uses this file for context (i.e. current folder) instead of
+B<minc> uses this file for context (i.e. current folder) instead of
`mhpath +`/context. This allows you some amount of freedom to use mh
-while minc is running. For example, you can changed folders without
+while B<minc> is running. For example, you can changed folders without
causing a message to be stored in the wrong folder. Care must still
be taken, however, about the unseen sequence; if you change it
(whether via show, or mark, or anything else) while in the same folder
-as minc, it is likely the new message minc stores will not end up
+as B<minc>, it is likely the new message B<minc> stores will not end up
marked unseen.
+=back
+
=cut
our @FILTERS;
}
}
+\f
__END__
=head1 THE FILTERS STRUCTURE