- dovecot - dovecot.org

duplicate Mails with dsync replication
by Dennis Kuhn 05 Jul '16

05 Jul '16

Hi! We have some strange replication issues. Some mails are duplicated when expunged. This bug is quite hard to reproduce, it just happens occasionally. It seems somehow related to sieve. When i deleted the sieve script i could not reproduce this behavior. Here are some logs, mjm-100010(a)mydomain.com is an alias for mjm(a)mydomain.com: # Master Jun 23 00:51:41 dobby4 dovecot: lmtp(mjm-100010(a)mydomain.com): copy from <lmtp DATA>: box=INBOX, uid=7816, msgid=<20160623005132EE517444BB$3A04DF25DD@ABRAHAM>, size=8933 Jun 23 00:51:41 dobby4 dovecot: lmtp(mjm-100010(a)mydomain.com): 4N23HaMVa1fpmQEAJEBNLA: sieve: msgid=<20160623005132EE517444BB$3A04DF25DD@ABRAHAM>: stored mail into mailbox 'INBOX' Jun 23 04:52:57 dobby4 dovecot: pop3(mjm(a)mydomain.com): expunge: box=INBOX, uid=7816, msgid=<20160623005132EE517444BB$3A04DF25DD@ABRAHAM>, size=8933 Jun 23 04:52:57 dobby4 dovecot: dsync-local(mjm(a)mydomain.com): save: box=INBOX, uid=7817, msgid=<20160623005132EE517444BB$3A04DF25DD@ABRAHAM>, size=8933 Jun 23 04:55:21 dobby4 dovecot: pop3(mjm(a)mydomain.com): expunge: box=INBOX, uid=7817, msgid=<20160623005132EE517444BB$3A04DF25DD@ABRAHAM>, size=8933 # Replica Jun 23 00:51:42 dobby5 dovecot: dsync-server(mjm-100010(a)mydomain.com): save: box=INBOX, uid=7816, msgid=<20160623005132EE517444BB$3A04DF25DD@ABRAHAM>, size=8933 Jun 23 04:52:57 dobby5 dovecot: dsync-server(mjm(a)mydomain.com): copy from INBOX: box=INBOX, uid=7817, msgid=<20160623005132EE517444BB$3A04DF25DD@ABRAHAM>, size=8933 Jun 23 04:52:57 dobby5 dovecot: dsync-server(mjm(a)mydomain.com): expunge: box=INBOX, uid=7816, msgid=<20160623005132EE517444BB$3A04DF25DD@ABRAHAM>, size=8933 Jun 23 04:55:22 dobby5 dovecot: dsync-server(mjm(a)mydomain.com): expunge: box=INBOX, uid=7817, msgid=<20160623005132EE517444BB$3A04DF25DD@ABRAHAM>, size=8933 The problem is the "dsync-server(mjm(a)mydomain.com): copy from INBOX: box=INBOX, uid=7817" on dobby5 at 04:52:57. This creates a new uid 7817 and the new mail is replicated back to dobby4. But i have no idea what triggers this copy. Any ideas? The dovecot version is 2.2.24. Thanks Dennis

1 0

many imap connections issue
by Бауыржан Сахариев 05 Jul '16

05 Jul '16

