[Dovecot] v1.2.0 released
http://dovecot.org/releases/1.2/dovecot-1.2.0.tar.gz http://dovecot.org/releases/1.2/dovecot-1.2.0.tar.gz.sig
As promised. No changes since v1.2.rc8 (except packaged in OS X, since
CentOS 5 autotools didn't add support for configure --docdir).
Below are the largest changes since v1.1:
* When creating files or directories to mailboxes, Dovecot now uses
the mailbox directory's permissions and GID for them. Previous
versions simply used 0600 mode always. For backwards compatibility
dovecot-shared file's permissions still override these with Maildir.
* SQL dictionary (quota) configuration file is different than in v1.1.
See doc/dovecot-dict-sql-example.conf for the new format.
* deliver -m: Mailbox name is now assumed to be in UTF-8 format,
not modified-UTF7. Stephan Bosch's new Sieve implementation also
assumes UTF-8 format in fileinto parameters.
+ Full support for shared mailboxes and IMAP ACL extension.
The code is mainly from Sascha Wilde and Bernhard Herzog.
+ IMAP: Added support for extensions: CONDSTORE, QRESYNC, ESEARCH,
ESORT, SEARCHRES, WITHIN, ID and CONTEXT=SEARCH.
+ SEARCH supports INTHREAD search key, but the rest of the INTHREAD
draft isn't implemented yet so it's not advertised in capability.
+ THREAD REFS algorithm where threads are sorted by their latest
message instead of the thread root message. There is also no base
subject merging.
+ IMAP: Implemented imap-response-codes draft.
+ Thread indexes for optimizing IMAP THREAD command and INTHREAD
search key.
+ Added userdb checkpassword (by Sascha Wilde)
+ Virtual mailboxes: http://wiki.dovecot.org/Plugins/Virtual
+ Autocreate plugin: http://wiki.dovecot.org/Plugins/Autocreate
+ Listescape plugin: http://wiki.dovecot.org/Plugins/ListescapeOn Jul 1, 2009, at 10:02 PM, Timo Sirainen wrote:
http://dovecot.org/releases/1.2/dovecot-1.2.0.tar.gz http://dovecot.org/releases/1.2/dovecot-1.2.0.tar.gz.sig
I'm going to sleep now. Try not to find horrible release mistake bugs
in the next few hours ;)
On 7/1/2009 4:13 PM, Timo Sirainen wrote:
On Jul 1, 2009, at 10:02 PM, Timo Sirainen wrote:
http://dovecot.org/releases/1.2/dovecot-1.2.0.tar.gz http://dovecot.org/releases/1.2/dovecot-1.2.0.tar.gz.sig
I'm going to sleep now. Try not to find horrible release mistake bugs in the next few hours ;)
Congrats Timo! This is really great stuff... can't wait for it to be available in portage...
Now, I hope you're planning on taking the whole weekend off, it would be well deserved...
:)
--
Best regards,
Charles
On Wed, Jul 1, 2009 at 4:58 PM, Charles MarcusCMarcus@media-brokers.com wrote:
On 7/1/2009 4:13 PM, Timo Sirainen wrote:
On Jul 1, 2009, at 10:02 PM, Timo Sirainen wrote:
http://dovecot.org/releases/1.2/dovecot-1.2.0.tar.gz http://dovecot.org/releases/1.2/dovecot-1.2.0.tar.gz.sig
I'm going to sleep now. Try not to find horrible release mistake bugs in the next few hours ;)
Congrats Timo! This is really great stuff... can't wait for it to be available in portage...
Now, I hope you're planning on taking the whole weekend off, it would be well deserved...
:)
--
Best regards,
Charles
sorry if i'm asking stupid question
i had 1.1.16 and i just ugpraded to 1.2.0 and dovecot won't even start now..
Jul 2 00:36:09 mx1 dovecot: Dovecot v1.2.0 starting up Jul 2 00:36:09 mx1 dovecot: auth(default): Fatal: passdb vpopmail: Unknown setting: vpopmail Jul 2 00:36:09 mx1 dovecot: dovecot: Fatal: Auth process died too early - shutting down
i compiled it through "./configure --enable-maintainer-mode --with-vpopmail" if you need logs i can attach them
I'm running FreeBSD-7.2-RELEASE-p1
On Thu, Jul 2, 2009 at 12:45 AM, Timo Sirainentss@iki.fi wrote:
On Jul 2, 2009, at 6:40 AM, alexus wrote:
Jul 2 00:36:09 mx1 dovecot: Dovecot v1.2.0 starting up Jul 2 00:36:09 mx1 dovecot: auth(default): Fatal: passdb vpopmail: Unknown setting: vpopmail
dovecot -n output?
-bash-3.2# ./src/master/dovecot -n # 1.2.0: /usr/local/etc/dovecot.conf # OS: FreeBSD 7.2-RELEASE-p1 amd64 protocols: imap imaps pop3 pop3s ssl_cert_file: /usr/local/etc/ssl/certs/dovecot.pem ssl_key_file: /usr/local/etc/ssl/private/dovecot.pem disable_plaintext_auth: no login_dir: /usr/local/var/run/dovecot/login login_executable(default): /usr/local/libexec/dovecot/imap-login login_executable(imap): /usr/local/libexec/dovecot/imap-login login_executable(pop3): /usr/local/libexec/dovecot/pop3-login first_valid_uid: 89 last_valid_uid: 89 mail_uid: 89 mail_gid: 89 mail_location: maildir:~vpopmail/domains/%d/%n/Maildir/ mail_debug: yes mail_executable(default): /usr/local/libexec/dovecot/imap mail_executable(imap): /usr/local/libexec/dovecot/imap mail_executable(pop3): /usr/local/libexec/dovecot/pop3 mail_plugin_dir(default): /usr/local/lib/dovecot/imap mail_plugin_dir(imap): /usr/local/lib/dovecot/imap mail_plugin_dir(pop3): /usr/local/lib/dovecot/pop3 auth default: mechanisms: plain login digest-md5 cram-md5 cache_size: 1024 debug: yes debug_passwords: yes passdb: driver: vpopmail args: cache_key=%u vpopmail -bash-3.2#
On Thu, Jul 2, 2009 at 11:45 AM, Timo Sirainentss@iki.fi wrote:
On Jul 2, 2009, at 2:27 PM, alexus wrote:
passdb: driver: vpopmail args: cache_key=%u vpopmail
Remove "vpopmail" from args. v1.1 ignored it, v1.2 gives error messages about unknown settings
okay, after doing that I'm getting new errors
Jul 2 15:16:07 mx1 dovecot: IMAP(XXXXX@alexus.org): Effective uid=89, gid=89, home=(none) Jul 2 15:16:07 mx1 dovecot: IMAP(XXXXX@alexus.org): maildir: data=~vpopmail/domains/alexus.org/XXXXX/Maildir/ Jul 2 15:16:07 mx1 dovecot: IMAP(XXXXX@alexus.org): maildir++: root=~vpopmail/domains/alexus.org/XXXXX/Maildir, index=, control=, inbox=~vpopmail/domains/alexus.org/postmaster/Maildir Jul 2 15:16:07 mx1 dovecot: IMAP(XXXXX@alexus.org): Namespace : Permission lookup failed from ~vpopmail/domains/alexus.org/XXXXX/Maildir Jul 2 15:16:07 mx1 dovecot: IMAP(XXXXX@alexus.org): Namespace : Using permissions from ~vpopmail/domains/alexus.org/XXXXX/Maildir: mode=0700 gid=-1
as soon as I roll it back to 1.1.16 and my old dovecot.conf, everything works no problem
On Jul 2, 2009, at 9:20 PM, alexus wrote:
okay, after doing that I'm getting new errors
Jul 2 15:16:07 mx1 dovecot: IMAP(XXXXX@alexus.org): Effective uid=89, gid=89, home=(none) Jul 2 15:16:07 mx1 dovecot: IMAP(XXXXX@alexus.org): maildir: data=~vpopmail/domains/alexus.org/XXXXX/Maildir/ Jul 2 15:16:07 mx1 dovecot: IMAP(XXXXX@alexus.org): maildir++: root=~vpopmail/domains/alexus.org/XXXXX/Maildir, index=, control=, inbox=~vpopmail/domains/alexus.org/postmaster/Maildir Jul 2 15:16:07 mx1 dovecot: IMAP(XXXXX@alexus.org): Namespace : Permission lookup failed from ~vpopmail/domains/alexus.org/XXXXX/Maildir
That's an informational more kind of like a warning. It's not written
unless you have mail_debug=yes. So it's not an error.
Jul 2 15:16:07 mx1 dovecot: IMAP(XXXXX@alexus.org): Namespace : Using permissions from ~vpopmail/domains/alexus.org/XXXXX/Maildir: mode=0700 gid=-1
This isn't an error either. You should have had a separate actual
error message, which could have given more information.
Anyway it looks like the problem is that ~vpopmail/ doesn't get
expanded to something like /home/vpopmail/. Hmm. I've changed that
part of the code, so I guess there could be a bug. Or perhaps I
decided to drop that feature.. Anyway, I'll look into it next week
once I get back to US.
On Thu, Jul 2, 2009 at 4:48 PM, Timo Sirainentss@iki.fi wrote:
On Jul 2, 2009, at 9:20 PM, alexus wrote:
okay, after doing that I'm getting new errors
Jul 2 15:16:07 mx1 dovecot: IMAP(XXXXX@alexus.org): Effective uid=89, gid=89, home=(none) Jul 2 15:16:07 mx1 dovecot: IMAP(XXXXX@alexus.org): maildir: data=~vpopmail/domains/alexus.org/XXXXX/Maildir/ Jul 2 15:16:07 mx1 dovecot: IMAP(XXXXX@alexus.org): maildir++: root=~vpopmail/domains/alexus.org/XXXXX/Maildir, index=, control=, inbox=~vpopmail/domains/alexus.org/postmaster/Maildir Jul 2 15:16:07 mx1 dovecot: IMAP(XXXXX@alexus.org): Namespace : Permission lookup failed from ~vpopmail/domains/alexus.org/XXXXX/Maildir
That's an informational more kind of like a warning. It's not written unless you have mail_debug=yes. So it's not an error.
Jul 2 15:16:07 mx1 dovecot: IMAP(XXXXX@alexus.org): Namespace : Using permissions from ~vpopmail/domains/alexus.org/XXXXX/Maildir: mode=0700 gid=-1
This isn't an error either. You should have had a separate actual error message, which could have given more information.
Anyway it looks like the problem is that ~vpopmail/ doesn't get expanded to something like /home/vpopmail/. Hmm. I've changed that part of the code, so I guess there could be a bug. Or perhaps I decided to drop that feature.. Anyway, I'll look into it next week once I get back to US.
yeah, that was it... i changed ~vpopmail to /home/vpopmail and that seems to be working now
thanks
On Thu, Jul 2, 2009 at 6:38 PM, alexusalexus@gmail.com wrote:
On Thu, Jul 2, 2009 at 4:48 PM, Timo Sirainentss@iki.fi wrote:
On Jul 2, 2009, at 9:20 PM, alexus wrote:
okay, after doing that I'm getting new errors
Jul 2 15:16:07 mx1 dovecot: IMAP(XXXXX@alexus.org): Effective uid=89, gid=89, home=(none) Jul 2 15:16:07 mx1 dovecot: IMAP(XXXXX@alexus.org): maildir: data=~vpopmail/domains/alexus.org/XXXXX/Maildir/ Jul 2 15:16:07 mx1 dovecot: IMAP(XXXXX@alexus.org): maildir++: root=~vpopmail/domains/alexus.org/XXXXX/Maildir, index=, control=, inbox=~vpopmail/domains/alexus.org/postmaster/Maildir Jul 2 15:16:07 mx1 dovecot: IMAP(XXXXX@alexus.org): Namespace : Permission lookup failed from ~vpopmail/domains/alexus.org/XXXXX/Maildir
That's an informational more kind of like a warning. It's not written unless you have mail_debug=yes. So it's not an error.
Jul 2 15:16:07 mx1 dovecot: IMAP(XXXXX@alexus.org): Namespace : Using permissions from ~vpopmail/domains/alexus.org/XXXXX/Maildir: mode=0700 gid=-1
This isn't an error either. You should have had a separate actual error message, which could have given more information.
Anyway it looks like the problem is that ~vpopmail/ doesn't get expanded to something like /home/vpopmail/. Hmm. I've changed that part of the code, so I guess there could be a bug. Or perhaps I decided to drop that feature.. Anyway, I'll look into it next week once I get back to US.
yeah, that was it... i changed ~vpopmail to /home/vpopmail and that seems to be working now
thanks
this is a bit off topic, but i also get following msg in my syslog
Jul 2 18:48:55 mx1 dovecot: auth(default): digest-md5(?,24.185.130.236): Invalid realm: alexus.org
when I check my email, any ideas what could be wrong?
On Thu, 2009-07-02 at 18:50 -0400, alexus wrote:
yeah, that was it... i changed ~vpopmail to /home/vpopmail and that seems to be working now
Fixed now: http://hg.dovecot.org/dovecot-1.2/rev/072a44932976
Jul 2 18:48:55 mx1 dovecot: auth(default): digest-md5(?,24.185.130.236): Invalid realm: alexus.org
when I check my email, any ideas what could be wrong?
It means your client tries to use alexus.org as the realm, but it's not listed in auth_realms setting.
http://dovecot.org/releases/1.2/dovecot-1.2.0.tar.gz http://dovecot.org/releases/1.2/dovecot-1.2.0.tar.gz.sig
As promised. No changes since v1.2.rc8 (except packaged in OS X, since CentOS 5 autotools didn't add support for configure --docdir).
Congratulation!
Is gssapi auth problem fixed in this version or not yet?
Regards, Michal Hlavinka
On Thursday 02 July 2009 07:31:00 Timo Sirainen wrote:
On Jul 2, 2009, at 7:25 AM, Michal Hlavinka wrote:
Is gssapi auth problem fixed in this version or not yet?
If I fix it for you, I break it for someone else. I'd need to find out what exacly is that patch doing wrong and how it should be fixed the correct way.
can I help you somehow with it? (unfortunately I don't how exactly gssapi works)
Timo Sirainen wrote:
http://dovecot.org/releases/1.2/dovecot-1.2.0.tar.gz http://dovecot.org/releases/1.2/dovecot-1.2.0.tar.gz.sig
It is so great news! Can`t wait for FreeBSD port upgrade.
-- Best regards, Proskurin Kirill
Sorry to ask again, but what's the status of the ManageSieve patch for 1.2? The rc5 version doesn't work and I would like to get 1.2 into pkgsrc.
managesieve works fine for me on 1.2.0
However -> it would be however a nice idea to include the patch of ManageSieve directly into the branch 1.2 of dovecot. -> I am still wondering how managesieve works between the "sieve script per virtual user" and the main script in the storage directory.
Edgar Fuß wrote:
Sorry to ask again, but what's the status of the ManageSieve patch for 1.2? The rc5 version doesn't work and I would like to get 1.2 into pkgsrc.
managesieve works fine for me on 1.2.0 How do you make that work?
$ tail +41 dovecot-1.2.0/src/imap-login/client.c | head -3 #if CLIENT_LOGIN_IDLE_TIMEOUT_MSECS < AUTH_REQUEST_TIMEOUT*1000 # error client idle timeout must be larger than authentication timeout #endif
$ tail +47 dovecot-1.2-managesieve-0.11.5/src/managesieve-login/client.c | head -3 #if CLIENT_LOGIN_IDLE_TIMEOUT_MSECS >= AUTH_REQUEST_TIMEOUT*1000 # error client idle timeout must be smaller than authentication timeout #endif
Am I missing something?
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Thu, 2 Jul 2009, Edgar Fuß wrote:
Date: Thu, 2 Jul 2009 12:53:00 +0200 From: Edgar Fuß ef@math.uni-bonn.de To: dovecot@dovecot.org Subject: Re: [Dovecot] ManageSieve for 1.2.0?
managesieve works fine for me on 1.2.0 How do you make that work?
$ tail +41 dovecot-1.2.0/src/imap-login/client.c | head -3 #if CLIENT_LOGIN_IDLE_TIMEOUT_MSECS < AUTH_REQUEST_TIMEOUT*1000 # error client idle timeout must be larger than authentication timeout #endif
$ tail +47 dovecot-1.2-managesieve-0.11.5/src/managesieve-login/client.c | head -3 #if CLIENT_LOGIN_IDLE_TIMEOUT_MSECS >= AUTH_REQUEST_TIMEOUT*1000 # error client idle timeout must be smaller than authentication timeout #endif
I'm using the Mercurial repository, see http://wiki.dovecot.org/ManageSieve#Mercurial
Steffen Kaiser -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux)
iQEVAwUBSkynMnWSIuGy1ktrAQI98gf/bM1/dBoNPOzQb1Z5ec2Yf0YWEQr4s/FT cO1cO3d0IPtHQf6sfmTHKoa7MqrMRKigX0hv4ykgA2dcbJ5aRLt00+PRpFd/lT1V EGClgrBJZYtFDnN+GnEVd/y/yGIluiW6h/t75L4s9W3VtvqZgkL8rI5BtVvggw3b 6sWo2N+ODmC+qit7GFhfTfRl69UbREXScM1Zj5cAm/9Y1yn1yb8fqEL5GdMpnL/R UUc9qTwTR/SWoqKy8f09a8Cdli774lof6FmtnInfbKzS5+6JUrbC+qKZ1Nydl0UU 41SY0vdARbiUHIEYAJE29rCO8ZoWK0rMxo6YMFL9e8tUX1drmmjPbw== =FIo7 -----END PGP SIGNATURE-----
yes, Mercurial repository has a working status.
Anybody to help on teh following ? : -> how managesieve works between the "sieve script per virtual user" and the main script in the storage directory.
thanks
jm
Steffen Kaiser wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Thu, 2 Jul 2009, Edgar Fuß wrote:
Date: Thu, 2 Jul 2009 12:53:00 +0200 From: Edgar Fuß ef@math.uni-bonn.de To: dovecot@dovecot.org Subject: Re: [Dovecot] ManageSieve for 1.2.0?
managesieve works fine for me on 1.2.0 How do you make that work?
$ tail +41 dovecot-1.2.0/src/imap-login/client.c | head -3 #if CLIENT_LOGIN_IDLE_TIMEOUT_MSECS < AUTH_REQUEST_TIMEOUT*1000 # error client idle timeout must be larger than authentication timeout #endif
$ tail +47 dovecot-1.2-managesieve-0.11.5/src/managesieve-login/client.c | head -3 #if CLIENT_LOGIN_IDLE_TIMEOUT_MSECS >= AUTH_REQUEST_TIMEOUT*1000 # error client idle timeout must be smaller than authentication timeout #endif
I'm using the Mercurial repository, see http://wiki.dovecot.org/ManageSieve#Mercurial
- -- Steffen Kaiser -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux)
iQEVAwUBSkynMnWSIuGy1ktrAQI98gf/bM1/dBoNPOzQb1Z5ec2Yf0YWEQr4s/FT cO1cO3d0IPtHQf6sfmTHKoa7MqrMRKigX0hv4ykgA2dcbJ5aRLt00+PRpFd/lT1V EGClgrBJZYtFDnN+GnEVd/y/yGIluiW6h/t75L4s9W3VtvqZgkL8rI5BtVvggw3b 6sWo2N+ODmC+qit7GFhfTfRl69UbREXScM1Zj5cAm/9Y1yn1yb8fqEL5GdMpnL/R UUc9qTwTR/SWoqKy8f09a8Cdli774lof6FmtnInfbKzS5+6JUrbC+qKZ1Nydl0UU 41SY0vdARbiUHIEYAJE29rCO8ZoWK0rMxo6YMFL9e8tUX1drmmjPbw== =FIo7 -----END PGP SIGNATURE-----
Joan wrote:
yes, Mercurial repository has a working status.
Anybody to help on teh following ? : -> how managesieve works between the "sieve script per virtual user" and the main script in the storage directory.
ManageSieve shouldn't be used to modify global scripts, only personal ones.
With older versions of Sieve, once a user creates a personal script (and marks it active), the global script will no longer be called. You can work around this by 'include'ing the global script in each personal script. Here is my active script, which runs the global script followed by a personal one:
require ["include"]; include :global "spamassassin-header-filter.sieve"; include :personal "mailing-lists.sieve";
In newer versions of Sieve (newer than v0.1.3 or v0.1.4, I think), you can use sieve_before or sieve_after to accomplish the same thing. Check the wiki:
http://wiki.dovecot.org/LDA/Sieve/Dovecot
If I were using sieve_before in my configuration, there would be no need to include the global script manually; it would always be executed before my active personal script.
thanks ! :-)
Michael Orlitzky wrote:
Joan wrote:
yes, Mercurial repository has a working status.
Anybody to help on teh following ? : -> how managesieve works between the "sieve script per virtual user" and the main script in the storage directory.
ManageSieve shouldn't be used to modify global scripts, only personal ones.
With older versions of Sieve, once a user creates a personal script (and marks it active), the global script will no longer be called. You can work around this by 'include'ing the global script in each personal script. Here is my active script, which runs the global script followed by a personal one:
require ["include"]; include :global "spamassassin-header-filter.sieve"; include :personal "mailing-lists.sieve";
In newer versions of Sieve (newer than v0.1.3 or v0.1.4, I think), you can use sieve_before or sieve_after to accomplish the same thing. Check the wiki:
http://wiki.dovecot.org/LDA/Sieve/Dovecot
If I were using sieve_before in my configuration, there would be no need to include the global script manually; it would always be executed before my active personal script.
Ok, but in the event of *virtual* users , how to setup the setting sieve_dir = ~/ ?
Michael Orlitzky wrote:
Joan wrote:
yes, Mercurial repository has a working status.
Anybody to help on teh following ? : -> how managesieve works between the "sieve script per virtual user" and the main script in the storage directory.
ManageSieve shouldn't be used to modify global scripts, only personal ones.
With older versions of Sieve, once a user creates a personal script (and marks it active), the global script will no longer be called. You can work around this by 'include'ing the global script in each personal script. Here is my active script, which runs the global script followed by a personal one:
require ["include"]; include :global "spamassassin-header-filter.sieve"; include :personal "mailing-lists.sieve";
In newer versions of Sieve (newer than v0.1.3 or v0.1.4, I think), you can use sieve_before or sieve_after to accomplish the same thing. Check the wiki:
http://wiki.dovecot.org/LDA/Sieve/Dovecot
If I were using sieve_before in my configuration, there would be no need to include the global script manually; it would always be executed before my active personal script.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Sat, 4 Jul 2009, Joan Moreau wrote:
Ok, but in the event of *virtual* users , how to setup the setting sieve_dir = ~/
You return a personel home directory from/with userdb.
Bye,
Steffen Kaiser -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux)
iQEVAwUBSlH46XWSIuGy1ktrAQL7/wf6A4DiQkWZA/TIEBtoJFdtotgG6Yh8FTup UMp7BPm/SS9fIRF32zb/Wvd/+o1kyseosAnR1UUZxp58ttO1YvwaBv20JuosV+mI 6VaaDu312XywjT/S9fgkVt+eUumdRZMoNfw9qs7YfK2sQ8Wcf3+HpZ2NV97anPFQ 6VuB9e6ZQCwYCHoMXVBcD6YNo7oLVogi77Eqi793tScNTG5guFfgtmHF2zRYJTD5 KoxoZoLyCvEWGPS600dV2LgcA4osoPTsCqhNIRECLFxYW4O3VFNohqOZSxPMYngr UJXIKX9q3iUNmq0cKYsB9LHMVQL2IsYTDNp+eNFc/fk6TYucxyNdBA== =rgW4 -----END PGP SIGNATURE-----
I'm using the Mercurial repository, see http://wiki.dovecot.org/ManageSieve#Mercurial I guess this is not an option for pkgsrc.
On 7/2/2009, Joan (jom@grosjo.net) wrote:
managesieve works fine for me on 1.2.0
However -> it would be however a nice idea to include the patch of ManageSieve directly into the branch 1.2 of dovecot.
This is getting to be an FAQ (asked and answered in the archives)...
The patch will no longer be needed for 2.0, but Sieve/Managesieve support will still be a separate package...
--
Best regards,
Charles
my point was: why waiting 2.0 ? why not doing it in 1.2 ?
Charles Marcus wrote:
On 7/2/2009, Joan (jom@grosjo.net) wrote:
managesieve works fine for me on 1.2.0
However -> it would be however a nice idea to include the patch of ManageSieve directly into the branch 1.2 of dovecot.
This is getting to be an FAQ (asked and answered in the archives)...
The patch will no longer be needed for 2.0, but Sieve/Managesieve support will still be a separate package...
On 7/4/2009 9:27 AM, Joan Moreau wrote:
-> it would be however a nice idea to include the patch of ManageSieve directly into the branch 1.2 of dovecot.
This is getting to be an FAQ (asked and answered in the archives)...
The patch will no longer be needed for 2.0, but Sieve/Managesieve support will still be a separate package...
my point was: why waiting 2.0 ? why not doing it in 1.2 ?
Because it is a major rewrite...
--
Best regards,
Charles
http://dovecot.org/releases/1.2/dovecot-1.2.0.tar.gz http://dovecot.org/releases/1.2/dovecot-1.2.0.tar.gz.sig
As promised. No changes since v1.2.rc8 (except packaged in OS X, since CentOS 5 autotools didn't add support for configure --docdir).
download page suggest using new dovecot sieve plugin. It's version 0.1.6 so I wonder how much stable and feature complete it is comparing to the old sieve plugin? Which one is better and why?
Regards, Michal Hlavinka
participants (10)
-
alexus
-
Charles Marcus
-
Edgar Fuß
-
Joan
-
Joan Moreau
-
Michael Orlitzky
-
Michal Hlavinka
-
Proskurin Kirill
-
Steffen Kaiser
-
Timo Sirainen