- dovecot - dovecot.org

[Dovecot] ot: execute a script via email?
by Voytek Eymont 22 Jul '12

22 Jul '12

anyone has any tips what's best way to execute a script via email ? I have a wget script that fetches some pages, and, emails me the output, there is no paramters passed, it's all in the script I'll like to email in and action the script to get the results email -- Voytek

5 16

[Dovecot] Upgrade Problem from 2.0.18 to 2.1.7
by Michael Domann 22 Jul '12

22 Jul '12

hi there, i'm running a debian wheezy in a chroot at a fritzbox 7230, running with freetz. Running well until the upgrade of version 2.1.7 from debian repros comming up. after upgrade, the server comes up, but login is not possible. Jul 20 20:13:46 master: Warning: Killed with signal 15 (by pid=15309 uid=0 code=kill) Jul 20 20:13:46 master: Info: Dovecot v2.1.7 starting up (core dumps disabled) Jul 20 20:14:15 lda: Debug: Loading modules from directory: /usr/lib/dovecot/modules Jul 20 20:14:15 lda: Debug: Loading modules from directory: /usr/lib/dovecot/modules Jul 20 20:14:15 lda: Debug: Module loaded: /usr/lib/dovecot/modules/lib90_sieve_plugin.so Jul 20 20:14:15 lda(mdomann): Debug: Effective uid=1000, gid=1000, home=/home/mdomann Jul 20 20:14:15 lda: Debug: Module loaded: /usr/lib/dovecot/modules/lib90_sieve_plugin.so Jul 20 20:14:15 lda(mdomann): Debug: Namespace : type=private, prefix=, sep=, inbox=yes, hidden=no, list=yes, subscriptions=yes location=maildir:/home/mdomann/Mail:LAYOUT=fs Jul 20 20:14:15 lda(mdomann): Debug: fs: root=/home/mdomann/Mail, index=, control=, inbox=/home/mdom ann/Mail, alt= Jul 20 20:14:15 lda(mdomann): Debug: Effective uid=1000, gid=1000, home=/home/mdomann Jul 20 20:14:15 lda(mdomann): Debug: Namespace : type=private, prefix=, sep=, inbox=yes, hidden=no, list=yes, subscriptions=yes location=maildir:/home/mdomann/Mail:LAYOUT=fs Jul 20 20:14:15 lda(mdomann): Debug: fs: root=/home/mdomann/Mail, index=, control=, inbox=/home/mdom ann/Mail, alt= Jul 20 20:14:15 lda(mdomann): Debug: userdb lookup skipped, username taken from USER environment Jul 20 20:14:15 lda(mdomann): Debug: none: root=, index=, control=, inbox=, alt= Jul 20 20:14:15 lda(mdomann): Debug: userdb lookup skipped, username taken from USER environment Jul 20 20:14:15 lda(mdomann): Debug: none: root=, index=, control=, inbox=, alt= Jul 20 20:14:16 lda(mdomann): Debug: Destination address: mdomann(a)fritz.fonwlan.box (source: user@ho stname) Jul 20 20:14:16 lda(mdomann): Debug: Destination address: mdomann(a)fritz.fonwlan.box (source: user@ho stname) Jul 20 20:14:16 lda(mdomann): Debug: sieve: include: sieve_global_dir is not set; it is currently no t possible to include `:global' scripts. Jul 20 20:14:16 lda(mdomann): Debug: sieve: include: sieve_global_dir is not set; it is currently no t possible to include `:global' scripts. Jul 20 20:14:16 lda(mdomann): Debug: sieve: using sieve path for user's script: /home/mdomann/.dovec ot.sieve Jul 20 20:14:16 lda(mdomann): Debug: sieve: using sieve path for user's script: /home/mdomann/.dovec ot.sieve Jul 20 20:14:16 lda(mdomann): Debug: sieve: opening script /home/mdomann/.dovecot.sieve Jul 20 20:14:16 lda(mdomann): Debug: sieve: opening script /home/mdomann/.dovecot.sieve Jul 20 20:14:16 lda(mdomann): Debug: sieve: script binary /home/mdomann/.dovecot.svbin successfully loaded Jul 20 20:17:15 imap: Error: dovecot/imap: error while loading shared libraries: libpthread.so.0: failed to map segment from shared object: Cannot allocate memory Jul 20 20:17:15 imap: Fatal: master: service(imap): child 22594 returned error 127 Jul 20 20:17:15 master: Error: service(imap): command startup failed, throttling for 2 secs Jul 20 20:17:15 imap-login: Error: read(imap) failed: Connection reset by peer Jul 20 20:17:15 imap-login: Info: Internal login failure (pid=22586 id=1) (internal failure, 1 succesful auths): user=<mdomann>, method=PLAIN, rip=192.168.2.105, lip=192.168.2.1, TLS, session=<gHEKlUjFNQDAqAJp> the libary is still there fritz:~# ldd /usr/sbin/dovecot libdovecot.so.0 => /usr/lib/dovecot/libdovecot.so.0 (0x2aaaa000) libc.so.6 => /lib/mips-linux-gnu/libc.so.6 (0x2ab48000) libdl.so.2 => /lib/mips-linux-gnu/libdl.so.2 (0x2accc000) librt.so.1 => /lib/mips-linux-gnu/librt.so.1 (0x2ace0000) /lib/ld.so.1 (0x55550000) libpthread.so.0 => /lib/mips-linux-gnu/libpthread.so.0 (0x2acfa000) the ulimit i have tried, but without success. root@fritz:/var/mod/root# ulimit -a -f: file size (blocks) unlimited -t: cpu time (seconds) unlimited -d: data seg size (kb) unlimited -s: stack size (kb) unlimited -c: core file size (blocks) unlimited -m: resident set size (kb) unlimited -l: locked memory (kb) unlimited -p: processes unlimited -n: file descriptors 16384 -v: address space (kb) unlimited -w: locks unlimited fritz:~# dovecot -n # 2.0.18: /etc/dovecot/dovecot.conf # OS: Linux 2.6.28.10 mips Debian wheezy/sid squashfs base_dir = /var/run/dovecot/ default_client_limit = 100 default_process_limit = 50 default_vsz_limit = 6 M disable_plaintext_auth = no lda_mailbox_autocreate = yes listen = * log_path = /var/log/dovecot login_greeting = Dovecot on sysiphus ready. mail_debug = yes mail_gid = 1000 mail_location = maildir:/home/mdomann/Mail:LAYOUT=fs mail_uid = 1000 namespace { hidden = no inbox = yes list = yes location = prefix = subscriptions = yes type = private } passdb { args = scheme=CRYPT username_format=%u /etc/dovecot/users driver = passwd-file } plugin { mail_log_events = delete undelete expunge copy mailbox_delete mailbox_rename mail_log_fields = uid box msgid size sieve = ~/.dovecot.sieve sieve_dir = ~/sieve sieve_global_path = /etc/dovecot/dovecot.sieve } postmaster_address = mdomann@localhost protocols = " imap" service anvil { client_limit = 210 } service auth-worker { user = $default_internal_user } service auth { unix_listener /var/spool/postfix/private/auth { mode = 0666 } unix_listener auth-userdb { group = mdomann mode = 0777 user = mdomann } } service imap-login { inet_listener imap { port = 143 } inet_listener imaps { port = 993 ssl = yes } service_count = 1 } service lmtp { unix_listener lmtp { mode = 0666 } } ssl_cert = </etc/ssl/certs/dovecot.pem ssl_key = </etc/ssl/private/dovecot.pem syslog_facility = debug userdb { args = username_format=%u /etc/dovecot/users driver = passwd-file } verbose_proctitle = yes protocol lda { mail_plugins = " sieve" syslog_facility = mail } protocol imap { imap_client_workarounds = tb-extra-mailbox-sep imap_idle_notify_interval = 24 mins mail_max_userip_connections = 20 } root@fritz:/var/mod/root# free -m total used free shared buffers Mem: 59512 52260 7252 0 2452 -/+ buffers: 49808 9704 Swap: 538608 8116 530492 I have no idea to solve this. The question is, is it possible a bug in debian wheezy mips or in dovecot. Hopefully someone can point me in the right direction. thanks and regards micha

4 5

[Dovecot] Performance based choices
by Hans J. Albertsson 22 Jul '12

22 Jul '12

I've stopped trying to find a HowTo that suits me right away, and instead I am happily trudging thru the Dovecot wiki, article by article. I have right up front thought of one question, a general one, and some detailed versions of that same question: Generally, is there much general performance and reliability background data available for making the basic choices? Say: 1st. delivery: maildrop or LDA or LMTP? I tend to think LMTP should be the ideal choice for me, from what I've gleaned so far. Above all it means that there's only one conceptual thing that needs to know, and postfix and other stuff can safely let dovecot deal with accessing and finding mailboxes. And it won't start and stop thousands of processes. 2nd. mailbox format: Maildir and mbox are the older forms. Are there any advantages to using dovecot's dbox instead? mdbox strikes me as having the potential for being a fast and reliable format. Is that an accurate impression? And, is mdbox mature enough for me to forget maildir and mbox? 3rd. I'm aiming for a poor man's High Availability system: I'm using zfs, and I'm hoping to place all config data for dovecot and postfix and everything else in one zfs file system, and all the user owned data (what should normally go in a home directory) in another (or two or three other) zfs file systems. Then I'm planning to copy over all data at regular intervals, to a second, normally passive, mail server. If the main server breaks, we'll manually (or using scripts and autodetection) fail over to the passive one, making it active, and turning power off to the failed guy using IPMI. The data transfer is to be zfs send/zfs recv over a separate highly redundant network connection. Is this a reasonable idea, or is there some advantage to letting dsync do some of the copying??? Or is there some totally different alternative? iscsi? 4th. With about a thousand users/accounts: does MySQL pay off? Or is LDAP the way to go? Or will a dovecot-specific passwd-file do the job well enough? Those are the three I'm used to since before. I'd like to stay with the flat file, but not the system password file: we're not going to let users in except into dovecot.

2 1

[Dovecot] Corrupted dbox file - purging found mismatched offsets
by Daniel Parthey 22 Jul '12

22 Jul '12

Hi, we are running a cluster using mdbox on NFS with director+mailbox on each node. After running our daily doveadm purge loop over all users, we got dbox corruption... doveadm user "*" |\ while read username do doveadm -c /etc/dovecot-director/dovecot-director.conf -D purge -u "$username" done For one user (which deleted a lot of messages from his mailboxes today), we got the following error in the dovecot.log: Jul 22 20:10:36 10.129.3.213 dovecot: doveadm(user(a)example.org): Error: Corrupted dbox file /mail/dovecot/example.org/user/mail/storage/m.24 (around offset=1380859): purging found mismatched offsets (1380829 vs 920527, 3/61) Jul 22 20:10:36 10.129.3.213 dovecot: doveadm(user(a)example.org): Warning: mdbox /mail/dovecot/example.org/user/mail/storage: rebuilding indexes What does this message exactly tell me and how to prevent this in the future? Now the indexes are broken and flags are lost. The "storage" directory content of the affected user looks as follows: drwx------ 2 vmail vmail 4096 2012-07-22 20:10 . drwx------ 4 vmail vmail 4096 2012-05-06 12:16 .. -rw------- 1 vmail vmail 99008 2012-07-22 20:10 dovecot.map.index -rw------- 1 vmail vmail 33016 2012-07-22 20:10 dovecot.map.index.log -rw------- 1 vmail vmail 34664 2012-07-22 20:10 dovecot.map.index.log.2 -rw------- 1 vmail vmail 8134 2012-05-16 11:36 m.22 -rw------- 1 vmail vmail 10572466 2012-06-02 23:09 m.24 -rw------- 1 vmail vmail 1380205 2012-05-27 10:59 m.24.broken -rw------- 1 vmail vmail 6506837 2012-06-09 15:42 m.25 -rw------- 1 vmail vmail 18201641 2012-06-17 22:50 m.26 -rw------- 1 vmail vmail 11345293 2012-07-01 14:37 m.28 -rw------- 1 vmail vmail 36707787 2012-07-08 23:05 m.29 -rw------- 1 vmail vmail 6062419 2012-07-15 23:34 m.30 -rw------- 1 vmail vmail 52396198 2012-07-22 20:10 m.31 -rw------- 1 vmail vmail 3067862 2012-07-20 14:31 m.32 -rw------- 1 vmail vmail 44520965 2012-07-20 14:31 m.33 -rw------- 1 vmail vmail 52426605 2012-07-22 20:10 m.34 -rw------- 1 vmail vmail 28984844 2012-07-22 20:10 m.35 -rw------- 1 vmail vmail 14465248 2012-07-22 20:10 m.36 -rw------- 1 vmail vmail 37451127 2012-07-22 20:10 m.37 -rw------- 1 vmail vmail 41494033 2012-07-22 20:10 m.38 -rw------- 1 vmail vmail 52066924 2012-07-22 20:10 m.39 -rw------- 1 vmail vmail 49785529 2012-07-22 20:10 m.40 -rw------- 1 vmail vmail 23509886 2012-07-22 20:10 m.41 -rw------- 1 vmail vmail 29339462 2012-07-22 20:10 m.42 -rw------- 1 vmail vmail 29510420 2012-07-22 20:10 m.43 -rw------- 1 vmail vmail 50896380 2012-07-22 20:10 m.44 -rw------- 1 vmail vmail 8331046 2012-07-22 20:10 m.45 -rw------- 1 vmail vmail 5903744 2012-07-22 20:10 m.46 -rw------- 1 vmail vmail 70281 2012-07-22 20:10 m.47 -rw------- 1 vmail vmail 27397909 2012-07-22 20:10 m.48 -rw------- 1 vmail vmail 3893509 2012-07-22 20:10 m.49 -rw------- 1 vmail vmail 1410097 2012-07-22 20:10 m.50 -rw------- 1 vmail vmail 1905759 2012-07-22 20:10 m.51 -rw------- 1 vmail vmail 51783968 2012-05-06 12:12 m.9 Any hints on how to prevent dbox corruption in this case? And what should I do with the "m.24.broken" file now? Regards Daniel -- https://plus.google.com/103021802792276734820

1 0

[Dovecot] Confusion when trying to set up a first postfix+dovecot mailserver
by Hans J. Albertsson 22 Jul '12

22 Jul '12

I'm trying to set up a first test for a dovecot + postfix (+ many other things) mail server for about 1000 accounts, and I keep stumbling on confusing inconsistencies in the HowTo documents I'm trying to follow. I tried to do a simple setup with virtual users using a howto saying it was for just that and that it's for Dovecot 2.x, and it shows a few text chunks to put in files, and then says it's better to do the changes in the example-config conf file.... And then the whole structure of config files and dirs is totally different from what is implied in the howto. And of course it won't run. Probably because of the structure of a conf.d dir is multiple files, and the instructions are explicitly written for the case of having a single conf file. Can anyone suggest an order in which to read docs that will take me thru w/o being totally confusing? I would very much like to be able to enable bit by bit, rather than have to understand all of dovecot before I can even begin to test it. P.S: I want to setup a server using postfix+dovecot+tls+virtualusers+maildir+dspam+mailman, at least that's the target I'm aiming for. Please suggest a good HowTo for this setup that will not be too confusing. Also, Sorry if I sound like a whining kid: I am new to dovecot and postfix, but I was a software support engineer for Sun for ages, and I should really be able to manage this if I just had some consistent and non-confusing HowTo or Tutorial to follow as a first try.

3 8

[Dovecot] Director for smtp-auth
by Patrick Westenberg 22 Jul '12

22 Jul '12

Hi all, isn't it possible to use the director functionality for smtp-auth too? I have a frontend system for imap and outgoing mails using sasl and I recognized that all sasl username/password combinations are accepted as these credentials aren't checked by the backend servers. Regards Patrick

2 2

[Dovecot] postfix/sendmail configuration
by Gary Partis 20 Jul '12

20 Jul '12

Hi all I have searched the net and cant find anything relating to this. In 15-lda.conf, the default sendmail is used to send messges from Dovecot, such as "out of hours" and "redirected" emails controlled by sieves. However, postfix/sendmail is looking in /etc/postfix/main.cf for the configuration file (as logged in /var/log/maillog), but I have the config file elsewhere, and I even have MAIL_CONFIG setup to point to the true config directory. Is there a method of setting 15-lda.conf sendmail config to ensure it uese the correct postfix config file? Thanks in advance Gary

2 1

Re: [Dovecot] Converting from Maildir format ?
by Nick＠5sg.eu 20 Jul '12

20 Jul '12

Hi Stan, >> I'm still trying to find out if anyone knows the correct >> way to either switch the existing Maildir multiple file >> format to the single file format I believe known as MBox. > Did you restart dovecot after the mailbox_location change? Yup... > Show 'dovecot -n' output It shows it - and 'plugin: convert_mail: mbox:%h/%u/mail' I also changed it in dovecot/conf.d/01-dovecot-postfix.conf Hi Charles, > format known as dbox Running v1.2.9 on Ubuntu v10.4 > The wiki/docs are pretty thorough for basic settings. That's where I got the mbox line above.. Thanks gentlemen, Nick. . . . . -- _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ . . . . . . . . ...---... (Stamp Out Spam and Save Our Servers) http://sosNow.ws -=[ do you know morse code ? ]=- . . . . . . . . _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/

3 2

[Dovecot] Append with literal+ and mailbox over quota
by Ewald Dieterich 19 Jul '12

19 Jul '12

I'm appending a mail with literal+ to a mailbox that is over quota: 1 APPEND INBOX {127+} From: <ewald.dieterich(a)fun.de> To: <ewald.dieterich(a)fun.de> Subject: Quota-Test Message-ID: <abcdefg(a)fun.de> Quota-Test 1 NO [OVERQUOTA] Quota exceeded (mailbox for user is full) 2 NOOP 1 BAD Error in IMAP command APPEND: Invalid arguments. 3 NOOP 3 OK NOOP completed. Somehow the first NOOP is considered to be part of the already failed APPEND. I have to add an empty line after to NO response for the NOOP to work: 1 APPEND INBOX {127+} From: <ewald.dieterich(a)fun.de> To: <ewald.dieterich(a)fun.de> Subject: Quota-Test Message-ID: <abcdefg(a)fun.de> Quota-Test 1 NO [OVERQUOTA] Quota exceeded (mailbox for user is full) 2 NOOP 2 OK NOOP completed. Can somebody confirm this to be bug? Here is the output of doveconf -n # 2.1.8: /usr/local/dovecot-orig/etc/dovecot/dovecot.conf # OS: Linux 2.6.32-5-amd64 x86_64 Debian 6.0.3 ext3 auth_debug = yes auth_verbose = yes debug_log_path = /var/log/dovecot/debug.log disable_plaintext_auth = no info_log_path = /var/log/dovecot/info.log log_path = /var/log/dovecot/error.log mail_debug = yes mail_location = mdbox:/var/spool/dovecot/%2.256Hu/%3.4096Hu/%u mail_plugins = notify mail_log quota acl namespace { inbox = yes location = prefix = INBOX. separator = . type = private } passdb { driver = pam } plugin { acl = vfile autocreate = INBOX.Drafts autocreate2 = INBOX.Sent autocreate3 = INBOX.Trash quota = dict:User quota::file:/var/spool/dovecot/%2.256Hu/%3.4096/%u/dovecot.dict quota_rule = *:bytes=2000 } ssl = no userdb { driver = passwd } protocol imap { mail_plugins = notify mail_log quota acl autocreate imap_quota imap_acl

1 1

[Dovecot] Disable W=<vsize> in filenames
by Daniel Pieper 19 Jul '12

19 Jul '12

Hi, I'm using Dovecot 2.1.8. Is it possible to deactivate the "W=" Maildir filename extension, so that dovecot not add it to maildir filenames?

2 1

[Dovecot] Converting from Maildir format ?
by Nick＠5sg.eu 19 Jul '12

19 Jul '12

Hi again, I'm still trying to find out if anyone knows the correct way to either switch the existing Maildir multiple file format to the single file format I believe known as MBox. Failing that, though it'll mean a LOT of work for me to manually convert all of the existing Maildirs, how do I get dovecot to work in future in MBox single file format. I tried entering 'mail_location = mbox:~/mail:INBOX=/%h/%u' in the 'dovecot.conf', but it still saves each message in a file of its own in the /new /cur /tmp directories ?? Thanks, Nick. . . . . -- _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ . . . . . . . . ...---... (Stamp Out Spam and Save Our Servers) http://sosNow.ws -=[ do you know morse code ? ]=- . . . . . . . . _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/

3 2

[Dovecot] Make a whole mailbox read-only
by Sandro Tosi 19 Jul '12

19 Jul '12

Hello, i've found an old thread [1] where it was stated that a whole mailbox can be made read-only only setting the according permissions on the filesystem side. [1] http://www.mailinglistarchive.com/html/dovecot@dovecot.org/2011-12/msg00300… i'd like to check if it's still the only option we have with dovecot v2.0.18 . Regards, -- Sandro Tosi Product Engineer Shared Hosting Products R&D | Dada.pro eml sandro.tosi(a)register.it

3 5

Re: [Dovecot] Issues with Plus addressing and detail part of subaddress.
by Sean Kamath 19 Jul '12

19 Jul '12

On Jul 17, 2012, at 3:18 AM, Charles Marcus wrote: >> I really thought it would be a simple "here's what you missed", since >> the logs are relatively uninformative... > > The point is, what may appear to be uninformative to you may tell Timo (or someone else who knows what to look for) all they need to know to pinpoint the problem. Whilst I would normally agree, at the same time I've had a fair amount of experience with dovecot and sendmail (been running them for over 10 years). Pigeonhole is new to me, however. . . > One thing I did notice is that you are sending this mail from an internal IP... since most people use very different checks for such mail (bypassing many/most checks), maybe you should be testing from an external address (one that comes in from outside your network)? So I have a DMZ that houses the mail server for my domain, which is where the private addresses are. Connections are passed through the OpenBSD router to the mail server. So testing from an external address would be essentially the same (since the connection to the SMTP server talks to the sendmail process as the /usr/lib/sendmail process). Regardless, my original tests were sending mail from the Mac off-network. > Also, it is always recommended when setting up a new server to start with the latest version... for 2.0.x that would be 2.0.19, but the latest is 2.1.8... When I set it up, 2.0.13 _was_ the latest. :-) I was hoping to avoid the pain of recompiling dovecot and pigeonhole. Not that big a deal, I guess. . . >> lda_original_recipient_header = X-Original-To >> lmtp_save_to_detail_mailbox = yes > > Ok, I think this is the problem... > > Dovecot's LMTP currently does NOT preserve the x-original-to header... in fact, brought this up recently (I was one of the ones interested in Timo adding support for it) on this (and the postfix, which is what I use) on this very list: > > http://www.dovecot.org/list/dovecot/2012-April/065075.html > > Apparently, after Timo discussed this on the postfix list, he determined that it would not be a very significant change for him to make to add support for this header in LMTP and that he would get to it sooner than later, but as of now, it has not been added. Actually, I'm not using lmtp. I whacked the lmtp_save_to_detail_mailbox in an effort to see if that was the issue before I realized I don't have it turned on. dovecot.conf has: protocols = imap though in 20-managesieve.conf I have: protocols = $protocols sieve I just turned it off and restarted dovecot (though lmtp was not running) and re-ran the test with the same result. So, I think what's going on is pretty straightforward. The local mailer definition in the sendmail.cf file is: Mlocal, P=/usr/local/libexec/dovecot/dovecot-lda, F=lsDFMAw5:/|@qSPhn9, S=EnvFromL/HdrFromL, R=EnvToL/HdrToL, T=DNS/RFC822/X-Unix, A=/usr/local/libexec/dovecot/dovecot-lda -d $u This is more or less right out of the wiki. Since dovecot-lda is passed the -d option, it's using that (and only that) for delivery. Since there's no X-Original-To: header, it doesn't really have any option (since the non-envelope-to address might not exist, or point to something other than the end user's mailbox, etc). It would appear that I have two options: 1) Figure out what macro(s) is(are) valid to pass to dovecot-lda with the -a option in the sendmail config file (sendmail.cf). 2) Get sendmail to put "X-Original-To: <address>" in the header. Both would appear to be a sendmail issue, not a dovecot/pigeonhole issue. Everything I find on the web seems to center around how to use plus addressing to accept mail from multiple email address and filter it into a single address for delivery, only to have the local delivery agent break it back out again. That's not my issue. :-( Sean Sean

1 1

[Dovecot] doesn't work at all
by David Drexler 19 Jul '12

19 Jul '12

Hi, I can't seem to get dovecot to work. When I connect with thunderbird, tbird complains that it can't find the settings for my email. When I connect with evolution, it seems to go through all the motions but it doesn't pick up the waiting messages. Those messages are marked Status: O s if it had read them. The log file for tbird looks like this: Jul 18 17:03:21 why dovecot: imap-login: Aborted login (no auth attempts): rip=68.12.110.134, lip=184.176.6.227 Jul 18 17:03:22 why dovecot: imap-login: Aborted login (no auth attempts): rip=68.12.110.134, lip=184.176.6.227 Jul 18 17:03:22 why dovecot: imap-login: Aborted login (no auth attempts): rip=68.12.110.134, lip=184.176.6.227 Jul 18 17:03:22 why dovecot: pop3-login: Aborted login (no auth attempts): rip=68.12.110.134, lip=184.176.6.227 Jul 18 17:03:22 why dovecot: pop3-login: Aborted login (no auth attempts): rip=68.12.110.134, lip=184.176.6.227 Jul 18 17:03:22 why dovecot: pop3-login: Aborted login (no auth attempts): rip=68.12.110.134, lip=184.176.6.227 Jul 18 17:03:22 why dovecot: imap-login: Aborted login (no auth attempts): rip=68.12.110.134, lip=184.176.6.227 Jul 18 17:03:22 why dovecot: pop3-login: Aborted login (no auth attempts): rip=68.12.110.134, lip=184.176.6.227 Jul 18 17:03:22 why dovecot: imap-login: Aborted login (no auth attempts): rip=68.12.110.134, lip=184.176.6.227 Jul 18 17:03:22 why dovecot: pop3-login: Aborted login (no auth attempts): rip=68.12.110.134, lip=184.176.6.227 Jul 18 17:03:22 why dovecot: pop3-login: Aborted login (no auth attempts): rip=68.12.110.134, lip=184.176.6.227 The log file with evolution is: Jul 17 19:36:43 why dovecot: imap-login: Login: user=<ddrex>, method=PLAIN, rip=68. 12.110.134, lip=184.176.6.227, mpid=22717, TLS Jul 17 19:36:43 why dovecot: imap(ddrex): Debug: Effective uid=500, gid=500, home=/ home/ddrex Jul 17 19:36:43 why dovecot: imap(ddrex): Debug: fs: root=/home/ddrex/mail, index=, control=, inbox=/var/mail/ddrex Jul 17 19:46:17 why dovecot: imap(ddrex): Error: Next message unexpectedly corrupte d in mbox file /var/mail/ddrex at 1504 My conf file: # 2.0.9: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-220.23.1.el6.x86_64 x86_64 CentOS release 6.2 (Final) base_dir = /var/run/dovecot/ imap_client_workarounds = "delay-newmail " listen = * mail_debug = yes mail_location = mbox:~/mail:INBOX=/var/mail/%u mail_privileged_group = mail mbox_very_dirty_syncs = yes mbox_write_locks = fcntl passdb { driver = pam } pop3_client_workarounds = outlook-no-nuls oe-ns-eoh protocols = imap pop3 service imap-login { vsz_limit = 64 M } service pop3-login { vsz_limit = 64 M } ssl_cert = </etc/pki/dovecot/certs/dovecot.pem ssl_key = </etc/pki/dovecot/private/dovecot.pem userdb { driver = passwd } -------------------------------------------------------------------- Thanks for any clues. dd

2 2

[Dovecot] SQLite dovecot query caching
by Dominic Malolepszy 19 Jul '12

19 Jul '12

Hi, I am wondering if Dovecot caches SQLite queries, and how well it works in high performance setups. I am particularly interested because in the below thread SQLite has been suggested as a means of Dovecot proxying connections to different ports. http://old.nabble.com/director%3A-non-standart-ports-at-backends-td33991991… Cheers, Dominic.

2 7

[Dovecot] MySQL dict issues
by list＠airstreamcomm.net 18 Jul '12

18 Jul '12

Testing using the mysql dict for quota storage (dovecot-2.0.12-2_127.el5), and ran into a couple issues. First is a permissions issue: dovecot: lmtp(26786, dude(a)test.tld) Error: net_connect_unix(/var/run/dovecot/dict) failed: Permission denied (euid=5000(<unknown>) egid=5000(<unknown>) missing +r perm: /var/run/dovecot/dict, euid is not dir owner) The file /var/run/dovecot/dict is listed with srw------- perms. I changes the perms to srw----rwx and it works, but I would like to figure out how to configure properly to run with the uid and gid 5000 as this is the user for virtual mail. The second issue is that two identical rows are created in the mysql database for each user quota. The next message delivered updates both rows. Here is my quota config: 90-quota.conf: plugin { quota_rule = *:storage=10G quota_rule2 = Trash:storage=+10% } plugin { quota = dict:user::proxy::userquota } dict { userquota = mysql:/etc/dovecot/dovecot-dict-sql.conf.ext } dovecot-dict-sql.conf.ext: connect = host=a.b.c.d dbname=mail user=user password=derp map { pattern = priv/quota/storage table = domain_user_quotas username_field = username value_field = bytes } map { pattern = priv/quota/messages table = domain_user_quotas username_field = username value_field = message_count } The last issue might be a documentation omission. Dovecot warned me that the mysql user did not have DELETE privileges on the quota table: dovecot: dict: Error: sql dict: commit failed: DELETE command denied to user 'user'@'a.b.c.d' for table 'domain_user_quotas' The quota dict documentation (at http://wiki2.dovecot.org/Quota/Dict) does not mention DELETE being needed: MySQL uses the following queries to update the quota. You need suitable privileges. INSERT INTO table (bytes,username) VALUES ('112497180','foo(a)spam.dom') ON DUPLICATE KEY UPDATE bytes='112497180'; INSERT INTO table (messages,username) VALUES ('1743','foo(a)spam.dom') ON DUPLICATE KEY UPDATE messages='1743'; UPDATE table SET bytes=bytes-14433,messages=messages-2 WHERE username = 'foo(a)spam.dom';

2 2

[Dovecot] Dovecot-2.1.8 process imap crashed
by Marcin Mirosław 18 Jul '12

18 Jul '12

Hello! I've just upgraded dovecot from 2.0.18 to 2.1.8 and configured impac. I notice dovecot/imap throws segfault from time to time. I'm not sure i know what steps are needed to reproduce problem. I'm using gentoo, hardened-kernel-3.4.2. Namespaces (and settings for imapc) are keept in database so i'm not sure doveconf would be useful. If would be needed please let me know. Thanks Marcin Core was generated by `dovecot/imap'. Program terminated with signal 11, Segmentation fault. #0 0x000002d0fbf908a2 in mail_storage_set_internal_error (storage=0x0) at mail-storage.c:466 466 mail-storage.c: No such file or directory. in mail-storage.c (gdb) bt #0 0x000002d0fbf908a2 in mail_storage_set_internal_error (storage=0x0) at mail-storage.c:466 #1 0x000002d0fbf5f025 in imapc_noop_callback (reply=<optimized out>, context=<optimized out>) at imapc-storage.c:691 #2 0x000002d0fbf5f07a in imapc_idle_noop_callback (reply=<optimized out>, context=0x2b466158c0) at imapc-storage.c:713 #3 0x000002d0fbf6208a in imapc_connection_abort_commands (conn=0x2b46579c10, disconnected=<optimized out>, keep_retriable=<optimized out>) at imapc-connection.c:271 #4 0x000002d0fbf624be in imapc_connection_disconnect (conn=0x2b46579c10) at imapc-connection.c:371 #5 0x000002d0fbf636b9 in imapc_connection_deinit (_conn=0x2b46579b20) at imapc-connection.c:178 #6 0x000002d0fbf60113 in imapc_client_deinit (_client=0x2b4655b6e8) at imapc-client.c:111 #7 0x000002d0fbf5ea77 in imapc_storage_destroy (_storage=<optimized out>) at imapc-storage.c:275 #8 0x000002d0fbf90600 in mail_storage_unref (_storage=0x2b46558910) at mail-storage.c:417 #9 0x000002d0fbf8a259 in mail_namespace_free (ns=0x2b465588c0) at mail-namespace.c:37 #10 0x000002d0fbf8a784 in mail_namespaces_deinit (_namespaces=0x2b4654c9e8) at mail-namespace.c:437 #11 0x000002d0fbf95311 in mail_user_deinit_base (user=0x2b4654c970) at mail-user.c:29 #12 0x000002d0f940f658 in stats_user_deinit (user=0x2b4654c970) at stats-plugin.c:506 #13 0x000002d0fa86b619 in quota_user_deinit (user=0x2b4654c970) at quota-storage.c:412 #14 0x000002d0fbf95597 in mail_user_unref (_user=<optimized out>) at mail-user.c:153 #15 0x0000002b4461b58e in client_destroy (client=0x2b465891d0, reason=0x0) at imap-client.c:219 #16 0x0000002b44615552 in idle_client_input (ctx=<optimized out>) at cmd-idle.c:113 #17 0x000002d0fbce3767 in io_loop_call_io (io=0x2b46622ff0) at ioloop.c:379 #18 0x000002d0fbce469a in io_loop_handler_run (ioloop=<optimized out>) at ioloop-epoll.c:213 #19 0x000002d0fbce3054 in io_loop_run (ioloop=0x2b46525aa0) at ioloop.c:398 #20 0x000002d0fbccc446 in master_service_run (service=0x2b46525950, callback=<optimized out>) at master-service.c:543 #21 0x0000002b44624e76 in main (argc=1, argv=0x2b46525790) at main.c:389 (gdb) bt full #0 0x000002d0fbf908a2 in mail_storage_set_internal_error (storage=0x0) at mail-storage.c:466 str = 0x2b4651e840 "Internal error occurred. Refer to server log for more information. [2012-07-17 16:06:09]" #1 0x000002d0fbf5f025 in imapc_noop_callback (reply=<optimized out>, context=<optimized out>) at imapc-storage.c:691 storage = <optimized out> #2 0x000002d0fbf5f07a in imapc_idle_noop_callback (reply=<optimized out>, context=0x2b466158c0) at imapc-storage.c:713 mbox = 0x2b466158c0 #3 0x000002d0fbf6208a in imapc_connection_abort_commands (conn=0x2b46579c10, disconnected=<optimized out>, keep_retriable=<optimized out>) at imapc-connection.c:271 cmdp = 0x2b4651e808 cmd = 0x2b466116a0 tmp_array = {arr = {buffer = 0x2b4651e7c8, element_size = 8}, v = 0x2b4651e7c8, v_modifiable = 0x2b4651e7c8} reply = {state = IMAPC_COMMAND_STATE_DISCONNECTED, resp_text_key = 0x0, resp_text_value = 0x0, text_full = 0x2d0fbfe768e "Disconnected from server", text_without_resp = 0x2d0fbfe768e "Disconnected from server"} #4 0x000002d0fbf624be in imapc_connection_disconnect (conn=0x2b46579c10) at imapc-connection.c:371 reconnecting = false #5 0x000002d0fbf636b9 in imapc_connection_deinit (_conn=0x2b46579b20) at imapc-connection.c:178 No locals. #6 0x000002d0fbf60113 in imapc_client_deinit (_client=0x2b4655b6e8) at imapc-client.c:111 client = 0x2b4655c6e0 connp = 0x2b4655c840 __FUNCTION__ = "imapc_client_deinit" #7 0x000002d0fbf5ea77 in imapc_storage_destroy (_storage=<optimized out>) at imapc-storage.c:275 storage = <optimized out> #8 0x000002d0fbf90600 in mail_storage_unref (_storage=0x2b46558910) at mail-storage.c:417 storage = 0x2b4655b5e0 __FUNCTION__ = "mail_storage_unref" #9 0x000002d0fbf8a259 in mail_namespace_free (ns=0x2b465588c0) at mail-namespace.c:37 No locals. #10 0x000002d0fbf8a784 in mail_namespaces_deinit (_namespaces=0x2b4654c9e8) at mail-namespace.c:437 ns = <optimized out> next = 0x2b46550dd0 #11 0x000002d0fbf95311 in mail_user_deinit_base (user=0x2b4654c970) at mail-user.c:29 No locals. #12 0x000002d0f940f658 in stats_user_deinit (user=0x2b4654c970) at stats-plugin.c:506 suser = 0x2b4654e8c8 stats_conn = 0x2b46552170 __FUNCTION__ = "stats_user_deinit" #13 0x000002d0fa86b619 in quota_user_deinit (user=0x2b4654c970) at quota-storage.c:412 quser = 0x2b4654e890 quota_set = 0x2b46551190 #14 0x000002d0fbf95597 in mail_user_unref (_user=<optimized out>) at mail-user.c:153 user = 0x2b4654c970 __FUNCTION__ = "mail_user_unref" #15 0x0000002b4461b58e in client_destroy (client=0x2b465891d0, reason=0x0) at imap-client.c:219 cmd = <optimized out> __FUNCTION__ = "client_destroy" #16 0x0000002b44615552 in idle_client_input (ctx=<optimized out>) at cmd-idle.c:113 ---Type <return> to continue, or q <return> to quit--- client = 0x2b465891d0 #17 0x000002d0fbce3767 in io_loop_call_io (io=0x2b46622ff0) at ioloop.c:379 ioloop = 0x2b46525aa0 t_id = 2 #18 0x000002d0fbce469a in io_loop_handler_run (ioloop=<optimized out>) at ioloop-epoll.c:213 ctx = 0x2b46525e10 events = <optimized out> event = 0x2b46525e80 list = 0x2b465a80a0 io = <optimized out> tv = {tv_sec = 5, tv_usec = 999824} msecs = <optimized out> ret = 1 i = <optimized out> j = <optimized out> call = <optimized out> #19 0x000002d0fbce3054 in io_loop_run (ioloop=0x2b46525aa0) at ioloop.c:398 No locals. #20 0x000002d0fbccc446 in master_service_run (service=0x2b46525950, callback=<optimized out>) at master-service.c:543 No locals. #21 0x0000002b44624e76 in main (argc=1, argv=0x2b46525790) at main.c:389 set_roots = {0x2b4482ad60, 0x0} login_set = {auth_socket_path = 0x2b4651d498 "/var/run/dovecot/auth-master", postlogin_socket_path = 0x0, postlogin_timeout_secs = 60, callback = 0x2b44624804 <login_client_connected>, failure_callback = 0x2b446244fd <login_client_failed>} service_flags = <optimized out> storage_service_flags = MAIL_STORAGE_SERVICE_FLAG_DISALLOW_ROOT username = 0x0 c = <optimized out>

