- dovecot - dovecot.org

[Dovecot] stopping dictionary attacks (pop3)
by other＠ahhyes.net 05 Sep '13

05 Sep '13

Hi Guys, I was really hoping a couple of years later this would be addressed... I'm running Dovecot 2.2.5 on FreeBSD. Is there anyway to limit the number of auth attempts allowed in a single session? The reason for this is because I have "fail2ban" setup to firewall out any IP addresses that repeatedly auth fails. The issue occurs when the connection is already in an "established" state and the attacker uses the existing session to hammer away, fail2ban becomes ineffective as dovecot appears to allow the person to attempt authentication ad infinitum. It would be nice if there was config option that would for example cause the software to close the connection after X failed attempts. I use "pf" as the firewall on FreeBSD. Unless there was some command I could have fail2ban run a command that would destroy any tcp sessions in an established state prior to adding the offending IP to the block list, that would be the only way around the problem. Ideally it would be nice for dovecot have an option to control the number of failed auth attempts. Any suggestions? Cheers, Alex.

2 3

[Dovecot] Received header only showing localhost
by Matt Devaney 05 Sep '13

05 Sep '13

Hi all, Im a new dovecot user and a first-time poster so please forgive me if this is a stupid question, or even (as I suspect it might be) not really a Dovecot question. My system is the fairly typical mix of postfix, amavis-new, and Dovecot. For some reason Ive noticed that when I look at the mail headers for delivered messages the Received header is missing the detail of any external servers that the mail went through, and additionally the tag appears twice; for example the Welcome to the dovecot mailing list email has: Received: from localhost (localhost [127.0.0.1]) by droplet.the-wyvern.net (Postfix) with ESMTP id DDDD163F73 for <myname(a)mydomain.net>; Mon, 26 Aug 2013 16:40:19 +0000 (UTC) Received: from droplet.the-wyvern.net ([127.0.0.1]) by localhost (droplet.the-wyvern.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6AFMiG0TAHUv for <myname(a)mydomain.net>; Mon, 26 Aug 2013 16:40:17 +0000 (UTC) Searching through the dovecot.markmail archive I can see this doesnt seem to be too unusual in that there are other examples where folk have posted message headers with the above format, however Im wondering if theres a good reason for it and if I can turn it off? I quite like being able to see where my mail came from :) If theres a man / wiki page to read somewhere that explains it then please feel free to tell me to RTM (.. long as you also point me in the right direction :p ) Thanks, Matt

2 4

[Dovecot] OT: z-Push
by Christian Rößner 04 Sep '13

04 Sep '13

Hi, just a short question: I have installed and configured z-Push to use BackendIMAP. On my iPhone I have created an account and I can see my mails. Also sending works. So far so good. Now the question: When I create a new folder i.e. Test under the root (/), then I get an error. And after resyncing the folder has been created not under /, but under /0/Test. Also I can not remove that folder over ActiveSync. Does somebody have z-Push fully working with Dovecot or is z-Push designed for Cyrus and only some features are working with Dovecot? So at the moment folder create/move/delete does not work here with z-Push-2.0.3 and Dovecot 2.1.9 Thanks in advance -Christian Rößner --- Bachelor of Science Informatik Erlenwiese 14, 36304 Alsfeld T: +49 6631 78823400, F: +49 6631 78823409, M: +49 176 93118939 USt-IdNr.: DE225643613, http://www.roessner-network-solutions.com

4 4

[Dovecot] Dovecot is not creating directories properly for new accounts
by Chris Lasater 04 Sep '13

04 Sep '13

