Free mail tribune software for linux

Mail::Abuse is a Perl module that helps parse and respond to miscellaneous abuse complaints.

SYNOPSIS
use Mail::Abuse;

This module and the accompaining software can be used to automatically parse and respond to various formats of abuse complaints. This software is geared towards abuse desk administrators who need sophisticated tools to deal with the complains.
Mail::Abuse is actually a bundle of modules that provide various services. This documentation provides a general description of the functions provided by each one. No useful code is provided in the Mail::Abuse module, appart from this documentation and the version information below.

The following classes/packages are part of this distribution.

Mail::Abuse::Report

A report is a collection made of the received report and ths incidents it describes. See Mail::Abuse::Report for more information.

Mail::Abuse::Incident

An incident is each of the individual policy violations that are presented in a given report. A report should have at least, one incident. See Mail::Abuse::Incident for more information.

Mail::Abuse::Processor

Once the reports are analyzed and its incidents are extracted, you will want to do something with the information. This is the job of a processor. See Mail::Abuse::Processor for more information.

Mail::Abuse::Reader

Abuse reports can be fetched from a variety of places and through various protocols. This is what readers do: Read a report. See Mail::Abuse::Reader for more information.

Mail::Abuse::Filter

An abuse report might contain incidents that are not to be handled by us. A filter remove incidents that does not belong to our network. See Mail::Abuse::Filter for more information.

All of the modules take a lot of their configuration information from a specially formatted file.

This distribution also includes a number of scripts. See the bin/ directory for more information.

Mail 2 Wordpress is an SMTP mailrobot for posting wordpress blog entries via SMTP mail.

Claws Mail Extra Plugins package contains plugins for Sylpheed-Claws e-mail client.
Claws Mail is the extended version of Sylpheed, a GTK+ based, lightweight, and fast email client. Almost all commands are accessible with the keyboard.
It also has many features such as multiple accounts, POP3/SMTP/IMAP/NNTP support, OpenSSL, GnuPG, and LDAP support, a plugin system, spell checking, filtering, Actions, spam and virus filters, an address book, internationalization, and more.
As the mechanism offered by Claws Mail to add new plugin functionality is under active development it is subject to change, therefore the required version is also given. The author has verified that the plugin works with this required version, however it may or may not work with other versions.
Enhancements:
- This release contains 15 plugins.
- It fixes a bug in the PDF Viewer plugin with GTK 2.6.x where the button images were not shown.

Mail Avenger is a highly-configurable, MTA-independent SMTP server daemon. Mail Avenger lets users run messages through filters like ClamAV and SpamAssassin during SMTP transactions, so the server can reject mail before assuming responsibility for its delivery.
Other unique features include TCP SYN fingerprint and network route recording, verification of sender addresses through SMTP callbacks, SPF (sender policy framework) as a general policy language, qmail-style control over both SMTP-level behavior and local delivery of extension addresses, mail-bomb protection, integration with kernel firewalls, and more.
Enhancements:
- Several minor bugs were fixed.
- The SMTPCB configuration directive was changed to give more options.
- An InsecureSASL configuration option was added by request of users.

SYNOPSIS

use Mail::Abuse::Report;

my $r = new Mail::Abuse::Report
(
-text => $report_text,
-reader => $reader,
-filters => [ $f1, $f2, ... ],
-parsers => [ $i1, $i2, ... ],
-processors => [ $p1, $p2, ... ],
-debug => 1,
-config => $config_file,
);

This class encapsulates an abuse report and provides methods to automate tasks such as extracting individual incidents from it, filtering the incidents, etc.

Each of the methods are described in detail, below:

->new(%args)

Creates a new Mail::Abuse::Report object. It accepts the following arguments:

-text
Specifies the text that will be used to fill the report with. This is incompatible with -reader, so choose one and stick to it. Defaults to undef.

-reader
Specifies the object (tipically a member of Mail::Abuse::Reader) that will be used to fetch the text of the next report. This is incompatible with -text, so pick one and stick to it. Defaults to undef.

-filters
A reference to a list of objects that can filter incidents. Normally, objects based on Mail::Abuse::Filter. Defaults to no filters.

-parsers
A reference to a list of objects that can parse incidents out of the report text. Normally, objects based on Mail::Abuse::Incident. Defaults to no parsers.

-processors
A reference to a list of objects that can process the incidents on the report, normally objects based on the Mail::Abuse::Processor class. Defaults to no processors.

-debug
A true value causes diagnostic messages to be sent via warn().

-config
Specifies the name of the config file to fetch configuration items from. Can be left unspecified.

Junk Mail Buffering Agent is a tool for preventing delivery of email until the sender has confirmed their address.

Junk Mail Buffering Agent can be used in conjunction with a spam filter to prevent delivery of spammy-looking email unless the sender is confirmed as valid.

jmba is designed to be used in conjunction with a spam filter such as QSF and the mail processor procmail. When the spam filter says it thinks an email is spam, it can be passed to jmba.

jmba will queue it and send an email to the sender containing a key; if the sender replies, the original email is "unfrozen" from the queue and delivered.

Mail::Box can manage a mailbox, a folder with messages.

INHERITANCE

Mail::Box
is a Mail::Reporter

Mail::Box is extended by
Mail::Box::Dir
Mail::Box::File
Mail::Box::Net

SYNOPSIS

use Mail::Box::Manager;
my $mgr = Mail::Box::Manager->new;
my $folder = $mgr->open(folder => $ENV{MAIL}, ...);
print $folder->name;

# Get the first message.
print $folder->message(0);

# Delete the third message
$folder->message(3)->delete;

# Get the number of messages in scalar context.
my $emails = $folder->messages;

# Iterate over the messages.
foreach ($folder->messages) {...} # all messages
foreach (@$folder) {...} # all messages

$folder->addMessage(Mail::Box::Message->new(...));
Tied-interface:
tie my(@inbox), Mail::Box::Tie::ARRAY, $inbox;

# Four times the same:
$inbox[3]->print; # tied
$folder->[3]->print; # overloaded folder
$folder->message(3)->print; # usual
print $folder->[3]; # overloaded message

tie my(%inbox), Mail::Box::Tie::HASH, $inbox;

# Twice times the same
$inbox{$msgid}->print; # tied
$folder->messageId($msgid)->print;# usual

A Mail::Box::Manager creates Mail::Box objects. But you already knew, because you started with the Mail::Box-Overview manual page. That page is obligatory reading, sorry!

Mail::Box is the base class for accessing various types of mailboxes (folders) in a uniform manner. The various folder types vary on how they store their messages, but when some effort those differences could be hidden behind a general API. For example, some folders store many messages in one single file, where other store each message in a separate file withing the same directory.

No object in your program will be of type Mail::Box: it is only used as base class for the real folder types.