- dovecot - dovecot.org

[Dovecot] nfs flush/fsync config settings problem
by Troton_admin 03 Apr '14

03 Apr '14

Hi, I need to place a maildir storage on a NFS filesystem, so I set up the config like this: mmap_disable = yes mail_nfs_storage = yes mail_nfs_index = yes mail_fsync = always lock_method = dotlock (also tried fcntl - local lockd is running, no success, now using dotlock, to be sure while debugging) The problem is that Dovecot (2.2.9/2.2.10 - the relevant code in mail-index.c is the same) logs a fatal error and quits the session (no daemon crash/coredump). Jan 07 14:13:31 auth: Debug: client in: AUTH 1 PLAIN service=pop3 session=fRCRJGHvbADDUKU9 lip=192.168.100.102 rip=IP_ADDR lport=1110 rport=48236 resp=AHRyb3RvbjEAdHJvdG9uMQ== (previous base64 data may contain sensitive data) Jan 07 14:13:31 auth: Debug: passwd-file(troton1,IP_ADDR,<fRCRJGHvbADDUKU9>): lookup: user=troton1 file=/usr/local/etc/dovecot/passwd-file Jan 07 14:13:31 auth: Debug: client passdb out: OK 1 user=troton1 Jan 07 14:13:31 auth: Debug: master in: REQUEST 1289355265 29049 1 4f9fdd9e4069fa503e8e6bcc09d4cf30 session_pid=29089 Jan 07 14:13:31 auth: Debug: passwd-file(troton1,IP_ADDR,<fRCRJGHvbADDUKU9>): lookup: user=troton1 file=/usr/local/etc/dovecot/passwd-file Jan 07 14:13:31 auth: Debug: master userdb out: USER 1289355265 troton1 uid=81 gid=81 home=/home/troton1 mail=maildir:~/Maildir Jan 07 14:13:31 pop3-login: Info: Login: user=<troton1>, method=PLAIN, rip=IP_ADDR, lip=192.168.100.102, mpid=29089, session=<fRCRJGHvbADDUKU9> Jan 07 14:13:31 pop3: Debug: Added userdb setting: mail=maildir:~/Maildir Jan 07 14:13:31 pop3(troton1): Debug: Effective uid=81, gid=81, home=/home/troton1 Jan 07 14:13:31 pop3(troton1): Debug: Namespace inbox: type=private, prefix=, sep=., inbox=yes, hidden=no, list=yes, subscriptions=yes location=maildir:~/Maildir Jan 07 14:13:31 pop3(troton1): Debug: maildir++: root=/home/troton1/Maildir, index=, indexpvt=, control=, inbox=/home/troton1/Maildir, alt= Jan 07 14:13:31 pop3(troton1): Info: DEBUG1: fsync_mode=2 , mask=0 Jan 07 14:13:31 pop3(troton1): Info: DEBUG2: fsync_mode=2 flags=85 Jan 07 14:13:31 pop3(troton1): Debug: Namespace : Using permissions from /home/troton1/Maildir: mode=0700 gid=default Jan 07 14:13:31 pop3(troton1): Info: DEBUG2: fsync_mode=0 flags=85 The user/passdb is just a plaintext file, for debugging purposes. But what is strange, the messages system log shows: Jan 7 14:13:31 mailhub2 dovecot: pop3(troton1): Fatal: nfs flush requires mail_fsync=always That is obviously wrong, even its own doveconf -n utility shows the correct value. # doveconf -n | grep -E 'sync|nfs' mail_fsync = always mail_nfs_index = yes mail_nfs_storage = yes maildir_very_dirty_syncs = yes Affected code seems to be in the lib-index/mail-index.c file, mail_index_file function - around line 585 : // my custom debug line i_info("DEBUG2: fsync_mode=%u flags=%u", (unsigned int)(index->fsync_mode),(unsigned int)flags); if ((flags & MAIL_INDEX_OPEN_FLAG_NFS_FLUSH) != 0 && index->fsync_mode != FSYNC_MODE_ALWAYS) i_fatal("nfs flush requires mail_fsync=always"); The first time it sees fsync_mode=2 (which is correct value of FSYNC_MODE_ALWAYS), but next function call is with index->fsync_mode=0 and an error is raised, see the logfile above. Dovecot correctly creates its working files in user's home directory - dovecot-uidlist, dovecot-uidvalidity, dovecot-uidvalidity.52cbfd7b, dovecot.index.log . The complete (testing, not production) doveconf -n is: == # 2.2.10: /usr/local/etc/dovecot/dovecot.conf # OS: FreeBSD 7.3-RELEASE-p3 amd64 auth_debug = yes auth_debug_passwords = yes auth_mechanisms = plain login auth_verbose = yes auth_verbose_passwords = sha1 default_process_limit = 200 disable_plaintext_auth = no first_valid_uid = 81 imap_client_workarounds = delay-newmail tb-extra-mailbox-sep info_log_path = /var/log/dovecot.log last_valid_uid = 81 listen = 192.168.100.102 lock_method = dotlock mail_debug = yes mail_fsync = always mail_gid = 81 mail_location = maildir:%h/Maildir mail_nfs_index = yes mail_nfs_storage = yes mail_prefetch_count = 5 mail_uid = 81 mailbox_list_index = yes maildir_stat_dirs = yes maildir_very_dirty_syncs = yes mmap_disable = yes namespace inbox { inbox = yes location = mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = separator = . type = private } passdb { args = scheme=plain username_format=%n /usr/local/etc/dovecot/passwd-file driver = passwd-file } plugin { mail_log_events = delete undelete expunge copy mailbox_delete mailbox_rename mail_log_fields = uid box msgid subject size } pop3_enable_last = yes pop3_save_uidl = yes protocols = imap pop3 service doveadm { inet_listener { port = 9292 } } service imap-login { inet_listener imap { port = 1143 } } service imap { process_limit = 250 } service pop3-login { inet_listener pop3 { port = 1110 } } service pop3 { process_limit = 200 } ssl = no userdb { args = username_format=%n /usr/local/etc/dovecot/passwd-file default_fields = uid=81 gid=0 home=/home/%n driver = passwd-file } protocol imap { mail_max_userip_connections = 5 } protocol pop3 { mail_max_userip_connections = 5 } == OS: 7.3-RELEASE-p3 FreeBSD 7.3-RELEASE-p3 #1 amd64 Affected Dovecot version: 2.2.9, 2.2.10 How to repeat: Anytime I enter the correct username/pass pair And I tried to place the homedir on a local disk too, and I got the same error as on NFS. Any ideas, what could possibly be wrong ? Is it a feature or a bug ? Thanks for your help. Regards, Troton

