similar to: Version Numbering and releases

Hello! I am moving my mail from the old server with 1.0.rc29 to a brand new server with 1.1.7. I use Maildir in both servers. A few questions: 1) The new server has another name, can I just copy the mail files as-is, will the server name in the file names matter? 2) The new server has a different architecture and different endian, so I plan not to copy the index and cache files; they seem to

Hi, I just migrated from dovecot 1.0.rc29 to 1.1.7, from Sparc platform to Intel, it went very well. In the process I merged folders and excluded folders from being copied. User rights on folders were kept/set. I thought I'd share my migration script with you folks. If there's an interest to put it on the wiki I can do that, but I'm not sure in what page. Use it as a starter if you

Just throwing out some thoughts here. I know Timo has high standards and is trying to make 1.0 bug free before calling it 1.0. But I want to argue for an earlier less perfect 1.0. Dovecot is already way past the quality of most 1.0 releases. So it is good enough by common standards. No one really expects a 1.0 release to be perfect. But - some people don't consider a product ripe until it

After sending a messasge about a problem (The folder 'Inbox' cannot contain items. Namespace problems) I found what seems to be a fix in the release for rc29. Besides any potential configuration files, do I need to delete the old index files? Any of the dovecot files? Based on the release notes for rc29 it seems the following will fix the problem we are experiencing: IMAP: LIST

Hi all, I'm having terrible time, and a lot of core dumps, building dovecot on Solaris 10. My environment: gcc 3.3.2 LDFLAGS=-L/usr/local/ssl/lib -lssl -lcrypto \ -L/usr/local/BerkeleyDB.4.2/lib -ldb -L/usr/local/lib -lldap CPPFLAGS=-I/usr/local/BerkeleyDB/include \ -I/usr/local/include -I/usr/local/ssl/include my configure: ./configure --prefix=/usr/local --with-ldap ...that is:

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

Hi, Not much left to fix in my migration script (moving between two dovecot servers). However, I discovered a mail folder .INBOX without cur, new and tmp subfolders, and the .imap.index files were rather old (feb 2006). Is this an old relic from early dovecot versions (I once ran 0.99 on this old server)? Or is it old client software? There are no data in it. TIA, Peter -- Peter Lindgren

http://dovecot.org/releases/dovecot-1.0.rc29.tar.gz http://dovecot.org/releases/dovecot-1.0.rc29.tar.gz.sig Probably one more RC after this. * Security fix: If zlib plugin was loaded, it was possible to open gzipped mbox files outside the user's mail directory. + Added auth_gssapi_hostname setting. - IMAP: LIST "" "" didn't return anything if there didn't

http://dovecot.org/releases/dovecot-1.0.rc29.tar.gz http://dovecot.org/releases/dovecot-1.0.rc29.tar.gz.sig Probably one more RC after this. * Security fix: If zlib plugin was loaded, it was possible to open gzipped mbox files outside the user's mail directory. + Added auth_gssapi_hostname setting. - IMAP: LIST "" "" didn't return anything if there didn't

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 It's a bit after 11pm, on the 11th day of the 11th month of the year, so what better time for a new release of X11! Release Candidate 1 of X11R7.6 has been posted at: http://www.x.org/releases/X11R7.6-RC1/ This includes all the source tar files for the versions of the modules currently considered part of the core release set (aka the

I think it's about time to start adding some new features to rsync 3 instead of just making bug fixes, so I'm planning to starting work on version 3.1.0. This will start the use of a new version numbering idiom where feature releases increment the sub-version number, while patch releases continue to increment the sub-sub-version number. I'm not using an odd/even scheme for

Help! I just noticed this error this morning, we have been getting a lot of these in rc28 and rc29, not in rc27 or before: Apr 6 07:22:52 karst dovecot: [ID 107833 mail.error] IMAP(jaearick): mbox file /var/mail/j/jaearick was modified while we were syncing, check your locking settings Pine coughed up an internal error, no core dump, and dovecot basically doubled the size of my mailbox by

Hi! Just updated to 1.0 rc15, but the problem remains. I think it could be client-dependent to some extent. I have only IMAPS access and Maildir. I have one mailbox which contains some 10,200 mails. That mailbox takes forever (have waited 30 minutes and then aborted) to open with Thunderbird 1.5.0.7. Other mailboxes (like dovecot :-), only 6984 mails) opens quickly. When Thunderbird tries to

http://dovecot.org/nightly/dovecot-latest.tar.gz Any comments about the doc/wiki/ contents? doc/documentation.txt? dovecot-example.conf's doc/wiki/ pointers? ./autogen.sh now updates the wiki from http://www.dovecot.org/tmp/wiki-export.tar.gz (updated each night) if doc/wiki/Authentication.txt doesn't exist. I guess I'll release rc29 tomorrow. The current changes are: + Added

Hi! I received the following error (I ran ./configure and make without options) when running make install: Making all in auth make: don't know how to make db-ldap.h. Stop in /tmp/dovecot-1.0b2/dovecot-1.0.beta2/src/auth. *** Error code 1 Stop in /tmp/dovecot-1.0b2/dovecot-1.0.beta2/src (line 284 of Makefile). *** Error code 1 Stop in /tmp/dovecot-1.0b2/dovecot-1.0.beta2 (line 340 of

Hello! I was looking for some information about which signals I can send to dovecot to do various things, but I couldn't find it. Since it's a wiki, is it ok to just edit the pages, or should I post here first? I thought I'd check with Timo and you guys first, maybe I missed that page that describes the signals... If it's ok, I can edit or add a new page. /Peter -- Peter

Hello! I am switching hardware platform for my dovecot 1.0beta3 installation. From Sun Sparc (SS4) to Intel i386. OS platform will only change from OpenBSD 3.7 to 3.9. From Dovecot 1.0beta3 to beta8. Is there anything special to consider, in terms of endianness or other incompatibilities? I plan on a fresh install (compile) on the new machine, migrate the settings manually (by hand), test

Hello! I have a simple (I think) problem. I have had IMAPS working fine for a long time. Now I want to start to use IMAP and STARTLS, since my mobile SonyEricsson P900 can't use IMAPS directly. But I can't connect even locally to the IMAP port (143), no-one listens there according to netstat (*.imaps is in LISTEN state). I have the following settings in my /etc/dovecot.conf:

Hi, Whitbox Linux 3 (RHEL) Dovecot 1.0.rc29 Using NFS From time to time does all mail get re-downloaded to Thunderbird. I would believe this has something to do with an index problem. I upgraded to 1.0 a few months ago but that didn't work well so I installed version 1.0.rc29 which worked better but we still get this problem from time to time. DOes anyone know if it is a good idea to

http://dovecot.org/releases/dovecot-1.0.rc28.tar.gz http://dovecot.org/releases/dovecot-1.0.rc28.tar.gz.sig Still a bit more fixes. My coding TODO list is again empty. Unless something special happens in the next few weeks, I'll still make rc29 with the documentation included and v1.0 will be released April 13. * deliver + userdb static: Verify the user's existence from passdb,