I'm using dovecot 2.1.7 I'm trying to connect to dovecot by imap via Java mail api. My approach described here <http://stackoverflow.com/questions/37991025/why-iterating-over-all-java-mai…>. Bill Shannon, author of the Java Mail api recommended me to check carefully my server side (I have dovecot at server side). Actually, imap login in loop works but very slow. Each store.connect(login,password) takes about 1 minute. I tried to increase mail_max_userip_connections client_limit and process limit but it didn't help. My dovecot sometimes performs query, sometimes not! My logs: Jul 04 18:23:25 auth: Error: pgsql: Query failed, aborting: SELECT email, 'maildir:/home/mailboxes/maildir/'||maildir as mail,'/home/mailboxes/home/'||maildir as home, 500 as uid, 500 as gid FROM users WHERE email = 'test(a)test.domain.com' Jul 04 18:23:25 auth: Error: sql(test(a)test.domain.com,127.0.0.1,<HGiPY842jgB/AAAB>): User query failed: ERROR: permission denied for relation users My user and password queries: password_query = SELECT email as user, password FROM users WHERE email = '%u' user_query = SELECT email as user, 'maildir:/home/mailboxes/maildir/'||maildir as mail, '/home/mailboxes/home/'||maildir as home, 500 as uid, 500 as gid FROM users WHERE email = '%u' My master conf *Please note, that I'm using same uid!* service imap-login { inet_listener imap { #port = 143 } inet_listener imaps { #port = 993 #ssl = yes } # Number of connections to handle before starting a new process. Typically # the only useful values are 0 (unlimited) or 1. 1 is more secure, but 0 # is faster. <doc/wiki/LoginProcess.txt> #service_count = 1 # Number of processes to always keep waiting for more connections. #process_min_avail = 0 # If you set service_count=0, you probably need to grow this. #vsz_limit = $default_vsz_limit } service imap { # Most of the memory goes to mmap()ing files. You may need to increase this # limit if you have huge mailboxes. #vsz_limit = $default_vsz_limit # Max. number of IMAP processes (connections) #process_limit = 1024 } service auth { unix_listener auth-userdb { #mode = 0666 #user = #group = } # Postfix smtp-auth #unix_listener /var/spool/postfix/private/auth { # mode = 0666 #} # Auth process is run as this user. #user = $default_internal_user } service auth-worker { # Auth worker process is run as root by default, so that it can access # /etc/shadow. If this isn't necessary, the user should be changed to # $default_internal_user. #user = root } I'm sure that long login *reason is poor dovecot config* but some things are not clear to me and I can't improve it. 1. Which service are being used when Java connects to dovecot? imap-login,imap or auth? My assumption - imap-login. Imap user for dealing with folders *after* login, auth is for delivery (my assotioations here are postfix,lmtp,lda) =) Is my assumptions about imap-login and other services correct? 2. Which user are being used when I login? One that specified in connection code(one of 50K users in loop) or uid(500) user? I suggested that only one user and increased mail_max_userip_connections is it correct? 3. May some troubles in connection (which I showed above) caused by mode(0660) bad config in master.cf services? 4. Almost each loop iteration connects to dovecot in 60 seconds and rarely connects in a few milliseconds. Is that fact somehow connected with deafult_idle_kill which equlas to 1 mins?

1 0

v2.2.25 released
by Timo Sirainen 04 Jul '16

04 Jul '16

