- dovecot - dovecot.org

[Dovecot] v1.2.15 released
by Timo Sirainen 05 Oct '10

05 Oct '10

http://dovecot.org/releases/1.2/dovecot-1.2.15.tar.gz http://dovecot.org/releases/1.2/dovecot-1.2.15.tar.gz.sig See the "ACL handling bugs" message for more details about the ACL merging bug. * acl: Fixed the logic of merging multiple ACL entries. Now it works as documented, while previously it could have done slightly different things depending on the order of the entries. * acl: Don't give admin rights to all owner mailboxes. This was originally done to make sure that mailbox owner couldn't accidentally remove their own admin rights. But this is already prevented by SETACL command, so it's not necessary. Also sysadmin may have intentionally removed some admin rights from some mailboxes (especially when using symlinked shared mailboxes). - Maildir: Fixed potential "Duplicate file entry" in dovecot-uidlist file errors. - Maildir: Avoid unnecessary uidlist recreation during mail delivery. - imap: When SELECT fails, it didn't close the previous mailbox. - Dovecot master process could have died if it got SIGCHLD signals very rapidly while it was trying to log. This could have happened for example if a lot of imap/pop3 sessions disconnected at the exact same time.

2 2

[Dovecot] deliver and time
by Rick Romero 05 Oct '10

05 Oct '10

Hi All, I've been experimenting with deliver on my personal domain, and so far everything has been peachy except for Mail.app. Mail.app (on multiple devices) is showing what looks to be GMT times, rather than the date header. Initially I thought it was something I did on my Mac, until I got an Ipad to test with - and never connected it to my Mac - and had the same time issue. It seems Mail.app uses the timestamp ('arrived date'?) on the mail file itself (Maildir here) to display the time. So.. I have dovecot 1.2.10 installed on top of vpopmail (multiple MXs, delivering to OpenSolaris NFS share via tcp), and it seems that deliver is using the GMT time when writing the Maildir file, and vdelivermail just uses the adjusted time.. Or maybe it just allows the OS to write the timestamp. Either way, is this a known issue with deliver - or is there a patch? I don't recall ever seeing it come up on the list, and I'm not seeing anything in the changelog. Rick

4 9

Re: [Dovecot] [COREDUMP]: Command died with signal 11: "/usr/libexec/dovecot/dovecot-lda"
by Timo Sirainen 05 Oct '10

05 Oct '10

On 5.10.2010, at 2.10, Marco Smiatek wrote: > #0 0x00584829 in maildir_sync_set_new_msgs_count () from > /usr/lib/dovecot/libdovecot-storage.so.0 Thanks. http://hg.dovecot.org/dovecot-2.0/rev/e2f9baa436f2 should fix this.

1 0

Re: [Dovecot] Command died with signal 11: "/usr/libexec/dovecot/dovecot-lda"
by spamvoll＠googlemail.com 04 Oct '10

04 Oct '10

dovecot-lda is called via transport master.cf: dovecot unix - n n - 10 pipe flags=DRhu user=vmail:vmail argv=/usr/libexec/dovecot/dovecot-lda -f ${sender} -d ${recipient} im currently trying to get a core dump postfix.. but no luck so far 2010/10/5 Stephan Bosch <stephan(a)rename-it.nl>: > On 10/4/2010 11:56 PM, spamvoll(a)googlemail.com wrote: >> >> my userdb is LDAP >> >> each uid has multiple email adresses like lastname@ and >> firstname.lastname@ >> >> if you send a mail to lastname@ and firstname.lastname@ that happens > > Hmm, so then it is triggered at the MTA level. Perhaps it has something to > do with the new -r argument to dovecot-lda (and similar changes in LMTP). > How does your MTA offer mail to Dovecot ? How is dovecot-lda called? > > Can you produce a gdb backtrace? > > http://www.dovecot.org/bugreport.html > > Regards, > > Stephan. > > > > > >

1 0

Re: [Dovecot] Command died with signal 11: "/usr/libexec/dovecot/dovecot-lda"
by Stephan Bosch 04 Oct '10

04 Oct '10

On 10/4/2010 11:42 PM, spamvoll(a)googlemail.com wrote: > ok i can reproduce it, > > it happens when a mail should be delivered to 2 mailadresses of the same user > Could you elaborate a little? I don't quite understand what you mean. Regards, Stephan.

