- dovecot - dovecot.org

Re: [Dovecot] Error "Initializing mail storage ..." after upgrading to 2.2.10
by Joseph Tam 27 Feb '14

27 Feb '14

G?tz Reinicke - IT Koordinator <goetz.reinicke(a)filmakademie.de> wrote: > But on one mailbox I do get an error: > > Error: user rechnnugseingang-animationsinstitut: Initialization failed: > Initializing mail storage from mail_location setting failed > > Error: Invalid user settings. Refer to server log for more information. And the server logs says ...? Maybe the '-' is not one of the allowed characters (is there a missing 'e' at the end?) Joseph Tam <jtam.home(a)gmail.com>

2 1

[Dovecot] dsync mirror to mailstores in director setup
by Murray Trainer 27 Feb '14

27 Feb '14

Hi All, I have dsync mirror command working between a standalone dovecot server and a backend mailstore in a Dovecot Director setup. Is it safe to do the dsync directly to the backend mailstore in this setup? It doesn't seem to work via the director proxy. Thanks Murray

1 0

Re: [Dovecot] Removing Mount Points
by Jeff Geiger 26 Feb '14

26 Feb '14

That's exactly where I pulled that information from. Are you saying that my assumption is correct and I can run that without ending the world as I know it? :) Thanks! Jeff Geiger jeff.geiger(a)firespring.com On Wed, Feb 26, 2014 at 1:03 AM, Steffen Kaiser < skdovecot(a)smail.inf.fh-brs.de> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > > On Tue, 25 Feb 2014, Jeff Geiger wrote: > > dsync(sales(a)foo.com): Error: Couldn't create index dir >> /mnt/ssd/indexes/6/a/ >> sales(a)foo.com/mailboxes: Can't create mailbox root dir >> /mnt/ssd/indexes/6/a/ >> sales(a)foo.com/mailboxes: Mountpoint /mnt/ssd isn't mounted. Mount it or >> remove it with doveadm mount remove >> >> Would doing a `doveadm mount remove /mnt/ssd` fix my issue, or cause some >> type of catastrophe? >> > > ;-) http://wiki2.dovecot.org/Tools/Doveadm/Mount > > - -- Steffen Kaiser > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.11 (GNU/Linux) > > iQEVAwUBUw2R3XD1/YhP6VMHAQLoRQf+LBey9f2o1+MLRSgJB+Sptp0aC746kAz6 > 8cddo6qfNGMogQ7ilfflqCpm1YA/iD29d+8/TL10616cDKZ0Tb1a4M+w8pNnImUa > ViUSBlf59QA6k9b7dshB6f191NPmFT5/lHusDZJywDcS1kal+D/lIsOPToy+Hfon > zkEslqh3Gksjj60yYrBbOBw0a2lesy7eSYunBcabTfumwFHJofWSlWuvQdxfBXKW > IMQ4yzKL1bv+UgfnJpfo6qzReV++sKS9IehGEygqEU7gCE/jhRZyZIICfXRqQAnC > 0jrboJwtfDdY7BX7LrjhaFYtQNCgNF3VqTPnHbyH+eT2KhlLkgMMMA== > =xo3d > -----END PGP SIGNATURE----- >

2 1

[Dovecot] 2 users database on same LDAP with different mail location
by Francesco 26 Feb '14

26 Feb '14

Hello, i know i know, i'm getting annoying but appearently i always come up with weird ideas and i cant seem to accomplish such a task. the scenario is that i have an LDAP server with a bunch of users. some of them are in a specific OU, and i'd like to define for all these users belonging to this OU an alternative mail location/storage. in details for all the users i'd like to use maildir storage in a directory, while for the users belonging to a specific OU i'd like to use dbox with an alternative storage attached. so i created 2 userdb like this: userdb { driver = ldap args = /etc/dovecot/dovecot-ldap-maildir.conf.ext } userdb { driver = ldap args = /etc/dovecot/dovecot-ldap-dbox.conf.ext } and then defined these 2 args files: maildir: hosts = localhost dn = CN=ldapadmin,OU=administrators,DC=plutone,DC=local dnpass = <password> auth_bind = yes ldap_version = 3 base = DC=plutone,DC=local user_attrs = sAMAccountName=home=/var/vmail/%$ dbox: hosts = localhost dn = CN=ldapadmin,OU=administrators,DC=plutone,DC=local dnpass = <password> auth_bind = yes ldap_version = 3 base = OU=dboxusers,OU=lowpriority,DC=plutone,DC=local user_attrs = sAMAccountName=home=/var/local_dbox/%$, =mail=dbox:/var/local_dbox/%$:ALT=/var/iscsi_dbox/%$ user_filter = (&(ObjectClass=person)(mail=%u)) yet it doesn't matter how hard i try if i send an email to a user belonging to the dboxusers OU i still have the user to be addressed to the maildir storage in /var/vmail am i missing something? Thanks Francesco