http://dovecot.org/releases/2.2/dovecot-2.2.25.tar.gz http://dovecot.org/releases/2.2/dovecot-2.2.25.tar.gz.sig Some minor fixes and (mainly logging) improvements since rc1. * lmtp: Start tracking lmtp_user_concurrency_limit and reject already at RCPT TO stage. This avoids MTA unnecessarily completing DATA only to get an error. * doveadm: Previously only mail settings were read from protocol doveadm { .. } section. Now all settings are. + quota: Added quota_over_flag_lazy_check setting. It avoids checking quota_over_flag always at startup. Instead it's checked only when quota is being read for some other purpose. + auth: Added a new auth policy service: http://wiki2.dovecot.org/Authentication/Policy + auth: Added PBKDF2 password scheme + auth: Added %{auth_user}, %{auth_username} and %{auth_domain} + auth: Added ":remove" suffix to extra field names to remove them. + auth: Added "delay_until=<timestamp>[+<max random secs>]" passdb extra field. The auth will wait until <timestamp> and optionally some randomness and then return success. + dict proxy: Added idle_msecs=<n> parameter. Support async operations. + Performance improvements for handling large mailboxes. + Added lib-dcrypt API for providing cryptographic functions. + Added "doveadm mailbox update" command + imap commands' output now includes timing spent on the "syncing" stage if it's larger than 0. + cassandra: Added metrics=<path> to connect setting to output internal statistics in JSON format every second to <path>. + doveadm mailbox delete: Added -e parameter to delete only empty mailboxes. Added --unsafe option to quickly delete a mailbox, bypassing lazy_expunge and quota plugins. + doveadm user & auth cache flush are now available via doveadm-server. + doveadm service stop <services> will stop specified services while leaving the rest of Dovecot running. + quota optimization: Avoid reading mail sizes for backends which don't need them (count, fs, dirsize) + Added mailbox { autoexpunge_max_mails=<n> } setting. + Added welcome plugin: http://wiki2.dovecot.org/Plugins/Welcome + fts: Added fts_autoindex_exclude setting. - v2.2.24's MIME parser was assert-crashing on mails having truncated MIME headers. - auth: With multiple userdbs the final success/failure result wasn't always correct. The last userdb's result was always used. - doveadm backup was sometimes deleting entire mailboxes unnecessarily. - doveadm: Command -parameters weren't being sent to doveadm-server. - If dovecot.index read failed e.g. because mmap() reached VSZ limit, an empty index could have been opened instead, corrupting the mailbox state. - imapc: Fixed EXPUNGE handling when imapc_features didn't have modseq. - lazy-expunge: Fixed a crash when copying failed. Various other fixes. - fts-lucene: Fixed crash on index rescan. - auth_stats=yes produced broken output - dict-ldap: Various fixes - dict-sql: NULL values crashed. Now they're treated as "not found".

6 8

Shared mailboxes not showing up in shared namespace
by Marti Markov 03 Jul '16

03 Jul '16