1 0

[Dovecot] Released Pigeonhole Sieve v0.1.18 and ManageSieve v0.11.12 for Dovecot v1.2.15
by Stephan Bosch 04 Oct '10

04 Oct '10

Hello Dovecot users, The recent release of Dovecot v1.2.15 is a good opportunity to release new versions of Sieve and ManageSieve for Dovecot v1.2. These releases consist entirely of bugfixes and introduce no new features. Changelog Sieve v0.1.18: - Imap4flags: fixed segfault bug occuring in multiscript context. Occured in specific situations when a script using imap4flags was followed in the sequence by scripts not using imap4flags. - Imap4flags: fixed bug in setflag command; when parameter was a stringlist, only the last item was actually set. - Prevented assertion failure due to currupt binary string representation. If the string were missing a final \0 character an assertion was produced in stead of a binary corruption error. - Multiscript: fixed duplicate implicit keep caused by erroneous execution state update. - Fixed Sieve script name checking to properly handle length limit and added 0x00ff as invalid character. - Removed spurious old stdio.h (top) includes; these caused compile issues on specific systems. - Fixed default Sieve capability (as reported by ManageSieve): extra extensions spamtest, spamtestplus and virustest were enabled by default. These should, however, only be enabled when properly configured and there is no default configuration. - Variables extension: fixed :length set modifier to recognize utf8 characters in stead of octets. - Fixed unnecessary reporting of dummy extensions in ManageSieve SIEVE capability; the comparator-i;octet and comparator-i;ascii-numeric 'extensions' were reported explicitly. - LDA Sieve plugin: added _version symbol to enable Dovecot's plugin version check. Without this check, people can forget to recompile the plugin, which can lead to unexpected effects. Changelog ManageSieve v0.11.12: - Fixed error handling of PUTSCRIPT commmand; save commit errors would not make the command fail. - Fixed PUTSCRIPT bug causing it to hang when given an empty script name. The releases are available as follows: Sieve http://www.rename-it.nl/dovecot/1.2/dovecot-1.2-sieve-0.1.18.tar.gz http://www.rename-it.nl/dovecot/1.2/dovecot-1.2-sieve-0.1.18.tar.gz.sig ManageSieve http://www.rename-it.nl/dovecot/1.2/dovecot-1.2-managesieve-0.11.12.tar.gz http://www.rename-it.nl/dovecot/1.2/dovecot-1.2-managesieve-0.11.12.tar.gz.… ManageSieve patch http://www.rename-it.nl/dovecot/1.2/dovecot-1.2.15-managesieve-0.11.12.diff… http://www.rename-it.nl/dovecot/1.2/dovecot-1.2.15-managesieve-0.11.12.diff… Refer to http://pigeonhole.dovecot.org and the Dovecot wiki for more information. Have fun testing this new release and don't hesitate to notify me when there are any problems. Regards, -- Stephan Bosch stephan(a)rename-it.nl

1 0

[Dovecot] log_timestamp is not recognized
by Patrick Westenberg 04 Oct '10

04 Oct '10

Hi @all, I tried to change the log_timestamp to log_timestamp = "%Y-%m-%d %H:%M:%S " However it is not recognized and log entries are still written with the default settings: Oct 4 22:04:42 discovery dovecot: imap-login: Login: Oct 4 22:04:42 discovery dovecot: imap: Debug: Module loaded: Oct 4 22:04:42 discovery dovecot: imap: Debug: Added userdb setting: plugin/quota_rule=*:storage=0M What´s wrong? # OS: Linux 2.6.26-2-amd64 x86_64 Debian 5.0.5 auth_mechanisms = plain login log_timestamp = "%Y-%m-%d %H:%M:%S " mail_debug = yes mail_gid = vmail mail_location = mdbox:~/mdbox mail_plugins = quota mail_uid = vmail managesieve_notify_capability = mailto managesieve_sieve_capability = comparator-i;octet comparator-i;ascii-casemap fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date namespace { inbox = yes location = prefix = INBOX. separator = . type = private } passdb { args = /usr/local/etc/dovecot/dovecot-sql.conf.ext driver = sql } plugin { quota = maildir:User quota } protocols = imap sieve service imap-login { service_count = 1 } service managesieve-login { inet_listener sieve { port = 4190 } inet_listener sieve_deprecated { port = 2000 } service_count = 1 } ssl = required ssl_cert = </etc/ssl/certs/imap_wk-serv_net.crt ssl_key = </etc/ssl/certs/imap_wk-serv_net.key userdb { args = /usr/local/etc/dovecot/dovecot-sql.conf.ext driver = sql } protocol imap { mail_plugins = $mail_plugins imap_quota }

