- dovecot - dovecot.org

[Dovecot] Capability info in hello message not complete?
by Michal Hlavinka 23 Oct '09

23 Oct '09

Hi, one Fedora user complains about not some troubles after update to dovecot 1.2. He suspects wrong capability information given by dovecot 1.2 In dovecot.conf he uses imap_capability= option. While response to 'A CAPABILITY' respects imap_capability value, the capability info in hello message does not. for imap_capability=IMAP4 IMAP4rev1 ACL NAMESPACE CHILDREN SORT QUOTA THREAD=ORDEREDSUBJECT UNSELECT IDLE STARTTLS AUTH=PLAIN A CAPABILITY response is: * CAPABILITY IMAP4 IMAP4rev1 ACL NAMESPACE CHILDREN SORT QUOTA THREAD=ORDEREDSUBJECT UNSELECT IDLE STARTTLS AUTH=PLAIN but hello message is: * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE STARTTLS AUTH=PLAIN] Dovecot ready. But it seems even when imap_capability is not used capability in hello message is not complete: * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE STARTTLS AUTH=PLAIN] Dovecot ready. vs. * CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE SORT THREAD=REFERENCES THREAD=REFS MULTIAPPEND UNSELECT IDLE CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH ESORT SEARCHRES WITHIN CONTEXT=SEARCH STARTTLS AUTH=PLAIN is this expected? Do you think capability information in hello message really can befool clients? Regards, Michal Hlavinka

2 7

[Dovecot] HA Dovecot Config?
by dovecot＠corwyn.net 23 Oct '09

23 Oct '09

Hi! I'm currently running Dovecot 1.1.8 on a HP server using CentOS 5.2 as my IMAP server, receiving mail from postfix, and also using squirrelmail as the frontend. As I look at upgrading the mail server, I'd like to change to a higher availability configuration (where the server can fail and I don't have to reconfig my imap users). For the SMTP that's easy, because I can use multiple MX records, and I can redirect a port forward from one server to another. But IMAP doesn't have the same functionality, because it's the storage that matters. What's the "best" way to do that? Clustered servers using a SAN? NAS? some sort of appliance in front? Suggestions? Thanks! Rick Rick Steeves http://www.sinister.net In reality nothing is more damaging to the adventurous spirit within a man than a secure future - Alexander Supertramp

11 16

[Dovecot] doveadm who
by Timo Sirainen 23 Oct '09

23 Oct '09

Pascal Volk suggested this, and it was pretty quick to implement for Dovecot v2.0. Ideas welcome how to improve it, or if it's already perfect :) The first line is written to stderr, so |sort can be used: # doveadm who|sort username # (ips) (pids) timo 1 (127.0.0.1) (2457) tss 2 (127.0.0.1) (617 1345) tss2 2 (127.0.0.2 127.0.0.1) (2392 2799) # doveadm who|sort -k2 -nr username # (ips) (pids) tss2 2 (127.0.0.2 127.0.0.1) (2392 2799) tss 2 (127.0.0.1) (617 1345) timo 1 (127.0.0.1) (2457) You can filter connections: # doveadm who 127.0.0.2 username # (ips) (pids) tss2 2 (127.0.0.2 127.0.0.1) (2392 2799) # doveadm who 127.0.0.0/24 username # (ips) (pids) tss2 2 (127.0.0.2 127.0.0.1) (2392 2799) timo 1 (127.0.0.1) (2457) tss 2 (127.0.0.1) (617 1345) # doveadm who tss username # (ips) (pids) tss2 2 (127.0.0.2 127.0.0.1) (2392 2799) tss 2 (127.0.0.1) (617 1345) # doveadm who tss 127.0.0.1 username # (ips) (pids) tss2 2 (127.0.0.2 127.0.0.1) (2392 2799) tss 2 (127.0.0.1) (617 1345)

1 0

[Dovecot] Need a little shadow to MySQL conversion help
by Marc Perkel 22 Oct '09

22 Oct '09

Excuse me for being stupid and confused. I'm trying to convert my dovecot install from passwd-file to mysql. I have a single table called "users" that has 3 fields, user_name, domain_name and password. The data came from passwd/shadow files so it uses the same password encryption as the shadow files do. The directory where the email is stored is calculated elsewhere and not stored in the database. The UID and GID are both mail for all virtual users. The user logs in passing the full email address and the password. So - what would be the config for using MySQL? Do I even need a userdb? If so - what would it be? Thanks in advance.

4 11

[Dovecot] VZW Blackberry BIS problems?
by B. Cook 22 Oct '09

22 Oct '09

Ever since Columbus day things have been strange with my two dovecot servers, according to my Blackberry users. We do not have a BES just the standard BIS that comes with a personal account. Several people have told me that since that Monday that they get occasional duplicate copies of messages which only appear singularly in their Maildir inboxes. I myself even called VZW and got transferred to RIM themselves where they 'reset' my account; (same as me going into the BIS server and deleting and adding again) only to have the same thing happen; again occasionally.. Below is relevant dovecot info.. -r-xr-xr-x 1 root wheel 164064 Oct 1 17:16 /usr/local/sbin/dovecot (date it was built; prior to any problems.. *whew*) ;) 1 # 1.2.4: /usr/local/etc/dovecot.conf 2 # OS: FreeBSD 7.2-RELEASE-p3 i386 3 ssl_cert_file: /usr/local/etc/lighttpd/ssl/mail.poughkeepsieschools.org.pem 4 ssl_key_file: /usr/local/etc/lighttpd/ssl/mail.poughkeepsieschools.org.pem 5 disable_plaintext_auth: no 6 verbose_ssl: yes 7 login_dir: /var/run/dovecot/login 8 login_executable: /usr/local/libexec/dovecot/imap-login 9 login_greeting: mail.poughkeepsieschools.org OK 10 first_valid_uid: 89 11 last_valid_uid: 89 12 first_valid_gid: 89 13 last_valid_gid: 89 14 maildir_copy_preserve_filename: yes 15 mail_plugins: quota imap_quota 16 imap_client_workarounds: delay-newmail outlook-idle tb-extra-mailbox-sep 17 auth default: 18 mechanisms: plain login 19 user: vpopmail 20 passdb: 21 driver: vpopmail 22 userdb: 23 driver: vpopmail 24 socket: 25 type: listen 26 client: 27 path: /var/run/dovecot/auth-client 28 mode: 438 29 plugin: 30 quota: maildir:User quota 31 expire: Trash 7 Spam 30 Now what does not show here is something that I put in that it looked like it was supposed to help but didn't.. mailbox_idle_check_interval = 30 after looking around at other people complaining about BIS and possible dovecot issues it seemed that that entry was the 'magic' the BIS was missing; except I never had it and never had troubles. I'm assuming this is a BIS issue of some sort, but I can't tell. After looking on the wiki I didn't see anything that says "BIS users look here for tips.. " So I'm assuming there aren't any; I think it should just work with the IMAP server.. Any help would be appreciated as everyone thinks this is 'our problem' and "if we had an exchange server we wouldn't be having these problems.." Thanks in advance..

3 3

[Dovecot] sieve + redirect + as attachment
by Jerry 22 Oct '09

22 Oct '09

Is it possible to use the 'redirect' function in 'sieve' to forward a message as an attachment rather than in-line? -- Jerry gesbbb(a)yahoo.com |::::======= |::::======= |=========== |=========== | A woman was in love with fourteen soldiers, it was clearly platoonic.

3 6

[Dovecot] Public Folders
by Peter Fraser 22 Oct '09

22 Oct '09

Hi All I'm trying to implement public folders. My dovecot -n readout is at the bottom. I created a maildir called resumes in /home/public Its contents are: mail# ls -la /home/public/resumes total 6 drwx------ 3 vmail vmail 512 Oct 22 08:58 . drwx------ 4 vmail vmail 512 Oct 22 08:47 .. drwx------ 5 vmail vmail 512 Oct 22 08:58 Maildir -rw------- 1 vmail vmail 0 Oct 21 18:30 dovecot-acl-list Then I created a directory called resumes in /usr/local/etc/dovecot-acls and in it, I created the file dovecot-acl I put the following entries in dovecot-acl owner lrwstiekxa user=user1 rwl When I connect as user1 in thunderbird, right click on the inbox and go subscribe, I see a greyed out public which I cannot subscribe to. I do not see resumes. Any ideas on why this is? mail# dovecot -n # 1.2.4: /usr/local/etc/dovecot.conf # OS: FreeBSD 7.2-RELEASE-p1 i386 protocols: imap imaps pop3 pop3s ssl_cert_file: /usr/local/etc/dovecot/ssl/certs/dovecot.pem ssl_key_file: /usr/local/etc/dovecot/ssl/private/dovecot.pem ssl_cipher_list: ALL:!ADH!LOW:!SSLv2:!EXP:+HIGH:+MEDIUM disable_plaintext_auth: no login_dir: /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_greeting: Mail Server ready. verbose_proctitle: yes first_valid_uid: 1000 first_valid_gid: 1000 mail_privileged_group: vmail mail_location: maildir:~/Maildir:INBOX=~/Maildir/:INDEX=~/Maildir/tmp/index 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_plugins(default): quota imap_quota acl imap_acl mail_plugins(imap): quota imap_quota acl imap_acl mail_plugins(pop3): quota 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 imap_client_workarounds(default): delay-newmail netscape-eoh tb-extra-mailbox-sep imap_client_workarounds(imap): delay-newmail netscape-eoh tb-extra-mailbox-sep imap_client_workarounds(pop3): pop3_client_workarounds(default): pop3_client_workarounds(imap): pop3_client_workarounds(pop3): outlook-no-nuls oe-ns-eoh dict_db_config: /usr/local/etc/dovecot-db.conf namespace: type: public separator: / prefix: public/ location: maildir:/home/public list: yes subscriptions: yes namespace: type: private separator: / location: maildir:/home/vmail/%u/Maildir inbox: yes list: yes subscriptions: yes lda: mail_plugins: quota acl postmaster_address: postmaster(a)example.com sendmail_path: /usr/sbin/sendmail auth default: mechanisms: plain login username_format: %Lu debug: yes passdb: driver: pam args: session=yes dovecot passdb: driver: ldap args: /usr/local/etc/dovecot-ldap.conf userdb: driver: static args: uid=1002 gid=1002 home=/home/vmail/%u allow_all_users=yes socket: type: listen client: path: /var/run/dovecot/auth-client mode: 432 master: path: /var/run/dovecot/auth-master mode: 384 plugin: quota: maildir quota2: maildir:user quota quota_rule: *:storage=512M quota_rule2: Trash:storage=10M quota_rule3: SPAM:ignore quota_warning: storage=95%% /usr/local/etc/dovecot/quota-warning.sh 95 quota_warning2: storage=80%% /usr/local/etc/dovecot/quota-warning.sh 80 acl: vfile:/usr/local/etc/dovecot-acls:cache_secs=300

2 1

Re: [Dovecot] pop3-login: Fatal: io_loop_handle_add: epoll_ctl(1, 5):
by Brandon Davidson 22 Oct '09

22 Oct '09

Hi Marco, On 10/22/09 1:50 AM, "Marco Nenciarini" <mnencia(a)prato.linux.it> wrote: > This morning it happened another time, another time during the daily > cron execution. > > Oct 22 06:26:57 server dovecot: pop3-login: Panic: Leaked file fd 5: dev > 0.12 inode 1005 > Oct 22 06:26:57 server dovecot: dovecot: Temporary failure in creating > login processes, slowing down for now > Oct 22 06:26:57 server dovecot: dovecot: child 21311 (login) killed with > signal 6 (core dumps disabled) > > I have dovecot 1.2.6 with Timo's patch to check leaked descriptors. I rebuilt the binaries on our hosts with optimization disabled, and I'm still waiting for it to reoccur so I can gather file descriptor information and a core. I don't have the leak-detect patch applied. Let's see what Timo has to say about that log file bit. Since it seems to happen to you fairly frequently, it might be worth enabling core dumps as well? -Brad

2 1

[Dovecot] NFS random redirects
by Thomas Hummel 22 Oct '09

22 Oct '09

Hello, Dovecot documentation states that the "random redirects to multiple servers" NFS solution is to be avoided and I'm investigation the actual risks of it and a way to put it to test. I'm running dovecot-1.2.6 with Maildir (indexes, mailboxes and control files are all on NFS) and I'm using procmail instead of deliver as the LDA. 1. Documentation says : "Dovecot locks the maildir while doing modifications to it or while looking for new messages in it" and then mention the "dovecot-uidlist.lock" dotlock file. a) if that file fcntl'ed in addition (i.e. dotlocked + fcntled or just dotlocked) ? b) is that file THE way to lock the Maildir mentionned above or is it just something else used only for updating that particular file (i.e. is Maildir locked in some way + dovecot-uidlist.lock created or just dovecot-uidlist.lock created) ? 2. Documentation says : "NFS caching is a big problem when multiple computers are accessing the same mailbox simultaneously" I guess it's because of the dotlocks files and not fcntl locking ? Is there anything else than dovecot-uidlist which is dotlocked ? If yes, is it dotlocked only or dotlocked and fcntled ? 3. Documentation says : "Dovecot v1.1 flushes NFS caches when needed if you set mail_nfs_storage=yes" How can a program flush the NFS caches ? By which (system) call ? 4. Documentation says : "Besides the NFS cache problems described above, mailbox contents can't be cached as well in the memory either." Is it about in-memory indexes or part of indexes loaded into memory ? 5. How can I torture-test concurrent access to the same mailbox through 2 dovecot servers ? I don't see imaptest.c anymore on http://dovecot.org/tools but I see 2 nfs_test ? Is there some command line options I should use ? 6. when and why can a random redirect to multiple server can cause mailbox corruption ? On flags only or on content as well ? Thanks -- Thomas Hummel | Institut Pasteur <hummel(a)pasteur.fr> | Pôle informatique - systèmes et réseau

4 9

[Dovecot] deliver+sieve: Destination address (-a) parsing changes
by Frank Behrens 21 Oct '09

21 Oct '09

When I upgraded my old, long running dovecot 1.1 to newer dovecot-1.2.4 + doevecot-sieve- 0.1.12 I observed a change in destination address (-a) parsing. Old behaviour: When Timo introduced this feature (http://www.dovecot.org/list/dovecot/2007-September/025813.html) it was possible to hand over only the detail part. In my sendmail configuration I used "-a +$h", where $h contains the detail part and may be empty. By default sendmail can call the delivery agent with the following information: $u: The recipient user (always set) $h: Detail part, may be empty $g: The sender address (relative to the recipient). New behaviour: The current sieve version needs a complete address with local- and domain-part. Otherwise we get a warning like deliver(user): sieve: envelope recipient address 'user' is unparseable. The problem is, that the domain part is not always available, e.g. for local delivered emails. This is the main problem, although the setup could be simplified if deliver would accept the old syntax. I'm going to make modifications to sendmail to be able to have all address information available, but this will not solve the problem with missing domain. Now comes my question: Is it better to enhance the address parsing in sieve plugin or should I use a wrapper around deliver? The latter is not very difficult, but introduces an additional process (that may fail). Regards, Frank -- Frank Behrens, Osterwieck, Germany PGP-key 0x5B7C47ED on public servers available.

3 7