Free mail 5.01 software for linux

Shohei is a multi-language, multi-function, multi-server, multi-user, multi-context, multi-media web-based mail client, news client, calendar and note server.
Shohei is a pop3 client which meets the requirements of Stockholm public network.
Main features:
- Sends mail using SMTP
- Receives mail using POP
- Handles users in any number of domains on any number of servers
- Web based administration with different admins for different domains
- MIME aware
- Usenet News client
- Online context-sensitive help
- Customizable using HTML templates with embedded macros
- Calendar
- Write simple notes
- English and Swedish message catalogs, new ones are easily added

Mail::Summary is a Perl module that can scan read your mail!

SYNOPSIS

my $ms = Mail::Summary->new({ maildir => /home/mwk/Maildir });

my @mail_summaries = $ms->summaries;

Too busy to read your mail? Subscribe to too many mailing lists? Take two folders into the shower? Well, for the busy on the go geek of today, here is the answer! Get all your messages summarised, to save you having to read them, or to read them by which summary looks better!

new

my $ms = Mail::Summary->new({ maildir => /home/mwk/Maildir });

This will make a new Mail::Summary object.

maildir

my $maildir = $ms->maildir;

This is the mail directory as defined by the user.

summaries

my @mail_summaries = $ms->summaries;

This will return a list, with every entry in the list being a summary of an individual message.

HTML::Mail is a Perl extension for sending emails with embedded HTML and media.

SYNOPSIS

use HTML::Mail;

### initialisation
my $html_mail = HTML::Mail->new(
HTML => http://www.cpan.org,
Text => This is the text representation of the webpage http://www.cpan.org,
From => me@myhost.org,
To => you@yourhost.org,
Subject => CPAN webpage);

### Send the email ("inherited" from MIME::Lite)
$html_mail->send();

#### Remove text representation
$html_mail->set_Text();

### Rebuild the message and send
$html_mail->build->send;

### Serialise to file for later reuse
$html_mail->dump_file(/tmp/cpan_mail.data);

### Restore from file
my $restored = HTML::Mail->restore_file(/tmp/cpan_mail.data);

HTML::Mail is supposed to help with the task of sending emails with HTML and images (or other media) embedded or externally linked. It uses MIME::Lite for all MIME related jobs, HTML::Parser to find related files and change the URIs and LWP::UserAgent to retrieve the related files.

Email can be multipart/alternative if both HTML and Text content exist and multipart/related if there is only HTML content.

If all you want is to send text-only email, you probably wont find this module useful at all, or at best a huge overkill.

Mail::Bulkmail is a platform independent mailing list module.

SYNOPSIS

use Mail::Bulkmail /path/to/conf.file

my $bulk = Mail::Bulkmail->new(
"LIST" => "~/my.list.txt",
"From" => "Jim Thomason" ,
"Subject" => "This is a test message",
"Message" => "Here is my test message"
) || die Mail::Bulkmail->error();

$bulk->bulkmail() || die $bulk->error;

Dont forget to set up your conf file!

Mail::Bulkmail gives a fairly complete set of tools for managing mass-mailing lists. I initially wrote it because the tools I was using at the time were just too damn slow for mailing out to thousands of recipients. I keep working on it because its reasonably popular and I enjoy it.

In a nutshell, it allows you to rapidly transmit a message to a mailing list by zipping out the information to them via an SMTP relay (your own, of course). Subclasses provide the ability to use mail merges, dynamic messages, and anything else you can think of.

Mail::Bulkmail 3.00 is a major major major upgrade to the previous version (2.05), which was a major upgrade to the previous version (1.11). My software philosophy is that most code should be scrapped and re-written every 6-8 months or so. 2.05 was released in October of 2000, and Im writing these docs for 3.00 in January of 2003. So Im at least 3 major re-writes behind. (philosophy is referenced in the FAQ, below)

But thats okay, because were getting it done now.