3 3

[Dovecot] [2.0.5] quota in maildirsize doesn't work with mdbox
by interfaSys sàrl 04 Oct '10

04 Oct '10

Hello, I'm using mdbox to store messages and maildirsize to store quotas I have the following in my dovecot.conf mail_plugins = quota trash zlib fts fts_squat imap_quota imap_zlib antispam quota = maildir:User quota quota_rule = ?:storage=1G quota_rule2 = Trash:storage=+10%% I noticed that the quotas were wrong, so I sent myself some emails in hope of seeing the ratio change to the correct values, but the amount of used space changed to the total of what was just received, not the total of what was in the mailbox. So I tried to recalculate the quota using doveadm quota recalc, but it didn't help, instead of recalculating the amount of used space, it just wrote 0 0 to maildirsize. Do I have a config problem or is someting broken in Dovecot? Cheers, Olivier

2 2

[Dovecot] v2.0.5 released
by Timo Sirainen 04 Oct '10

04 Oct '10

http://dovecot.org/releases/2.0/dovecot-2.0.5.tar.gz http://dovecot.org/releases/2.0/dovecot-2.0.5.tar.gz.sig See the "ACL handling bugs" message for more details about the ACL merging bug. * acl: Fixed the logic of merging multiple ACL entries. Now it works as documented, while previously it could have done slightly different things depending on the order of the entries. * virtual: Allow opening virtual mailboxes that refer to non-existing mailboxes. It seems that the benefits of this outweigh the lack of error message when typoing a mailbox name. + Added some disk I/O optimizations to Maildir and index code. They're especially helpful with short-lived connections like POP3. + pop3: Added pop3_fast_size_lookups setting. - doveconf sometimes failed with complaining about missing ssl_key setting, causing e.g. dovecot-lda to fail. - lda: If there's an error in configuration, doveconf didn't exit with EX_TEMPFAIL as it should have. - sdbox: Fixed memory leak when copying messages with hard links. - zlib + sdbox combination didn't work - zlib: Fixed several crashes, which mainly showed up with mbox. - quota: Don't crash if user has quota disabled, but plugin loaded. - doveadm fetch uid was actually returning sequence, not uid. - v2.0.4's subscription listing ignored (and logged a warning about) subscriptions=no namespaces' entries in some configurations. (So listing shared mailboxes' subscriptions could have been broken.) - acl: Fixed crashing when sometimes listing shared mailboxes via dict proxy.

4 8

[Dovecot] Setting up the Director
by Jason 'XenoPhage' Frisvold 04 Oct '10

04 Oct '10

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi all, I'm trying to wrap my head around the Director and how it works, but I'm not having much luck finding documentation. Currently, I have two front end mail servers that use NFS for mail storage. I'm using Cisco's SLB for load balancing, though I may switch over to a server-based load balancing solution at some point. SLB works great, but it doesn't guarantee that a given user will stick to the same server. At least, not as it's configured now.. But, regardless, I want to move away from SLB so I can have a bit more control. If I want to implement the Director, do I need to have additional machines, or does it get configured on the front end mail machines? I'm thinking the former, but hoping for the latter.. :P Does anyone know of a really good write-up about the director and how it works? thanks, - --------------------------- Jason 'XenoPhage' Frisvold xenophage(a)godshell.com - --------------------------- "Any sufficiently advanced magic is indistinguishable from technology." - - Niven's Inverse of Clarke's Third Law -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.14 (Darwin) iEYEARECAAYFAkypPLcACgkQ8CjzPZyTUTT+/QCfUpOS4mdc6hMCZLXAYIlnfOdL XfcAmgIH0n1peB1qHKSfIps0wQ8dbHxF =h8Xt -----END PGP SIGNATURE-----

2 1