similar to: 0.99.13-rc3

http://dovecot.org/rc/ Another one. Unless there are some bugs this will be the final version in a few days. * GNUTLS support hasn't been working for a while, so it's not even tried to be used anymore unless explicitly wanted. + Added CRAM-MD5 authentication mechanism. Patch by Joshua Goodall + Added SMD5 password scheme support and changed MD5 scheme with LDAP to act as

v0.99.13 2005-01-06 Timo Sirainen <tss at iki.fi> * GNUTLS support hasn't been working for a while, so it's not even tried to be used anymore unless explicitly wanted. + Added CRAM-MD5 authentication mechanism. Patch by Joshua Goodall + Added SMD5 and LDAP-MD5 password schemes and changed MD5 scheme to use LDAP-MD5 if the password isn't in MD5crypt format. Patch by

http://dovecot.org/releases/1.1/dovecot-1.1.14.tar.gz http://dovecot.org/releases/1.1/dovecot-1.1.14.tar.gz.sig http://dovecot.org/releases/1.2/rc/dovecot-1.2.rc3.tar.gz http://dovecot.org/releases/1.2/rc/dovecot-1.2.rc3.tar.gz.sig Fixed lots of bugs in v1.2 related to shared mailboxes and virtual mailboxes. Keep on testing and sending bug reports and hopefully we'll get v1.2.0 release out

http://dovecot.org/releases/1.1/dovecot-1.1.14.tar.gz http://dovecot.org/releases/1.1/dovecot-1.1.14.tar.gz.sig http://dovecot.org/releases/1.2/rc/dovecot-1.2.rc3.tar.gz http://dovecot.org/releases/1.2/rc/dovecot-1.2.rc3.tar.gz.sig Fixed lots of bugs in v1.2 related to shared mailboxes and virtual mailboxes. Keep on testing and sending bug reports and hopefully we'll get v1.2.0 release out

http://dovecot.org/releases/2.0/rc/dovecot-2.0.rc3.tar.gz http://dovecot.org/releases/2.0/rc/dovecot-2.0.rc3.tar.gz.sig A lot of dsync fixes. I think I've fixed now all of the bugs ever reported about dsync and I'm hopeful that it's now stable. All the rest of Dovecot looks pretty good too. Maybe v2.0.0 will be out next week. Changes since rc2: * Single-dbox is now called

http://dovecot.org/releases/2.0/rc/dovecot-2.0.rc3.tar.gz http://dovecot.org/releases/2.0/rc/dovecot-2.0.rc3.tar.gz.sig A lot of dsync fixes. I think I've fixed now all of the bugs ever reported about dsync and I'm hopeful that it's now stable. All the rest of Dovecot looks pretty good too. Maybe v2.0.0 will be out next week. Changes since rc2: * Single-dbox is now called

http://dovecot.org/rc/ Maybe this one works? :) -------------- next part -------------- A non-text attachment was scrubbed... Name: PGP.sig Type: application/pgp-signature Size: 186 bytes Desc: This is a digitally signed message part URL: <http://dovecot.org/pipermail/dovecot/attachments/20040903/4e4d3578/attachment-0001.bin>

Hi I have a question regarding the IMAP CAPABILITY command behavior of Dovecot 2.0.rc3. While connecting to a Dovecot 1.2.4 server and requesting the supported capabilities, Dovecot returns all capabilities: * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE STARTTLS AUTH=PLAIN] Dovecot ready. a1 CAPABILITY * CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE

We're doing a "mini-RC3" to encourage testing of the Highpoint driver (hptrr) backout. Testing of 7.0-RC2 showed there were problems with the driver update done between RC1 and RC2. Because it's a "mini-RC" targetted at testing of one particular thing we have not bothered with setting up FreeBSD Update. You can use the normal cvsup-and-build method of doing an update

http://dovecot.org/rc/ I guess the RCing in 0.99.12 didn't help that much. SQL/LDAP authentication crashed because memory was freed wrong. Please test so it would actually work in 0.99.13. Also fixed SEARCH UNKEYWORD which wasn't working. Also added 1.0-test's oe-ns-eoh POP3 workaround built-in. -------------- next part -------------- A non-text attachment was scrubbed... Name:

Hi, right now I have default_pass_scheme = MD5-CRYPT in my dovecot-sql-auth.conf file. This works; however I noticed because of history a lot of my users still have a CRYPT password (not a MD5-CRYPT password). Now I get these errors: dovecot: Feb 26 13:08:17 Info: auth-worker(default): sql(***, *******): MD5-CRYPT(0lifant) != 'i3/S6ZswGSfbk' Any way to make Dovecot

Hi, another imap crash with latest dovecot. segmentation fault in fetch_bodystructure src/imap/imap-fetch.c static int fetch_bodystructure(struct imap_fetch_context *ctx, struct mail *mail, void *context ATTR_UNUSED) { const char *bodystructure; if (mail_get_special(mail, MAIL_FETCH_IMAP_BODYSTRUCTURE,

Fixed all the reported bugs. Changed PAM service to "dovecot". Anything left? http://dovecot.procontrol.fi/rc/

v0.99.11 2004-09-04 Timo Sirainen <tss at iki.fi> + 127.* and ::1 IP addresses are treated as secured with disable_plaintext_auth = yes + auth_debug setting for extra authentication debugging + Some documentation and error message updates + Create PID file in /var/run/dovecot/master.pid + home setting is now optional in static userdb + Added mail setting to static userdb - After

I'm getting a lot of entries like this in my log: Apr 16 10:10:18 postamt dovecot: auth(default): shadow(doxxxris,141.42.206.38): CRYPT(wrongpassword) != '$1$qSe71xxx$09MoMqNyll.wPLCdSaFuA0', try MD5-CRYPT scheme instead It seems that changing the password via SquirrelMail (poppasswd) breaks the authentication scheme somewhat. Users cannot log in anymore. -- Ralf Hildebrandt

http://dovecot.org/releases/2.1/rc/dovecot-2.1.rc3.tar.gz http://dovecot.org/releases/2.1/rc/dovecot-2.1.rc3.tar.gz.sig Whops, rc2 was missing a file. I always run "make distcheck", which should catch these, but recently it has always failed due to clang static checking giving one "error" that I didn't really want to fix. Because of that the distcheck didn't finish and

http://dovecot.org/releases/2.1/rc/dovecot-2.1.rc3.tar.gz http://dovecot.org/releases/2.1/rc/dovecot-2.1.rc3.tar.gz.sig Whops, rc2 was missing a file. I always run "make distcheck", which should catch these, but recently it has always failed due to clang static checking giving one "error" that I didn't really want to fix. Because of that the distcheck didn't finish and

Is there any other mechanism than using passwd files with md5-hashed passwords created by dovecotpw that will support cram-md5 authentication? Has anyone created setups where the passwd databases reside in the individual users home directories? Is it possible to persuade dovecotpw to update the passwd databases automatically. Having to use a text editor to paste in the passwords sets a high

There are constantly pretty basic questions in this list (and in my inbox) about how to get user authentication work correctly. This means that the documentation how it all works is either bad, or people don't find it easily. Any ideas how to improve it? I did this now: - Documentation link in dovecot.org now points directly to Wiki, so people don't go read the outdated documents

http://dovecot.org/releases/dovecot-1.0.rc3.tar.gz http://dovecot.org/releases/dovecot-1.0.rc3.tar.gz.sig Does this fix the hangs people have been reporting? - SSL connections hanged sometimes, especially when saving messages. - mbox: Mail bodies were saved with CR+LF linefeeds - Mail forwarding was broken with deliver/Sieve - dbox fixes. Might actually be usable now. - Index file handling