similar to: 0.99.13 released

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

Dear All, Thanks for all your replied but still I don't know how to install from 1.0.7 to 1.2.14. What should I consider to keep the same configuration during or after upgrade? It is the first time I am trying to upgrade my Dovecot. Thank a lot for your help --- On Fri, 1/10/10, dovecot-request at dovecot.org <dovecot-request at dovecot.org> wrote: From: dovecot-request at

Dear All, Is there any easy way to upgrade Dovecot like yum command? Or I have to delete the current and install the new version then change the setting?> I will appreciate if you can tell me the steps please? Best Regards Arif --- On Fri, 1/10/10, dovecot-request at dovecot.org <dovecot-request at dovecot.org> wrote: From: dovecot-request at dovecot.org <dovecot-request at

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! I understand that it is not trivial to move away from vpopmail and does require changing a working system. But then again, one should be able to configure MySQL passdb/userdb with vpopmail schema. I am not familiar with vpopmail but if someone comes with instructions we can polish them a bit (if necessary) and publish them as howto on doc.dovecot.org. Aki > On 18/03/2020 17:52 Remo

Can anyone tell me what's going on and how I can fix it? bash-2.05a# make make all-recursive Making all in src Making all in lib make[3]: Nothing to be done for `all'. Making all in lib-settings make[3]: Nothing to be done for `all'. Making all in lib-charset make[3]: Nothing to be done for `all'. Making all in lib-mail make[3]: Nothing to be done for `all'. Making all in

Hello, am I right, that dovecot can't cope with ldap so authentification is handled by ldap itself? And, for that I have to use {CRYPT} and cannot use other mechanisms as {SMD5} Are there any other possibilities? A --

With these planned changes, you mention they will be removed from 'core', so is the intention to allow more of these legacy plugins to more to their own repo's for those that might still want to use them? Eg, more in the the path of plug-in architecture? Just curious for clarity. Oh, and have to add.. still waiting on the variable capability patch, to allow plugins to modify

Amongst other plug-ins, yes.. On 2020-03-17 10:15 p.m., Aki Tuomi wrote: > Those plugins can be resurrected with simple `git revert`. > > Are you planning on open sourcing your client id authetication plugin? > > Aki >> On 18/03/2020 01:44 Michael Peddemors < michael at linuxmagic.com >> <mailto:michael at linuxmagic.com>> wrote: >> >>

Hi, after upgrading from 2.0.15 to 2.0.16 authentication with vpopmail won?t work anymore. 2.0.x and 1.2.x works (this output is from 2.0.15): Nov 28 18:29:21 mail dovecot: auth: Debug: auth client connected (pid=3855) Nov 28 18:29:21 mail dovecot: auth: Debug: client in: AUTH 1 PLAIN service=imap secured lip=10.114.57.11 rip=10.114.57.11 lport=143 rport=37693

So I am on of the many users with qmail, and using vpopmail auth, I guess chatting with some other guys in the other mailing list we will convert to mysql driver but this is a lot of work for many people. I do understand dropping things out but a valid solutions needs to be proposed. Remo > On Mar 18, 2020, at 06:49, Michael Peddemors <michael at linuxmagic.com> wrote: > >

Hi, I have a qplot like the one in the minimal example below, except I also have faceting like this: qplot(jitter(Goodall),jitter(Better.adapt),colour=Second.adapt,facets=~Pol,data=d1) and with the real data I get quite a lot of overplotting, so I would like to add an alpha channel. In addition, I would like to be able to control which colors are used for each value of Second.adapt (which

Hi! Dovecot is now a nearly 20 year old product, and during that time it has accumulated many different features and plugins in its core repository. We are starting to gradually remove some of these parts, which are unused, untested or deprecated. We will provide advance notification before removing anything. To start, the following features are likely to be removed in next few releases of

Hi! Dovecot is now a nearly 20 year old product, and during that time it has accumulated many different features and plugins in its core repository. We are starting to gradually remove some of these parts, which are unused, untested or deprecated. We will provide advance notification before removing anything. To start, the following features are likely to be removed in next few releases of

<!doctype html> <html> <head> <meta charset="UTF-8"> </head> <body> <div> Those plugins can be resurrected with simple `git revert`. </div> <div> <br> </div> <div> Are you planning on open sourcing your client id authetication plugin? </div> <div> <br> </div>

Just upgrading to 1.0.0 and I'm trying to switch from PAM (using pam-mysql) to a direct mysql query from dovecot, and I've got both md5crypt and crypt passwords in a password db. http://wiki.dovecot.org/Authentication/PasswordSchemes seems to indicate that I have to pick 1, but that is per auth-worker, right? So, I created 2 auth workers using 2 dovecot-sql config files specifying

Hello, I've just installed dovecot to replace courier-imap and I've found out it didn't support some of the typical LDAP userPassword schemes, so I've written some based on OpenSSL API. Furthermore I noticed that the MD5 one seems broken. If it isn't a requirement to ship its own implementation of a crypto algorithm, I would send in a patch to replace schema checks with

I am using a FreeBSD 11-2 amd/64 system with dovecot version 2.3.4 installed. I was playing around with different encryption schemes. doveadm pw -l SHA1 SSHA512 BLF-CRYPT PLAIN HMAC-MD5 OTP SHA512 SHA RPA DES-CRYPT CRYPT SSHA MD5-CRYPT SKEY PLAIN-MD4 PLAIN-MD5 SCRAM-SHA-1 LANMAN SHA512-CRYPT CLEAR CLEARTEXT SSHA256 NTLM MD5 PBKDF2 SHA256 CRAM-MD5 PLAIN-TRUNC SHA256-CRYPT SMD5 DIGEST-MD5

I mis-spoke. It seems I had two collections of functions in the same directory. One by Colin Goodall, and one by David Scott (I have no record of where he is/was located). It is the *latter* collection that does all its work from within Fortran. I'll have another look at what Colin Goodall actually wrote to see if it could be useful to guarav. cheers, Rolf Turner rolf at

I have a couple of questions regarding the default dovecot packaged with RedHat ES 4. The dovecot version is 0.99.11-2.EL4.1 which I assume is considerably behind the current stable version of 0.99.14. Is it the fact that I am using an older version of dovecot that SSHA passwords in an openldap directory are not recognized and give the following error: dovecot-auth: Unknown password scheme