Hi, I think I have configured everything correctly but for some reason I can’t get a list of the shared mailboxes to show up. When I run: doveadm acl debug -u m.markov Shared/d.marteva/INBOX doveadm(root): Debug: Skipping module doveadm_fts_plugin, because dlopen() failed: /usr/lib/dovecot/modules/doveadm/lib20_doveadm_fts_plugin.so: undefined symbol: fts_backend_rescan (this is usually intentional, so just ignore this message) doveadm(m.markov): Debug: Added userdb setting: plugin/=yes doveadm(m.markov): Debug: Effective uid=1000, gid=1000, home=/home/vmail/domain.com/m.markov doveadm(m.markov): Debug: Namespace inbox: type=private, prefix=, sep=/, inbox=yes, hidden=no, list=yes, subscriptions=yes location=maildir:~/Maildir doveadm(m.markov): Debug: maildir++: root=/home/vmail/domain.com/m.markov/Maildir, index=, indexpvt=, control=, inbox=/home/vmail/domain.com/m.markov/Maildir, alt= doveadm(m.markov): Debug: acl: initializing backend with data: vfile doveadm(m.markov): Debug: acl: acl username = m.markov(a)domain.com doveadm(m.markov): Debug: acl: owner = 1 doveadm(m.markov): Debug: acl vfile: Global ACLs disabled [ Read 8 lines ] doveadm(m.markov): Debug: Namespace : type=public, prefix=Public/, sep=/, inbox=no, hidden=no, list=yes, subscriptions=yes location=maildir:/home/vmail/Public:INDEXPVT=~/Maildir/Publics doveadm(m.markov): Debug: maildir++: root=/home/vmail/Public, index=, indexpvt=/home/vmail/domain.com/m.markov/Maildir/Public, control=, inbox=, alt=ext ^T To Spell doveadm(m.markov): Debug: acl: initializing backend with data: vfile doveadm(m.markov): Debug: acl: acl username = m.markov(a)domain.com doveadm(m.markov): Debug: acl: owner = 0 doveadm(m.markov): Debug: acl vfile: Global ACLs disabled doveadm(m.markov): Debug: Namespace : type=shared, prefix=Shared/%u/, sep=/, inbox=no, hidden=no, list=yes, subscriptions=yes location=maildir:/home/vmail/domain.com/%u/Maildir:INDEXPVT=~/Maildir/share… doveadm(m.markov): Debug: shared: root=/var/run/dovecot, index=, indexpvt=, control=, inbox=, alt= doveadm(m.markov): Debug: acl: initializing backend with data: vfile doveadm(m.markov): Debug: acl: acl username = m.markov(a)domain.com doveadm(m.markov): Debug: acl: owner = 0 doveadm(m.markov): Debug: acl vfile: Global ACLs disabled doveadm(m.markov): Debug: maildir++: root=/home/vmail/domain.com/d.marteva/Maildir, index=, indexpvt=/home/vmail//d.marteva/Maildir/shared/d.marteva, control=, inbox=/home/vmail/domain.com/d.marteva/Maildir, alt= doveadm(m.markov): Debug: acl: initializing backend with data: vfile doveadm(m.markov): Debug: acl: acl username = d.marteva doveadm(m.markov): Debug: acl: owner = 1 doveadm(m.markov): Debug: acl vfile: Global ACLs disabled doveadm(m.markov): Debug: maildir++: root=/home/vmail/domain.com/d.marteva/Maildir, index=, indexpvt=/home/vmail/domain.com/m.markov/Maildir/shared/d.marteva, control=, inbox=/home/vmail/domain.com/d.marteva/Maildir, alt= doveadm(m.markov): Debug: acl: initializing backend with data: vfile doveadm(m.markov): Debug: acl: acl username = m.markov(a)domain.com doveadm(m.markov): Debug: acl: owner = 0 doveadm(m.markov): Debug: acl vfile: Global ACLs disabled doveadm(m.markov): Info: Mailbox 'INBOX' is in namespace 'Shared/d.marteva/' doveadm(m.markov): Info: Mailbox path: /home/vmail/domain.com/d.marteva/Maildir doveadm(m.markov): Info: Per-user private flags in mailbox: \Seen doveadm(m.markov): Debug: acl vfile: reading file /home/vmail/domain.com/d.marteva/Maildir/dovecot-acl doveadm(m.markov): Info: User m.markov(a)domain.com has rights: lookup read write create doveadm(m.markov): Info: Mailbox found from dovecot-acl-list doveadm(m.markov): Info: User d.marteva found from ACL shared dict doveadm(m.markov): Info: Mailbox Shared/d.marteva/INBOX is visible in LIST Here is how I have defined the namespace: namespace { type = shared separator = / prefix = Shared/%%u/ # a) Per-user seen flags. Maildir indexes are shared. (INDEXPVT requires v2.2+) location = maildir:/home/vmail/domain.com/%%u/Maildir:INDEXPVT=~/Maildir/shared/%%u # b) Per-user seen flags. Maildir indexes are not shared. If users have direct filesystem level access to their mails, this is a safer option: #location = maildir:%%h/Maildir:INDEX=~/Maildir/shared/%%u:INDEXPVT=~/Maildir/shared/%%u subscriptions = yes # list = children list=yes } And here is the ACL config: plugin { #acl = vfile:/etc/dovecot/global-acls:cache_secs=300 acl = vfile } # To let users LIST mailboxes shared by other users, Dovecot needs a # shared mailbox dictionary. For example: plugin { #acl_shared_dict = file:/var/lib/dovecot/shared-mailboxes acl_shared_dict = file:/home/vmail/domain.com/shared-mailboxes2 #acl_lookup_dict = file:/home/vmail/domain.com/shared-mailboxes } Any suggestions?

3 7

RE: quota-status service
by Michael Fox 03 Jul '16

03 Jul '16

??? From: Michael Fox [mailto:news@mefox.org] Sent: Thursday, June 30, 2016 1:59 PM To: Dovecot Mailing List (dovecot(a)dovecot.org) <dovecot(a)dovecot.org> Subject: quota-status service I'm trying to understand the quota-status service, but I can't find complete documentation. The quota-status service is mentioned here: http://wiki.dovecot.org/Quota And an example configuration is shown: service quota-status { executable = quota-status -p postfix inet_listener { port = 12340 # You can choose any port you want } client_limit = 1 } But I can't find any information on quota-status. "man quota-status" returns nothing. I am unable to find a "quota-status" file on my machine. Where is the executable located? What does the "-p postfix" option do? Are there any other command line options? The above wiki page shows three quota_status_* options in use: quota_status_success = DUNNO quota_status_nouser = DUNNO quota_status_overquota = "552 5.2.2 Mailbox is full" Where are their meanings documented? What are the allowed values? Are there other quota_status_* options? Thanks in advance. Thanks, Michael

2 3

Re: FW: quota-status service
by Aki Tuomi 03 Jul '16

03 Jul '16

If you need fast and timely support you can contact OX sales for an support agreement . It is somewhat impolite to except such from a public mailing list over weekend. ---Aki TuomiDovecot oy -------- Original message --------From: Michael Fox <news(a)mefox.org> Date: 03/07/2016 09:00 (GMT+02:00) To: Dovecot Mailing List <dovecot(a)dovecot.org> Subject: FW: quota-status service ??? 3rd request -----Original Message----- From: dovecot [mailto:dovecot-bounces@dovecot.org] On Behalf Of Michael Fox Sent: Friday, July 1, 2016 5:56 PM To: Dovecot Mailing List <dovecot(a)dovecot.org> Subject: RE: quota-status service ??? From: Michael Fox [mailto:news@mefox.org] Sent: Thursday, June 30, 2016 1:59 PM To: Dovecot Mailing List (dovecot(a)dovecot.org) <dovecot(a)dovecot.org> Subject: quota-status service I'm trying to understand the quota-status service, but I can't find complete documentation. The quota-status service is mentioned here: http://wiki.dovecot.org/Quota And an example configuration is shown: service quota-status { executable = quota-status -p postfix inet_listener { port = 12340 # You can choose any port you want } client_limit = 1 } But I can't find any information on quota-status. "man quota-status" returns nothing. I am unable to find a "quota-status" file on my machine. Where is the executable located? What does the "-p postfix" option do? Are there any other command line options? The above wiki page shows three quota_status_* options in use: quota_status_success = DUNNO quota_status_nouser = DUNNO quota_status_overquota = "552 5.2.2 Mailbox is full" Where are their meanings documented? What are the allowed values? Are there other quota_status_* options? Thanks in advance. Thanks, Michael

4 4

Error on upgrade to 2.2.25 from 2.2.24
by Goetz R Schultz 01 Jul '16

01 Jul '16

Hi, I have compiled the latest version with those flags: ./configure --with-pgsql --with-sql under FreeBSD/amd64. This worked fine with the previous version. Compilation also works without errors. Yet when I start DC I get this error: Jul 1 22:48:55 section31 dovecot: master: Dovecot v2.2.25 () starting up for imap Jul 1 22:48:55 section31 dovecot: master: Panic: kevent(EV_ADD, READ, 55) failed: Bad file descriptor This does not hapen with the previous version. I could not find any change note that would point in that direction. Any clues? Did I miss something to set? -- Thanks and regards Goetz "I intend to live forever - so far, so good." =============================================== /"\ Get the rootcertificate at www.cacert.org \ / ASCII Ribbon Campaign against HTML e-mail X / \ Verify the cert @ CaCert.Com =============================================== "Si forte in alienas manus oberraverit hec peregrina epistola incertis ventis dimissa, sed Deo commendata, precamur ut ei reddatur cui soli destinata, nec preripiat quisquam non sibi parata."

1 0

Re: Looking for GSSAPI config [was: Looking for NTLM config example]
by Mark Foley 01 Jul '16

01 Jul '16

