- dovecot - dovecot.org

[Dovecot] ACLs, imap and launchd
by Axel Luttgens 30 Jun '09

30 Jun '09

I was going to experiment with ACLs when I faced a small problem. It is just sufficient to enable the acl plugin for getting the behavior described hereafter. When launching dovecot from the command line, one gets: sh-3.2# /usr/local/dovecot/sbin/dovecot -F ILoading modules from directory: /usr/local/dovecot-1.2.rc6/lib/ dovecot/imap IModule loaded: /usr/local/dovecot-1.2.rc6/lib/dovecot/imap/ lib01_acl_plugin.so IEffective uid=65534, gid=65534, home=/tmp Iacl: No acl setting - ACLs are disabled ^C In fact, a "dummy" imap process is run so as to fetch the capability (see master-settings.c); that process is run with an hardcoded uid/gid 65534. But this appears to be problematic when dovecot is started from launchd; clearly, launchd doesn't like arbitrary users, as it may be seen from system.log: org.dovecot[28382]: ^AILoading modules from directory: /usr/local/ dovecot-1.2.rc6/lib/dovecot/imap org.dovecot[28382]: ^AIModule loaded: /usr/local/dovecot-1.2.rc6/lib/ dovecot/imap/lib01_acl_plugin.so com.apple.launchd[1] (com.apple.launchd.peruser.65534[28384]): getpwuid("65534") failed com.apple.launchd[1] (com.apple.launchd.peruser.65534[28384]): PID 28383 "imap" has no account to back it! Real/effective/saved UIDs: 65534/65534/65534 com.apple.launchd[1] (com.apple.launchd.peruser.65534[28384]): Exited with exit code: 1 com.apple.launchd[1] (com.apple.launchd.peruser.65534): Throttling respawn: Will start in 10 seconds com.apple.launchd[1] (org.dovecot[28382]): Stray process with PGID equal to this dead job: PID 28383 PPID 1 imap com.apple.launchd[1] (org.dovecot[28382]): Exited abnormally: Alarm clock com.apple.launchd[1] (org.dovecot): Throttling respawn: Will start in 5 seconds com.apple.launchd[1] (com.apple.launchd.peruser.65534[28386]): getpwuid("65534") failed com.apple.launchd[1] (com.apple.launchd.peruser.65534[28386]): Exited with exit code: 1 com.apple.launchd[1] (com.apple.launchd.peruser.65534): Throttling respawn: Will start in 10 seconds ... and so on ... A workaround is to create the corresponding system user and group; launchd then doesn't complain anymore and everything seems to be working fine. But I feel somewhat uncomfortable with that... Wouldn't it be possible, for example, to consider using a system user such as "nobody" (unless I'm wrong, it should be defined on any unix flavor)? TIA, Axel sh-3.2# /usr/local/dovecot/sbin/dovecot -n # 1.2.rc6: /usr/local/etc/dovecot.conf # OS: Darwin 9.7.0 i386 protocols: pop3 imap ssl: no disable_plaintext_auth: no login_dir: /usr/local/var/run/dovecot/login login_executable(default): /usr/local/dovecot-1.2.rc6/libexec/dovecot/ imap-login login_executable(imap): /usr/local/dovecot-1.2.rc6/libexec/dovecot/ imap-login login_executable(pop3): /usr/local/dovecot-1.2.rc6/libexec/dovecot/ pop3-login first_valid_uid: 2001 last_valid_uid: 65533 mail_location: mbox:~/_mailboxes:INBOX=~/_mailboxes/inbox mail_debug: yes mbox_read_locks: flock mbox_write_locks: flock dotlock mail_executable(default): /usr/local/dovecot-1.2.rc6/libexec/dovecot/ imap mail_executable(imap): /usr/local/dovecot-1.2.rc6/libexec/dovecot/imap mail_executable(pop3): /usr/local/dovecot-1.2.rc6/libexec/dovecot/pop3 mail_plugins(default): acl mail_plugins(imap): acl mail_plugins(pop3): mail_plugin_dir(default): /usr/local/dovecot-1.2.rc6/lib/dovecot/imap mail_plugin_dir(imap): /usr/local/dovecot-1.2.rc6/lib/dovecot/imap mail_plugin_dir(pop3): /usr/local/dovecot-1.2.rc6/lib/dovecot/pop3 pop3_lock_session(default): no pop3_lock_session(imap): no pop3_lock_session(pop3): yes pop3_uidl_format(default): %08Xu%08Xv pop3_uidl_format(imap): %08Xu%08Xv pop3_uidl_format(pop3): %08Xv%08Xu auth default: debug: yes passdb: driver: pam args: * userdb: driver: passwd

2 4

Re: [Dovecot] Under POP attack - now to prevent?
by James Brown 30 Jun '09

30 Jun '09

