Free imap vs pop software for linux

IMAP utils software contains a set of simple utilities for managing IMAP emails.
imap-purge
Purges old read and unread mails from folders.
imap-folders
Creates folders on IMAP.
imap-stats
Shows summary about unread and unseen mails.
Enhancements:
- Several new scripts for reading and storing messages were added.

IMAP Spam Begone is a script that scans an IMAP inbox for spam using SpamAssassin, moving any found to another folder. Unlike the normal mode of deployments for SpamAssassin, isbg does not need to be involved in mail delivery, and can run on completely different machines to where your mailbox actually is.
It has been filtering my work email, some of which comes from a legacy email address that is from a spam unfiltered system. I run it as a cronjob every 15 minutes, and have had it doing that for 6 months. I get about 500 spams a month. Many other users are using it for a various servers abd a variety of platforms.
There are no known outstanding bugs.
Main features:
- Works with all common IMAP servers
- Works on Linux, MacOS X and Windows
- Can do IMAP over SSL
- Can remember your password
- Will work painlessly against multiple IMAP accounts and servers
- Is not involved in the mail delivery process, and so can run on any machine that can contact your IMAP server
- Highly configurable
- Sensible defaults so you dont have to do any configuring :-)

sKimap SuperKaramba theme will display the number of new and unread emails in your imap mail account. It can monitor your imap server mailboxes for new and unread messages. It will auto-size itself to accommodate the number of mailboxes you are watching.

The number of mailboxes is only limited by your screen real-estate. You can choose which of the mailboxes on your account you want to watch.

You can set the update interval, and which email client opens when you click the top of the theme. Configuration is all done through a configuration dialog.

Debian vs Pimientos is an arcade game developed using the SDL libraries SDL, SDL_image, SDL_mixer, and SDL_ttf. This permits the portability of the game to some systems and machines.
Debian vs Pimientos is the first game of NEOPONTEC Games, and the first to use the NNG Engine (New Neopontec Gaming Engine) developed by Hector Blanco (me) that uses the mentioned SDL Libraries.
The game concept is very easy to understand and to play. There are a lot of peppers (pimientos is the spanish word for peppers) that are flying by the sky, and you, armed with the Debian logo must fight them. The Debian logo shoots GNU heads to kill these devil pimientos
Main features:
- 800x600 resolution at 32 bits.
- High quality images.
- Addictive and funny playing experience
- Cross-platform open source game: (binaries for Win32 & Linux, and sources for other systems).
- Different classes of peppers (pimientos).

squid-imap provides a piece of oftware to authenticate squid users via an IMAP server.

squid-imap is a basic squid auth helper that authenticates usernames and passwords via an IMAP server.

pam_imap is a PAM module that authenticates against a remote IMAP or IMAPS server.
pam_imap program supports multiple servers, SSL, password caching, user blacklists (for admin users), and many configuration abilities.
Examples of recommended use:
1) A lab of UNIX/Linux machines that would require an easily accessible password database from an IMAP server
2) Authenticating users against a centralized password server that you have no control over, and it conveniently has an IMAP server. (The arms-tied-behind-your-back scenario)
3) Authenticating with applications that do not run as root. (Apache is a good example -- read user-testimonials below)
4) An IMAP cluster authentication relay -- pam-imap can be used for a cheap IMAP cluster solution. Have one or two master IMAP servers that have a username/password database (be it LDAP, shadow, etc) and an IMAP server. Have several cluster node servers to handle the bandwidth of client requests , and use pam-imap on each node to authenticate against the master server(s). (The node machines will use pam-imap in their imap service file)
Tie everything together with round-robin DNS and NFS mail folders, and you have yourself an IMAP cluster!
Main features:
- User BlockList: Allows pam-imap to ignore authenticating users such as root, apache, and others.
- Password caching: Possibly usefull in situations where network connections are slow, or server loads are high. Has a few security risks however. Checkout the README file for more info.
- Support for username@domain.com style logins. With Micro$oft style IMAP servers, the "@domain.com" can be appended to the UNIX username for easy compatability.
- Customizable "Password: " string... You could change it to anything! Maybe, "IMAP Password: " The possibilities are endless.

IMAP::Admin is a Perl module for basic IMAP server administration.

SYNOPSIS

use IMAP::Admin;

$imap = IMAP::Admin->new(Server => name.of.server.com,
Login => login_of_imap_administrator,
Password => password_of_imap_adminstrator,
Port => port# (143 is default),
Separator => ".", # default is a period
CRAM => 1, # off by default, can be 0,1,2
SSL => 1, # off by default
# and any of the SSL_ options from IO::Socket::SSL
);

$err = $imap->create("user.bob");
if ($err != 0) {
print "$imap->{Error}n";
}
if ($err != 0) {
print $imap->error;
}
$err = $imap->create("user.bob", "green");
$err = $imap->delete("user.bob");
$err = $imap->h_delete("user.bob");

$err = $imap->subscribe("user.bob");
$err = $imap->unsubscribe("user.bob");

$err = $imap->rename("bboard", "newbboard");

@quota = $imap->get_quotaroot("user.bob");
@quota = $imap->get_quota("user.bob");
$err = $imap->set_quota("user.bob", 10000);

