Free mail boxes software for linux

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.

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

KMail Power Tools is meant to be a suite of enhancements to KMail and may be other mail user agents.
It is currently composed of only one (perl) script that acts as a filter (take input from stdin, outputs the modified mail to stdout), adds dialog boxes to kmail, and allows the user to:
- remove all attachments from an email (no user interaction),
- remove selectively attachments, after asking the user,
detach (i.e. save then remove) any attachment to a directory chosen by the user,
- hence reducing the size of your mailbox, while allowing you to backup important attached files.
All these actions are logged within a sentence in the mail body (see below).
Note: removing and detaching is already supported by Thunderbird, but my favourite mailer program is KMail, then...
How it works
KMail allows the definition of filters (like any other email program), but you can define filters:
- which are launched manually,
- which can be programs reading your email on stdin and outputing the result on stdout (or "pipe through").
So I had the idea to use this in order to enhance KMail, and allow it to remove and detach attachments: kmailpt will read and interpret the email (thank you Perl MIME::Parser), then depending on the command line switches, popup a dialog box to ask the user for a directory where to save attachments, and ask him which attachment to remove/detach (thank you Kdialog!).
Also, the sentence "[Attachment removed by jice (26/02/2007 20:33:01): bill.zip]" will be added to the mail body. When you detach an email, it will add a similar sentence, and if the mail body is html, you will even get a link to the new location of the file: "[Attachment saved by jice (26/02/2007 20:36:17) to heavenly.gif]", on which you can even click in order to view the detached file. For text/plain messages, the sentence will be something like: "[Attachment saved by jice (26/02/2007 20:36:17) to file:///home/jice/Images/heavenly.gif]" (unfortunately, although kmail renders http:// or ftp:// urls as links, file:// are not (yet?) - I should enter a bug on bugs.kde.org for this...).
Should you want to know the currently available command line switches, here is the help:
Usage: kmailpt [options]
kmailpt takes an email on stdin, performs actions based
on this mail, then output an email on stdout.
Without any option, it will remove any file attached.
Options:
-d detach the attachments (save and remove)
-q ask which attachment to remove
-h prints this help

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 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.

libnewmail is a generic mail checking library for Unix/Linux and other operating systems. It supports a simple API, an extensible plugin architecture and asynchronous queries among other features.
libnewmail library is intented to be a replacement for all that crappy and incomplete code of all those mail checking utilities available. Applications linking to libnewmail may enumerate configured mailboxes, query mail box information and status and request a mail spool auto-detection for users without any libnewmail specific configuration. The library offers a clean API to implement your own mail checking plugins.
Programs using libnewmail may query for both the boolean availability and the number of available mails. (The former is usually much faster than the latter) The library is able to distuingish between new (unread) and old (read, current) mails. It includes four CLI tools easy, nmail, nmail-async and nm-spoolhackusing the libnewmail API for mail checking. They are intended to be an example how to use the API with either the synchronous or the asynchronous interface.
The utility nm-spoolhack serves a special purpose: mail checking applets using the stat() trick to check the status of Unix mail spools may be tought new tricks by pointing them to the emulated mail spool generated by this tool according to another (remote) mail spool. The emulated spool is at most a single byte in size but carries the right stat() attributes to fool the applets. This way you may use the Gnome mail check applet to query IMAPS mail spools, as an example. Its a hack, but it works quite well.
Currently libnewmail includes plugins for the following mailbox protocols:
- Unix mail spool (libunix.so)
- qmail Maildir (libmaildir.so)
- POP3 with SSL and APOP (libpop3.so)
- IMAP4rev1 with SSL (libimap.so)
There is an API for a graphical configuration interface. However, this is currently a NOOP. This feature will be added eventually

wmmaiload monitors your incomming mails in your mail boxes.
Installation:
1. Configure the sources :
Run ./configure to select what kind of mailbox you want to enable wmmaiload for. To get some help type ./configure -help
If you have non-standard libraries or libraries in non-standard path, you can add the includes path with -Ipath to the USER_CPPFLAGS in Init.make in each directory that need it. Same thing for link options : just add -Lpath to USER_LDFLAGS.
2. Compile the sources :
make
3. Install the sources :
make install-strip
or, if you want a system-wide installation
su -c "make install-strip"
You can specify a destination directory other than / (which $PREFIX is added to) :
make install-strip DESTDIR=./debian
The resulting installation will be in ./debian/$PREFIX/...
You can also simply overwrite PREFIX using the -prefix option with
./configure
Enhancements:
- fixed bugs in threads handling
- fixed bugs in IMAP and SSL

Mail Notification is a status icon (aka tray icon) that informs you if you have new mail.
Mail Notification works with system trays implementing the freedesktop.org System Tray Specification, such as the GNOME Panel Notification Area, the Xfce Notification Area and the KDE System Tray.
Main features:
- multiple mailbox support
- mbox, MH, Maildir, Sylpheed, POP3, IMAP and Gmail support
- SASL authentication support
- APOP authentication support
- SSL/TLS support
- automatic detection of mailbox format
- immediate notification (the status icon is updated within seconds after a mailbox changes)
- a mail summary
- HIG 2.0 compliance.