DESCRIPTION

This module is a small POE::Component::IRC plugin which uses POE::Component::IRC::Plugin for its base. It provides interface to generate <a href="mailto:foo@bar">... links that escape every single characters preventing dumb spam bots from harvesting the email addresses. I did not do any actual research on how useful this technique actually is but people who employ it say that it's effective as long as you encode the mailto: part as well. The plugin accepts input from public channel events, /notice messages as well as /msg (private messages); although that can be configured at will.

The new() method constructs and returns a new POE::Component::IRC::Plugin::AntiSpamMailTo object suitable to be fed to POE::Component::IRC's plugin_add method. The constructor takes a few arguments, but all of them are optional. Note: you can change the values of the arguments dynamically by accessing them as hashref keys in your plugin's object; e.g. to ban some user during runtime simply do push @{ $your_plugin_object->{banned} }, qr/user!mask/ The possible arguments/values are as follows:

max_length

->new( max_length => 350 );

Optional. Takes a positive integer as a value. Specifies the maximum length of the output (this does not include the prepended nickname or '...' at the end of cut output). If length of the output is longer than the value you specify here it will be cut off and '...' will be appended to the output indicating it was cut off. Defaults to:350

auto

->new( auto => 0 );

Optional. Takes either true or false values, specifies whether or not the plugin should auto respond to requests. When the auto argument is set to a true value plugin will respond to the requesting person with the results automatically. When the auto argument is set to a false value plugin will not respond and you will have to listen to the events emitted by the plugin to retrieve the results (see EMITTED EVENTS section and response_event argument for details). Defaults to:1.

response_event

->new( response_event => 'event_name_to_receive_results' );

Optional. Takes a scalar string specifying the name of the event to emit when the results of the request are ready. See EMITTED EVENTS section for more information. Defaults to:irc_antispam_mailto

banned

->new( banned => [ qr/aol\.com$/i ] );

Optional. Takes an arrayref of regexes as a value. If the usermask of the person (or thing) making the request matches any of the regexes listed in the banned arrayref, plugin will ignore the request. Defaults to:[] (no bans are set).

root

->new( root => [ qr/\Qjust.me.and.my.friend.net\E$/i ] );

Optional. As opposed to banned argument, the root argument allows access only to people whose usermasks match any of the regexen you specify in the arrayref the argument takes as a value. By default: it is not specified. Note: as opposed to banned specifying an empty arrayref to root argument will restrict access to everyone.

trigger

->new( trigger => qr/^mailto\s+(?=\S)/i );

Optional. Takes a regex as an argument. Messages matching this regex, irrelevant of the type of the message, will be considered as requests. See also addressed option below which is enabled by default as well as triggers option which is more specific. Note: the trigger will be removed from the message, therefore make sure your trigger doesn't match the actual data that needs to be processed. Defaults to:qr/^mailto\s+(?=\S)/i

triggers

Optional. Takes a hashref as an argument which may contain either one or all of keys public, notice and privmsg which indicates the type of messages: channel messages, notices and private messages respectively. The values of those keys are regexes of the same format and meaning as for the trigger argument (see above). Messages matching this regex will be considered as requests. The difference is that only messages of type corresponding to the key of triggers hashref are checked for the trigger. Note: the trigger will be matched irrelevant of the setting in triggers, thus you can have one global and specific "local" triggers. See also addressed option below which is enabled by default as well as triggers option which is more specific. Note: the trigger will be removed from the message, therefore make sure your trigger doesn't match the actual data that needs to be processed. Defaults to:qr/^mailto\s+(?=\S)/i

addressed

->new( addressed => 1 );

Optional. Takes either true or false values. When set to a true value all the public messages must be addressed to the bot. In other words, if your bot's nickname is Nick and your trigger is qr/^trig\s+/ you would make the request by saying Nick, trig EXAMPLE. When addressed mode is turned on, the bot's nickname, including any whitespace and common punctuation character will be removed before matching the trigger (see above). When addressed argument it set to a false value, public messages will only have to match trigger regex in order to make a request. Note: this argument has no effect on /notice and /msg requests. Defaults to:1

listen_for_input

->new( listen_for_input => [ qw(public notice privmsg) ] );

Optional. Takes an arrayref as a value which can contain any of the three elements, namely public, notice and privmsg which indicate which kind of input plugin should respond to. When the arrayref contains public element, plugin will respond to requests sent from messages in public channels (see addressed argument above for specifics). When the arrayref contains notice element plugin will respond to requests sent to it via /notice messages. When the arrayref contains privmsg element, the plugin will respond to requests sent to it via /msg (private messages). You can specify any of these. In other words, setting ( listen_for_input = [ qr(notice privmsg) ] )> will enable functionality only via /notice and /msg messages. Defaults to:[ qw(public notice privmsg) ]

eat

->new( eat => 0 );

Optional. If set to a false value plugin will return a PCI_EAT_NONE after responding. If eat is set to a true value, plugin will return a PCI_EAT_ALL after responding. See POE::Component::IRC::Plugin documentation for more information if you are interested. Defaults to: 1

debug

->new( debug => 1 );

Optional. Takes either a true or false value. When debug argument is set to a true value some debugging information will be printed out. When debug argument is set to a false value no debug info will be printed. Defaults to:0.

The event handler set up to handle the event, name of which you've specified in the response_event argument to the constructor (it defaults to irc_antispam_mailto) will receive input every time request is completed. The input will come in $_[ARG0] on a form of a hashref. The possible keys/values of that hashrefs are as follows: