Displaying 20 results from an estimated 40000 matches similar to: "MySQL passdb, auth_verbose, and documentation"
2005 May 08
1
trouble getting digest-md5 & ldap working
hi,
I am trying to set up dovecot with digest-md5 as authentication mechanism and
openldap as passdb.
My problem is ... that I just can't get it working. PLAIN authentication works
as expected, but no luck with digest-md5.
An excerpt from the two configuration files:
dovecot.conf:
--------CUT--------
auth = default
auth_mechanisms = plain digest-md5
auth_userdb = ldap
2018 Dec 20
3
Authentication Problem
I am using SHA512-CRYPT scheme for passwords.
In my dovecot-sql.conf.ext, I have: default_pass_scheme = CRYPT
In 10-auth.conf, I have:
auth_mechanisms = plain login digest-md5
M$ Outlook is refusing to authenticate, with error: Requested DIGEST-MD5
scheme, but we have only CRYPT
What an I missing??
I hate it that this has taken me round in circles :-)
--
Best regards,
Odhiambo WASHINGTON,
2006 Jan 12
2
dovecot-ldap.conf for usernames/homes/UID/GID
hi there,
I?m getting such a headache today, I?ve added myself to three mailing lists
trying to figure this out, okay here it goes.
I?ve got a Fedora Core 4 box running dovecot imap, squirrel mail, postfix,
samba/winbind.
I?m running winbind to authenticate against Active Directory, I?ve edited my
?/etc/pam.d/dovecot? pam module so to let my users login with there Active
directory password, but
2018 Dec 20
2
Authentication Problem
You've made this more difficult to understand, even :-)
So the answer is:
Set the following in 10-auth.conf
1. disable_plaintext_auth = no
2. auth_mechanisms = plain
And yes, the encrypted passwords are stored in MySQL.
On Thu, 20 Dec 2018 at 13:36, Nikolai Lusan <nikolai at lusan.id.au> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA512
>
> Greetings
> On
2018 Mar 07
2
Authentication Problem with dovecot-2.3.0.1
I am a little confused here.
I have been running 2.2.34 which I installed in /opt/dovecot2.2
I installed 2.3.0.1 to /opt/dovecot23
I then used config files from /opt/dovecot2.2/etc/dovecot to
/opt/dovecot2.3/etc/dovecot and all I did was sed -i.BAK
's/dovecot2.2/dovecot2.3/g'. Dovecot started and was running file.
Next, I manually crafted config files for 2.3.0.1 based on the example
2004 Jul 22
2
Authentification with PostgreSQL
Hi all,
I found Dag Wieers' Fedora Core 2 rpm on
http://dag.wieers.com/packages/dovecot/ and installed it. Now
dovecot-auth isn't complaining anymore about an unknown userdb type
but I can't get authentication working.
/etc/dovecot.conf
(...)
# Authentication process name.
auth = default
# plain digest-md5 anonymous
auth_mechanisms = plain
auth_userdb = pgsql
2004 Dec 12
2
Problem with LDAP and Dovecot
I am trying to set up Dovecot so that it uses LDAP, but I keep getting
this error message in /var/log/syslog:
Dec 12 03:38:17 mydomain dovecot-auth: LDAP: ldap_search() failed (filter
user_filter = (mail=user at mydomain.tld)): Bad search filter
Relevant configuration files:
/etc/dovecot-ldap.conf:
hosts = localhost
dn = cn=dovecot,ou=sysAccounts,dc=mydomain,dc=tld
dnpass = password
2013 Sep 03
1
setup of dovecot as proxy to dbmail
Can anyone point me in the direction of a detailed how-to for setting up a postfix and dovecot (proxy) node with dbmail?
In particular I'm looking for a how-to which shows dovecot authenticating against the dbmail database directly.
The only example I've found is this one which requires a duplication of the user database.
2012 Jun 08
3
upgrade from 1.0.5 to 2.1.7
Hello!
I want to upgrade the docevot-installation from v 1.0.5 to 2.1..7
Now I get the following executing
doveconf -n -c /etc/dovecot/dovecot.conf > /home/mail1/dovecot-2.conf
doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:217: add auth_ prefix to all settings inside auth {} and remove the auth {} section completely
doveconf: Warning: Obsolete setting in
2007 May 24
1
Dovecot LDA and address extensions
I'm converting over a virtual user installation that used Postfix and
maildrop with a MySQL back-end for mailbox lookups to use Dovecot LDA.
The maildrop setup used a database table like:
+-------------------------+--------+-------------+--------------------+
| address | owner | domain | mailbox |
2007 May 05
2
ldap and digest-md5 problem
Hi,
I'm using dovecot-1.0.0 on gentoo box and I have problem with authentication
using digest-md5 and passwords stored as plain text in ldap database, when I
use cram-md5 it works, while digest-md5 give this error (squirrelmail login):
May 5 16:03:32 srv dovecot: auth(default): client in: AUTH 1
DIGEST-MD5 service=IMAP secured lip=127.0.0.1 rip=127.0.0.1
May 5
2004 Jun 08
1
authentication configuration
I've included the non-defaulted bits of my dovecot.conf file at the
bottom of this email.
As I understand my set-up it's using unix authentication methods
(/etc/passwd via pam?).
Considering disable_plaintext_auth and auth_mechanisms, what exactly is
being passed? I was hoping to get
auth_mechanism = digest-md5
but that's not working out very well right now. It seems I can only
2017 Oct 04
3
moving from mysql to pgsql
Hello,
I hope that this mailing list is "alive", since I am looking for a
solution for my problem for a long time.
I would like to migrate my existing dovecot installation from mysql to
pgsql. But I have problems with the passwords when using pgsql.
The existing and working mysql-based installation looks like this:
dovecot-sql.conf.ext:
driver = mysql
default_pass_scheme =
2008 Jul 08
2
Dovecot CRAM-MD5 & DIGEST-MD5
Hello all.
Im try to make a SMTP Auth using Docecot SASL.
Im use swaks for tests.
Im store users in LDAP.
As im understand for CRAM & DIGEST MD5 we need to store pass in a clear
text?... Ok.
mail: admin3 at domain.off
userPassword: 123 <- Clear text
What im do
%swaks -a CRAM-MD5 -au admin3 at domain.off -ap 123
To: admin3 at domain.off
=== Trying mx.domain.off:25...
=== Connected to
2006 Aug 02
2
Cyrus + ldap
Hi,
I need some help
I am currently setting up my FC5 box with ldap + samba + postfix +
dovecot support as prescribed in howto
http://wanderingbarque.com/howtos/mailserver/mailserver.html
My problem is in starting the dovecot server.
I get the following error
Starting Dovecot Imap: Error: Error in configuration
file /etc/dovecot.conf line 16: Unknown setting: passdb
My dovcot.conf file:
2004 Jun 11
2
auth failure
well, with some help I've made a fair amount of progress on my box.
It's working out much easier than I had anticipated and perhaps my notes
will be useful some day.
I have two questions...
Here is where I am:
cling:~# egrep -v "^($|\#)" /etc/dovecot.conf
protocols = imap imaps
login = imap
login_max_processes_count = 16
login = pop3
max_mail_processes = 512
2015 Oct 27
1
Proxy with director accept only plain login
Hello, i'm test system dovecot (proxy with director) and backend
storage, auth LDAP server (user plain passwords)
If i use plain auth, work fine.
If connect DIGEST-MD5 or CRAM-MD5 proxy not redirect connection
(Requested DIGEST-MD5 scheme, but we have a NULL password)
### Frontend proxy+director
# dovecot -n
# 2.2.19: /usr/local/etc/dovecot/dovecot.conf
# OS: FreeBSD 10.2-RELEASE amd64
2018 Dec 06
3
argonid and dovecote
on a FreeBSD 11.2 amd64 machine, I am trying to get Dovecot 2.3.4 to play
nice with "argonid" encryption.
In the "10-auth.conf" file, I tried:
auth_mechanisms = plain argon2id
Upon restarting dovecot, I received an error message when attempting to
actually it:
auth: FATAL: Unknown authentication mechanism "ARGON2ID"
Output from doveadm pw -l
doveadm pw -l
SHA1
2012 Jun 08
1
dovecot ignores entries in virtual_alias_maps when using dovecot lda
hello list,
i need help. dovecot dont look into my virtual_alias_maps .
i set via postzfixadmin an alias postmaster at domain.tld to
newmail at domainother.tld.
when i send mails to postmaster at domain.tld mails are rejected. dovecot
authworker tells
me in log: user unknown.
but i can request the data via postmap -v -q postmaster at domain.tld
mysql:/etc/postfix/mysql_virtual_alias.cf
and get
2011 Dec 29
1
Trouble with proxy_maybe and auth_default_realm
Hello,
I'm using proxy_maybe and auth_default_realm. It seems that when a user
logs in without the domain name, relying on auth_default_realm, and the
"host" field points to the local server, I get the Proxying loops to
itself error. It does work as expected - log on to the local server
without proxying, if the user does include the domain name in the login.
(IP's and