On 05/06/2009, at 4:19 PM, James Brown wrote: > > Thanks to Curtis and others who replied. > > I managed to block the IP at our Firewall (learnt a few quirky > things about Astaro Security Gateway on the way!) > > In order to automate the process, Fail2Ban has been suggested. I > know this is getting a bit off topic, but has anyone installed in > Mac OS X 10.5.7? There is a how-to for 10.4 ( HOWTO Mac OS X Server > (10.4) - Fail2ban )- does this work unchanged in 10.5? > > Anyone managed to get Fail2Ban working on Leopard with Dovecot 1.2 > RC4? I'll answer my own question! There is a OS X Installer file at: LSA Mac OS X Ported and Developed Software | LSA Information Technology | University of Michigan Any regex experts out there that can help me set up Fail2Ban to stop this? Jun 5 11:48:20 mail dovecot[2620]: pop3-login: Aborted login (auth failed, 1 attempts): user=<audrey>, method=PLAIN, rip=85.189.169.94, lip=192.168.1.9 Jun 5 11:48:24 mail dovecot[2620]: pop3-login: Aborted login (auth failed, 1 attempts): user=<august>, method=PLAIN, rip=85.189.169.94, lip=192.168.1.9 Jun 5 11:48:24 mail dovecot[2620]: pop3-login: Aborted login (auth failed, 1 attempts): user=<autumn>, method=PLAIN, rip=85.189.169.94, lip=192.168.1.9 Jun 5 11:48:25 mail dovecot[2620]: pop3-login: Aborted login (auth failed, 1 attempts): user=<austin>, method=PLAIN, rip=85.189.169.94, lip=192.168.1.9 Jun 5 11:48:27 mail dovecot[2620]: pop3-login: Aborted login (auth failed, 1 attempts): user=<audrey>, method=PLAIN, rip=85.189.169.94, lip=192.168.1.9 Jun 5 11:48:28 mail dovecot[2620]: pop3-login: Aborted login (auth failed, 1 attempts): user=<autumn>, method=PLAIN, rip=85.189.169.94, lip=192.168.1.9 Jun 5 11:48:30 mail dovecot[2620]: pop3-login: Aborted login (auth failed, 1 attempts): user=<august>, method=PLAIN, rip=85.189.169.94, lip=192.168.1.9 Jun 5 11:48:31 mail dovecot[2620]: pop3-login: Aborted login (auth failed, 1 attempts): user=<autumn>, method=PLAIN, rip=85.189.169.94, lip=192.168.1.9 Many thanks, James.

2 1

[Dovecot] No folders listed in felamimail
by Jonathan Knight 30 Jun '09

30 Jun '09

Egroupware 1.4.004 I thought I try and solve a long standing bug we've had with felamimail not listing folders from our dovecot server. Watching dovecot's packet dumps I'm seeing dovecot do a namespace call and the a list call. Felamimail does a namespace and gets back * NAMESPACE (("" "/")) NIL NIL which is how I've configured dovecot to keep the client configuration very simple. Now Felamimail does a LIST "" "" which gets no folders returned and is obviously why it won't show anything in the felamimail display. I was expecting felamimail to do something more like: LIST "" "%" or LIST "" "*" Is there something I need to configure to make felamimail happy with our dovecot configuration? We use dovecot with outlook express, thunderbird (1,2,3), Mozilla, squirrelmail, iPod, iPhone and symbian with no issues so I'm tending towards felamimail being the source of the problem. Jon.

1 0

[Dovecot] Location of sieve_global_dir setting
by Rainer Frey 30 Jun '09

30 Jun '09

Hi, I'm a bit confused by the Wiki. Do the settings "sieve_dir" and "sieve_global_dir" belong to the lda or the plugin section (Dovecot 1.1.11)? Thanks Rainer

2 1

[Dovecot] SSL / TLS
by Carlos Williams 30 Jun '09

30 Jun '09

I am running Postfix and Dovecot on my mail server. I am required now to have SSL/TLS on my mail server. I did check and found out that I have a SSL certificate with Verisign issued to my mail servers FQDN. Now my question is when reading the Dovecot Wiki, I noticed it said that it is not common to use SSL but rather TLS on most mail servers. Even though SSL will work, which should I use on my server? We already have a purchased SSL certificate but does that really matter? Should I simply just revoke that certificate & use TLS instead? So when I read this link: http://wiki.dovecot.org/SSL/DovecotConfiguration Is it talking about a actual SSL certificate or TLS? Thanks for any clarification! - Carlos

8 12

[Dovecot] Users with large (4GB) inboxes crippling dovecot
by robforrest 29 Jun '09

29 Jun '09