2 2

[Dovecot] expire-tool stops on first box with nothing to expire in it
by Michael Wessel 18 Jul '12

18 Jul '12

Hi, I'm running dovecot 1.2.11 on Centos and have the expire plugin enabled. I've had this in place for some time but until now never actually ran the expire-tool. I'm now trying to put this to use. The expire plugin as such is working fine and also the tool is working fine - up to a point. When I run it with --test it goes through a bunch of boxes and lists the messages it would expunge and the new date being logged at the end. As soon as it hits the first box that has nothing in it that's expired however, it stops and goes no further. As an example here are the last two lines of the output when I just ran it: Info: user(a)domain.com/Trash: timestamp 1342320464 (Sat Jul 14 19:47:44 2012) -> 1342937319 (Sat Jul 21 23:08:39 2012) Info: nextuser(a)domain.com/Trash: stop, expire time in future: Sat Jul 14 20:41:49 2012 If I run it again after the indicated expire time it will now also go through the nextuser(a)domain.com but then again stop as soon as it encounters another user with nothing to expire. As far as I can tell the same happens when I actually run the tool. Harder to tell of course as there is no output, but I can tell that not all boxes are expunged as they should be. Any ideas why this would be? Any way to get debug logging on this? Michael

2 2

[Dovecot] Compile issue Dovecot 2.1.8, OS X 10.6.x
by Jim 18 Jul '12

18 Jul '12

Hey all. I'm running Mac OS X 10.6.4, and had Dovecot 2.0.7 installed built from source. I'm now wanting to upgrade to Dovecot 2.1.8, but I can't get MAKE to finish without errors: ./configure --with-mysql (snip) Install prefix . : /usr/local File offsets ... : 64bit I/O polling .... : kqueue I/O notifys .... : kqueue SSL ............ : yes (OpenSSL) GSSAPI ......... : no passdbs ........ : static passwd passwd-file pam checkpassword sql : -shadow -bsdauth -sia -ldap -vpopmail userdbs ........ : static prefetch passwd passwd-file checkpassword sql : -ldap -vpopmail -nss SQL drivers .... : mysql : -pgsql -sqlite Full text search : squat : -lucene -solr sudo make (snip) Undefined symbols: "_libiconv_open", referenced from: _charset_to_utf8_begin in libcharset.a(charset-iconv.o) "_libiconv", referenced from: _charset_to_utf8_reset in libcharset.a(charset-iconv.o) _charset_to_utf8 in libcharset.a(charset-iconv.o) "_libiconv_close", referenced from: _charset_to_utf8_end in libcharset.a(charset-iconv.o) ld: symbol(s) not found collect2: ld returned 1 exit status make[3]: *** [libdovecot.la] Error 1 make[2]: *** [all-recursive] Error 1 make[1]: *** [all-recursive] Error 1 make: *** [all] Error 2 The reason for the 'sudo make' was to get around a permissions issue, but I don't think that's related to my issue here. I had build Dovecot 2.0.7 and earlier without issue on this system, but I'm a bit stumped on this particular problem. I also found that the configure parameter --with-sql-drivers no longer seems to work, even though it's still shown in the wiki for 2.x. As far as I can tell, I had used this parameter when compiling 2.0.7.

2 4

[Dovecot] Different LDAP filters for different protocols
by James Devine 18 Jul '12

18 Jul '12

Is it possible to query LDAP differently for different protocols? I am using dovecot for both pop3/imap and lmtp deliveries and there are different enable flags in ldap for them. I tried wrapping user_filter inside the protocols in the file dovecot-ldap.conf.ext as shown below but this didn't seem to work. protocol lmtp { user_filter = (&(objectClass=posixAccount)(cn=%u)(active=1)(msmtp=1)) } protocol imap { user_filter = (&(objectClass=posixAccount)(cn=%u)(active=1)(mpop=1)) } protocol pop3 { user_filter = (&(objectClass=posixAccount)(cn=%u)(active=1)(mpop=1)) }

1 1

[Dovecot] outlook and redirect sieve
by Lazy 18 Jul '12

18 Jul '12

Hi Aall, we are having issues with outlook clients, running exchange or lotus being unable to parse the email messages redirected by dovecot's sieve 0.3.1, the command is plain redirect "email(a)lotusmail.xxx"; redirects from mta also work correctly exchange was fixed by removing this commit http://hg.rename-it.nl/dovecot-2.1-pigeonhole/raw-diff/082216ad12d6/src/lib… are there any other modifications to the email body or headers that can make those mesages not parsable for outlook ? looking at http://hg.rename-it.nl/dovecot-2.1-pigeonhole/raw-diff/082216ad12d6/src/lib… maybe removing HEADER_FILTER_NO_CR fromi_stream_create_header_filter() will make redirected messages more in tact ? what can I do to make redirect more verbatim ? Thanks in advance for any information. Regards, Michal Grzedzicki

