search for: jpeacock

...est regards CHEIKH SARR"; #################################################### Amadou TOURE Sonatel Multimedia, 136 Sacre Coeur, Pyrotechnie, BP 21100 Dakar Tel +221-8699810. Fax +221-8641094 http://www.sentoo.sn DAKAR - SENEGAL ----- Original Message ----- From: "John Peacock" <jpeacock at rowman.com> To: "Amadou Toure" <atoure at sentoo.sn> Cc: <dovecot at dovecot.org> Sent: Monday, September 11, 2006 2:44 PM Subject: Re: [Dovecot] sieve unresolved problem > Amadou Toure wrote: >> What about the directory sieve script storage ? >> We use...

After v1.0 is released, I can finally get back to sane version numbers. But any comments on which one is better: a) Postfix-style: "1.1.UNSTABLE.YYYYMMDD" -> 1.1.0 (stable) b) Odd-even numbering: 1.1.x (unstable) -> 1.2.0 (stable) With a) style the releases could be done by simply copying a nightly snapshot to releases/ directory and announcing the changes since the last

I'm in the final stages of testing my e-mail server to come and I seem to have hit a roadblock. One option of current vpopmail is to store all aliases in a valias table, that looks like this: +-------------+----------+------+-----+---------+-------+ | Field | Type | Null | Key | Default | Extra | +-------------+----------+------+-----+---------+-------+ | alias | char(32) |

I'm vainly trying to get a new server ready to become the default mail server. We have a SAN, so I don't need to move the mailboxes (I can mount the same partition from both machines), but the question is what version of dovecot to load. I'm assuming that I cannot run both 0.99.14 and 1.00.x on the same maildirs (the indexes differ?). However, is it safe for me to mount the

The sample dovecot-example.conf contains these lines: > # PEM encoded X.509 SSL/TLS certificate and private key. They're opened before > # dropping root privileges, so keep the key file unreadable by anyone but > # root. Included doc/mkcert.sh can be used to easily generate self-signed > # certificate, just make sure to update the domains in dovecot-openssl.cnf > #ssl_cert_file

It doesn't seem like this code path has been tested recently, since it fails to compile without the following patch (works fine with it): --- src/auth/userdb-vpopmail.c 7 Aug 2005 11:41:19 -0000 1.17 +++ src/auth/userdb-vpopmail.c 11 Sep 2005 11:57:42 -0000 @@ -84,7 +84,7 @@ } } - reply = auth_stream_reply_init(); + reply =

I'm setting up a new box with Dovecot 1.0 beta1 and vpopmail. Normal operations works like a charm, i.e. vpopmail virtual can log in sucessfully using TLS. However, when trying to test dovecot-lda out of CVS, it is not locating the user: > *** Starting dovecot-imapd service... > dovecot: Info: Dovecot v1.0.beta1 starting up > dovecot: Info: auth(default): master in: USER 1

Just a heads up for all interested in using the Dovecot LDA with SIEVE scripting: I've started work on a proof-of-concept managesieve daemon, since the only one available right now is dependent on Cyrus. It appears that the only choice available for sites not using timsieved is the Ingo component of Horde, which is way too fat to install by itself (plus it uses FTP for a transport,

I have just moved our corporate e-mail over to qmail/dovecot and am very happy with the performance. However, I have had two reports of messages going missing which may or may not be directly related to Dovecot. I was able to observe this in action this morning: 1) I got the user out of their e-mail client (Mozilla 1.7.2) and forced an email to be delivered. It showed up in Maildir/new. 2)