- dovecot - dovecot.org

[Dovecot] LDA Connection Refused with auth-userdb
by Adam Ramirez 21 Jun '13

21 Jun '13

Hi there, I've encountered an issue with the LDA in which I get a "Connection refused" error. There is a serverfault question ( http://serverfault.com/questions/517262/dovecot-with-postfix-configuration-…) if you would like to read that version, otherwise, the details are as follows: Dovecot 2.0.19 Postfix 2.9.6 Ubuntu 12.04 The actual error message I receive is --------------------------------------------------------------- postfix/pickup[16842]: 019023A06AB: uid=1000 from=<vagrant> postfix/cleanup[19542]: 019023A06AB: message-id= <20130620140358.019023A06AB@mail-server-berkshelf> postfix/qmgr[16843]: 019023A06AB: from=<vagrant(a)mail-server-berkshelf.localdomain>, size=382, nrcpt=1 (queue active) dovecot: lda: Debug: Loading modules from directory: /usr/lib/dovecot/modules dovecot: lda: Debug: Module loaded: /usr/lib/dovecot/modules/lib90_sieve_plugin.so ---> dovecot: lda: Error: userdb lookup: connect(/var/run/dovecot/auth-userdb) failed: Connection refused dovecot: lda: Fatal: Internal error occurred. Refer to server log for more information. postfix/pipe[19545]: 019023A06AB: to=<test(a)chefdovecot.com>, relay=dovecot, delay=1.2, delays=0.04/0.01/0/1.1, dsn=4.3.0, status=deferred (temporary failure) dovecot -n snippet: -------------------------------------------------------------- # 2.0.19: /etc/dovecot/dovecot.conf # OS: Linux 3.2.0-23-generic x86_64 Ubuntu 12.04 LTS ext4 auth_debug = yes auth_debug_passwords = yes auth_mechanisms = plain login auth_socket_path = /var/run/dovecot/auth-userdb auth_verbose = yes auth_verbose_passwords = plain mail_debug = yes mail_location = maildir:/var/vmail/%d/%n/Maildir managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date ihave passdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } plugin { sieve = ~/.dovecot.sieve sieve_dir = ~/sieve } postmaster_address = info(a)*****.com protocols = imap pop3 sieve imap pop3 service auth-worker { user = vmail } service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } unix_listener auth-userdb { group = vmail mode = 0644 user = vmail } user = dovecot } service managesieve-login { inet_listener sieve { port = 4190 } } ssl = no ssl_cert = </etc/ssl/certs/star_***_com.crt ssl_key = </etc/ssl/private/star_***_com.key userdb { args = uid=5000 gid=5000 home=/var/vmail/%d/%n allow_all_users=yes driver = static } verbose_ssl = yes protocol lda { info_log_path = /var/log/dovecot-lda.log log_path = /var/log/dovecot-lda-errors.log mail_plugins = sieve } protocol imap { mail_max_userip_connections = 20 } Extra from auth-sql ----------------------------------------- userdb { driver = static args = uid=vmail gid=vmail home=/var/vmail/%d/%n allow_all_users=yes } File permissions on auth-userdb ----------------------------------------- srw-r--r-- 1 vmail vmail 0 Jun 20 13:04 /var/run/dovecot/auth-userdb I have tried changing the permissions and owner of auth-userdb to 777 and dovecot:dovecot, but there wasn't a change. Any leads or ideas are appreciated. I'm happy to research on my own, but atm I'm not sure where to continue looking. Adam

2 2

[Dovecot] Would attempting plaintext auth repeatably cause a DOS and server to crash?
by Hugh Davenport 21 Jun '13

21 Jun '13

Hey All, I'm just wondering whether this is what caused my server to crash. Started last night in NZ land. Jun 20 19:22:11 elm dovecot: imap-login: Disconnected (tried to use disallowed plaintext auth): user=<>, rip=attackerip, lip=10.0.0.3, session=<0C8LzpDfZQDINsQC> occasionally get Jun 20 19:22:52 elm dovecot: imap-login: Disconnected (no auth attempts in 1 secs): user=<>, rip=attackerip, lip=10.0.0.3, session=<bHdz0JDfpwDINsQC> or in 0 secs last at Jun 20 19:26:24 elm dovecot: imap-login: Disconnected (tried to use disallowed plaintext auth): user=<>, rip=attackerip, lip=10.0.0.3, session=<1MUR3ZDfcwDINsQC> and a minute later the server lost contact to the world. When I checked a bit later, the underlying host machine (dovecot runs on a VM (KVM)) had been powered off. Now, here in NZ land, there was also a crazy storm last night, and lots of brown outs. There could potentially of been a surge that killed it, but the UPS was still running fine when I started it again. The "attack" lasted around 4 minutes, in which there was 1161 lines in the log for a single attacker ip, and no other similar logs previously. Would this be enough to kill not only the VM running dovecot, but the underlying host machine? All up to date with patches, running debian stable (wheezy). dovecot-core debian package version 1:2.1.7-7 dovecot version 2.1.7 I notice there is a version 2.2.3 out, but not in debian yet. Could this fix this issue? I don't particularly want to have it happen again :D. Any thoughts? Cheers, Hugh

3 2

[Dovecot] Allowing clients to test their Sieve scripts
by Frerich Raabe 21 Jun '13

21 Jun '13

Hi, One thing which came up repeatedly is that clients using the IMAP server I run (using Dovecot 2.1) wonder whether they broke their Sieve scripts, i.e. it often goes like "I don't know whether I just didn't receive any mail, or whether my filters broke. Can you check the logs?". I then usually just run the sieve-test binary (part of the Pigeonhole distribution) and send them the output. However, I was wondering - is there maybe a way for them to try it themselves? Like, maybe a tiny web server which just prints a form asking for a mail file and a sieve script, and then it runs sieve-script and prints the output of that? I wonder how other people do that. -- Frerich Raabe - raabe(a)froglogic.com www.froglogic.com - Multi-Platform GUI Testing

