Free imap settings software for linux

simplesettings 0.5 is an excellent tool for programmers. It provides simple settings for initialization for third party apps and libraries in Python.

Magic Settings Wizard is designed to quickly and easily restore or backup your favorite applications settings.
Magic Settings Wizard can backup/restore through an FTP location used as a storage medium.
Main features:
- backup or restore applications settings : select which ones from a list.
- personal home dir is automatically detected by default, but another directory can be specified.
- communicates with a FTP server specified by the user.
- FTP settings may be saved in a config file.
- a FTP directory may be created from the interface if needed.
- add your own applications settings definitions if yours dont exist in the database (edit settings_definitions.py).

imap2rss.php is a simple PHP application that generates an RSS 2.0 feed from the messages within an IMAP folder.
imap2rss.php requires PHP version 4 to run. To install you have only to rename the downloaded text file to imap2rss.php and copying it to the directory in your web server where you wish to make the service available.
Configuration is simply a matter of editing the script and setting the variables defined near the beginning of the script. The possibility exists for one script to use several configurations, and this is covered in the following section.
Main features:
- The RSS feed contains the full message text.
- Includes a simple viewer for individual items in HTML, to ensure working permalinks.
- Understands multipart MIME messages, and displays a list of attachments as links as well as providing a way of downloading these attachments.
- Does some minor processing to plain-text messages to make them readable in HTML-aware newsreaders, as well as automatic URL link generation.
Enhancements:
- Fixed bug that caused invalid XML to be generated when using HTML entities in body descriptions.

imapsync is a tool for facilitating incremental recursive IMAP transfers from one mailbox to another.

imapsync is useful for mailbox migration, and reduces the amount of data transferred by only copying messages that are not present on both servers.

Read, unread, and deleted flags are preserved, and the process can be stopped and resumed. The original messages can optionally be deleted after a successful transfer.

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

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.

Fantastik-NG is based on Fantastik SuperKaramba theme (http://www.kde-look.org/content/show.php?content=17775).

Fantastik-NG has new more polished Aero-G background (with the same width and smoothnes as Liquid Weather ++).

It displays CPU and system temperature, there is new Python script for displaying number of e-mails (it supports imap, imap-ssl, pop3, pop3-ssl) and better Python script for displaying IP address.

The Cyrus IMAP server is generally intended to be run on sealed systems, where normal users are not permitted to log in.

Electronic mail is a major infrastructure service of almost all organizations. At Carnegie Mellon the use of electronic mail has overshadowed the use of all other distributed services since the early 1990s. It is a core part of the business process of most departments. The universal availability of the Andrew Mail and Bulletin Board System (AMS) has helped a great deal to create this situation. Departments without AMS have run their own mail systems and see heavy use, as well. With the end of the lifetime of the AMS in sight, Project Cyrus began to build a new campus mail system.

The Cyrus Electronic Mail Project is continuing to build a highly scalable enterprise mail system designed for use in a small to large enterprise environments using standards based technologies. The Cyrus technologies will scale from independent use in small departments to a system centrally managed in a large enterprise.

Visitors to this site may want to also view The Cyrus Wiki, which is likely to be updated more frequently.

This document gives an overview of the Cyrus IMAP server. The Cyrus IMAP (Internet Message Access Protocol) server provides access to personal mail and system-wide bulletin boards through the IMAP protocol. The Cyrus IMAP server is a scalable enterprise mail system designed for use from small to large enterprise environments using standards-based technologies.

A full Cyrus IMAP implementation allows a seamless mail and bulletin board environment to be set up across multiple servers. It differs from other IMAP server implementations in that it is run on "sealed" servers, where users are not normally permitted to log in. The mailbox database is stored in parts of the filesystem that are private to the Cyrus IMAP system. All user access to mail is through software that is using the IMAP, POP3, or KPOP protocols.

The private mailbox database design gives the server large advantages in efficiency, scalability, and administratability. Multiple concurrent read/write connections to the same mailbox are permitted. The server supports access control lists on mailboxes and storage quotas on mailbox hierarchies.