- dovecot - dovecot.org

[Dovecot] Internal server
by Guy 16 Oct '09

16 Oct '09

Hi, I'm looking at doing some testing for a little internal IMAP server. Basically use fetchmail (or some such thing to bring in mail) so users have a local IMAP server to connect to. I'm interested in trying out mdbox, but since I'd have to use dovecot 2.0 with it I thought I'd just check what peoples' experience with 2.0 is like so far? Is it reasonably stable already? Is there also a page showing the differences in config for dbox over maildir? Or is it simply just the change in mail_location and nothing else? Thanks Guy -- Don't just do something...sit there!

2 1

[Dovecot] FS Quota broken for delivering BIG message
by Kostik 16 Oct '09

16 Oct '09

Hi everybody. I have Linux file system quota for users and enabled "fs quota" and quota plugin for LDA. My test user is already deep over quoted: --- Filesystem blocks quota limit nfse:/export 23768* 10240 10240 --- 1. If I tries to deliver _short_ message to user mbox - quota works: $ echo "123123123123" | /usr/local/libexec/dovecot/deliver -d koc --- Quota root: name=Quota backend=fs args=group:mount=/var/virtual/home/I/I/koc Quota rule: root=Quota mailbox=* bytes=10383360 messages=0 mbox: data=~/:INBOX=/var/virtual/mail/I/I/koc:INDEX=MEMORY fs: root=/var/virtual/home/I/I/koc, index=, control=, inbox=/var/virtual/mail/I/I/koc fs quota add storage dir = /var/virtual/home/I/I/koc fs quota block device = nfse:/export fs quota mount point = /mount/m5 quota-fs: host=nfse, path=/export, gid=5751796, bytes quota-fs: gid=5751796, value=24338432, limit=10485760, active=1 from=<>, msgid=: save failed to INBOX: Quota exceeded (mailbox for user is full) from=<>, msgid=: rejected: Quota exceeded (mailbox for user is full) msgid=: Return-Path missing, rejection reason: Quota exceeded (mailbox for user is full) --- 2. But if I tries to deliver _BIG_ message to user mbox - quota broken: $ cat big.msg | /usr/local/libexec/dovecot/deliver -d koc --- Quota root: name=Quota backend=fs args=group:mount=/var/virtual/home/I/I/koc Quota rule: root=Quota mailbox=* bytes=10383360 messages=0 mbox: data=~/:INBOX=/var/virtual/mail/I/I/koc:INDEX=MEMORY fs: root=/var/virtual/home/I/I/koc, index=, control=, inbox=/var/virtual/mail/I/I/koc fs quota add storage dir = /var/virtual/home/I/I/koc fs quota block device = nfse:/export fs quota mount point = /mount/m5 quota-fs: host=nfse, path=/export, gid=5751796, bytes quota-fs: gid=5751796, value=24338432, limit=10485760, active=1 write_full(/var/virtual/home/I/I/koc/.temp.pigeon01.8822.64dfacc7e57d71b4) failed: Disk quota exceeded stat(/tmp/Dovecot Delivery Mail) failed: Disk quota exceeded from=<>, msgid=: save failed to INBOX: BUG: Unknown internal error --- This "write_full() failed" from: src/lib/istream-seekable.c --- static ssize_t i_stream_seekable_read(struct istream_private *stream) { ... /* save to our file */ data = i_stream_get_data(sstream->cur_input, &size); if (write_full(sstream->fd, data, size) < 0) { i_assert(errno != 0); stream->istream.stream_errno = errno; i_error("write_full(%s) failed: %m", sstream->temp_path); i_stream_close(&stream->istream); return -1; } ... } --- =kostik

2 2

[Dovecot] Dovecot inactive after an intermittent connection with LDAP
by Thu Nguyen 16 Oct '09

16 Oct '09

Hello all, I'm facing the problem below: 1. Firstly, the connection between dovecot and ldap was down. dovecot: Oct 10 09:11:12 Info: auth(default): ldap(user1,x.x.x.x): Aborting (timeout), we're not connected to LDAP server dovecot: Oct 10 09:11:12 Info: auth(default): master out: USER 265490 user1 2. There is many new connection from user created.... dovecot: Oct 10 09:11:12 Info: auth(default): new auth connection: pid=21114 dovecot: Oct 10 09:11:12 Info: auth(default): new auth connection: pid=21113 3. ....but it obviously failed. dovecot: Oct 10 09:11:12 Info: pop3-login: Internal login failure (auth failed,1 attempts): user=<user1>, method=PLAIN, rip=x.x.x.x, lip= x.x.x.x dovecot: Oct 10 09:11:12 Info: pop3-login: Internal login failure (auth failed,1 attempts): user=<user2>, method=PLAIN, rip= x.x.x.x,lip= x.x.x.x ................. dovecot: Oct 10 09:11:15 Info: auth(default): new auth connection: pid=21125 dovecot: Oct 10 09:11:15 Info: auth(default): new auth connection: pid=21126 dovecot: Oct 10 09:11:22 Info: auth(default): client in: AUTH 1 PLAIN service=pop3 lip= x.x.x.x rip= x.x.x.x lport=110 rport=4504 resp=<hidden> dovecot: Oct 10 09:11:22 Info: auth(default): client in: AUTH 1 PLAIN service=pop3 lip= x.x.x.x rip= x.x.x.x lport=110 rport=6316 resp=<hidden> dovecot: Oct 10 09:11:22 Info: auth(default): new auth connection: pid=21132 dovecot: Oct 10 09:11:24 Info: auth(default): client in: AUTH 1 PLAIN service=pop3 lip= x.x.x.x rip= x.x.x.x lport=110 4. LDAP connection is back to normal, however, it still failed. dovecot: Oct 10 09:14:14 Info: auth(default): new auth connection: pid=21250 dovecot: Oct 10 09:14:14 Info: auth(default): new auth connection: pid=21251 dovecot: Oct 10 09:14:14 Info: auth(default): client in: AUTH 1 PLAIN service=pop3 lip= x.x.x.x rip= x.x.x.x lport=110 rport=2959 resp=<hidden> dovecot: Oct 10 09:14:14 Info: pop3-login: Disconnected: Inactivity (auth failed, 1 attempts): method=PLAIN, lip= x.x.x.x rip= x.x.x.x dovecot: Oct 10 09:14:15 Info: pop3-login: Disconnected: Inactivity (auth failed, 1 attempts): method=PLAIN, lip= x.x.x.x rip= x.x.x.x dovecot: Oct 10 09:14:15 Info: pop3-login: Disconnected: Inactivity (auth failed, 1 attempts): method=PLAIN, lip= x.x.x.x rip= x.x.x.x dovecot: Oct 10 09:14:15 Info: auth(default): client in: AUTH 1 PLAIN service=pop3 lip= x.x.x.x rip= x.x.x.x lport=110 rport=3765 resp=<hidden> dovecot: Oct 10 09:14:15 Info: auth(default): client in: AUTH 1 PLAIN service=pop3 lip= x.x.x.x rip= x.x.x.x lport=110 rport=48 08 resp=<hidden> dovecot: Oct 10 09:14:15 Info: pop3-login: Disconnected: Inactivity (auth failed, 1 attempts): method=PLAIN, rip=199.30.31.48, lip=199.30.26.18 5. Then the request queue is full ... Dovecot is completely inactive. Of course it try to fail back to pam but as the password is not the same so it's failed also. dovecot: Oct 10 09:38:53 Error: auth(default): ldap(user1,10.0.0.7): Request queue is full (oldest added 1660 secs ago) dovecot: Oct 10 09:38:53 Info: auth-worker(default): pam(user1,10.0.0.7): lookup service=dovecot dovecot: Oct 10 09:38:53 Info: auth-worker(default): pam(user1.vn,10.0.0.7): #1/1 style=1 msg=Password: dovecot: Oct 10 09:38:53 Info: auth(default): new auth connection: pid=22405 dovecot: Oct 10 09:38:54 Info: auth(default): client in: AUTH 1 PLAIN service=pop3 lip= x.x.x.x rip= x.x.x.x lport=110 rport=2789 resp=<hidden> dovecot: Oct 10 09:38:56 Info: auth-worker(default): pam(user1,x.x.x.x): pam_authenticate() failed: Authentication failure (password mismatch?) ---------------------------------------------------------------- Bref, I suggest that when the connection between LDAP and dovecot is dropped, the connection from user is still there and as they don't receive a result from dovecot [Fail or Success]... And it still "pending" somehow to wait a response from dovecot. But when ldap is connected to the system, these pending connection (from user) is still pending .... so it makes the "request queue is full". Isn't it? Should I do something to work-through or work-around this problem? May I did something wrong in my configuration. Below is usual information may it helps us analyze the problem! Thanks many much for your help! ----------------------------------------------------------------- [root ~]# dovecot -n # 1.1.14: /etc/dovecot.conf # OS: Linux 2.6.18-92.el5PAE i686 CentOS release 5.2 (Final) ext3 log_path: /var/log/dovecot.log protocols: imap pop3 ssl_disable: yes login_dir: /var/run/dovecot/login login_executable(default): /usr/libexec/dovecot/imap-login login_executable(imap): /usr/libexec/dovecot/imap-login login_executable(pop3): /usr/libexec/dovecot/pop3-login verbose_proctitle: yes mail_gid: 100 mail_location: maildir:/home/%u/Maildir mail_debug: yes mail_executable(default): /usr/libexec/dovecot/imap mail_executable(imap): /usr/libexec/dovecot/imap mail_executable(pop3): /usr/libexec/dovecot/pop3 mail_plugin_dir(default): /usr/lib/dovecot/imap mail_plugin_dir(imap): /usr/lib/dovecot/imap mail_plugin_dir(pop3): /usr/lib/dovecot/pop3 auth default: verbose: yes debug: yes passdb: driver: ldap args: /etc/dovecot-ldap.conf passdb: driver: pam userdb: driver: ldap args: /etc/dovecot-ldap.conf userdb: driver: static socket: type: listen master: path: /var/run/dovecot/auth-master mode: 384 user: dovecot group: dovecot plugin: sieve: /home/%u/.dovecot.sieve -------------------------------------------------------------------- [root ~]# grep -v '^ *$#.*$\?$' /etc/dovecot-ldap.conf hosts = ldap.tma.com.vn dn = ##### dnpass = ###### auth_bind = yes auth_bind_userdn = uid=%u,ou=Users,dc=tma,dc=com,dc=vn ldap_version = 3 base = ou=Users,dc=,dc=com,dc=vn scope = subtree user_attrs = uid=uid,mailQuota=quota_rule=*:storage=%$M user_filter = (&(objectClass=posixAccount)(uid=%u)) pass_attrs = uid=user,userPassword=password pass_filter = (&(objectClass=posixAccount)(uid=%u)) default_pass_scheme = CRYPT -------------------------------------------------------------------- Regards, Thu NGUYEN.

2 2

[Dovecot] 2.0 config info for dovecot-dict-sql.conf?
by PGNet Dev 16 Oct '09

16 Oct '09

reading, /usr/local/share/doc/dovecot/wiki/Quota.Dict.txt refers to config, e.g. dovecot-dict-sql.conf, for, "v1.2 +" is the v1.2+ info there valid/correct for 2.0+?

1 1

[Dovecot] @2.0, Fatal error (Expecting '=') in trash plugin config
by PGNet Dev 16 Oct '09

16 Oct '09

i've setup trash plugin as, grep trash imap.conf mail_plugins = autocreate fts fts_squat fts_solr imap_quota quota trash zlib cat plugin.conf plugin { ... trash = /data/mail/Conf/dovecot/conf.d/trash.conf } cat /data/mail/Conf/dovecot/conf.d/trash.conf 1 Spam 2 Trash 3 Sent 3 Sent Messages but, @ dovecot -n # 2.0.alpha1: /data/mail/Conf/dovecot/dovecot.conf doveconf: Fatal: Error in configuration file /data/mail/Conf/dovecot/conf.d/trash.conf line 1: Expecting '=' bug, or change frp, v1.x in config/parsing?

2 4

[Dovecot] pop3-login process
by ogu_yo＠yahoo.co.jp 16 Oct '09

16 Oct '09

Hi, I would like to know if the pop3-login process would be create more than one while a user connection is established. http://wiki.dovecot.org/RunningDovecot ------------------------------------ imap-login and pop3-login processes handle new IMAP and POP3 connections until user has logged in. ------------------------------------ I'm sorry to ask you this kind of question... Regards, -------------------------------------- GyaO! - Anime, Dramas, Movies, and Music videos [FREE] http://pr.mail.yahoo.co.jp/gyao/

3 7

[Dovecot] Expire plugin: wrong mailbox separators in database?
by Andreas Ntaflos 16 Oct '09

16 Oct '09

Hi all, I'm experimenting with the expire plugin and seem have run into a small problem. I am using Dovecot 1.2.4 on a test server. The config is taken mostly verbatim from the expire plugin wiki page [1], using MySQL as a database. See below for detailed output. Namespace "private" has "/" configured as mailbox separator: namespace private { separator = / prefix = inbox = yes } The "expire =" section from dovecot.conf thus looks like this: plugin { expire = Trash 7 INBOX/Spam 8 INBOX/Spam/To-Discard 3 ... } Three mailboxes/folders are kept track of: Trash, INBOX/Spam and INBOX/Spam/Spam-To-Discard (this one holds messages that scored high enough to very unlikely be legitimate and should be deleted soon). But when a message is put into one of these folders the mailbox attribute of the expires table uses "." as mailbox separator: mysql> select * from expires; +-----------------+----------------------------+--------------+ | username | mailbox | expire_stamp | +-----------------+----------------------------+--------------+ | foo(a)example.org | INBOX.Spam.Spam-To-Discard | 1253114526 | | foo(a)example.org | INBOX.Spam | 1253114528 | +-----------------+----------------------------+--------------+ Consequently, expire-tool --test seems to choke on this: # dovecot --exec-mail ext /usr/local/libexec/dovecot/expire-tool --test Info: foo(a)example.org/INBOX.Spam.Spam-To-Discard: \ mailbox 'INBOX.Spam.Spam-To-Discard' removed from config Info: foo(a)example.org/INBOX.Spam: mailbox 'INBOX.Spam' \ removed from config When I manually update the mailbox attribute to use "/" as separator expire-tool seems to work correctly: # dovecot --exec-mail ext /usr/local/libexec/dovecot/expire-tool --test Info: foo(a)example.org/INBOX/Spam/Spam-To-Discard: stop, expire \ time in future: Wed Sep 16 17:22:06 2009 Using "." as separator in the "expire =" line doesn't work either: the expires table isn't written to at all when a message is put in one of the specified folders. Presumably because INBOX/Spam is the real mailbox but INBOX.Spam is monitored by the expire plugin and there is no INBOX.Spam to put in messages. So I believe this is not the expected behaviour? Or am I doing anything wrong? I'd rather not change the separator from "/" to "." in all the namespaces if that can be avoided. Thanks in advance, Andreas dovecot -n: ========== # 1.2.4: /usr/local/etc/dovecot.conf # OS: Linux 2.6.26-2-686 i686 Debian 5.0.2 log_timestamp: %Y-%m-%d %H:%M:%S protocols: managesieve imap imaps pop3 pop3s listen: 83.65.168.220 127.0.0.1 login_dir: /usr/local/var/run/dovecot/login login_executable(default): /usr/local/libexec/dovecot/imap-login login_executable(imap): /usr/local/libexec/dovecot/imap-login login_executable(pop3): /usr/local/libexec/dovecot/pop3-login login_executable(managesieve): /usr/local/libexec/dovecot/managesieve-login mail_access_groups: mail mail_privileged_group: mail mail_location: maildir:~/Maildir mail_drop_priv_before_exec: yes mail_executable(default): /usr/local/libexec/dovecot/imap mail_executable(imap): /usr/local/libexec/dovecot/imap mail_executable(pop3): /usr/local/libexec/dovecot/pop3 mail_executable(managesieve): /usr/local/libexec/dovecot/managesieve mail_plugins(default): autocreate acl expire mail_plugins(imap): autocreate acl expire mail_plugins(pop3): expire mail_plugins(managesieve): mail_plugin_dir(default): /usr/local/lib/dovecot/imap mail_plugin_dir(imap): /usr/local/lib/dovecot/imap mail_plugin_dir(pop3): /usr/local/lib/dovecot/pop3 mail_plugin_dir(managesieve): /usr/local/lib/dovecot/managesieve namespace: type: public separator: / prefix: Public/ location: maildir:/var/mail/public:CONTROL=~/Maildir/control/public:INDEX=~/Maildir/index/public list: yes namespace: type: private separator: / prefix: Backup/ location: maildir:~/Maildir-backup hidden: yes list: no namespace: type: private separator: / inbox: yes list: yes subscriptions: yes lda: log_path: info_log_path: auth_socket_path: /var/run/dovecot/auth-master postmaster_address: postmaster(a)mailtest0.rise-s.com mail_plugins: sieve acl expire auth default: mechanisms: plain login passdb: driver: pam passdb: driver: sql args: /etc/dovecot/dovecot-sql.conf userdb: driver: passwd userdb: driver: static args: uid=vmail gid=vmail home=/var/vmail/%Ld/%Ln allow_all_users=yes socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: postfix group: postfix master: path: /var/run/dovecot/auth-master mode: 384 user: vmail plugin: expire: Trash 7 INBOX/Spam 5 INBOX/Spam/Spam-To-Discard 3 expire_dict: proxy::expire sieve: ~/.dovecot.sieve sieve_dir: ~/sieve sieve_global_path: /etc/dovecot/sieve/default.sieve sieve_global_dir: /etc/dovecot/sieve/global/ sieve_before: /etc/dovecot/sieve/before/ autocreate: Trash autocreate2: Drafts autocreate3: Sent autocreate4: INBOX/Spam autocreate5: INBOX/Spam/Spam-To-Discard autosubscribe: Trash autosubscribe2: Drafts autosubscribe3: Sent autosubscribe4: INBOX/Spam autosubscribe5: INBOX/Spam/Spam-To-Discard acl: vfile:/etc/dovecot/acl dict: expire: mysql:/etc/dovecot/dovecot-dict-expire.conf /etc/dovecot/dovecot-dict-expire.conf: ===================================== connect = host=127.0.0.1 dbname=mailserver user=mailuser password=xxx map { pattern = shared/expire/$user/$mailbox table = expires value_field = expire_stamp fields { username = $user mailbox = $mailbox } } The expires table: CREATE TABLE expires ( username varchar(100) not null, mailbox varchar(255) not null, expire_stamp integer not null, primary key (username, mailbox) ); [1] http://wiki.dovecot.org/Plugins/Expire -- Andreas Ntaflos Vienna, Austria GPG Fingerprint: 6234 2E8E 5C81 C6CB E5EC 7E65 397C E2A8 090C A9B4

3 3

[Dovecot] Error (IMHO) with --with-doc option
by Jacek Osiecki 16 Oct '09

16 Oct '09

Hi, I was trying to create complete rpm package for my system, containing dovecot 1.2.5 intregrated with dovecot-sieve and dovecot-managesieve. Finally I succeeded and it works great, but I found something that might be treated as wrong behaviour... When you run ./configure --with-docs=no, Makefile does not build docs anymore, but... installs them anyway :) It caused some troubles because rpmbuild complained about documents moved to <buildroot>/usr/share/doc/dovecot I have created a small patch that fixes this - hope it doesn't introduce any mess: diff -Nur 2/Makefile.in 1/Makefile.in --- 2/Makefile.in 2009-09-29 00:17:22.000000000 +0200 +++ 1/Makefile.in 2009-09-29 00:17:38.000000000 +0200 @@ -75,7 +75,7 @@ distclean-recursive maintainer-clean-recursive ETAGS = etags CTAGS = ctags -DIST_SUBDIRS = src doc +DIST_SUBDIRS = $(SUBDIRS) DISTFILES = $(DIST_COMMON) $(DIST_SOURCES) $(TEXINFOS) $(EXTRA_DIST) distdir = $(PACKAGE)-$(VERSION) top_distdir = $(distdir) Best regards, -- Jacek Osiecki joshua(a)ceti.pl GG:3828944 I don't want something I need. I want something I want.

2 1

[Dovecot] Questions regarding dbox migration
by Mikkel 16 Oct '09

16 Oct '09

It has been my wish to move to dbox for a long time hoping to reduce the number of writes which is really killing us. Now I wonder what may be the best way of doing so. I'm considering some sort of intermediate migration where the existing Maildir users are changed to single-dbox and then later upgraded to 2.0 and changed to multi-dbox when it becomes stable. But is this a reasonable task to perform on a production system or at all? The alternative is to wait for 2.0 to become completely stable and then go all the way at once. I would however much prefer to take it one step at a time and I think it would be safer to start out with single-dbox as it appears less complex. Now the big question is whether multi-dbox and single-dbox are compatible formats. If a Maildir->dbox migration is made on a system running dovecot v. 1.1, would it then be trivial later changing to multi-dbox after upgrading to 2.0 or is a completely new migration then needed? Would this scenario be much different if the system is upgraded to version 1.2 before the change to single-dbox? Kind regards, Mikkel

5 31

[Dovecot] master:Error @2.0 TLS login, "Too large auth data_size sent"
by PGNet Dev 16 Oct '09

16 Oct '09

fyi, hg log | head -n 7 | grep changeset changeset: 10074:1d2d55d9779e @ LOGIN via Tbird ... Oct 15 11:22:35 master: Error: service(imap-login): Too large auth data_size sent Oct 15 11:22:35 imap-login: Info: Disconnected: Shutting down (auth failed, 1 attempts): user=<blakers(a)mx.pgnetwork.net>, method=PLAIN, rip=192.168.1.4, lip=192.168.1.14, TLS

4 16