Aki - made your suggested changes, but no joy :( My /etc/krb5.conf: ------SNIP-------- [libdefaults] default_realm = HPRS.LOCAL dns_lookup_realm = false dns_lookup_kdc = true [libdefaults] default_realm = HPRS.LOCAL dns_lookup_kdc = true kdc_timesync = 1 ccache_type = 4 forwardable = true proxiable = true fcc-mit-ticketflags = true [realms] HPRS.LOCAL = { default_domain = hprs.local auth_to_local_names = { Administrator = root } } [domain_realm] hprs.local = HPRS.LOCAL # this is not a mistake .hprs.local = HPRS.LOCAL ------PINS----------- you wrote: > You can remove the krb4_ stuff I've remove krb4_ stuff from the [libdefaults] and eliminated the [login] section altogether. Question on [realms]Administrator: should that really be root or should it be my AD Administrator? my doveconf -n is exactly the same as posted below, but in particular: auth_krb5_keytab = /etc/krb5.keytab auth_mechanisms = plain login gssapi When I reloaded dovecot no mail was delivered to anyone (even though everyone was still using plain/ssl, no one yet configured for gssapi). In /var/log/maillog I got (repeatedly): Jun 28 09:43:36 mail dovecot: imap-login: Warning: Auth process not responding, delayed sending initial response (greeting): user=<>, rip=192.168.0.54, lip=192.168.0.2, session=<Jy/e0lY2WADAqAA2> Jun 28 09:43:37 mail dovecot: auth: Fatal: Unknown authentication mechanism 'gssapi' Jun 28 09:43:37 mail dovecot: master: Error: service(auth): command startup failed, throttling for 60 secs Jun 28 09:43:37 mail dovecot: imap-login: Warning: Auth process not responding, delayed sending initial response (greeting): user=<>, rip=166.170.27.161, lip=98.102.63.107, TLS, session=</GXn0lY22wCmqhuh> This looks pretty bad right off. Why "Unknown authentication mechanism 'gssapi'"? Do you have any idea from the configs I've posted? I'm rather depressed about this. I thought I'd finally able to get AD authentication going for Dovecot. Not ready to give up though! Suggestions? THX -- Mark -----original Message----- > Subject: Re: Looking for GSSAPI config [was: Looking for NTLM config example] > To: dovecot(a)dovecot.org > From: Aki Tuomi <aki.tuomi(a)dovecot.fi> > Date: Tue, 28 Jun 2016 15:13:11 +0300 > > On 28.06.2016 09:27, Mark Foley wrote: > > Aki, > > > > To review your 5 points: > > > > On Mon, 27 Jun 2016 09:18:54 +0300 Aki Tuomi <aki.tuomi(a)dovecot.fi> wrote: > > > >> 1. Functional AD or Kerberos environment > >> 2. Time synced against your KDC (which is your Domain Controller on Windows) > >> 3. /etc/krb5.conf configured > >> 4. Both forward / reverse DNS names correct for clients and servers. > >> Reverse is only mandatory for servers, but having them right will work > >> wonders. Most kerberos problems are about DNS problems. > >> 5. You need a keytab. This keytab needs to hold entries like > >> IMAP/your.host.name@REALM and IMAP/$HOSTNAME@REALM. You can generate > >> these on any Windows DC server (at least). > > I believe I am good on 1,2 and 4. I downloaded and installed kerberos and tested it with kinit > > and klist according to the instructions at > > https://wiki.samba.org/index.php/Setup_a_Samba_Active_Directory_Domain_Cont… > > > > As to the the keytab (#5) I did the following: > > > > $ samba-tool domain exportkeytab /etc/krb5.keytab > > > > which created the file. I made this owned and readable by group dovecot, per instructions at > > http://wiki2.dovecot.org/Authentication/Kerberos. Running `klist -k /etc/krb5.keytab` shows me > > configuration listing all the users and computers in the domain, mostly in triplicate. A > > partial list: > > > > Keytab name: FILE:/etc/krb5.keytab > > KVNO Principal > > ---- -------------------------------------------------------------------------- > > 18 COMMON$(a)HPRS.LOCAL > > 18 COMMON$(a)HPRS.LOCAL > > 18 COMMON$(a)HPRS.LOCAL > > 1 MAIL$(a)HPRS.LOCAL > > 1 MAIL$(a)HPRS.LOCAL > > 1 MAIL$(a)HPRS.LOCAL > > 1 charmaine(a)HPRS.LOCAL > > 1 charmaine(a)HPRS.LOCAL > > 1 charmaine(a)HPRS.LOCAL > > > > where COMMON and MAIL are hosts and charmaine is a user. I don't really understand the listing, > > but am assuming it is OK. > > Strange that you do not have any host/ entries. Maybe it works without. > > >> setspn -q is helpful here, also setspn command in general. > > I have no such command in my system. Is that a Windows thing? > > > > Yes, but you can do those kind of things in Samba too. > > > As to the /etc/krb5.conf, the default one generated by samba is: > > > > [libdefaults] > > default_realm = HPRS.LOCAL > > dns_lookup_realm = false > > dns_lookup_kdc = true > > > > I'd like to modify that to your suggestions, but I need more help. You have (with my questions): > > > >> Here is a *SAMPLE* configuration: > >> > >> [libdefaults] > >> default_realm = YOUR.REALM > >> dns_lookup_kdc = true > >> krb4_config = /etc/krb.conf > >> krb4_realms = /etc/krb.realms > > Here, you have krb4_*. Do you mean that? My config file is krb5.conf. Should I rather have: > > You can remove the krb4_ stuff > > > krb5_config = /etc/krb5.conf > > > > Also, I have no /etc/krb*.realms file. Do I need this? If so, what should be in there? > You don't necessarely require that. > > >> kdc_timesync = 1 > >> ccache_type = 4 > >> forwardable = true > >> proxiable = true > >> fcc-mit-ticketflags = true > >> > >> [realms] > >> YOUR.REALM = { > >> default_domain = your.domain.name > >> auth_to_local_names = { > >> Administrator = root > >> } > >> } > > I suppose my "YOUR.REALM" is HPRS.LOCAL, right? Is my "your.domain.name" my FQDN for my AD > > server: mail.hprs.local, or is it just hprs.local? (or something else!) > > HPRS.LOCAL is your REALM, hprs.local is your domain name. > > > >> [domain_realm] > >> your.domain.name = YOUR.REALM > >> # this is not a mistake > >> .your.domain.name = YOUR.REALM > >> [login] > >> krb4_convert = true > >> krb4_get_tickets = false > > Likewise here a question on the whole krb4 versus krb5 thing. > > > > Your closing comment: > > > >> Also, note that kerberos can only act as AUTHENTICATION system. It > >> cannot act as USER DATABASE. For that you need to configure LDAP or > >> something else. With Active Directory LDAP is probably a damn good idea. > > I have the following doveconf -n: > > > > # 2.2.15: /usr/local/etc/dovecot/dovecot.conf > > # OS: Linux 3.10.17 x86_64 Slackware 14.1 > > auth_debug_passwords = yes > > auth_krb5_keytab = /etc/krb5.keytab > > auth_mechanisms = plain login gssapi > > auth_verbose = yes > > auth_verbose_passwords = plain > > disable_plaintext_auth = no > > info_log_path = /var/log/dovecot_info > > mail_location = maildir:~/Maildir > > passdb { > > driver = shadow > > } > > protocols = imap > > ssl_cert = </etc/ssl/certs/OHPRS/GoDaddy/Apache/2015-08-14/57aa6ed6ae98b4c7.crt > > ssl_key = </etc/ssl/certs/OHPRS/GoDaddy/mail.ohprs.org.key > > userdb { > > driver = passwd > > } > > verbose_ssl = yes > > > > I assume the passwd driver for the userdb is OK? Seems to me it should work with gssapi, but in > > any case I still have all but this test workstation NOT using gssapi, so I still need to > > accomodate them. > > > > Thanks, --Mark > passwd driver is fine, yes, if you ensure that users can be found. > > Aki >

5 12

Suggestions? Moving maildir to new storage and may be switch to mdbox
by Götz Reinicke - IT Koordinator 01 Jul '16

01 Jul '16

Hi, we got a new storage for our mails and now we think about the best way to use it. Currently about 1TB is stored in maildirs, some mail has been moved to client side local storage temporarily to get space on the old storage. I think of different options, some downtime in mind: a) stay with maildir and just rsync/move all mail to the new storage, mount the new storage at the old mountpoint (or may be new mountpoint and edit the dovecot config). b) "dsync backup" users maildir to mdboxes at a temp mountpoint and change the dovecot config afterwords. c) your suggestions or best practice Thanks for feedback . Götz