4 7

[Dovecot] Dovecot upgrade 1 to 2 on Debian Squeeze : broken /var/run/dovecot
by Si L 26 Feb '14

26 Feb '14

Hi, I just upgraded from version 1 to version on Debian Squeeze using their backports. Like I expected my dovecot1 config had to be converted using doveconf and this I did. However, I see problems with files inside directory: drwxr-xr-x 4 dovenull root 4096 Feb 25 20:35 /var/run/dovecot All of them were created owned by root:root rw. I tried to changed, for example : chown postfix:dovecot /var/run/dovecot/auth-master but noticed when I restarted dovecot it reset the permissions back to root:root rw. Here's the version: # dovecot --version 2.1.7 Here's my slightly redacted conf. # grep -v ^# dovecot.conf|grep -v ^$ auth_mechanisms = plain login auth_verbose = yes dict { quotadict = mysql:/etc/dovecot/dovecot-dict-quota.conf } disable_plaintext_auth = no first_valid_uid = 106 log_timestamp = "%Y-%m-%d %H:%M:%S " mail_location = maildir:/var/xx/%d/%u/ mail_plugins = quota mail_privileged_group = mail maildir_very_dirty_syncs = yes passdb { args = /etc/dovecot/dovecot-mysql.conf driver = sql } plugin { quota_rule = *:storage=262144:messages=20000 quota_rule2 = Trash:storage=282144:messages=23000 } service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } unix_listener auth-master { mode = 0600 user = vmail } user = root } service imap-login { chroot = login inet_listener imap { address = 127.0.0.1 port = 3993 } inet_listener imaps { address = * port = 993 } process_limit = 256 process_min_avail = 24 service_count = 1 vsz_limit = 48 M } service pop3-login { chroot = login process_limit = 256 process_min_avail = 24 service_count = 1 vsz_limit = 48 M } ssl = required ssl_ca = </etc/ssl/certs/xxx.combined_for_dovecot.pem ssl_cert = </etc/ssl/private/xx.xx.xx.crt ssl_cipher_list = TLSv1+HIGH:!SSLv2:RC4+MEDIUM:!aNULL:!eNULL:!3DES:@STRENGTH ssl_key = </etc/ssl/private/xx.xx.xx.key ssl_verify_client_cert = yes userdb { args = uid=5000 gid=5000 home=/var/xx/%d/%u allow_all_users=yes driver = static } userdb { args = /etc/dovecot/dovecot-mysql.conf driver = sql } valid_chroot_dirs = /var/xx protocol imap { mail_max_userip_connections = 96 mail_plugins = quota imap_quota } protocol pop3 { pop3_uidl_format = %08Xu%08Xv } protocol lda { auth_socket_path = /var/run/dovecot/auth-master log_path = mail_plugins = sieve quota postmaster_address = xxxx@xxxxx } I really don't understand how I should make this work, and the after I read the docs on dovecot.org and googled I realised I was really lost getting this back up and runing :( I should be really grateful if somebody would give me some advice. Thanks, Soph'

3 6

[Dovecot] Upgrading from 1.2.x -> 2.2.x in one step possible
by Götz Reinicke - IT Koordinator 26 Feb '14

26 Feb '14

Hi, after some off-ML discussions to and some reconsiderations, we might do the "big jump" from our current 1.2.17 to the atrpms 2.2. From googling and reading the dovecot upgrade wiki I don't see any (big) pitfalls. Basically we use the default config options, mbox, pop3s/imaps on RH EL 5. So "just" run the upgrade-config script, fingers crossed and thats it? Ii it possible to do such a big step form 1.2 to 2.2? Thanks for comments and suggestions . Götz -- Götz Reinicke IT-Koordinator Tel. +49 7141 969 82 420 E-Mail goetz.reinicke(a)filmakademie.de Filmakademie Baden-Württemberg GmbH Akademiehof 10 71638 Ludwigsburg www.filmakademie.de Eintragung Amtsgericht Stuttgart HRB 205016 Vorsitzender des Aufsichtsrats: Jürgen Walter MdL Staatssekretär im Ministerium für Wissenschaft, Forschung und Kunst Baden-Württemberg Geschäftsführer: Prof. Thomas Schadt

