Free msgid software for linux

Mail::SendEasy can send plain/html e-mails through SMTP servers (platform independent). Supports SMTP authentication and attachments.

This modules will send in a easy way e-mails, and doesnt have dependencies. Soo, you dont need to install libnet.
It supports SMTP authentication and attachments.

USAGE:

OO

use Mail::SendEasy ;

my $mail = new Mail::SendEasy(
smtp => localhost ,
user => foo ,
pass => 123 ,
) ;

my $status = $mail->send(
from => sender@foo.com ,
from_title => Foo Name ,
reply => re@foo.com ,
error => error@foo.com ,
to => recp@domain.foo ,
cc => recpcopy@domain.foo ,
subject => "MAIL Test" ,
msg => "The Plain Msg..." ,
html => "The HTML Msg..." ,
msgid => "0101" ,
) ;

if (!$status) { print $mail->error ;}

STRUCTURED

use Mail::SendEasy ;

my $status = Mail::SendEasy::send(
smtp => localhost ,
user => foo ,
pass => 123 ,
from => sender@foo.com ,
from_title => Foo Name ,
reply => re@foo.com ,
error => error@foo.com ,
to => recp@domain.foo ,
cc => recpcopy@domain.foo ,
subject => "MAIL Test" ,
msg => "The Plain Msg..." ,
html => "The HTML Msg..." ,
msgid => "0101" ,
) ;

if (!$status) { Mail::SendEasy::error ;}

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.

Email::Store is a framework for database-backed email storage.

SYNOPSIS

use Email::Store dbi:mysql:mailstore;
Email::Store->setup; # Do this once

Email::Store::Mail->store( $rfc822 );
Email::Store::Mail->retrieve( $msgid );

...

Email::Store is the ideal basis for any application which needs to deal with databases of email: archiving, searching, or even storing mail for implementing IMAP or POP3 servers.

Email::Store itself is a very lightweight framework, meaning it does not provide very much functionality itself; in effect, it is merely a Class::DBI interface to a database schema which is designed for storing email. Incidentally, if you dont know much about Class::DBI, youre going to need to in order to get much out of this.

Despite its minimalist nature, Email::Store is incredibly powerful. Its power comes from its extensibility, through plugin modules and hooks which allow you to add new database tables and concepts to the system, and so access the mail store from a "different direction". In a sense, Email::Store is a blank canvas, onto which you can pick and choose (or even write!) the plugins which you want for your application.

For instance, the core Email::Store::Entity plugin module addresses the idea of "people" in the email universe, allowing you to search for mails to or from particular people; (despite their changing names or email addresses) Email::Store::Thread interfaces Email::Store to Mail::Thread allowing you to navigate mails by their position in a mail thread; the planned non-core Email::Store::Plucene module plugs into the indexing process and stores information about emails in a Plucene search index for quick retrieval later, and so on.

News::Archive is a Usenet news archiving package for downloading and later accessing news articles in bulk.

It can load articles laid out in INN format, retrieve them from a running news server, or just take articles one-by-one. News::Archive module is compatible with News::Web and Net::NNTP::Server, so the articles can be shared either via the Web or via NNTP.

SYNOPSIS

use News::Archive;
my $archive = new News::Archive
( basedir => /home/tskirvin/kiboze );

# Get a news article
my $article = News::Article->new(*STDIN);
my $msgid = article->header(message-id);

die "Already processed $msgidn"
if ($archive->article( $messageid ));

