Free email message software for linux

Wily::Message is a Perl extension to handle Wily Messages.

SYNOPSIS

use Wily::Message;
use Wily::Connect;

# opens a file in wily and exits when the window is destroyed

my $win_id;

my $ws = Wily::Connect::connect();

my $wm = Wily::Message->new(Wily::Message::WMnew, 0, 0, 0, 1,
/tmp/file_to_edit);
$ws->syswrite($wm->flatten());

my $buffer = ;
until (Wily::Message::complete_message($buffer)) {
$ws->sysread($buffer, 1024, length($buffer));
}

$buffer = $wm->from_string($buffer);

if ($wm->{type} == Wily::Message::WRerror) {
die "Error WMnew: $wm->{s}n";
} elsif ($wm->{type} == Wily::Message::WRnew) {
$win_id = $wm->{window_id};
$wm = Wily::Message->new(Wily::Message::WMattach, $win_id, 0, 0,
Wily::Message::WEdestroy);
$ws->syswrite($wm->flatten());
until (Wily::Message::complete_message($buffer)) {
$ws->sysread($buffer, 1024, length($buffer));
}
$buffer = $wm->from_string($buffer);
if ($wm->{type} == Wily::Message::WRerror) {
die "Error WMattach: $wm->{s}n";
} elsif ($wm->{type} == Wily::Message::WRattach) {
} else {
die "Expected a WRattach, but didnt get one";
}
} else {
die "Expected a WRnew, but didnt get one";
}

while (1) {
until (Wily::Message::complete_message($buffer)) {
$ws->sysread($buffer, 1024, length($buffer));
}
$buffer = $wm->from_string($buffer);
if ($wm->{type} == Wily::Message::WEdestroy and $wm->{window_id} == $win_id) {
last;
}
}

A simple object wrapper around Wily messages with a helper function to assist in extracting messages from the wily connection.

Mail::Message::Field contains one line of a message header.

INHERITANCE

Mail::Message::Field
is a Mail::Reporter

Mail::Message::Field is extended by
Mail::Message::Field::Fast
Mail::Message::Field::Flex
Mail::Message::Field::Full

SYNOPSIS

my $field = Mail::Message::Field->new(From => fish@tux.aq);
print $field->name;
print $field->body;
print $field->comment;
print $field->content; # body & comment
$field->print(*OUT);
print $field->string;
print "$fieldn";
print $field->attribute(charset) || us-ascii;

This implementation follows the guidelines of rfc2822 as close as possible, and may there produce a different output than implementations based on the obsolete rfc822. However, the old output will still be accepted.

These objects each store one header line, and facilitates access routines to the information hidden in it. Also, you may want to have a look at the added methods of a message:

my @from = $message->from;
my $sender = $message->sender;
my $subject = $message->subject;
my $msgid = $message->messageId;

my @to = $message->to;
my @cc = $message->cc;
my @bcc = $message->bcc;
my @dest = $message->destinations;

my $other = $message->get(Reply-To);