1 0

v2.2.25 release candidate released
by Timo Sirainen 01 Jul '16

01 Jul '16

http://dovecot.org/releases/2.2/rc/dovecot-2.2.25.rc1.tar.gz http://dovecot.org/releases/2.2/rc/dovecot-2.2.25.rc1.tar.gz.sig Quite a lot of changes. Please test out before the final v2.2.25 release, which I'm planning for tomorrow. Especially the new lib-dcrypt might have compiling problems with some OpenSSL versions. * lmtp: Start tracking lmtp_user_concurrency_limit and reject already at RCPT TO stage. This avoids MTA unnecessarily completing DATA only to get an error. * doveadm: Previously only mail settings were read from protocol doveadm { .. } section. Now all settings are. + quota: Added quota_over_flag_lazy_check setting. It avoids checking quota_over_flag always at startup. Instead it's checked only when quota is being read for some other purpose. + auth: Added a new auth policy service: http://wiki2.dovecot.org/Authentication/Policy + auth: Added PBKDF2 password scheme + auth: Added %{auth_user}, %{auth_username} and %{auth_domain} + auth: Added ":remove" suffix to extra field names to remove them. + auth: Added "delay_until=<timestamp>[+<max random secs>]" passdb extra field. The auth will wait until <timestamp> and optionally some randomness and then return success. + dict proxy: Added idle_msecs=<n> parameter. Support async operations. + Performance improvements for handling large mailboxes. + Added lib-dcrypt API for providing cryptographic functions. + Added "doveadm mailbox update" command + imap commands' output now includes timing spent on the "syncing" stage if it's larger than 0. + cassandra: Added metrics=<path> to connect setting to output internal statistics in JSON format every second to <path>. + doveadm mailbox delete: Added -e parameter to delete only empty mailboxes. Added --unsafe option to quickly delete a mailbox, bypassing lazy_expunge and quota plugins. + doveadm user & auth cache flush are now available via doveadm-server. + doveadm service stop <services> will stop specified services while leaving the rest of Dovecot running. + quota optimization: Avoid reading mail sizes for backends which don't need them (count, fs, dirsize) + Added mailbox { autoexpunge_max_mails=<n> } setting. + Added welcome plugin: http://wiki2.dovecot.org/Plugins/Welcome + fts: Added fts_autoindex_exclude setting. - v2.2.24's MIME parser was assert-crashing on mails having truncated MIME headers. - auth: With multiple userdbs the final success/failure result wasn't always correct. The last userdb's result was always used. - doveadm backup was sometimes deleting entire mailboxes unnecessarily. - doveadm: Command -parameters weren't being sent to doveadm-server. - If dovecot.index read failed e.g. because mmap() reached VSZ limit, an empty index could have been opened instead, corrupting the mailbox state. - imapc: Fixed EXPUNGE handling when imapc_features didn't have modseq. - lazy-expunge: Fixed a crash when copying failed. Various other fixes. - fts-lucene: Fixed crash on index rescan. - auth_stats=yes produced broken output - dict-ldap: Various fixes - dict-sql: NULL values crashed. Now they're treated as "not found".

6 9