- dovecot - dovecot.org

[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

[Dovecot] [Bug] doveadm pw Fatal: open(/etc/dovecot/dovecot.conf) failed: Permission denied
by Dwain Blazej 01 Apr '14

01 Apr '14

dovecot --version => 2.1.7 When I as a normal user the command: doveadm pw -s sha512-crypt -p example_password the command exit with return code 89 and the message doveconf: Fatal: open(/etc/dovecot/dovecot.conf) failed: Permission denied If I make Dovecot's configuration files world readable the error goes away. Please remove configuration file dependencies from "doveadm pw".

4 4

[Dovecot] Specifying passwd-file with virtual domains?
by Jeffrey Walton 01 Apr '14

01 Apr '14

I'm trying to use virtual domains and I'm suffering a disconnect. I have two domains - foo.com and bar.com. On the filesystem, they are located at /var/mail/foo.com/ and /var/mail/bar.com/. Users are located at /var/mail/foo.com/john/, /var/mail/bar.com/jane/, etc. There are two password files with <user>:<scheme><password> entries. The scheme is {PLAIN}. They are located at /var/mail/foo.com/users and /var/mail/bar.com/users. According to the wiki, these are passwd-file databases (http://wiki2.dovecot.org/AuthDatabase/PasswdFile) I specified the following in my dovecot.conf. passdb { args = /var/mail/%d/users driver = passwd-file } Attempts to use the configuration result in an authentication failure. Here's an entry from dovecot.log when the failure happens: Mar 31 16:04:12 imap-login: Info: Disconnected (auth failed, 1 attempts in 5 secs): user=<jeff(a)foo.com>, method=PLAIN, rip=127.0.0.1, lip=127.0.1.1, secured, session=<n5/ajez1FgB/AAAB> What exactly goes where to have Dovecot use the 'users' files to authenticate users? Thanks in advance and my apologies for the question. Two days of blog posts, mini-HowTo's and mailing lists has only help me discover ways to do things incorrectly. ********** # 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 login_trusted_networks = 127.0.0.1 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 }

2 1

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

01 Apr '14

Jeffrey Walton <noloader(a)gmail.com> writes: > I specified the following in my dovecot.conf. > > passdb { > args = /var/mail/%d/users > driver = passwd-file > } > > Attempts to use the configuration result in an authentication failure. > Here's an entry from dovecot.log when the failure happens: > > Mar 31 16:04:12 imap-login: Info: Disconnected (auth failed, 1 > attempts in 5 secs): user=<jeff(a)foo.com>, method=PLAIN, rip=127.0.0.1, > lip=127.0.1.1, secured, session=<n5/ajez1FgB/AAAB> Just to confirm, your <user> specified in the passdb corresponds to what is being authenticated (i.e. client is authenticating as "jeff(a)foo.com", not "jeff")? Otherwise, you'll need to add domains to your passdb, or configure "username_format=%n" Joseph Tam <jtam.home(a)gmail.com>

2 2