@acl = $imap->get_acl("user.bob");
%acl = $imap->get_acl("user.bob");
$err = $imap->set_acl("user.bob", "admin", "lrswipdca", "joe", "lrs");
$err = $imap->delete_acl("user.bob", "joe", "admin");

@list = $imap->list("user.bob");
@list = $imap->list("user.b*");

$imap->{Capability} # this contains the Capabilities reply from the IMAP server

$imap->close; # close open imap connection

IMAP::Admin provides basic IMAP server adminstration. It provides functions for creating and deleting mailboxes and setting various information such as quotas and access rights.

Its interface should, in theory, work with any RFC compliant IMAP server, but I currently have only tested it against Carnegie Mellon Universitys Cyrus IMAP and Mirapoints IMAP servers. It does a CAPABILITY check for specific extensions to see if they are supported.

Operationally it opens a socket connection to the IMAP server and logs in with the supplied login and password. You then can call any of the functions to perform their associated operation.

Separator on the new call is the hiearchical separator used by the imap server. It is defaulted to a period ("/" might be another popular one).

CRAM on the new call will attempt to use CRAM-MD5 as the login type of choice. A value of 0 means off, 1 means on, 2 means on with fallback to login. *Note* this options requires these perl modules: Digest::MD5, Digest::HMAC, MIME::Base64

SSL on the new call will attempt to make an SSL connection to the imap server. It does not fallback to a regular connection if it fails. It is off by default. IO::Socket::SSL requires a ca certificate, a client certificate, and a client private key. By default these are in current_directory/certs, respectively named ca-cert.pem, client-cert.pem, and client-key.pem. The location of this can be overridden by setting SSL_ca_file, SSL_cert_file, and SSL_key_file (youll probably want to also set SSL_ca_path).

I generated my ca cert and ca key with openssl: openssl req -x509 -newkey rsa:1024 -keyout ca-key.pem -out ca-cert.pem
I generated my client key and cert with openssl: openssl req -new -newkey rsa:1024 -keyout client-key.pem -out req.pem -nodes openssl x509 -CA ca-cert.pem -CAkey ca-key.pem -req -in req.pem -out client-cert.pem -addtrust clientAuth -days 600

Setting up SSL Cyrus IMAP v 2.x (completely unofficial, but it worked for me) add these to your /etc/imapd.conf (remember to change /usr/local/cyrus/tls to wherever yours is) tls_ca_path: /usr/local/cyrus/tls tls_ca_file: /usr/local/cyrus/tls/ca-cert.pem tls_key_file: /usr/local/cyrus/tls/serv-key.pem tls_cert_file: /usr/local/cyrus/tls/serv-cert.pem
For my server key I used a self signed certificate: openssl req -x509 -newkey rsa:1024 -keyout serv-key.pem -out serv-cert.pem -nodes -extensions usr_cert (in openssl.cnf I have nsCertType set to server)
I also added this to my /etc/cyrus.conf, it shouldnt strictly be necessary as clients that are RFC2595 compliant can issue a STARTTLS to initiate the secure layer, but currently IMAP::Admin doesnt issue this command (in SERVICES section): imap2 cmd="imapd -s" listen="simap" prefork=0
where simap in /etc/services is: simap 993/tcp # IMAP over SSL

Courier-IMAP is a fast, scalable, enterprise IMAP server that uses Maildirs. Many E-mail service providers use Courier-IMAP to easy handle hundreds of thousands of mail accounts.
With the built-in IMAP and POP3 aggregation proxy in Courier-IMAP 4.0, the only practical limit to Couriers horizontal scalability is available LAN bandwidth. In proxy mode, a pool of Courier servers receive IMAP and POP3 connections from clients, wait for the clients to send a login request, look up the mail accounts server, and establish a proxy connection to the actual server that hosts the mail account.
Please note that this IMAP server does NOT handle traditional mailbox files (/var/spool/mail, and derivatives), it was written and optimized for the specific purpose of providing IMAP access to Maildirs.
"Maildir" is a directory-based mail storage format originally introduced in the Qmail mail server, and adopted as an alternative mail storage format by both Exim and Postfix. Courier-IMAP is popular on Qmail/Exim/Postfix sites that are configured to use maildirs. The primary advantage of maildirs is that multiple applications can access the same Maildir simultaneously without requiring any kind of locking whatsoever. Maildir is a faster and more efficient way to store mail. It works particularly well over NFS, which has a long history of locking-related woes.
This is the same IMAP server thats included in the Courier mail server, but configured as a standalone IMAP server that can be used with other mail servers - such as Qmail, Exim, or Postfix - that deliver to maildirs. A Courier/Postfix combination is very popular. If you already have Courier installed, you do not need to download this version. If you install this version, you must remove it if you later install the entire Courier server. Its possible to have both versions installed, but this will require a delicate juggling act that youll have to learn on your own.
Enhancements:
- A bug in quota calculation on 64-bit platforms has been fixed.
- The IMAP server will try to log the clients bandwidth usage if the server process gets killed by a signal.
- New messages created by the IMAP server will use the servers umask setting.
- Many compiler warnings, error messages, and manual page typos were fixed.