3 2

[Dovecot] how to enable debugging in imapc
by Tobias Oetiker 03 Apr '14

03 Apr '14

Hi Net, How can I enable debug messages in the imap-proxy client? Trying to figure why the imap-proxy mode does not work towards ngnix. specifically, how can i set conn->client->set.debug in ./src/lib-imap-client/imapc-connection.c cheers tobi -- Tobi Oetiker, OETIKER+PARTNER AG, Aarweg 15 CH-4600 Olten, Switzerland www.oetiker.ch tobi(a)oetiker.ch +41 62 775 9902 *** We are hiring IT staff: www.oetiker.ch/jobs ***

2 3

[Dovecot] Is replication broken?
by IT geek 31 03 Apr '14

03 Apr '14

Hi, Apologies for this being my 248th post about replication... The current error I'm getting is: Jan 30 12:10:54 Server1 dovecot: dsync-local(MailUser1): Error: dsync( Server2.test.com) read() failed: read((fd)) failed: Connection reset by peer Subsequent errors are: Jan 30 12:15:47 Server1 dovecot: dsync-local(MailUser1): Error: read( Server2.test.com) failed: EOF The above error is seen on Server1, after the initial sync completes of the first mailbox (Sent folder to be precise). Does anyone have an ideas as to what might be causing it? These are brand new rebuilds, running the latest build - I just can't seem to get this working. Bug maybe? Configs are as follows: Server1: # 2.2.10: /usr/pkg/etc/dovecot/dovecot.conf # OS: NetBSD 5.2 cobalt auth_mechanisms = plain login doveadm_password = secret doveadm_port = 12345 first_valid_uid = 1003 last_valid_uid = 1020 listen = 192.168.1.1 login_greeting = test.com mail_location = mbox:~/mail:INBOX=/var/mail/%u mail_plugins = " notify replication" passdb { driver = passwd } plugin { mail_replica = tcp:Server2.test.com } protocols = imap service aggregator { fifo_listener replication-notify-fifo { mode = 0666 } unix_listener replication-notify { mode = 0600 } } service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } user = root } service imap-login { inet_listener imap { port = 0 } } service replicator { process_min_avail = 1 unix_listener replicator-doveadm { mode = 0600 } } ssl_cert = </etc/openssl/certs/Server1.test.crt ssl_key = </etc/openssl/private/Server1.test.key userdb { driver = passwd } protocol lda { postmaster_address = postmaster(a)test.com } ServerB: # 2.2.10: /usr/pkg/etc/dovecot/dovecot.conf # OS: NetBSD 5.1 cobalt auth_mechanisms = plain login doveadm_password = secret doveadm_port = 12345 listen = 192.168.1.2 login_greeting = test.com mail_location = mbox:~/mail:INBOX=/var/mail/%u passdb { driver = passwd } protocols = imap service aggregator { fifo_listener replication-notify-fifo { mode = 0666 } unix_listener replication-notify { mode = 0600 } } service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } user = root } service doveadm { inet_listener { port = 12345 } } service imap-login { inet_listener imap { port = 0 } } service replicator { process_min_avail = 1 unix_listener replicator-doveadm { mode = 0600 } } ssl_cert = </etc/openssl/certs/Server2.test.com.crt ssl_key = </etc/openssl/private/Server2.test.com.key userdb { driver = passwd } protocol lda { postmaster_address = postmaster(a)test.com }

