Free imap software for linux

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.

imapbiff checks IMAP accounts for new mail. It uses images similar to those of the classic xbiff program. The project works similar to xbiff, except it is only used to check for new mail in IMAP accounts.

It is written in perl, and requires the Tk module for perl. It was written spefically to be docked in my fvwm2 button bar, as I could not find a simple xbiff like app that would do IMAP checks.

imap_tools consists of three programs: imap_search, imap_filter, and imap_rename.

All programs run from your PC against your IMAP server, so there is no need to install any server side software. imap_filter provides a way to write easy filter rules.

IMAP Proxy server is a caching IMAP proxy server. It was written to compensate for webmail clients that are unable to maintain persistent connections to an IMAP server. Most webmail clients need to log in to an IMAP server for nearly every single transaction.

This behaviour can cause tragic performance problems on the IMAP server. imapproxy tries to deal with this problem by leaving server connections open for a short time after a webmail client logs out.

When the webmail client connects again, imapproxy will determine if theres a cached connection available and reuse it if possible.

How does imapproxy keep track of which server connection is for which user?

Upon the first successful login to the real IMAP server (through the proxy), imapproxy fills in a little record that contains the username, an md5 digital signature of the password and the server socket descriptor thats being used.

After you log out and then log back in again, imapproxy just has to find a record that matches your username and password. These records are stored in a hash table (with the username being the hash key) in memory, so the lookups are pretty fast.

Can IMAP Proxy support multiple backend servers?

If you want IMAP Proxy to be able to proxy to multiple backend IMAP servers, you can run multiple instances of IMAP Proxy and make sure each instance is looking at a different configuration file.

Before you do this, take a look at perdition which appears to have been designed with this specific task in mind.

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

IMAPFilter is a mail filtering utility. It connects to remote mail servers using the Internet Message Access Protocol (IMAP), sends searching queries to the server and processes mailboxes based on the results.
IMAPFilter can be used to delete, copy, flag, move, etc. messages residing in mailboxes at the same or different mail servers. The 4rev1 and 4 versions of the IMAP protocol are supported.
IMAPFilter uses the Lua programming language as a configuration and extension language.
Main features:
- Definition of filters using many searching criteria available in the IMAP protocol, such as:
- Matching of a string in the headers or the body of a message.
- Size of a message.
- Date of a message.
- Status (recent, unread, etc.) of a message.
- Ability to use logical operators (and/or/not) while defining filters.
- Different actions when a filter matches a message, including:
- Deleting of a message.
- Moving of a message to a mailbox in the same of different servers
- Copying of a message to a mailbox in the same or different servers.
- Changing of a messages flags.
- Listing of the available and/or subscribed mailboxes, along with support for the IMAP CHILDREN extension.
- Internationalisation (I18N) support.
- Server namespace support using the IMAP NAMESPACE extension.
- Secure Socket Layer (SSL) or Transport Layer Security (TLS) encrypted imaps (port 993) connections.
- Encrypted connections using the IMAP STARTTLS extension.
- User authentication with the Challenge-Response Authentication Mechanism (CRAM), specifically CRAM-MD5.

xbmcmail-imap is an IMAP/IMAPS email reader for the XBox using the XBox Media Centers builtin Python engine.
xbmcmail-imap supports attachments, folders, mail management (copy, move, delete), printing (text or postscript), background polling, multiple accounts, RTF and HTML converters, and more.
Enhancements:
- fixed skinning issues with XBMC 2.x
- bug fixes for process dialog handling
- IMAP compatibility issues
- better control handling
- minor corrections