similar to: v1.0.2 released

http://dovecot.org/tmp/dovecot-1.0.2-rc.tar.gz Unless someone finds something broken, I'll release v1.0.2 in a few days. The most important changes since v1.0.1: * dbox isn't built anymore by default. It will be redesigned so it shouldn't be used. + Maildir: Support reading dovecot-uidlist (v3) files created by Dovecot v1.1. - Maildir: "UIDVALIDITY changed" errors

Hello. tl;dr = v1.0.0 can boot my LXC containers, v.1.0.1 and v.1.0.2 fails. Paraphrased error message: "lxcContainerMountProcFuse:616 : Failed to mount ..../meminfo" I'd like to know if my host is misconfigured, or my domains, or ... why 1.0.2 and 1.0.1 are not working for me. I've been using libvirt for a while to manage QEMU instances. I have experimented with lxc.

Hi, I've run into a bit of a problem and exhausted my knowledge and research. I'm hoping that I've overlooked something very obvious! I moved from a single Apple OS X 10.6.2 server Dovecot environment to a NFS clustered environment, currently with two servers. Both servers are identical hardware, software. Currently both the Dovecot index and data files are on the NFS RAID array.

Dear All, We would like to migrate our existing courier to dovecot. After reading document on website and doing some tests, here are some issues we met. 1. According the the wiki, it seems to imply that once migrating from courier to dovecot, pop3 users may "lost/forget" their download "index/ history" which cause them to download again old mails that are kept on

On Thu, 2020-04-09 at 13:48 +0300, Sami Ketola wrote: > > > > > On 31 Mar 2020, at 23.18, Ben Mulvihill <ben.mulvihill at gmail.com> > > wrote: > > > > Hello again, > > > > I am still stuck I'm afraid. > > > > I now have doveadm backup working perfectly from > > a small gmail mailbox (a few hundred messages), but >

http://dovecot.org/releases/1.2/dovecot-1.2.1.tar.gz http://dovecot.org/releases/1.2/dovecot-1.2.1.tar.gz.sig Mainly fixes to some issues found by people when upgrading to v1.2.0. * GSSAPI: Changed logging levels and improved the messages. Changed the way cross-realm authentication handling is done, hopefully it's working now for everyone. * imap/pop3 logins now fail if home

http://dovecot.org/releases/1.2/dovecot-1.2.1.tar.gz http://dovecot.org/releases/1.2/dovecot-1.2.1.tar.gz.sig Mainly fixes to some issues found by people when upgrading to v1.2.0. * GSSAPI: Changed logging levels and improved the messages. Changed the way cross-realm authentication handling is done, hopefully it's working now for everyone. * imap/pop3 logins now fail if home

Hello List, Getting ready to setup a new dovecot sendmail squirrelmail server for our school which is currently running on a 4 year old install of the same, which has worked like a champ by the way. --------------------- EL5 dovecot-1.1 rc10 rpm sendmail squirrelmail --------------------- Problem: I can not get my dovecot 1.1 rc10(rpm) to generate an maildirsize file in each of the users

I found a problem with maildir++ quota. When dovecot creates maildirsize file, it counts quota wrong. This is, how I reproduce a situation on version 1.2.0: First, I remove maildirsize file: # cd /var/mail/test # rm -f maildirsize # ls -la total 32 drwx--S--- 5 mbox mbox 4096 Jul 12 20:45 . drwxrwsr-x 3 root mbox 4096 Jul 12 20:39 .. drwx--S--- 2 mbox mbox 4096 Jul 9 20:45 cur -rw------- 1 mbox

http://dovecot.org/releases/1.1/alpha/dovecot-1.1.alpha1.tar.gz http://dovecot.org/releases/1.1/alpha/dovecot-1.1.alpha1.tar.gz.sig This is the first alpha release of Dovecot v1.1. I hope that it stabilizes into final release within a few months. There are a lot of new features since v1.0. The most important ones are listed at the end of this post. This is the only v1.1.alpha announcement I send