3 2

[Dovecot] Removing Mount Points
by Jeff Geiger 26 Feb '14

26 Feb '14

Dovecot version 2.1.7 If a dovecot mount point (drive) dies, and the data is restored into the same path that's no longer a mount point (subfolder), dovecot complains about a missing mount point. Is it safe to do a `doveadm mount remove {path}` to fix the error since it's no longer a legit mount point? Example: We were storing indexes on an SSD drive mounted at /mnt/ssd. That drive died. I was able to put everything back into the /mnt/ssd folder (no longer mounted, just a folder). Everything seems to be working as expected. But, when I just went to dsync an account from another server to this one, I got the following error: dsync(sales(a)foo.com): Error: Couldn't create index dir /mnt/ssd/indexes/6/a/ sales(a)foo.com/mailboxes: Can't create mailbox root dir /mnt/ssd/indexes/6/a/ sales(a)foo.com/mailboxes: Mountpoint /mnt/ssd isn't mounted. Mount it or remove it with doveadm mount remove Would doing a `doveadm mount remove /mnt/ssd` fix my issue, or cause some type of catastrophe? Thanks, Jeff Geiger jeff.geiger(a)firespring.com

2 1

[Dovecot] Auto-response
by Si L 26 Feb '14

26 Feb '14

Dear Sir, Thank-you for your message. I shall not be reading Yahoo Mail for quite some time. You should presume that your message remains unloved and unread. ** If you know who I am (in other words you are not a Bulk Emailer), then you already know how to contact me either on my _normal_ EMail address, or on the telephone. Yours faithfully.

1 0

Re: [Dovecot] AUTH_USER variable has invalid value in checkpassword Script
by dovecot.pkoch＠dfgh.net 26 Feb '14

26 Feb '14

answering my own questions: > This has somehow changed and now AUTH_USER always > contains the username. This has fatal consequences as no > every owner of a valid certificate can logon as any user. I now use auth_ssl_username_from_cert = yes and this temporarily fixes my problem. Now if user A authenticates with his certificate and claims to be user B he will be logged on as user A. With ssl_username_from_cert = no (default) he was logged in as User B. > I'm absolutely sure that the value of the x500UniqueIdentifier > was stored into the AUTH_USER when I tested my setup > last year. If one looks at the source code, in particular routine env_put_auth_vars() in src/auth/db-checkpassword.c and routine auth_request_get_var_expand_table() in src/auth/auth-request.c it is clear, that this has never worked. The environemnt variable AUTH_USER always contais the username (in all Dovecot versions). It dows NOT contain the Dovecot auth_user-variable. Comparing AUTH_USER with the username makes no sense in a checkpassword-script So here's my next question: How do I find out the original username from within a chackpassword script after it has been replaced by the x500UniqueIdentifier value from a client certificate? Why is request->requested_login_user == NULL in env_put_auth_vars(). request->user contains the x500UniqueIdentifier value from the clients certificate so the original username was replaced and therefore should have been moved into request->requested_login_user. Kind regards Peter Koch

1 0

[Dovecot] Oldies but Goldies - Dovecot 1.2 and Sieve
by Götz Reinicke - IT Koordinator 25 Feb '14

25 Feb '14

Hi, we still run dovecot 1.2.17 and upgrading is not planed for some time. But I'm asked to install a sieve system to be used with SOGo soon. What do I have to install / configure? Is installing/configuring the dovecot-sieve-0.1.19 and dovecot-managesieve-0.11.13 enough? We still use mostly the default settings for imaps/pop3s. And of course configure SOGo. Thanks for any feedback. Regards . Götz -- Götz Reinicke IT-Koordinator Tel. +49 7141 969 82 420 E-Mail goetz.reinicke(a)filmakademie.de Filmakademie Baden-Württemberg GmbH Akademiehof 10 71638 Ludwigsburg www.filmakademie.de Eintragung Amtsgericht Stuttgart HRB 205016 Vorsitzender des Aufsichtsrats: Jürgen Walter MdL Staatssekretär im Ministerium für Wissenschaft, Forschung und Kunst Baden-Württemberg Geschäftsführer: Prof. Thomas Schadt

4 3