9 27

[Dovecot] doveadm move syntax
by vincent truc 20 Jun '13

20 Jun '13

Hello I want to forward an email to user1(a)domain.com box to the box user2(a)domain.com For this I try to use 'doveadm move', but I'm having problems with the syntax. Could you give me an example please? thanks

2 1

[Dovecot] MySQL tables and official documenttation
by Mohsen Pahlevanzadeh 20 Jun '13

20 Jun '13

Dear all, Unfortunately, i created my tables according to the older tutorial, i search in dovecot.org and postfix.org but i didn't find any official documentation for tables. I want to use PF 2.10 and dovecot 2. Its tutorial was wrote on debian etch. eatch is very old. ---mohsen

3 2

[Dovecot] HowTo / VirtualUserFlatFilesPostfix
by treanorv 20 Jun '13

20 Jun '13

The following is an excerpt from the HOWTO mentioned Per-domain authentication and configuration structure /var/vmail dr-x------ 3 doveauth dovecot 4096 2010-03-17 19:09 auth.d |--> domain.tld Can anybody decypher the "|--> domain.tld" part please. Regards, treanorv -- View this message in context: http://dovecot.2317879.n4.nabble.com/HowTo-VirtualUserFlatFilesPostfix-tp42… Sent from the Dovecot mailing list archive at Nabble.com.

2 2

[Dovecot] dovecot enterprise release
by mourik jan SOGo 20 Jun '13

20 Jun '13

Hi all, Not sure if this is the right place to ask, but...: On the dovecot enterprise release pages, only debian 6 compatibility is shown. Are there any plans to support wheezy? (as 7 is stable now, and we are running it...) Regards, Mourik Jan

6 12

[Dovecot] pop3 and imap don't run
by Mohsen Pahlevanzadeh 20 Jun '13

20 Jun '13

Dear all, I run dovecot and when i use 'ps ax |egrep dovecot' command , i get the following result: ////////////////// 9290 pts/3 S+ 0:00 tail -f /var/log/dovecot.err 9597 ? Ss 0:00 /opt/dovecot/sbin/dovecot 9598 ? S 0:00 dovecot/anvil 9599 ? S 0:00 dovecot/log 9601 ? S 0:00 dovecot/config 9606 pts/0 S+ 0:00 egrep --color=auto dovecot /////////////// I dont see any pop or imap process. --mohsen

3 2

[Dovecot] Patch for pigeonhole 0.4.0 avoiding PATH_MAX
by Svante Signell 19 Jun '13

19 Jun '13

Hi, I recently downloaded and built dovecot-2.2.2 and dovecot-2.2-pigeonhole-0.4.0 on GNU/Linux and GNU/Hurd. The changes needed will be sent to the Debian maintainer shortly. Latest Debian release is 2.1.7-7 and dovecot-2.1-pigeonhole-0.3.1. When building dovecot-2.2.2 there were no PATH_MAX problems on GNU/Hurd, thank you for that. However, pigeonhole 0.4.0 had one remaining PATH_MAX construct. The attached patch solves this problem. It it good enough to be accepted upstream? (According to the description of t_malloc, free is not needed, right?) Thanks, Svante Signell

3 4

[Dovecot] A common, read-only IMAP INBOX for all accounts
by Gus 19 Jun '13

19 Jun '13

Hi, since I had no luck finding people available on IRC, I hope someone here can provide me with some answers to, hopefully, 2 simple questions (and have the solution recorded in the archives for everyone with the same need). A little background, as the subject says it - I want to have a single INBOX shared among all the accounts on my system, where only one account would have writing rights, and all the rest would only be able to read the messages. Note this is different than providing a shared mailbox in addition to an INBOX - I actually want the shared INBOX to be the one and only folder that users can see and read as they will not be receiving any personal mails on this system. Naturally, I would also want that each account keeps track of read/unread messages independently of others. So, this is what I came up with (showing the relevant part of configuration only): # Per-user mail root and private/shared INBOX namespace userdb { driver = static args = uid=vmail gid=vmail home=/var/vmail/users/%u } namespace { type = private separator = / prefix = location = maildir:/var/vmail/public:INDEX=~/public inbox = yes } # The ACL contents of /var/vmail/public/dovecot-acl user=admin lrwstipekx anyone lrs Now, this actually results in exactly what I want (apart from a problem I'll describe below), but I'm not sure if it's the right way to do it. So the questions: 1. I have doubts that this solution could cause problems with dot file locking or dovecot data files corruption in the /var/vmail/public mailbox/directory when multiple users access the box simultaneously (and this could be thousands of users in production). Is this a valid concern and have I gone completely wrong with this solution, or there should be no problem with locking and I can keep it this way? If this is not the way to do it, can someone advise on the proper configuration that would achieve the same result, if it's possible at all (or what are the alternatives if it can't be done). 2. For testing purposes, I used a perl script (using the Maildir::Lite module) to create a test message in this mailbox (it gets stored in the new/ subdirectory, as I suppose it should). Now this message shows up as "unread" for all accounts, however when I read it in an IMAP client and then refresh the mailbox, it shows up as unread again. Per-user INDEX directory is writable and I see some files created there by dovecot, so shouldn't they contain the \Seen flags that indicate the message has been read? Is this maybe a client problem and how can I check that dovecot actually saves the flag correctly? The dovecot version I'm using is 2.0.9 (from the CentOS 6.x repositories). Thanks in advance and kind regards, Tin

2 2