tags: IMAP

Action executed in 0.000

Each Tag

IMAP

Common tags - number of posts

email (2), Cyrus (2), protocol (1), SMTP (1), open source (1), TLS (1), server (1), configure (1), authentication (1), Sieve (1), standard (1), client (1), JMAP (1), KMail (1),

2 way join

Cyrus, IMAP, IMAP, email

●●●●●○○○

JSON Meta Application Protocol Specification (JMAP)

JMAP is intended to be a new standard for email clients to connect to mail stores. It therefore intends to primarily replace IMAP + SMTP submission. It is also designed to be more generic such that it can be extended with contacts, calendars in the future (replacing CardDAV/CalDAV). It does not replace MTA-to-MTA SMTP transmission.

url: http://jmap.io/

type: project, format: page

●●●●●○○○

Bug 2642 – TLS client authentication: allow optional client certificate

I have reworked the way how in imap/tls.c:tls_init_serverengine the CA certificates are handled: * I added the new (optional) parameter "tls_server_ca_file" containing the CA certificates that build the certificate chain for the server certificate. (if it is not set, the certificates are collected from tls_ca_file and tls_ca_path)

url: https://bugzilla.andrew.cmu.edu/show_bug.cgi?id=2642

type: none, format: none

●●●●●○○○

Configuring Cyrus IMAP

This document guides you through the installation of the Postfix mail transportation agent (MTA), the Cyrus IMAP server. The goal is a fully functional high-performance mailsystem with user-administration with Web-cyradm, a webinterface. Data like virtualusers, aliases etc. are stored in a mysql database.

url: http://www.delouw.ch/linux/Postfix-Cyrus-Web-cyradm-HOWTO/html/t1.html

type: project, format: page

How to Configure Sieve

This "article" is about how to configure Sieve. Sieve is a simple filter for email that's used on the client or server side. It's useful to configure it on the server side if you connect from multiple mail user agents (MUAs).

Cyrus IMAP comes with Sieve enabled by default, though distributors may disable it. Start by uncommenting the line in cyrus.conf:

sieve cmd="timsieved" listen="192.168.0.1:sieve" prefork=0 maxchild=100 Restart cyrus. Test that it works by running this on another machine telnet 192.168.0.1 sieve You should get something like this: "IMPLEMENTATION" "Cyrus timsieved v2.1.18-IPv6-Debian-2.1.18-1+sarge2"

Two tutorials to help you write sieve scripts are Wikipedia's page and FastMailWiki's BasicSieve.

Kmail can upload your script to your IMAP server. First let Kmail know that your server supports it by modifying your IMAP account and setting "Server supports Sieve". You may need to open port 2000 of your firewall.

Then upload your script through the Settings / Manage Sieve Scripts dialog box. You should get a successful response. Finally make sure that your script is activated; make sure the circle "radio button" is filled. If Kmail bitches at you about activating scripts, you can use sieveshell to disactivate all scripts and active one of them.

If i missed any details, please let me know.