Luis Muñoz > Mail-Abuse > abuso

Download:
Mail-Abuse-1.026.tar.gz

Annotate this POD

CPAN RT

New  1
Open  0
View/Report Bugs
Source  

NAME ^

abuso - Front-end for Mail::Abuse

SYNOPSIS ^

    abuso [-Iincident1,incident2,...] [-Pproc1,proc2,...] [-Ffilter1,filter2,...] [-Rreader] [-c config] [-d] [-v]

DESCRIPTION ^

abuso, spanish for "abuse" is really a front-end that helps use the services provided by the Mail::Abuse classes. This is designed to be a tool for parsing and hopefully, responding promptly to abuse complaints sent to abuse desks at ISPs and other entities connected to the Internet.

abuso has a configuration file that can supply all of its operational parameters, such as which filters to use, etc. The name of this file can be specified in the command line with the -c switch. Alternatively, you can leave abuso look for its config file according to the documentation of Config::Auto.

The entries that are supported in the config file, are described below. Note that all of them can be overrided by the corresponding option in the command line.

abuso reader

The name of the class that will be instantiated to "read" new abuse reports. This can be overriden with the -R option. abuso will try to require the class as given, tacking a Mail::Abuse::Reader:: if failed.

A reader is mandatory. abuso will terminate if no reader can be loaded.

abuso parsers

The classes that will be instantiated to parse the abuse reports and extract individual incident information. This can be overriden with the -P option. abuso will try to require the class as given, tacking a Mail::Abuse::Incident:: if failed.

Although the parsers are not mandatory, this code can be quite useless without specifying at least one parser.

abuso filters

The classes that will be instantiated to filter the incidents found in the abuse reports. This can be overriden with the -F option. abuso will try to require the class as given, tacking a Mail::Abuse::Filter:: if failed.

Filtering the incidents is very important because in many cases, you will end up receiving reports for things outside your control.

abuso processors

The classes that will be instantiated process the reports once parsed and filtered. This can be overriden with the -P option. abuso will try to require the class as given, tacking a Mail::Abuse::Processor:: if failed.

By giving the <-d> option, debug messages are produced via warn(). -v produces some progress indications, also through the use ow warn().

This is where the final part of the work is done, be it storing the report, opening a ticket, sending an email, etc.

HISTORY ^

Jun, 2003

Begin working in the first version of the code, as a replacement of a more rudimentary proof of concept.

LICENSE AND WARRANTY ^

This code and all accompanying software comes with NO WARRANTY. You use it at your own risk.

This code and all accompanying software can be used freely under the same terms as Perl itself.

AUTHOR ^

Luis E. Muñoz <luismunoz@cpan.org>

SEE ALSO ^

perl(1), Mail::Abuse.

syntax highlighting: