- dovecot - dovecot.org

[Dovecot] Quota fs (don't start script quota-warning.sh)
by Peter Ignatov 13 Sep '11

13 Sep '11

Hi, # doveadm -Dv quota get -u pit doveadm(pit): Debug: auth input: pit system_groups_user=pit uid=500 gid=500 home=/home/pit doveadm(pit): Debug: Effective uid=500, gid=500, home=/home/pit doveadm(pit): Debug: Quota root: name=INBOX backend=fs args=mount=/var/spool/mail doveadm(pit): Debug: Quota rule: root=INBOX mailbox=* bytes=19922944 messages=0 doveadm(pit): Debug: Quota warning: bytes=3984588 (20%) messages=0 reverse=no command=quota-warning 20 pit doveadm(pit): Debug: fs: root=/home/pit/mail, index=, control=, inbox=/var/spool/mail/pit doveadm(pit): Debug: fs quota add mailbox dir = /var/spool/mail doveadm(pit): Debug: fs quota block device = /dev/mapper/mpath1p1 doveadm(pit): Debug: fs quota mount point = /var/spool/mail doveadm(pit): Debug: fs quota mount type = ext2 Quota name Type Value Limit % INBOX STORAGE 4824 19456 24 But don't start script quota-warning.sh: #!/bin/sh PERCENT=$1 USER=$2 cat << EOF | /usr/libexec/dovecot/dovecot-lda -d $USER -o "plugin/quota=fs:INBOX:mount=/var/spool/mail:noenforcing" From: postmaster(a)domen.org Subject: quota warning Your mailbox is now $PERCENT% full. EOF #dovecot -n # 2.0.13: /etc/dovecot/dovecot.conf # OS: Linux 2.6.18-274.3.1.el5.asp121 x86_64 Red Hat Enterprise Linux Server release 5.6 (Tikanga) disable_plaintext_auth = no listen = * log_path = /var/log/dovecot.log mail_debug = yes mail_location = mbox:~/mail:INBOX=/var/spool/mail/%u mail_plugins = quota mail_privileged_group = mail mbox_write_locks = fcntl passdb { driver = pam } plugin { quota = fs:INBOX:mount=/var/spool/mail quota_rule = *:storage=19456 quota_warning = storage=20%% quota-warning 20 %u } protocols = pop3 service quota-warning { executable = script /usr/local/bin/quota-warning.sh unix_listener quota-warning { mode = 0666 } user = root } ssl_cert = </etc/pki/dovecot/certs/dovecot.pem ssl_key = </etc/pki/dovecot/private/dovecot.pem userdb { driver = passwd } verbose_proctitle = yes protocol lda { mail_plugins = quota } protocol imap { mail_plugins = quota imap_quota } protocol pop3 { mail_plugins = quota }

2 1

Re: [Dovecot] director ignoring director_mail_servers for lmtp connections
by mailing lists 13 Sep '11

13 Sep '11

On 09/13/2011 08:34 AM, Jan-Frode Myklebust wrote: > On Mon, Sep 12, 2011 at 04:55:51PM +0100, mailing lists wrote: >> >> director_mail_servers = 101.180.245.101 >> director_servers = 101.180.245.101 it works with imap connections, so I assumed it also would do it for lmtp. Sep 13 09:04:03 imap1 dovecot: imap-login: proxy(user001): started proxying to 10.180.245.101:143: user=<user001>, method=PLAIN, rip=::1, lip=: :1, secured > Is this a loop maybe? director_mail_servers should list all > your backend dovecot servers, space separated. Here's mine: > > director_mail_servers = 192.168.42.7 192.168.42.8 192.168.42.9 192.168.42.10 192.168.42.11 192.168.42.28 192.168.42.29 using only one director and backend would be fine for tests purposes (as it was with imap and not loops were formed) What I don't understand is why director insists in providing a proxy host from passdb when all it needs to do is pick the ones in director_mail_servers ¿? Sep 12 17:14:13 imap1 dovecot: lmtp(25682): Error: proxy: host not given please could you post you lmtp configuration??

1 0

[Dovecot] director ignoring director_mail_servers for lmtp connections
by mailing lists 13 Sep '11

13 Sep '11

Hello, Following Jan-Frode's advise I am trying this configuration: {postfix} ---lmtp---> {director} ---lmtp---> {dovecot} so I have two dovecot instances for director/proxy and lmtp delivery on ports 1024 and 24 respectively. whilst for imap connections I can specify a pool of imap backend servers via 'director_mail_servers' it seems is not possible with lmtp. Sep 12 17:14:13 imap1 dovecot: auth: Debug: master in: PASS 1 user001(a)example.com service=lmtp lip=::1 lport=1024 rip=::1 rpor5 Sep 12 17:14:13 imap1 dovecot: auth: Debug: static(user001@example.com,::1): lookup Sep 12 17:14:13 imap1 dovecot: auth: Debug: password(user001@eexample.com,::1): Credentials: Sep 12 17:14:13 imap1 dovecot: auth: Debug: master out: PASS 1 user=user001(a)example.com proxy port=24 Sep 12 17:14:13 imap1 dovecot: lmtp(25682): Debug: auth input: user=user001(a)example.com proxy port=24 Sep 12 17:14:13 imap1 dovecot: lmtp(25682): Error: proxy: host not given Sep 12 17:14:13 imap1 dovecot: lmtp(25682): Debug: Loading modules from directory: /usr/lib64/dovecot/modules Sep 12 17:14:13 imap1 dovecot: lmtp(25682): Debug: Module loaded: /usr/lib64/dovecot/modules/lib01_acl_plugin.so Sep 12 17:14:13 imap1 dovecot: auth: Debug: master in: USER 2 user001(a)example.com service=lmtp lip=::1 rip=::1 Sep 12 17:14:13 imap1 dovecot: auth: Debug: static(user001@example.com,::1): lookup Sep 12 17:14:13 imap1 dovecot: auth: Debug: password(user001@example.com,::1): Credentials: Sep 12 17:14:13 imap1 dovecot: auth: Debug: master out: USER 2 user001(a)example.com Sep 12 17:14:13 imap1 dovecot: lmtp(25682): Debug: auth input: user001(a)example.com Sep 12 17:14:43 imap1 dovecot: lmtp(25682): Disconnect from ::1: Client quit (in RCPT TO) how I can redirect incoming lmtp request to backend lmtp servers (and not just one)? what I'm missing here? /----------/ # dovecot -c /etc/dovecot-director/dovecot.conf -n # 2.0.14: /etc/dovecot-director/dovecot.conf # OS: Linux 2.6.34.7-0.7-xen x86_64 openSUSE 11.3 (x86_64) auth_debug = yes auth_debug_passwords = yes auth_verbose = yes auth_verbose_passwords = plain base_dir = /var/run/dovecot-director/ director_mail_servers = 101.180.245.101 director_servers = 101.180.245.101 disable_plaintext_auth = no lmtp_proxy = yes mail_debug = yes mail_fsync = always mail_gid = 5000 mail_nfs_index = yes mail_nfs_storage = yes mail_plugins = acl mail_uid = 5000 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 mmap_disable = yes passdb { args = proxy=y nopassword=y driver = static } plugin { acl = vfile sieve = ~/.dovecot.sieve sieve_dir = ~/sieve } protocols = imap lmtp service auth { unix_listener auth-userdb { group = vmail mode = 0666 user = vmail } } service director { fifo_listener login/proxy-notify { mode = 0666 } inet_listener { port = 9090 } unix_listener director-userdb { mode = 0666 } unix_listener login/director { mode = 0666 } } service imap-login { executable = imap-login director inet_listener imap { port = 10143 } } service lmtp { inet_listener lmtp { port = 1024 } } ssl = no verbose_proctitle = yes protocol lmtp { passdb { args = proxy=y nopassword=y port=24 driver = static } } protocol imap { mail_max_userip_connections = 100 }

2 1

[Dovecot] signal 11 crash, sometimes, during mbox bz2 decompression
by Mike Brown 13 Sep '11

13 Sep '11

Hello again, I'm running dovecot 1.2.16 from the ports collection on FreeBSD 8.1-STABLE, amd64. To enable IMAP read-only access to gzip or bzip2 compressed mbox files, I added the following to my dovecot.conf, in the protocol imap { ... } section: mail_plugins = zlib My compressed mbox files are all .bz2 files in an 'old' subdirectory of my main mail directory. I am trying to access them with Thunderbird. I 'subscribed' to them just fine, and at first I thought it was working, but I just got lucky on the first couple I accessed. Dovecot actually fails to decompress them about 90% of the time, seemingly at random; the same box will not work a bunch of times, then work once, then not work again and again. When it works, sometimes only some of the messages get transmitted. Most of the failures are accompanied by this pair of messages in my log: Aug 16 00:25:33 myhost dovecot: dovecot: child 943 (imap) killed with signal 11 (core not dumped - set mail_drop_priv_before_exec=yes) Aug 16 00:25:33 myhost kernel: pid 943 (imap), uid 1001: exited on signal 11 Some of the failures have only the "exited on signal 11" message. The very first failure had this: Aug 16 00:22:47 myhost dovecot: IMAP(mike): Next message unexpectedly lost from mbox file (read-only mbox stream) at 2761 (cached) Aug 16 00:22:47 myhost dovecot: IMAP(mike): read(mail, uid=2) failed: Invalid argument Is this a problem with dovecot? Let me know if/how I can help, or what other info you need. Thanks, Mike

2 4

[Dovecot] two little fixes for 2.0.14
by Mike Abbott 13 Sep '11

13 Sep '11

--- a/dovecot/src/lib-index/mail-index-view.c +++ b/dovecot/src/lib-index/mail-index-view.c @@ -9,7 +9,7 @@ void mail_index_view_clone(struct mail_index_view *dest, const struct mail_index_view *src) { - memset(dest, 0, sizeof(dest)); + memset(dest, 0, sizeof(*dest)); dest->refcount = 1; dest->v = src->v; dest->index = src->index; --- a/dovecot/src/lib-storage/mail-storage-service.c +++ b/dovecot/src/lib-storage/mail-storage-service.c @@ -870,7 +870,7 @@ } user = p_new(user_pool, struct mail_storage_service_user, 1); - memset(user_r, 0, sizeof(user_r)); + memset(user_r, 0, sizeof(*user_r)); user->pool = user_pool; user->input = *input; user->input.userdb_fields = NULL;

2 1

[Dovecot] Custom error messages.
by Lauro C. 12 Sep '11

12 Sep '11

I am using Dovecot 1.2.9. Is it possible to have custom error messages? I want to translate some of the messages (for instance mailbox full), so it can be more user friendly. I already use the quota warning feature. But I need to translate the messages anyways, is it possible? Lauro

2 1

[Dovecot] Possible to Customize File Naming Scheme?
by Dave Stubbs 12 Sep '11

12 Sep '11

Hello all, [Sorry if this has been covered already - I searched back a little way in the archive and didn't find anything recent on the topic.] I'm wondering if it is possible to customize the way dovecot creates or modifies filenames in the maildir directories? I'm watching how my mail system works, and I see that procmail creates a new file in the <folder>/new directory, each time an email is received. This file is some complex combination of UIDs and things, suffixed by the server name. So far, the filename has alphanumerics, a couple underscores, and a dot or two only. But once dovecot gets it's hands on the file and moves it to the <folder>/cur directory, it starts doing "terrible" things to the file name. Now, the filename starts to have "evil" things in it, like colons and commas. Is there a way to change this? I'm asking this primarily because I use dovecot as a massive long-term email archiving system. One of the things one needs to be able to do when running a long-term archive like this is keep things as simple and accessible as possible. The reason I use maildir is that I totally buy into the "one email, one file" idea - it means I don't have to store messages in big consolidated database files that are changeable with each new version of the vendor's software release (such as exchange DBs or Outlook PST files) or that are horrible performers (such as mbox). One of the nice things about the maildir "each email is a separate file" idea is that you are not limited to maildir or dovecot or any other piece of software to handle, read, and process the files. For instance, I would like to backup my maildir by using rsync to synchronize my dovecot-managed maildir to a Windows server running NFS. From there the files are synchronized via Windows DFS ( to which there is no open source solution that is even close) to several other servers around the continent. Only thing: The evil commas and colons in the filenames are anathema to Windows. So instead I tar the maildir folders to tgz files on the windows server, and the tgz's are synchronized to other DR sites. If I could do without the need for tar (mandated solely because of the colons and commas in the dovecot filename scheme) I could minimize the time to backup (only synchronizing changes) and suddenly I would have a lot of other benefits opened up. One simple one would be that if I could configure dovecot to append the .eml extension to the end of every file (technically each file in a maildir is an eml file regardless of the extension being present or not - eml is just a raw mail file just like what you'd find in a maildir) I would have instant access to them using Search Server Express, which can read eml files but strongly prefers to use extentions to recognize files as such. To be clear: I'm not requesting that dovecot's file naming convention be changed to match my quirky requirements - I'm just asking if it could be made configurable, so I could change it to match my needs and others could change it to match theirs. In the interests of REALLY being able to use the elegantly simple idea of each mail being a separate file, I'm trying to get more out of that great pile of folders and files I'm amassing in my mail archive server. The more use I can make of them with other software other than dovecot (i.e. data crawling, indexing, easy recovery in a catastrophe, etc) the more valuable this format is. Is this possible?

3 4

[Dovecot] How to get rid of sub-folders ?
by Spyros Tsiolis 12 Sep '11

12 Sep '11

Hello, OK, no answers on my previous e-mail. I'll rephrase it. How can I get rid of subfolders on a users' tree-like structure on dovecot ? Which file must I "touch" ? TIA, s. ---- "I merely function as a channel that filters music through the chaos of noise" - Vangelis

2 2

[Dovecot] userdb static & Quota from LDAP?
by Christian Schmidt 12 Sep '11

12 Sep '11

Hi all, I just configured Dovecot 2.0.14 for "virtual" (i.e. non-system-) users: passdb { driver = ldap args = /etc/dovecot/conf.d/ldap-passdb.ext } userdb { driver = static args = uid=vmail gid=vmail home=/var/maildir/%u } Works fine so far - thanks for this great piece of software, Timo!!! Now I'd like to add per-user quotas that will also be stored in the LDAP directory, and I'm not sure how to put things together. IMHO quota is the only "userdb information" requested from LDAP, and I'd like to leave all the other "userdb pieces" as the are. I changed the userdb definition to: userdb { driver = ldap args = /etc/dovecot/conf.d/ldap-userdb.ext } My /etc/dovecot/conf.d/ldap-userdb.ext contains (along other lines): user_attrs = uid=vmail,gid=vmail,home=/var/maildir/%u,mailQuota=quota=quota_rule=*:storage=%$ My quota configuration looks like this: plugin { quota = maildir:Mailbox-Quota quota_rule = *:storage=1G quota_warning = storage=80%% /usr/local/bin/quotawarn.sh 80 %u quota_warning2 = storage=95%% /usr/local/bin/quotawarn.sh 95 %u } Using this setup, "doveadm quota get -u username" doesn't reveal any quota information (except from the "headings"). Instead, dovecot logs: doveadm(username): Fatal: GID 0 isn't permitted When switching back to userdb static, I receive the correct (but also) static quota information. What am I doing wrong? Thank you very much, Christian Schmidt -- question = ( to ) ? be : ! be; -- Wm. Shakespeare

3 2

[Dovecot] Attacking Dovecot
by Nikos Papadopoulos 12 Sep '11

12 Sep '11

Hello, I am using Dovecot ver.1.0.7 on an x86 server with RedHat Linux Enterprise 5 and the following configuration: # 1.0.7: /etc/dovecot.conf protocols: pop3 login_dir: /var/run/dovecot/login login_executable: /usr/libexec/dovecot/pop3-login mail_location: mbox:~/mail:INBOX=/var/mail/%u mail_executable: /usr/libexec/dovecot/pop3 mail_plugin_dir: /usr/lib/dovecot/pop3 pop3_client_workarounds: outlook-no-nuls oe-ns-eoh auth default: passdb: driver: pam userdb: driver: passwd It seems that my mail server is being attacked by someone who tries to retrieve users' credentials. Please read below an output of logwatch. dovecot-auth: pam_succeed_if(dovecot:auth): error retrieving information about user sandra dovecot-auth: pam_succeed_if(dovecot:auth): error retrieving information about user tanya dovecot-auth: pam_succeed_if(dovecot:auth): error retrieving information about user tanya dovecot-auth: pam_succeed_if(dovecot:auth): error retrieving information about user dark dovecot-auth: pam_succeed_if(dovecot:auth): error retrieving information about user dark dovecot-auth: pam_succeed_if(dovecot:auth): error retrieving information about user gibson dovecot-auth: pam_succeed_if(dovecot:auth): error retrieving information about user frank dovecot-auth: pam_succeed_if(dovecot:auth): error retrieving information about user frank Besides, some of the local users receive "spam" emails, which seem to be sent by another local user. Please assist me on how to prevent the aforementioned attack. Best Regards, Nikos

3 2