http://dovecot.org/releases/1.1/alpha/dovecot-1.1.alpha1.tar.gz http://dovecot.org/releases/1.1/alpha/dovecot-1.1.alpha1.tar.gz.sig This is the first alpha release of Dovecot v1.1. I hope that it stabilizes into final release within a few months. There are a lot of new features since v1.0. The most important ones are listed at the end of this post. This is the only v1.1.alpha announcement I send

Hi, testing expire plugin I get an error message "User lookup failed": /usr/sbin/dovecot --exec-mail ext /usr/libexec/dovecot/expire-tool -test Error: userdb(lukas at manual.at) didn't return uid Info: User lookup failed: lukas at manual.at Info: gkaefer2 at manual.at/INBOX.Sent: stop, expire time in future: Wed Mar 31 14:38:33 2010 Reviewing the expires database I see simmilar

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sun, 20 Sep 2015, lists at lazygranch.com wrote: > No problem sending email, but I can't receive email. Diagnostics follow: this is a pretty unspecific information. At which stage the message is stuck and not delivered to Dovecot? Which MTA do you use and how is it configurated? Or are the messages delivered to Dovecot and are spooled

I'm leaving soon and I'll be away until sunday. Sorry about not replying to all mails yet, most of them are somewhat tricky and require some time to reply (other than "I don't know"). The new index code for v1.1 seems to be finally working pretty nicely. After 9 hours of running imaptest I haven't gotten a single error yet. I'll leave it running until I'm back.

http://dovecot.org/releases/1.1/rc/dovecot-1.1.rc1.tar.gz http://dovecot.org/releases/1.1/rc/dovecot-1.1.rc1.tar.gz.sig Finally the first v1.1 release candidate. Please test so we can have a fully stable v1.1.0 release. v1.1.betas are already running in a few large installations, so I don't expect there to be many bugs left. There are no release critical bugs left and no known crash bugs.

http://dovecot.org/releases/1.1/rc/dovecot-1.1.rc1.tar.gz http://dovecot.org/releases/1.1/rc/dovecot-1.1.rc1.tar.gz.sig Finally the first v1.1 release candidate. Please test so we can have a fully stable v1.1.0 release. v1.1.betas are already running in a few large installations, so I don't expect there to be many bugs left. There are no release critical bugs left and no known crash bugs.

No problem sending email, but I can't receive email. Diagnostics follow: a login user at domain.com password a OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE SORT SORT=DISPLAY THREAD=REFERENCES THREAD=REFS THREAD=ORDEREDSUBJECT MULTIAPPEND URL-PARTIAL CATENATE UNSELECT CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH ESORT SEARCHRES

http://dovecot.org/releases/1.1/dovecot-1.1.0.tar.gz http://dovecot.org/releases/1.1/dovecot-1.1.0.tar.gz.sig Two hours later than promised, I slept longer than intended. :) No changes since v1.1.rc13. Below are the largest changes since v1.0: * After Dovecot v1.1 has modified index or dovecot-uidlist files, they can't be opened anymore with Dovecot versions earlier than v1.0.2. *

http://dovecot.org/releases/1.1/dovecot-1.1.0.tar.gz http://dovecot.org/releases/1.1/dovecot-1.1.0.tar.gz.sig Two hours later than promised, I slept longer than intended. :) No changes since v1.1.rc13. Below are the largest changes since v1.0: * After Dovecot v1.1 has modified index or dovecot-uidlist files, they can't be opened anymore with Dovecot versions earlier than v1.0.2. *

Hello, after dealing with shared folder within version 2.0 rc* I started using it with a group of users. user1 shares a folder to user2. user2 has access to messages of this shared folder. After a "random" time (minutes up to several days) user2 doesn't see those messages anymore. user1 (the owner) hasn't changed anything inside this folder. All messages are still in place