3.00 is about as backwards compatible to 2.00 as 2.00 is to 1.00. That is to say, sorta. Ive tried to make a note of things where they changed, but Im sure I missed things. Some things can no longer be done, lots are done differently, some are the same. You will need to change your code to update from 1.x or 2.x to 3.00, though. Thats a given.

So whats new for 3.00? Lots of stuff.

Immediate changes are:

* code compartmentalization
* multi-server support
* conf file

The immediate change is that the code is now compartmentalized. Mail::Bulkmail now just handles ordinary, non-dynamic mailings. See Mail::Bulkmail::Dynamic for the merging and dynamic text abilities from the prior versions.

Server connections are no longer handled directly in Mail::Bulkmail (Smtp attribute, Port attribute, etc.), there is now a separate Mail::Bulkmail::Server object to handle all of that.

And everything subclasses off of Mail::Bulkmail::Object, where I have my super-methods to define my objects, some helper stuff, and so on.
Its just a lot easier for me to maintain, think about it, etc. if its all separated. Its also easier for you, the user, if you want to make changes to things. Just subclass it, tweak it, and use it. Very straightforward to modify and extend now. 2.x and below *could* do it, but it wasnt really that easy (unless you were making very trivial changes). This should rectify that.

Another major change is the addition of multi-server support. See the docs in Mail::Bulkmail::Server for more information. You can still specify one SMTP relay if thats all youve got, but if you have multiple servers, Mail::Bulkmail can now load balance between them to help take the stress off. No matter what, the biggest bottleneck to all of this is network performance (both to the SMTP relay and then from the relay to the rest of the world), so i wanted to try and help alleviate that by using multiple servers. I know that some people were doing that on there own with small changes, but this allows you to do it all invisibly.
And finally, finally, finally there is a conf file. Documentation on the format is in Mail::Bulkmail::Object. Its pretty easy to use. This is the conf file format that I designed for my own use (along with most of the rest of Mail::Bulkmail::Object). The software also has the ability to read multiple conf files, if so desired. So no more worrying about asking your sysadmin to tweak the values in your module somewhere up in /usr/lib/whatever

Just have him create the conf file you want, or pass in your own as desired.
conf_files are specified and further documented in Mail::Bulkmail::Object, in an internal array called @conf_files, right at the top of the module. To specify a universal conf file, put it in that array (or have your sysadmin do so). Alternatively, you can also add a conf_file via the conf_files accessor.

Mail::Bulkmail->conf_files(/path/to/conf_file, /path/to/other/conf_file); #, etc.

But the recommended way is to specify your conf file upon module import.

use Mail::Bulkmail 3.00 "/path/to/conf/file";

In addition, there is the usual plethora of bug fixes, tweaks, clean-ups, and so on.

And yes, the horrid long-standing bug in the Tz method is fixed! No, honest.
Im also trying a new documentation technique. The pod for a given method is now in the module by that method, as opposed to everything being bunched up at the bottom. Personally, I prefer everything being bunched up there for clarities sake. But from a maintenance point of view, spreading it all out makes my life much easier.

Mail::Field is a base class for manipulation of mail header fields.

SYNOPSIS

use Mail::Field;

$field = Mail::Field->new(Subject, some subject text);
print $field->tag,": ",$field->stringify,"n";

$field = Mail::Field->subject(some subject text);

Mail::Field is a base class for packages that create and manipulate fields from Email (and MIME) headers. Each different field will have its own sub-class, defining its own interface.

This document describes the minimum interface that each sub-class should provide, and also guidlines on how the field specific interface should be defined.

Mail::Action is a Perl module for building modules that act on incoming mail.

SYNOPSIS

use base Mail::Action;

Sometimes, you just need a really simple mailing address to last for a few days. You want it to be easy to create and easy to use, and you want it to be sufficiently anonymous that your real address isnt ever exposed.

Mail::TempAddress, Mail::TempAddress::Addresses, and Mail::TempAddress::Address make it easy to create a temporary mailing address system.