4 15

[Dovecot] Test outgoing email on director setup
by Murray Trainer 03 Apr '14

03 Apr '14

HI All, I have a several Exim MTA's relaying mail to a pair of director proxies via LMTP which then relayi to several mailstores via LMTP Incoming mail is working fine. My outgoing mail uses LMTP also in the reverse of above. How do I manually test outgoing mail on the mailstores and proxies as I only have dovecot and not exim installed on them? I have the following set in dovecot.conf for LMTP submission_host = mailproxy01:24 mailproxy02:24 Hopefully that works with multiple submission hosts to give redundancy? Thanks Murray

1 0

[Dovecot] Info on Config Sharing or Unfied Config?
by Jeffrey Walton 02 Apr '14

02 Apr '14

Is there a wiki page or other resource on configuration sharing between Postfix and Dovecot? Or is there a unified config file somewhere that I can use for mail components (like Postfix, Dovecot, Clam, and Spam Assassin)? I'm finding that I need to add the same information in multiple places. For example, Postfix users go in /etc/postif/vmailboxes, but Dovecot uses a user/password database stored in /var/mail/%d/%u (or other methods). And the same certificates and keys get entered multiple times. I think (or hope) there's something better, but I have not come across the resource.

2 1

Re: [Dovecot] Dovecot not honoring configuration settings (auth failure)
by Joseph Tam 02 Apr '14

02 Apr '14

Jeffrey Walton <noloader(a)gmail.com> writes: > passdb { > args = /var/mail/%d/users > driver = passwd-file > } > ... > userdb { > driver = passwd > } Your userdb and passdb are not using the same DB: did you intend this? Does the userdb have "user@domain" entries, rather than just "user" entries? The diagnostics I referred to in my last post would have been helpful here. > # postconf -n If you're having problems authenticating to the IMAP service, then you ought to concentrate on that problem: it's likely your LDA problem is dependent on that solution. Joseph Tam <jtam.home(a)gmail.com>

2 2

[Dovecot] Book on Postfix/Dovecot or Postfix/Dovecot/Clam/Spam Assassin?
by Jeffrey Walton 01 Apr '14

01 Apr '14