LAFmessage is a feature-complete library for fetching, parsing, generating and delivering MIME-compliant email messages. The project has C++, JNI (Java) and Win32 COM APIs.
For generating mail messages, LAFmessage provides an object-oriented API that represents all the pieces of a message and allows the caller to assemble them in (nearly) limitless combinations to programatically reproduce any feature that is to be found in interactive mail clients (and a few that arent!). These include:
RFC 822-compliant (non-MIME) plain text email.
RFC 2045-compliant (MIME-compliant) plain text email.
RFC 2045-compliant (MIME-compliant) HTML email.
RFC 2045-compliant (MIME-compliant) attachments, both external and embedded.
RFC 822-compliant user-defined header fields.
Messages can also be parsed from RFC 822 or RFC 2045 format into the same object structure to allow programmatic parsing of message content, saving of attachments, forwarding of whole messages, etc.
For fetching and delivering messages, LAFmessage provides the following features:
- RFC 1939-compliant POP3 system for connecting to arbitrary POP3 servers, retrieving and deleting email messages. Downloaded messages are parsed into the object structure for programmatic handling or presentation to an end user.
- RFC 821-compliant SMTP system for connecting to arbitrary SMTP servers, authenticating and delivering email messages. Messages may be delivered synchronously or queued within LAFmessage for asynchronous delivery. Delivery status is available during batch delivery and optimizations are available to speed delivery such as:
- Multiple recipients per SMTP transaction -- greatly reduces network traffic and mail server load.
- Multiple worker threads to deliver queued messages -- can greatly reduce delivery time.
LAFmessage has the capability to canonicalize strings to render strings safe for insertion into HTML, HTML TEXTAREAs, JavaScript and SQL statements.
LAFmessage presents several different APIs:
- A COM interface for use from COM-aware environments on Win32 platforms
- A JNI interface for use from Java applications on Win32 and Linux platforms
- A C++ interface that can be used directly in new programs by simply including the necessary files on Win32 and Linux platforms
LAFmessage is completely thread-safe and suitable for use from ASP pages.

Newsmail was created to allow easy news publication to one or more sites, using email messages to insert, delete, and manage news.
It is a simple PHP news ticker that allows you to publish news via email. Newsmail can generate RSS feeds for news matching a given category.
Main features:
- import plain text or HTML email messages with or without attachments, and with or without Markdown syntax.
- store messages in database (currently Postgresql and MySQL are supported, but the PHP code uses Pear::DB abstraction) and attachments in filesystem.
- request a confirmation message before publishing or deleting news.
- require an approvation from a moderator before publishing or deleting news.
- answer to some administration commands directly via email (e.g. news listing, news delete and update).
- generate an RSS feed with news matching a particular category or with category equal to all
Enhancements:
- A small improvement was made to the install instructions.
- An approval option was added, which requires BCC_ADDRESS approval for inserting and deleting messages.
- The approval process uses a randomly generated token password to improve security.
- The database structure was changed to use a token for approval security.
- The MySQL table definition was improved to use INNODB.

Mail::Message::Head::Complete is a Perl module with the header of one message.

INHERITANCE

Mail::Message::Head::Complete
is a Mail::Message::Head
is a Mail::Reporter

Mail::Message::Head::Complete is extended by
Mail::Message::Head::Partial
Mail::Message::Replace::MailHeader

Mail::Message::Head::Complete is realized by
Mail::Message::Head::Delayed
Mail::Message::Head::Subset

SYNOPSIS

my $head = Mail::Message::Head::Complete->new;
See Mail::Message::Head

E-mails message can be in various states: unread, partially read, and fully read. The class stores a message of which all header lines are known for sure.

Gtk2::Ex::Dialogs::Message provides a simple message dialog.

SYNOPSIS

use Gtk2::Ex::Dialogs::Message ( destroy_with_parent => TRUE,
modal => TRUE,
no_separator => FALSE );

# do some stuff like creating your apps main $window then,
# to ensure that all messages use the right parent, set it:
$Gtk2::Ex::Dialogs::Message::parent_window = $window;

# now popup a new dialog ( blocking the main loop if there is one )
new_and_run
Gtk2::Ex::Dialogs::Message ( title => "Dialog Title",
text => "This is a simple message" );

# now popup a somwhat useful dialog that doesnt block any main loop
# but on the other side of the coin, if there is no main loop the
# dialog will be completely unresponsive.
new_show
Gtk2::Ex::Dialogs::Message ( title => "Uhm",
text => "Use when there is a main loop." );

This module provides a simple dialog api that wraps Gtk2::Dialog objectively. The objective is a clean and simple message dialog (only an "OK" button).

Mail::Message::Construct::Build is a Perl module for building a Mail::Message from components.

SYNOPSIS

my $msg3 = Mail::Message->build
(From => me, data => "only twonlinesn");

my $msg4 = Mail::Message->buildFromBody($body);

Complex functionality on Mail::Message objects is implemented in different files which are autoloaded. This file implements the functionality related to building of messages from various components.