2 3

[Dovecot] Selective TLS per local IP
by Robert Blayzor 17 Jul '12

17 Jul '12

We have the requirement to provide SSL on some IP addresses, but not others on our servers. Providing SSL is the easy part and we're able to use multiple SSL certificates now. (thanks Timo!) All is working ok, but we several IP hosts that do not require SSL and do not have valid certificates. While we can limit access via a firewall ACL to TLS connect ports (993/995) we can't do so on port 110/143. The problem is that some clients now are smart enough to look for an offered STARTTLS or STLS, and if it's offered, they try to use it. While not normally a problem if your setup for SSL with valid key/certs, if you have a self signed or no CERT at all, it starts connection warnings and errors on the client side. So is there any way possible to turn off advertising of TLS on port or turn it off/on per IP? Something like: ssl = yes ssl_cert = </etc/ssl/cert/default.pem ssl_key = </etc/ssl/cert/default.pem local 10.1.1.1 { protocol imap { ssl_cert = </etc/ssl/cert/site1.pem ssl_key = </etc/ssl/cert/site1.pem } protocol pop3 { ssl_cert = </etc/ssl/cert/site1.pem ssl_key = </etc/ssl/cert/site1.pem } } local 10.1.1.2 { ssl = no } *or* ssl = no local 10.1.1.1 { ssl = yes protocol imap { ssl_cert = </etc/ssl/cert/site1.pem ssl_key = </etc/ssl/cert/site1.pem } protocol pop3 { ssl_cert = </etc/ssl/cert/site1.pem ssl_key = </etc/ssl/cert/site1.pem } } -- Robert Blayzor INOC, LLC rblayzor(a)inoc.net http://www.inoc.net/~rblayzor/

2 4

[Dovecot] files missed from install
by Tim Dickson 17 Jul '12

17 Jul '12

version: using dovecot 2.1.8 or 2.0.12 bug: installation - some files missed details: dovecot-openssl.cnf and mkcert.sh are not copied from the src/doc folder to the installation doc folder on installation (make install) both are referred to in the documentation and are useful. is there any chance of updating the build scripts to include these files? thanks, Tim

3 3

[Dovecot] [PATCH] Interop problem with Cyrus SASL and GSSAPI
by Ben Morrow 17 Jul '12

17 Jul '12

[I sent this a while ago, but it seems not to have made it to the list. I'm resending it having subscribed first; I apologise if anyone get it twice.] I have been trying to get a Postfix mail server using Dovecot SASL to accept GSSAPI AUTH from another Postfix server using Cyrus SASL, and I believe I have found a couple of bugs in Dovecot's GSSAPI implementation. The first problem is that, because of the way the client invokes libsasl, it sends a GSSAPI request which does not ask for mutual authentication. This means that on the server gss_accept_sec_context returns GSS_S_COMPLETE with a zero-length output token. Dovecot currently sends this to the client as a zero-length continuation response, but this is incorrect according to RFC 4752: what it ought to do instead is proceed straight to the security layer negotiations, and send a gss_wrap packet. The second is that Cyrus sends an empty authz identity; that is, the security layer negotiation packet, when gss_unwrapped, is exactly 4 bytes long. Dovecot objects to this, but in RFC 4422 this is explicitly allowed, and means the authz identity is identical to the authn identity. I believe the attached patches (for the 1.2 and 2.1 branches) fix the problem, though I'm not entirely sure if the difference between the p_strndup in mech_gssapi_unwrap and the t_strndup in get_display_name is important. Ben

2 1

[Dovecot] Timeout (180s) while waiting for lock for transaction log file
by Angel L. Mateo 17 Jul '12

17 Jul '12

Hello, We still have problems with our updated dovecot servers... The problem now is that we are having errors like: Jul 9 10:22:02 myotis31 dovecot: lmtp(15431, <user>): Error: Timeout (180s) while waiting for lock for transaction log file /var/indexes/<user>/.INBOX/dovecot.index.log Jul 9 10:22:02 myotis31 dovecot: lmtp(15431, <user>): Error: +4YfCwKS+k9HPAAAmo+UlA: sieve: msgid=<4FFA8700.2080003(a)um.es>: failed to store into mailbox 'INBOX': Internal error occurred. Refer to server log for more information. [2012-07-09 10:19:02] Jul 9 10:22:02 myotis31 dovecot: lmtp(15431, <user>): Error: +4YfCwKS+k9HPAAAmo+UlA: sieve: script /home/pdi/88/185188/.dovecot.sieve failed with unsuccessful implicit keep (user logfile /home/pdi/88/185188/.dovecot.sieve.log may reveal additional details) in the .dovecot.sieve.log all we have is just: sieve: info: started log at Jul 09 10:22:02. error: msgid=<4FFA8700.2080003(a)um.es>: failed to store into mailbox 'INBOX': Internal error occurred. Refer to server log for more information. [2012-07-09 10:19:02]. maildir are in a nfs storage, but indexes are in local disk. I don't know if the problem could be related with a some "specific" messages or something specific to the user, because we are having this problem only with a few users and the problem repeatedly happens when our mta tries to deliver the queued message. Any idea? -- Angel L. Mateo Martínez Sección de Telemática Área de Tecnologías de la Información y las Comunicaciones Aplicadas (ATICA) http://www.um.es/atica Tfo: 868887590 Fax: 868888337

2 1