similar to: RFE: MD5 encryption with for plain text passwords

Hi, after getting dovecot working with PostgreSQL and plaintext passwords I tried to use md5 encrypted passwords with mozilla. www.roughtrade.net/dovecot says that Mozilla only supports CRAM-MD5 and that CRAM-MD5 is included in HEAD. Now I have two questions: 1) Is the md5 hash stored in passdb with cram-md5 the same as in digest-md5? 2) Is a new dovecot stable build planned within the next two

Hi, I'm wondering what is dovecot's support for CRAM-MD5? The mailing list for November 2003 seems to indicate that Timo has included it into the CVS tree, however the ChangeLogs in the latest version does not say anything about it. The online docs has indicated that it's supported, but the doc files in 0.99.10.4 doesn't seem to mention about it.... Thanks in advance.

Hello! Upgrading manual tells that authdb [NSS module was removed][1] some time ago. [1]: https://wiki2.dovecot.org/Upgrading/2.3#line-100 > userdb nss was removed. Use userdb passwd instead. Can this change be reverted? I'd like to use only libnss_sss.so.2 as dovecot userdb source. It's also essential for me to enable files backend in nsswitch.conf so the system could use local

I use LDAP right now, but local cached sssd queries are much faster and reliable. On July 15, 2019 6:49:18 AM GMT+03:00, Aki Tuomi <aki.tuomi at open-xchange.com> wrote: > > >On 15/07/2019 02:54 Eugene via dovecot < dovecot at dovecot.org> wrote: > > > >Hello! > > >Upgrading manual tells that authdb [NSS module was removed][1] some >time ago. >

Hi! I'm trying to use MD5 hashed password in a passwd-file (not the system one). I've set auth_userdb = passwd-file /my/passwd/file auth_passdb = passwd-file /my/passwd/file auth.txt additionally describes a syntax like: auth_userdb = passwd-file[34] /my/passwd/file to denote MD5 passwords in the file, but I've been unable to get any combination of using []'s after

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

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

Since no-one have complained about previous RCs, I guess it's release time. Since -rc2 I added the ioloop.c assert fix, and 64bit Solaris fix. Here's the full change summary again: v0.99.10.6 2004-06-20 Timo Sirainen <tss at iki.fi> + SHA1 password support using OpenSSL crypto library + mail_extra_groups setting + maildir_stat_dirs setting + Added NAMESPACE capability and

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 --

Hi, Is there any way to use something like OPIE (one-time passwords in everything, S/KEY) with dovecot? Here's what I want to do ultimately: * have an AUTH=XYZ method that relies on S/KEY as provided by the libpam-opie module (well, maybe not through pam) * have dovecot advertise authentication as follows: - local : PLAIN, XYZ - remote (encrypted) : EXTERNAL, and

Just achieved success using syslinux to multi-OS boot, including a WinXP System (boot) partition that's been encrypted with TrueCrypt (TC). You'll need syslinux version 3.81-pre13 or newer to get a working altmbr.bin file. I used: http://www.kernel.org/pub/linux/utils/boot/syslinux/Testing/syslinux-3.81-pre13.zip Background: I started with a 'normal' multi-OS boot setup as

Hi, Curtis (and the group), I tried setting up Dovecot's auth default section as you described, with both authdb and userdb set to 'passwd.' It let the authenticated session start on the POP side, but I got consistent authentication failures on the client side that the passwords didn't match. I don't have any more time to mess with it this morning, but I will make it a

Problem: Using MySQL storage for the user and password db with MD5-CRYPT hashes, Dovecot fails to successfully authenticate when the MD5-CRYPT or MD5 settings are specified as default_pass_scheme in dovecot-mysql.conf. Dovecot /does/ successfully authenticate against MD5-CRYPT hashes when default_pass_scheme is set to CRYPT, which according to the docs should be DES encryption. (I do not

Hi! I'm wondering how close Dovecot can be said to be to 1.0 "Final". How stable can the alpha branch be said to be? I was browsing around the Dovecot homepage, but I couldn't find any answer to this question. I hope it hasn't been asked (too many times) before. Fredrik Tolf

Hi, we are just testing postfix 2.3 in combination with its new dovecot SASL plugin. Now what we would like to have was dovecot SASL without acutally running dovecot ... The reason for this is because we have the "real" dovecot running on a different server than the postfix instance and it would be nice if it would not be necessary running an "full" dovecot on that server for

I'm currently setting up a large mail system, with different services split out onto different machines. What I want is this: machine1: dovecot smtp auth, no pop/imap machine2: dovecot lda, no pop/imap machine3: pop/imap, nothing else machine3 is obviously not the issue. Is there a way to run machine1 and machine2 with just their respective services, but no pop/imap? -- Marshal Newrock

Hey all, A few minutes ago, I installed Dovecot, hoping things would get clear by just looking at the relevant config files, but since they don't, I hope someone here could give me a clue... What I want to achieve is really only basic functionality. It's just for personal use, so it shouldn't get too complicated. Up til now, I have been using fetchmail to get my mail off of several

Gedalya-san Thank you for the information. It seems to be difficult... morikawa -----Original Message----- From: dovecot [mailto:dovecot-bounces at dovecot.org] On Behalf Of Gedalya Sent: Thursday, October 29, 2020 1:17 PM To: dovecot at dovecot.org Subject: Re: dovecot quota-warning detection mail Aha. Then it's not a straightforward case of just adding the domain name to the same

After I found out that {CRYPT} doesn't support passwords longer than 8 characters, I decided to switch over to MD5 for user passwords in my LDAP database. However, while I have no problem with Postfix + SASL, Dovecot fails to authenticate. Relevant bits from /etc/dovecot-ldap.conf: user_attrs = mailAddress,,,,, # The search string is identical to what's found in /etc/saslauthd.conf: