search for: dovecotlist

Hello list, The dovecot version is 1.2.6 running on Solaris x86 11 (nv-b91). The relevant configuration lines are: passdb ldap { # LDAP database (doc/wiki/AuthDatabase.LDAP.txt.) args = /pfx/etc/dovecot/dovecot-ldap.conf } The file dovecot-ldap.conf is correct and LDAP authentication is working well. We would like to make it possible for users with a X.509 client certificate to log in

The wiki[1] says: If all the passwords are in same format, you can use default_pass_scheme to specify it. Otherwise each password needs to be prefixed with "{password-scheme}", for example "{plain}plaintext-password". Why doesn't dovecot recognize the crypt scheme identifier ($1$ for MD5-CRYPT, $6$ for SHA512-CRYPT etc.)? At the moment I have to have the following in my db

Hello List, The only passdb block in /pfx/etc/dovecot/dovecot.conf is: passdb ldap { args = /pfx/etc/dovecot/dovecot-ldap.conf } In /pfx/etc/dovecot/dovecot-ldap.conf: auth_bind = no dn = cn=mymgr,dc=host,dc=tld dnpass = ******** default_pass_scheme = LDAP-MD5 In /pfx/etc/openldap/slapd.conf: password-hash {MD5} If I try: $ /pfx/bin/ldapsearch <...> \ | grep

...gure --with-gssapi=yes Otherwise, settings are pretty simple. Add the following 3 settings to 10-auth.conf: auth_gssapi_hostname = "$ALL" auth_krb5_keytab = /etc/dovecot/dovecot.keytab auth_mechanisms = plain login gssapi The auth_gssapi_hostname is supposedly not required according to dovecotList comments, but my 10-auth.conf template implies differently, so it can't hurt. I couldn't get any of this working until I rebooted the Samba AD/DC-Dovecot server, but that just may have been me not stopping/starting Samba and Dovecot in the right sequence (or, I needed a Samba upgrade to 4....

...ple. Add the following 3 settings to 10-auth.conf: > > > > auth_gssapi_hostname = "$ALL" > > auth_krb5_keytab = /etc/dovecot/dovecot.keytab > > auth_mechanisms = plain login gssapi > > > > The auth_gssapi_hostname is supposedly not required according to dovecotList comments, but my > > 10-auth.conf template implies differently, so it can't hurt. > > > > I couldn't get any of this working until I rebooted the Samba AD/DC-Dovecot server, but that > > just may have been me not stopping/starting Samba and Dovecot in the right seque...

I can't seem to find any documentation on the meaning/syntax of the "pattern" variable in map sections that are found in dovecot-dict-sql.conf.ext for example. I am trying to setup shared folders. The only thing[1] I found is: >>First you'll need to know what kind of dict paths the code uses. ACL >>plugin uses these paths: >>

...rwise, settings are pretty simple. Add the following 3 settings to 10-auth.conf: > > auth_gssapi_hostname = "$ALL" > auth_krb5_keytab = /etc/dovecot/dovecot.keytab > auth_mechanisms = plain login gssapi > > The auth_gssapi_hostname is supposedly not required according to dovecotList comments, but my > 10-auth.conf template implies differently, so it can't hurt. > > I couldn't get any of this working until I rebooted the Samba AD/DC-Dovecot server, but that > just may have been me not stopping/starting Samba and Dovecot in the right sequence (or, I > need...

...rwise, settings are pretty simple. Add the following 3 settings to 10-auth.conf: > > auth_gssapi_hostname = "$ALL" > auth_krb5_keytab = /etc/dovecot/dovecot.keytab > auth_mechanisms = plain login gssapi > > The auth_gssapi_hostname is supposedly not required according to dovecotList comments, but my > 10-auth.conf template implies differently, so it can't hurt. > > I couldn't get any of this working until I rebooted the Samba AD/DC-Dovecot server, but that > just may have been me not stopping/starting Samba and Dovecot in the right sequence (or, I > need...

...wing 3 settings to 10-auth.conf: >>> >>> auth_gssapi_hostname = "$ALL" >>> auth_krb5_keytab = /etc/dovecot/dovecot.keytab >>> auth_mechanisms = plain login gssapi >>> >>> The auth_gssapi_hostname is supposedly not required according to dovecotList comments, but my >>> 10-auth.conf template implies differently, so it can't hurt. >>> >>> I couldn't get any of this working until I rebooted the Samba AD/DC-Dovecot server, but that >>> just may have been me not stopping/starting Samba and Dovecot in the...

Hi, I've noticed a possible minor issue with long encoded filenames for attachments where these filenames are split across multiple lines. My understanding of character encoding and MIME is not as good as it should be, so I may easily have got this all mixed up, in which case sorry for the noise... Although I understand the preferred method for handling filenames split across multiple

Hi All, I currently have a small Dovecot server (Server A) and I've installed a second dovecot mailbox server (server B) and am trying to sync mailboxes from Server A to Server B. Both servers sit behind two dovecot directors on separate hosts and have identical config files (doveconf -n output below). Mailboxes on Server A are on an NFS mount. Server A has been working fine with no

...ple. Add the following 3 settings to 10-auth.conf: > > > > auth_gssapi_hostname = "$ALL" > > auth_krb5_keytab = /etc/dovecot/dovecot.keytab > > auth_mechanisms = plain login gssapi > > > > The auth_gssapi_hostname is supposedly not required according to dovecotList comments, but my > > 10-auth.conf template implies differently, so it can't hurt. > > > > I couldn't get any of this working until I rebooted the Samba AD/DC-Dovecot server, but that > > just may have been me not stopping/starting Samba and Dovecot in the right seque...

...f: > >>> > >>> auth_gssapi_hostname = "$ALL" > >>> auth_krb5_keytab = /etc/dovecot/dovecot.keytab > >>> auth_mechanisms = plain login gssapi > >>> > >>> The auth_gssapi_hostname is supposedly not required according to dovecotList comments, but my > >>> 10-auth.conf template implies differently, so it can't hurt. > >>> > >>> I couldn't get any of this working until I rebooted the Samba AD/DC-Dovecot server, but that > >>> just may have been me not stopping/starting Samb...

More info ... when I do MAIL=imap://mark at mail.ohprs.org/ mutt (using the domain of the registered certificate). I do not get the message "Certificate host check failed: certificate owner does not match hosthame ..." I do get the same (mutt?) edit screen shown below with the "(r)eject, accept (o)nce, (a)ccept always" action at the bottom. If I "accept (o)nce",

Hello I use exim/dovecot combination for mail delivery and pickup and I'm wondering how I can prevent users from moving, deleting or renaming particular IMAP folders. I use the MailDir mailbox format. The reason for doing this is that I have some special exim filters which deliver mail to specified directories. I don't want users to be able to change these folders because it will

Hi We run "Dovecot 1.0 Stable" when I try to use the ACL plugin I get the following message: Error: Error in configuration file /etc/dovecot.conf line 391: Unknown setting: mail_plugins Are plugins unsupported in our version, or could this be something else? Thanks, Darren. |------------------------------------------------------------------------------- Any opinions expressed in

I'm curious about exactly what this means in my log: Mar 13 10:56:20 cerebus dovecot: imap-login: Disconnected [130.94.242.20] Mar 13 10:56:51 cerebus last message repeated 177 times Mar 13 10:57:32 cerebus last message repeated 179 times Now...does Dovecot ONLY log the names of users on successful attempts? Is this "Disconnected" log entry an indication someone ran a

This may be trivial but reading the documentation I can't find a clear answer: If multiple authentication mechanisms (or multiple databases for one) are defined, does it allow one user account to have several (at least two) alternative passwords (so that any of them would work)? Or does it first map an account to a fixed authentication mechanism/password and if it fails, others won't be

The default configuration file for Dovecot in Debian uses: ssl_cert = </path/to/cert I checked my current configuration and I use: ssl_cert =/path/to/cert What is the difference? (pipe?) And is the former better somehow?

Dovecot 2.2.9-1 accepts SETACL commands that share mailboxes to non-existent mailboxes. There is no error message. Is this intended behavior? I think it's bad because clients present a success message when indeed the intent of the user failed. Typos are hard to catch.