I'm looking for a book on Postfix/Dovecot or Postfix/Dovecot/Clam/Spam Assassin The blog posts and the mini-HowTo's I am reading lack the detail to be useful to me (due to my own ignorance). Amazon does not list any books for sale. There are some hits when searching for Dovecot, but I expect them to be one section with the quality of a blog post or mini-HowTo. (I have two books on Red Hat and Fedora administration, and the discussions don't meet the quality of a blog post). Does anyone know of a book on Postfix/Dovecot or Postfix/Dovecot/Clam/Spam Assassin? If there are no books with a structured treatment, then O'Reilly is always looking for authors: http://oreilly.com/oreilly/author/intro.csp.

3 3

[Dovecot] Dovecot not honoring configuration settings (auth failure)
by Jeffrey Walton 01 Apr '14

01 Apr '14

My dovecot.conf has the following: # No results when searching the wiki disable_plaintext_auth = no # http://wiki2.dovecot.org/Authentication/Mechanisms auth_mechanisms = plain login digest-md5 cram-md5 When I attempt to run imapsync, I receive an error: Host2: <host> says it has NO CAPABILITY for AUTHENTICATE LOGIN imapsync also dumps the helo string, and it is missing: Host2: * OK [CAPABILITY IMAP4rev1 LITERAL+ ... STARTTLS AUTH=PLAIN] Dovecot ready. I've restarted the dovecot service with 'service dovecot restart' and even rebooted the machine. There is nothing reported in any on the log files (/var/mail/dovecot.log and /var/log/mail.<level>). Any ideas why dovecot is not honoring the setting in its config file? ********** # dovecot --version 2.1.7 # doveconf -n # 2.1.7: /etc/dovecot/dovecot.conf # OS: Linux 3.2.0-4-686-pae i686 Debian 7.4 disable_plaintext_auth = no log_path = /var/log/dovecot.log mail_location = mbox:~/mail:INBOX=/var/mail/%u namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } ... prefix = } passdb { args = /var/mail/%d/users driver = passwd-file } passdb { driver = pam } plugin { sieve = ~/.dovecot.sieve sieve_dir = ~/sieve } protocols = " imap pop3" ssl_cert = </etc/dovecot/dovecot.pem ssl_key = </etc/dovecot/private/dovecot.pem userdb { driver = passwd }

5 12

Re: [Dovecot] Connection refused userdb lookup ..dovecot/auth-userdb
by Simon 01 Apr '14

01 Apr '14

On Mon, Mar 31, 2014 at 7:37 PM, Steffen Kaiser < skdovecot(a)smail.inf.fh-brs.de> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > > On Mon, 31 Mar 2014, Simon wrote: > > On 3/24/2014 7:10 PM, Simon <greminn(a)gmail.com> wrote: >>>>>> >>>>>>> Mar 13 09:55:44 vmail1 dovecot: lda: Error: userdb lookup: >>>>>>> connect(/usr/local/dovecot/var/run/dovecot/auth-userdb) >>>>>>> failed: Connection refused >>>>>>> >>>>>> > What's the output of: > > lsof -c dovecot|grep auth-userdb > > [root@vmail1 ~]# lsof -c dovecot|grep auth-userdb dovecot 3147 root 38u unix 0xffff88004fce0680 0t0 24739 /var/run/dovecot/auth-userdb

2 1

[Dovecot] Deduplicate not processing all messages - bug?
by Jiri Bourek 01 Apr '14

01 Apr '14

Hello, I'm trying to create automated backup recovery using "doveadm import" and "doveadm deduplicate". During testing I noticed that deduplicate only deletes some duplicates and has to be called multiple times to find them all. Here's what I've been trying (in shell commands): First, expunge inbox (the end result is the same even if you delete only some messages): # doveadm expunge -u test mailbox inbox all # ls /home/mailboxes/test/cur | wc -l 0 Then import data from backup - twice, so duplicates are created (again, if you don't delete all messages and call import only once, resulting behaviour is the same.) # doveadm import -u test maildir:/home/test "" mailbox INBOX # doveadm import -u test maildir:/home/test "" mailbox INBOX # ls /home/mailboxes/test/cur | wc -l 1046 Then try to deduplicate # doveadm deduplicate -u test mailbox INBOX # ls /home/mailboxes/test/cur | wc -l 1040 And again # doveadm deduplicate -u test mailbox INBOX # ls /home/mailboxes/test/cur | wc -l 1029 And so on until the message count holds on 523 Each repetition removes 10 - 30 duplicates so eventually all duplicates are removed if "doveadm deduplicate" is called enough times in a row. I also noticed that when I repeat the test, import the backup again and call deduplicate, the steps - how many messages are removed at one time - are the same. That is I start with 1046 messages in the mailbox, after first run there's 1040, then 1029 and so on. My guess would be the behaviour depends on what is stored in the mailbox, but that's pretty much all I can figure out on my own at this time. My question is - is this intended behaviour, ie. are you supposed to run doveadm deduplicate as long as the number of messages in the mailbox keeps changing? Or is it a bug? Tried to Google for the answer but no luck, so thanks for any answers. Tested on Dovecot version 2.2.9 and 2.2.12 (both from Debian repositories.)

2 1