similar to: dovecot auth feature request

I am currently running v1.1.20 and was wondering if there is any compelling reason to upgrade to v1.2 or v2.0? For example is there any security updates in v1.2 or v2.0 that aren't included in v1.1.20? The other major thing I would be interested in knowing is there any speed enhancements in the newer versions? I am using basic PAM Auth and Maildir mailboxes on a Linux box. Let me know

Now supported by v2.0. Also as a patch to v1.2: http://dovecot.org/patches/1.2/zlib-compress.diff I'm not really sure if I should commit it to v1.2 code tree. The code contains ugly copy&pasted io_stream_copy() and v1.2 is supposed to be feature complete.. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature

We have both dovecot and a webmail application that are both modifying our users maildirs, so dovecot indexes can be out of sync when the webmail has been messing with the maildirs. We also have a webservice that report how many unread messages a user has in his inbox, which is simply counting files in the maildirs (plus caching the result, and present old values if the directory timestamps hasn?t

On Sat, March 17, 2007 10:51 pm, Timo Sirainen <tss at iki.fi> said: > Oh, and as for when the rewrite is in CVS, I'm not really sure. I'm > still wondering if I should put it there soon and make the release after > v1.0 be v2.0, or if I should first stabilize the current new CVS HEAD > features (which shouldn't take too long), do a v1.2 release and only > then

http://dovecot.org/releases/1.2/alpha/dovecot-1.2.alpha2.tar.gz http://dovecot.org/releases/1.2/alpha/dovecot-1.2.alpha2.tar.gz.sig Mainly the same fixes as in v1.1.3 -> v1.1.4 plus some more v1.2-specific fixes. Not many people have been testing v1.2 releases. Wonder if there's something I could do to improve that. I guess v1.2 is kind of missing those killer features that would get a

hi, I've used dovecot 1.1.16 but after upgrade to dovecot 1.2.4 per-user ldap quotas stoped working. My configuration: # 1.2.4: /etc/dovecot.conf # OS: Linux 2.6.18-128.7.1.el5xen x86_64 CentOS release 5.3 (Final) ext3 protocols: imap imaps pop3 pop3s managesieve listen(default): *, [::] listen(imap): *, [::] listen(pop3): *, [::] listen(managesieve): *:20000 login_dir:

Hi all, I'm building a mail system where two machines are functioning both as POP3/IMAP-proxy (using dovecot 1.2.12) and SMTP-server with authentication for outgoing mail. The SMTP-server is postfix with dovecot SASL as authentication backend. User credentials for SMTP auth as well as the mapping from account to final server for the proxy is stored in a MySQL-database which dovecot queries.

Hi Timo, I've just tried to convert my v1.2 configuration to a v2.0 configuration. Below a few obsolete warnings, among others "mail_executable has been replaced by service { executable }", was an interesting error: "doveconf: Error: duplicate listener: 198:" The broken parts of the converted configuration: # 2.0.beta4 (84ffb38839b9): /etc/dovecot/dovecot.conf # OS: Linux

v1.1.0 is finally getting closer, so it's time to start planning what happens after it. Below is a list of some of the larger features I'm planning on implementing. I'm not yet sure in which order, so I think it's time to ask again what features companies would be willing to pay for? Sponsoring Dovecot development gets you: - listed in Credits in www.dovecot.org - listed in

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

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

http://dovecot.org/releases/1.2/dovecot-1.2.8.tar.gz http://dovecot.org/releases/1.2/dovecot-1.2.8.tar.gz.sig This is mainly to fix the 0777 base_dir creation issue, which could be considered a security hole, exploitable by local users. An attacker could for example replace Dovecot's auth socket and log in as other users. Gaining root privileges isn't possible though. This affects only

http://dovecot.org/releases/1.2/dovecot-1.2.8.tar.gz http://dovecot.org/releases/1.2/dovecot-1.2.8.tar.gz.sig This is mainly to fix the 0777 base_dir creation issue, which could be considered a security hole, exploitable by local users. An attacker could for example replace Dovecot's auth socket and log in as other users. Gaining root privileges isn't possible though. This affects only

Hi, I have error with dovecot 1.2.10 + compress on deliver patch and zlib plugin. logfile sample: [...] mail.err: Feb 16 14:22:25 dovecot: IMAP(hidden at domain.com): zlib_istream.seek() failed: Invalid argument mail.err: Feb 16 14:22:25 dovecot: IMAP(hidden at domain.com): FETCH for mailbox Meursault UID 101 failed to read message input: Invalid argument mail.err: Feb 16 14:22:26 dovecot:

Is there a way? Postfix does this by default, and it makes it much less likely to miss/overlook a setting... If there is no way, any chance to modify it so that it does? Thanks for dovecot! Really looking forward to 1.1 release! -- Best regards, Charles

I forked the wiki to http://wiki1.dovecot.org/ is the old docs for v1.x http://wiki2.dovecot.org/ is the new docs for v2.0 For now wiki.dovecot.org points to wiki1, but once v2.0 is released I'll change it to point to wiki2. I symlinked the user directory, so users should stay synced between the wikis. The main reason for wiki2 is to be able to describe Dovecot v2.0's actual behavior

maybe this is a silly question ;-) But why is it possible to login on a machine with a locked account (passwd -l ) via pubkey-authentication (authorized_keys) ? I use OpenSSH3.01p1on Solaris8 with PAM support so I thought this should not happen. If this is the normal behaviour and built in intentionally what would be the easiest way to lock an account without deleting the users authorized_keys ?

I read in the list archives about work in progress on an lmtp delivery agent.As a previous cyrus user where that was the preferred delivery method from postfix, this sounds interesting. I was wondering whether it will handle recipient delimiters. ie will it be able to map user+foo at example.com to user at example.com? I'm not interested in the delivery into folder stuff, just the plain

Hi, we've defined a public namespace "shared" and use the acl and lazy-expunge plugins among others. The problem is, that a mailbox is deleted by the DELETE-command without the x-flag to be set (# 1.2.9): a myrights shared/aclDeleteTest * MYRIGHTS "shared/aclDeleteTest" lrsed a OK Myrights completed. b delete shared/aclDeleteTest b OK Delete completed. c myrights

Hi, I've some virtual folders which seem a bit odd when they are listed. a LIST "virtual.spam." "*" * LIST (\Noselect \HasNoChildren) "." "virtual.spam." * LIST (\HasNoChildren) "." "virtual.spam.unchecked" * LIST (\Noselect \HasChildren) "." "virtual.spam.disagree" * LIST (\HasNoChildren) "."