Free aim mail software for linux

"You don`t have to be an America Online member to experience the immediate cross-Internet communication made possible by AOL Instant Messenger.
This program allows Internet users to communicate via private, personalized text messages.
The program indicates when friends, family members, and business colleagues are online, making Internet communications faster, easier, and more efficient.
AOL Instant Messenger combines AOL`s popular Buddy List and Instant Message features, enabling users to send and respond to messages immediately."
Enhancements:
- Improved Popups Preferences
- Support for @mac.com addresses
- The wireless icon is the visual indication on the buddy list that a buddy is using a mobile device.
- File Transfer (with Drag&Drop support)
- Displays idle time
- Ability to install anywhere. (Extract everything into a single directory and then run aim with option "--install_dir %path" where %path is the path to directory containing all the libraries)

IDMS DBMA provides a fast, efficient c10k compliant mail agent.
IDMS DBMA is an effort to develop a highly scalable (c10k compliant), plugin-based mail agent aimed at fighting spam and viruses.
It is meant to replace hard-to-maintain, complex, resource hungry configurations used by small to large users today.
Enhancements:
- Added configure script
- Bug with catchall aliases fixed
- Small code cleanups

Fetch and deliver mail is a simple, lightweight replacement for mail fetching, filtering, and delivery programs such as fetchmail and procmail.
It can fetch using POP3, POP3S, IMAP, IMAPS, or stdin, and deliver to a pipe, file, maildir, mbox, or SMTP server, based on a set of regexps.
Fetch and deliver mail can be used for both single user and multiuser setups, and is designed with privilege separation when running as root.
Enhancements:
- Mostly configuration file enhancements and code cleanup were done since 1.2. ifdef/endif blocks and inline shell commands are allowed in the configuration file.
- A built-in string cache using TDB was added.
- Some extra default tags were added. NNTPS fetching was implemented.

AIM Sniff is a utility for monitoring and archiving AOL Instant Messenger messages across a network.
You can either do a live dump (actively sniff the network) or read a PCAP file and parse the file for IM messages. You also have the option of dumping the information to a MySQL database, a flat file, STDOUT, or any combination of the three.
AIM Sniff allows administrators to see how often users are chatting to monitor for abuse and you can also use AIM Sniff to monitor for cases of harassment or pirated software trading. It has been tested on FreeBSD, Linux, and OS X.
AIM Sniff is licensed under the GNU General Public License (GPL).
Enhancements:
- Several bugfixes from the alpha release are included, as well as a few feature enhancements.
- Daemon mode is now working, and there is a feature to not use a handles file (useful when using the software behind a NAT).
- In addition, the install will prompt for MySQL admin credentials for creating the database.
- Issues with the MSN message types crashing the DB and connections to the DB timing out after a period of time have been fixed.
- Also fixed is "noise" from database SQL statements.

Net::AIM is a Perl extension for AOL Instant Messenger TOC protocol.

SYNOPSIS

use Net::AIM;

$aim = new Net::AIM;
$conn = $aim->newconn(Screenname => Perl AIM,
Password => yaddayadda);
$aim->start;

This module implements an OO interface to the Aol Instant Messenger TOC protocol.

This version contains not much more than hacked code that merely connects to the aol TOC servers and acts on instant messages.

METHODS

Net::AIM->new()

This is the Net::AIM constructor. No arguments needed.

$aim->debug($debug)

Set whether to print DEBUGGING information to STDERRR. Accepts $debug which should be a boolean value.

$aim->set($key, $val)

This method simply sets $key to $val in an internal hash for variables

$aim->get($key)

This method simply gets the value of $key from the internal hash

$aim->newconn()

This method creates a new AIM::Connection object

$aim->getconn()

This method returns a pointer to the AIM::Connection object

$aim->do_one_loop()

This executes one read off the socket.

$aim->start()

This just starts an infinte loop of $aim->do_one_loop;

$aim->timeout($secs);

This sets or returns the current timeout in seconds for the select loop. Takes 1 optional argument. Fractional timeout values are ok.

$aim->add_buddy($send_bool, $group, @buddies);

This adds @buddies to your buddy list, under the group $group. if $send_bool evaluates to TRUE then the toc_add_buddy command is sent to the server. Otherwise it is not sent out. This function will also save the list internally.

$aim->add_permit($send_bool, $group, @buddies);

This adds @buddies to your permit list, under the group $group. if $send_bool evaluates to TRUE then the toc_add_permit command is sent to the server. Otherwise it is not sent out. This function will also save the list internally.

$aim->add_deny($send_bool, $group, @buddies);

This adds @buddies to your deny list, under the group $group. if $send_bool evaluates to TRUE then the toc_add_deny command is sent to the server. Otherwise it is not sent out. This function will also save the list internally.

$aim->remove_buddy($send_bool, $group, @buddies);

This removes @buddies from your buddy list. $group must be the group they were orginally set with for them to be deleted from the internal $aim memory and prevent them from getting added again incase a set_config method is called.

if $send_bool evaluates to TRUE then the toc_add_deny command is sent to the server. Otherwise it is not sent out. This function will also save the list internally.

$aim->set_idle($idle_time)

This method sets our idle time to $idle_time. If $idle_time is omitted it will be set to 0.

$aim->get_info($screen_name)

Sends an info request to the server for $screen_name. The server should reply with a URL which will contain the info requested about the user.

$aim->set_info($info)

This method sets your info or profile information to $info on the server.

$aim->evil($user, $anon)

Warn $screen_name. $anon: boolean value which will determine whether to warn the user anonymously or normally. Anonymous warnings are less severe.

$aim->send($message)

Send $message to the server. This is used internally by other functions to send commands to the server.

$aim->send(toc_add_buddy perlaim)

$aim->chat_invite($room, $msg, @buddies)

Invite @buddies to $room with the message $msg

$aim->chat_accept($room_id)

This will accept an invitation that was sent to us for $room_id

$aim->chat_leave($room_id)

This method instructs the server to take you out of the room $room_id

$aim->chat_whisper($room_id,$user,$msg)

Whisper $msg to $user in the room $room_id

$aim->chat_send($room_id, $message)

Send $message in chat room $room_id

$aim->chat_join($roomname)

Send a request to enter the room $roomname

$aim->send_im($screen_name, $message)

This method sends $message to $screen_name.

$aim->list_rooms();

This method returns an @array of rooms each consisting of ID:ROOM_NAME. For instance: 235236:Perl AIM Chat12 234323:Perl AIM Chat13 235832:Perl AIM Chat14 125082:Perl AIM Chat15

$aim->get_roomname($id)

This method returns the name of the room with id $id.

$aim->set_roomname($id, $roomname)

This saves $roomname in the $aim object in a %hash keyed on $id.

$aim->del_roomname($id)

Deletes $id and its associate value from our roomname hash in $aim

$aim->encode($str)

This method returns $str encoded as per the TOC specs: escaped special chars ({}[]$) and enclosed in quotes (")

$aim->send_config()

This method instructs the module to send our configurations which are the mode (permit/deny/all) and our buddy list to the server and to set it as our saved config on the server

$aim->send_buddies()

This method instructs the module to send all our current buddies to the AOL server.

$set_config_str($config_str, add_bool)

This parses a config string of the form: g Buddies p permit1 p permit2 d deny1 d deny2 b budd1 b budd2

Key: g - Buddy Group (All Buddies until the next g or the end of config are in this group.) b - A Buddy p - Person on permit list d - Person on deny list m - Permit/Deny Mode. Possible values are 1 - Permit All 2 - Deny All 3 - Permit Some 4 - Deny Some

$aim->normalize($data)

This method normalizes $data by killing all but strict alphnumeric characters. Typically used for screen_names.

ConceptRM (RssMail) project is an email client using RSS as a means to deliver the list of email to the user.
Main features:
- Support pop3 mailbox
- Support for multiple mailboxes (display a preferred format e.g. html as opposed to plain email format)
- multipart email
- email deletion
- RSS 1.0 and 2.0 support

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.