Hi all, I'm new here and would very much appreciate any help you can give me. We are running a rather outdated mail server that until recently has been running beautifully. Under the pretense of "it is ain't broke, don't fix it" it hasn't been updated so is running Fedora Core 4 and dovecot v0.99.14. What is happening is that as users log in (via thunderbird), they are shown the contents of their mailboxes. However, when they try and access a given email, they get no response even if they wait upwards of 10 minutes. I believe that the problem has arisen from their huge inboxes, several users have inboxes in excess of 4GB. Do any of you know how I could split these large mbox files down in to manageable chunks of 1GB? Please be aware that I only have remote access to the server over a modest internet connection. Thanks again for any suggestions. Rob -- View this message in context: http://www.nabble.com/Users-with-large-%284GB%29-inboxes-crippling-dovecot-… Sent from the Dovecot mailing list archive at Nabble.com.

16 28

[Dovecot] Recommended Groupware?
by it-dovecot＠ml.epigenomics.com 29 Jun '09

29 Jun '09

Hi, is there a recommended groupware (email + calendar + address book + syncing with mobile devices) on top of an existing dovecot installation? Most existing commercially supported groupwares come with their own mail storage engine. I would like to keep dovecot as the email storage engine because of the maildir format which greatly helps with backup & restore. Regards -- Robert Sander

3 2

[Dovecot] Dovecot Expire doesn't work
by Stef Simoens 29 Jun '09

29 Jun '09

Hello, I'm using dovecot and I want to use the "expire" plugin. However, it doesn't work, i.e. mails do not get deleted. I ran `/usr/sbin/dovecot --exec-mail ext /usr/libexec/dovecot/expire-tool --test` and besides printing Info: stef/Trash: no messages left Info: stef/Spam: no messages left it doesn't do anything (especially not deleting e-mails). Obviously, in stef/Trash and stef/Spam, there are e-mails waiting to be deleted. I'm using dbox as mail storage; and use dbox:/var/mail/%u as mail_location in dovecot.conf. Furthermore, I'm running 1.1.16 on a gentoo PPC system. This is the output from `dovecot -n` # 1.1.16: /etc/dovecot/dovecot.conf # OS: Linux 2.6.29-gentoo-r2 ppc Gentoo Base System release 1.12.11.1 xfs listen: *, [::] ssl_cert_file: /etc/ssl/dovecot/server.pem ssl_key_file: /etc/ssl/dovecot/server.key login_dir: /var/run/dovecot/login login_executable: /usr/libexec/dovecot/imap-login verbose_proctitle: yes mail_privileged_group: mail mail_location: dbox:/var/mail/%u mail_plugins: expire auth default: verbose: yes debug: yes passdb: driver: pam args: * userdb: driver: passwd socket: type: listen master: path: /var/run/dovecot/auth-master mode: 384 plugin: quota: fs:Disk Quota expire: Trash 7 Spam 30 expire_dict: proxy::expire dict: expire: db:/var/lib/dovecot/expire.db A strace on `/usr/sbin/dovecot --exec-mail ext /usr/libexec/dovecot/expire-tool --test` shows the following output: mkdir("/var/mail/root", 0770) = -1 EEXIST (File exists) stat64("/var/mail/root/Trash/dbox-Mails", 0xbfda2708) = -1 ENOENT (No such file or directory) write(2, "Info: stef/Trash: no messages lef"..., 35Info: stef/Trash: no messages left ) = 35 which explains why nothing happens (stat64("/var/mail/root/Trash/dbox-Mails", which is empty, it should not even exist, but it passes by a mkdir), but why does it want to check /var/mail/root and not /var/mail/%u (i.e. why no stat64(/var/mail/stef/Trash/dbox-Mails))? Thanks for your help and kind regards, -- Stef Simoens

4 14

[Dovecot] LDAP Plugin fails to build in 1.2.rc7
by Paul Howarth 29 Jun '09

29 Jun '09

Hi, The LDAP Plugin fails to build (it doesn't attempt to build it) in 1.2.rc7 because $have_ldap_plugin is checked before it's assigned in configure.in. Patch attached. This was not a problem in 1.2.rc6 and earlier versions. Cheers, Paul.

2 1

[Dovecot] v1.2.rc7 released
by Timo Sirainen 29 Jun '09

29 Jun '09

http://dovecot.org/releases/1.2/rc/dovecot-1.2.rc7.tar.gz http://dovecot.org/releases/1.2/rc/dovecot-1.2.rc7.tar.gz.sig I'll make RC releases daily now until v1.2.0 is released, which will be either on Monday or Wednesday. Please test as much as possible. * Removed configure --with-deliver, --with-pop3d and --disable-ipv6 parameters. + Improved permission related error messages. - mbox: Don't write garbage to mbox if message doesn't have a body. - virtual: Fixed saving messages with keywords. - virtual: Fixed infinite looping bug. - zlib: Fixed error handling.

3 3