Hi, I have just set up a new dovecot server with Dovecot 2.2.5. When I create a new user and try to authenticate I get the following error Sep 03 14:33:38 imap(test2): Error: user test2: Initialization failed: Initializing mail storage from mail_location setting failed: mkdir(/home/user/apps/var/mail/imap/test2/mailboxes) failed: Permission denied (euid=503(imapd) egid=503(imapd) missing +w perm: /home/user/apps/var/mail, we're not in group 502(dovecot), dir owned by 502:502 mode=0775) Sep 03 14:33:38 imap(test2): Error: Invalid user settings. Refer to server log for more information. imapd is in the dovecot group and here are the permissions [user@MB1 logs]$ ll /home/user/apps/var/ total 4 drwxrwxr-x 4 dovecot dovecot 4096 Sep 3 14:35 mail [user@MB1 logs]$ id imapd uid=503(imapd) gid=503(imapd) groups=503(imapd),500(user),502(dovecot) if I su - imapd and then run mkdir -p /home/user/apps/var/mail/imap/test2/mailboxes everything starts working and the user can log in. Isn't Dovecot supposed to be able to create these?

2 1

[Dovecot] dsync - convert plugin missing?
by Regan Yelcich 04 Sep '13

04 Sep '13

I'm looking to convert my mbox mailboxes over to Maildir. But when I try to run the dsync command: (changed with my variables) dsync -u username mirror mbox:~/mail:INBOX=/var/mail/username found on this dovecot v2.X page here: http://wiki2.dovecot.org/Migration/MailFormat I get an error that it can't find the "convert" plugin. Am I doing something wrong? Thanks.

1 0

Re: [Dovecot] Deleting messages with Mac Mail via IMAP
by Tim Schneider 04 Sep '13

04 Sep '13

The right wording (expunge) provided me with some clues. Anyway, Mac Mail does not have such a flag. It seems to be deliberately designed to do the expunge on quitting the application. Expunge can also be triggered by using cmd+shift+k with no marked messages to empty all trashes. Using this command, one can also mark a message and expunge it directly, bypassing the trash. I don't want to exclude the possiblity that this has got something to do with the IDLE system, and could be resolved by, for example, providing the right IMAP capabilities flags upon com init. Interestingly, iOS mail does delete the message in the inbox directly when moving it to trash. Thanks anyway to the contributors of this thread, I think I will have to accept this behavior, since Apple does usually not care about customer requests to resolve bugs. Mostly they declare them to be intended stupidity, even when they sell items that behave just the opposite way. Anyway, Zarafa mail server has a flag imap_expunge_on_delete. Perhaps this would be a useful feature for Dovecot to protect admins from angry customers who use well-designed Apple products. On 2013-09-03, at 20:16 , lists-dovecot <replies-lists-a1z2-dovecot(a)listmail.innovate.net> wrote: > > > ------------ Original Message ------------ >> Date: Tuesday, September 03, 2013 07:11:40 PM +0200 >> From: Tim Schneider <tim.schneider(a)portabile.net> >> To: dovecot(a)dovecot.org >> Subject: [Dovecot] Deleting messages with Mac Mail via IMAP >> >> Hello mailing list subscribers! >> >> When I delete a message in Mac Mail 6.5 (OS X 10.8.4), >> with the option to move messages to the trash set in Mac Mail >> account preferences, the message is copied to the trash, and >> markes as trashed in the cur/inbox directory on the server (STa >> flag in the file name). >> >> My horde webmail then displays this messages correctly as trashed >> in the inbox. However, I want the message to be gone from the >> inbox. >> >> Quitting Mac Mail deletes it in the inbox reliably. >> >> Is there any IMAP setting for dovecot to get move, and not copy >> and mark as trashed behavior? >>

1 0

[Dovecot] Deleting messages with Mac Mail via IMAP
by Tim Schneider 03 Sep '13

03 Sep '13

Hello mailing list subscribers! When I delete a message in Mac Mail 6.5 (OS X 10.8.4), with the option to move messages to the trash set in Mac Mail account preferences, the message is copied to the trash, and markes as trashed in the cur/inbox directory on the server (STa flag in the file name). My horde webmail then displays this messages correctly as trashed in the inbox. However, I want the message to be gone from the inbox. Quitting Mac Mail deletes it in the inbox reliably. Is there any IMAP setting for dovecot to get move, and not copy and mark as trashed behavior? Here are my dovecot settings: # 2.1.7: /etc/dovecot/dovecot.conf # OS: Linux 3.2.0-4-amd64 x86_64 Debian 7.1 ext4 auth_mechanisms = plain login mail_location = maildir:/var/mail/vhosts/%d/%n mail_privileged_group = mail 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 = admin(a)xxx.xxx protocols = imap pop3 lmtp sieve service auth-worker { user = vmail } service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0666 user = postfix } unix_listener auth-userdb { mode = 0600 user = vmail } user = dovecot } service imap-login { inet_listener imap { port = 0 } inet_listener imaps { port = 993 ssl = yes } } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } } service pop3-login { inet_listener pop3 { port = 0 } inet_listener pop3s { port = 995 ssl = yes } } ssl = required ssl_cert = </etc/ssl/certs/mailportabile.pem ssl_key = </etc/ssl/private/mailportabile.key submission_host = localhost userdb { args = uid=vmail gid=vmail home=/var/mail/vhosts/%d/%n driver = static } protocol lda { mail_plugins = " sieve" }

3 2

Re: [Dovecot] Logging passwords on auth failure/dealing with botnets
by Joseph Tam 03 Sep '13

03 Sep '13

Michael Smith writes: > We're already running fail2ban, but it doesn't seem that effective > against botnets, when they only do one attempt per IP. Yeah, distributed BFDs are tough to block unless you can characterize the clients well. > That leaves us back to getting dovecot to log the tried password for > unknown users. Another tactic might be to hook in a authentication script: http://wiki2.dovecot.org/AuthDatabase/CheckPassword You can run this as an external plugin and won't have to muck into the dovecot innards. From here, you can log attempts, keep track of bad IPs, or take action if you spot a username/password combination that merits instant blacklisting. Joseph Tam <jtam.home(a)gmail.com>

5 10

[Dovecot] sync re-copies emails assigning new UIDs
by Anand Kumria 03 Sep '13

03 Sep '13

Hi, I have been (attempting) to transition a company from in-house dovecot 1.x to a hosted dovecot 2.2 setup. I am running the doveadm sync command, and for the four mailboxes have been blocked -- sync'ing seem to be copying the same mails, over and over (note, initially I was using doveadm backup but my reading has indicated that 'doveadm sync' is better) Example: # date && doveadm -v -o imapc_user=kaye(a)example.com -o imapc_password=*pass* -o imapc_host=imap.example.com -o imapc_port=993 -o imapc_ssl=imaps -o imap c_ssl_dir=/etc/ssl -o imapc_feature=rfc822.size -o imapc_ssl_verify=no sync -1 -R -u kaye(a)example.com imapc: Sat Aug 3 09:05:37 UTC 2013 [...] dsync(kaye(a)example.com): Info: copy from INBOX: box=INBOX, uid=5306, msgid=<FB3A2E1C62B148F8B057476BDCBB4A9B@THENORMANS>, size=13544 dsync(kaye(a)example.com): Info: copy from INBOX: box=INBOX, uid=5307, msgid=<006b01ce8dad$b8864930$2992db90$(a)com.au>, size=10163563 [...] dsync(kaye(a)example.com): Info: copy from INBOX: box=INBOX, uid=5311, msgid=< cm.083930.bijjdjk.jdkimlhij.r(a)createsend5.com>, size=46658 [...] # date && doveadm -v -o imapc_user=kaye(a)example.com -o imapc_password=*pass* -o imapc_host=imap.example.com -o imapc_port=993 -o imapc_ssl=imaps -o imapc_ssl_dir=/etc/ssl -o imapc_feature=rfc822.size -o imapc_ssl_verify=no sync -1 -R -u kaye(a)example.com imapc: Sat Aug 3 10:01:48 UTC 2013 [...] dsync(kaye(a)kamdha.com): Info: copy from INBOX: box=INBOX, uid=5324, msgid=<FB3A2E1C62B148F8B057476BDCBB4A9B@THENORMANS>, size=13544 dsync(kaye(a)kamdha.com): Info: copy from INBOX: box=INBOX, uid=5325, msgid=<006b01ce8dad$b8864930$2992db90$(a)com.au>, size=10163563 [...] dsync(kaye(a)kamdha.com): Info: copy from INBOX: box=INBOX, uid=5329, msgid=< cm.083930.bijjdjk.jdkimlhij.r(a)createsend5.com>, size=46658 [...] The exact same number of emails (some in the INBOX, some in the Sent folder) are transferred each time. In this case, I've firewalled the origin - so their entire mail system is stopped whilst I do the transfer just in case modifications of IMAP flags or additional delivieres might have been the problem. I am using Dovecot v2.2.4; is this normal expected behaviour? If so, what is the best way to ensure that a migration is done without data loss. If this isn't expected, has anyone else seen this kind of error before? Thanks, Anand

1 1

[Dovecot] setup of dovecot as proxy to dbmail
by Regan Yelcich 03 Sep '13

03 Sep '13

Can anyone point me in the direction of a detailed how-to for setting up a postfix and dovecot (proxy) node with dbmail? In particular I'm looking for a how-to which shows dovecot authenticating against the dbmail database directly. The only example I've found is this one which requires a duplication of the user database. http://content.fens.org/index.php?q=admin-howto/mail/dovecot2dbmail-proxy Thanks.

2 1