# Get the list of groups were supposed to be saving the article into
my @groups = split(s*,s*, $article->header(newsgroups) );
map { s/s+//g } @groups;

# Make sure were subscribed to these groups
foreach (@groups) { $archive->subscribe($_) }

# Actually save the article.
my $ret = $archive->save_article(
[ @{$article->rawheaders}, , @{$article->body} ], @groups );
$ret ? print "Accepted article $messageidn"
: print "Couldnt save article $messageidn";

News::Archive keeps several files to keep track of its archives:

active file

Keeps track of all newsgroups we are "subscribed" to and all of the information that changes regularly - the number of articles we have archived, the current first and last article numbers, etc.

Watched over with News::Active.

history database

A simple database keeping track of articles by Message-ID. Makes access by ID easy, and ensures that we dont save the same article twice. The database chosen to maintain these is user-determined.

newsgroup file

Keeps track of more static information about the newsgroups we are subscribed to - descriptions, creation dates, etc.

Watched over with News::GroupInfo.

archive directory

Directory structure of all articles, with each article saved as a single textfile within a directory structure laid out at one section of the group name per directory, such as "rec/games/mecha". Crossposts are hardlinked to other directory structures.

Articles are actually divided into sub-directories containing up to 500 articles, to avoid Unix directory size performance limitations. Individual files are thus stored in a file such as "rec/games/mecha/1.500/1".

Each newsgroup also contains overview information, watched over with
News::Overview. This overview file goes in the top of the structure,
such as "rec/games/mecha/.overview".

You may note that these files are very similar to how INN does its work. This is intentional - this package is meant to act in many ways like a lighter-weight INN.

Usage:

Global Variables

The following variables are set within News::Archive, and are global throughout all invocations.

$News::Active::DEBUG
Default value for "debug()" in new objects.

$News::Active::HOSTNAME
Default value for "hostname()" in new objects. Obtained using
"Sys::Hostname::hostname()".

$News::Active::HASH
The number of articles to keep in each directory. Default is 500;
change this at your own peril, since things may get screwed up later
if you change it after archiving any articles!

Mail::Webmail::Yahoo is a Perl module that enables bulk download of yahoo.com -based webmail.

SYNOPSIS

use Mail::Webmail::Yahoo;
$yahoo = Mail::Webmail::Yahoo->new(%options);
@folders = $yahoo->get_folder_list();
@messages = $yahoo->get_mail_messages(Inbox, all);
# Write messages to disk here, or do something else.

This module grew out of the need to download a large archive of web mail in bulk. As of the modules creation Yahoo did not provide a simple method of performing bulk operations.

This module is intended to make up for that shortcoming.

METHODS

$yahoo = new Mail::Webmail::Yahoo(...)

Creates a new Mail::Webmail::Yahoo object. Pass parameters in key => value form, and these must include, at a minimum:

username
password

You may also pass an optional cookie file as cookie_file => /path/to/file.
$yahoo->connect();

Connects the application with the site. Really this is not necessary, but its in here for hysterical raisins.
$yahoo->login();

Method which performs the login stage of connecting to the site. This method can take a while to complete since there are at least several re-directs when logging in to Yahoo.

Returns 0 if already logged in, 1 if successful, otherwise sets $@ and returns undef.
@headers = $yahoo->get_mail_headers($folder);

***REMOVED***

@messages = $yahoo->get_mail_messages($folder);

Returns an array of message headers for the $folder folder. These are mostly in Mail::Internet format, which is nice but involves constructing them from what Yahoo provides -- which aint much. When an individual message is requested, we can get more info via turning on the headers, so this method requests each method in turn (caching for future use, unless cache_messages is turned off) and builds a Mail::Internet object from each message.

You can get the raw headers from get_folder_index().

Note that for reasons of efficiency this method collects headers and the full text of the message, and this is cached to avoid having to go back to the network each time. To force a refresh, set the Snagmail objects cache to 0 with

$yahoo->cache_messages(0);
$yahoo->cache_headers(0);

Note: There used to be a $callback parameter to this method, but since it was never used it has been removed.

my $msg = $yahoo->_process_message($page, $yahoo_msg_id);

Extracts and returns as a Mail::Internet object the headers and message body from the provided HTML ($page).

my $msg = $yahoo->_extract_headers($page, $yahoo_msg_id);

Performs the actual extraction of the message headers from the given HTML in $page. Pushes the $yahoo_msg_id into the headers as X-Yahoo-MsgId. Also adds a version header.

my $ok = $yahoo->_extract_body($mhdr, $page);

Extracts and adds to the Mail::Internet object in $mhdr the message body, including any attachments parsed out of $page. Returns 1 to indicate success, although no error conditions are currently checked for/ handled.

$page = $yahoo->download_attachment($download_uri, $mailmsg);

Downloads an attachment from the specified URI. $mailmsg is a reference to a Mail::Internet object. The downloaded attachment is added to the mailmsg via add_attachment_to_message()

$yahoo->add_attachment_to_message($msg, $attachment, $filename);

Adds the $attachment to $msg, adjusting Content-Type and MIME-Version as necessary.

$yahoo->make_multipart_boundary()

Currently does nothing useful. So far all messages have had correct types.

$yahoo->get_folder_action_link($mbox, $linktype, $force);

Returns and stores the action link for the given $linktype. This is a URI that will cause an action to be performed on a message set, such as DELETE or MOVE.

@message_headers = $yahoo->get_folder_index($folder);

Returns a list of all the messages in the specified folder. These messages are stored as URIs. Logs the user in if necessary.

@messages = $yahoo->_get_message_links($page)

(Private instance method)

Returns the actual links (as an array) needed to pull down the messages. This method is used internally and is not intended to be used from applications, since the messages returned are not in a very friendly form. This method returns only the messages referenced on a given page, and is called from get_folder_index() to build up a complete list of all messages in a folder.

@folders = $yahoo->get_folder_list();

Returns a list of folders in the account. Logs the user in if necessary. Also stores the two special folders (Trash and Bulk) so they can be emptied later.

$ok = $yahoo->send($to, $subject, $body, $cc, $bcc, $flags);

Attempts to send a message to the recipients listed in $to, $cc, and $bcc, with the specified subject and body text. $to,$cc, and $bcc can be scalars or arrayrefs containing lists of recipients.

Logs the user in if necessary.

$flags may contain any combination of the constants exported by this package. Currently, these constants are:
SAVE_COPY_TO_SENT_FOLDER : saves a copy of a sent message
ATTACH_SIG : attaches the senders Yahoo signature
SEND_AS_HTML : sends the message in HTML format.
cc and bcc come after subject and body in the parameter list (instead of with to) since it is expected that

send(to, subject, body)

will be more common than sending to Cc or BCc recipients - at least, this is how it is in my experience.

As of this version, address-book lookups are not supported.
As of this version, mail attachments are not supported.
$resp = $yahoo->_get_a_page($uri, $method, $params);
(Private instance method)

Requests and returns a page found at the specified $uri via the specified $method. If $params (an arrayref) is present it will be formatted according to the method.

If method is empty or undefined, it defaults to GET. The ordering of the parameters, while seemingly counter-intuitive, allows one of the great virtues of programming (laziness) by not requiring that the method be passed for every call.

Returns the response object if no error occurs, undef on error.
$current_trace_level = $yahoo->trace($new_trace_level);
if $new_trace_level exists, sets the new level for tracing the operation of the object. Returns the current trace level (i.e. before setting a new one).

Trace levels are:

0 no tracing output; warning messages only.
> 0 informative messages ("what I am doing")
> 1 URIs being fetched
> 2 request response codes
> 3 request parameters
> 4 any other extra debugging info.
> 9 request response content

$yahoo->debug(...);

Sends debugging messages to STDERR, appended with a newline.
$yahoo->make_host($uri) or Yahoo::make_host($uri)

Returns a string consisting of just the scheme, host, and port parts of the URI. The URI::URL::as_string method returns the full URI (including path) but leaves out the port number, which is why its unsuitable here.

Locale::Maketext::Lexicon is a Perl module to use other catalog formats in Maketext.

SYNOPSIS

As part of a localization class, automatically glob for available lexicons:

package Hello::I18N;
use base Locale::Maketext;
use Locale::Maketext::Lexicon {
* => [Gettext => /usr/local/share/locale/*/LC_MESSAGES/hello.mo],
### Uncomment to decode lexicon entries into Unicode strings
# _decode => 1,
### Uncomment to fallback when a key is missing from lexicons
# _auto => 1,
### Uncomment to use %1 / %quant(%1) instead of [_1] / [quant, _1]
# _style => gettext,
};
Explicitly specify languages, during compile- or run-time:
package Hello::I18N;
use base Locale::Maketext;
use Locale::Maketext::Lexicon {
de => [Gettext => hello_de.po],
fr => [
Gettext => hello_fr.po,
Gettext => local/hello/fr.po,
],
};
# ... incrementally add new lexicons
Locale::Maketext::Lexicon->import({
de => [Gettext => local/hello/de.po],
})

Alternatively, as part of a localization subclass:

package Hello::I18N::de;
use base Hello::I18N;
use Locale::Maketext::Lexicon (Gettext => *DATA);
__DATA__
# Some sample data
msgid ""
msgstr ""
"Project-Id-Version: Hello 1.3.22.1n"
"MIME-Version: 1.0n"
"Content-Type: text/plain; charset=iso8859-1n"
"Content-Transfer-Encoding: 8bitn"

#: Hello.pm:10
msgid "Hello, World!"
msgstr "Hallo, Welt!"

#: Hello.pm:11
msgid "You have %quant(%1,piece) of mail."
msgstr "Sie haben %quant(%1,Poststueck,Poststuecken)."

This module provides lexicon-handling modules to read from other localization formats, such as Gettext, Msgcat, and so on.

If you are unfamiliar with the concept of lexicon modules, please consult Locale::Maketext and http://www.autrijus.org/webl10n/ first.

A command-line utility xgettext.pl is also installed with this module, for extracting translatable strings from source files.

gtranslator project is an enhanced gettext po file editor for the GNOME desktop environment. It handles all forms of gettext po files like compiled gettext po files (gmo/mo files), compressed po files (po.gz/po.bz2 etc.) and features many comfortable everyday usage features likeFind/Replace, Auto Translation, Message Translation Learning, Messages Table (for having an overview of the translations/messages in the po file), Easy Navigation and Editing of translation messages & comments of the translation where accurate. It has got really very much to offer therefore you should simply test it and be happy with it!
Main features:
- Highly customizable syntax highlighting (colorschemes are in xml and very easy to write).
- Different views of po files are supported.
- In-GUI compiling of the po file.
- Instant, customizable spell checking (ispell-based).
- Advanced history/recent files menu with project name & version -- not only the filename like other apps do it.
- Very comfortable header editing with selection boxes and automatical change of the other fields corresponding to your current selection.
- Opening of compiled (.gmo/.mo) gettext po files and compressed gettext po files is directly supported (open your gnumeric.mo and edit it to make your individual translation!).
- Navigation within untranslated/fuzzy messages.
- Update functionality with the help of xml-i18n-tools/gnu-i18n-tools.
- Query capability to search for already made translations in the gettext domains.
- Autoaccomplishment of found translations from the default query domain.
- Autofilling of po file headers with the entries from the preferences (never edit header comments again).
- Full DnD support and session awareness, therefore good integration into your GNOME desktop.
- Find/replace dialogs/functions.
- HTMLizer function which converts your po file into a syntactically highlighted html file to allow web-viewing of your po files.
- Old, obsolete entries can be kept if you wish to keep them.
- Status indiciation through status bar and progress bar.
- Docbook- & Scrollkeeper-enabled help which does also appear in the Nautilus help sidebar.
- URI support for all cases; opening of remote URLs is also supported.
- Signal handling which makes it possible to rescue po files which couldnt be saved due to a crash/interrupting/etc. in gtranslator -- loose less work with gtranslator!
- UTF-8 po files editing (in versions >= 0.39).
- List view for message which is very comfortable and sortable (its based upon ETable/ETree from GAL).
- Personal learn buffer to support auto accomplishment with personal/learned translations from an UMTF file.
- Very comfortable messages table with colored, grouped display of the messages: group headers also show up the resting messages count.
- Useful undo for deletion, insertion.
- Importing from/converting to UTF-8 is possible from the GUI.
- Direct taking over the msgid as the msgstr.
- Enhanced learn buffer techniques added ("fuzzy" matching routines with a grade of voodoo).
- Messages table popup menu with translation look up for untranslated and fuzzy messages with the possibility to insert/take over the found the translation found in the learn buffer.
- pozilla !!!