July 2012 - dovecot - dovecot.org

Re: [Dovecot] what best for anti-spam filter?
by Joseph Tam 24 Jul '12

24 Jul '12

Morten Stevens <mstevens(a)imt-systems.com> writes: > So it is now RFC compliant. Anyway I think delaying mail traffic is not > a good solution. Well, OK, if you not keen on greylisting, you can try greet pausing, which introduces a shorter delay. It tests a bot's patience by inserting a pre-HELO pause. RFC allows 5 minutes before timeout. This is last week's stat for one of my mail server and the count of early-talker or early-disconnecter, almost all of which are bots. A greet pause of over 20s dumps a lot of bots. Expect to whitelist the odd server here and there because they've tuned their servers to some aggressively small RFC non-compliant timeouts. Delay Disconnect/early-talkers 00 = 9 01 = 1 02 = 1 03 = 11 04 = 34 05 = 5 06 = 1 07 = 1 08 = 3 09 = 3 10 = 9 11 = 1 12 = 2 16 = 7 17 = 10 18 = 4 19 = 17 20 = 1161 21 = 431 22 = 61 23 = 43 24 = 13 Joseph Tam <jtam.home(a)gmail.com>

3 2

[Dovecot] Fwd: official dev team position regarding multiple times requested feature (global sieve)
by mailing list subscriber 24 Jul '12

24 Jul '12

forwarding to the proper list address since your reply came with a Reply-To header ---------- Forwarded message ---------- From: mailing list subscriber <mailinglists35(a)gmail.com> Date: Tue, Jul 24, 2012 at 10:24 AM Subject: Re: official dev team position regarding multiple times requested feature (global sieve) To: awilliam(a)opengroupware.us On Mon, Jul 23, 2012 at 11:47 PM, Adam Tauno Williams <awilliam(a)opengroupware.us> wrote: > On Mon, 2012-07-23 at 23:26 +0300, mailing list subscriber wrote: >> With above figure in mind, I'm looking at the history of request for >> ability to have a forced, default, site-wide sieve script that the >> user or any other sieve client is unable to alter (I'll just pick most >> relevant): > > Indeed, this would be terribly useful. > >> 2004, with reference to 2001: >> http://goo.gl/Gbo0k >> 2006: A submitted patch >> http://www.irbs.net/internet/info-cyrus/0612/0231.html >> 2007: A very good synthesis: >> http://goo.gl/Lo33b >> 2010: sieve include implemented in v.2.3.0, still fails to meet above >> requirements > > But you fail to reference an open bug?! > The page at http://cyrusimap.web.cmu.edu/mediawiki/index.php/Report_A_Bug says: "If you are absolutely positive you have discovered a bug[...]". This might be misleading since this is a feature request and not a bug. Leaving the technical details of the proper way to report this I'm still curios if the developers are actually AWARE of these repeated requests. >> With all due respect, what is the development's team position >> regarding this feature and how do the development team see a solution >> that meets both requirements? > > I find "SIEVE scripts assigned to folders are not executed" > <https://bugzilla.cyrusimap.org/show_bug.cgi?id=3617> > > "People forget to cancel their vacation message" > <https://bugzilla.cyrusimap.org/show_bug.cgi?id=2985> > NOTE: this is really a UI issue, IMO, multiple web clients solve this by > generating intelligent scripts. That's another problem with the poor IT guy trying to assemble bricks from different vendors: when he finally is heard, the answer is "uhm, the feature you requested fail beyond the scope of my brick. I'm sorry, I can't do that", even when there is a proposed patch available! If you read carefully all my referenced links you'll find one that is listing other imap servers that support it. From what I've tested, at least one implementation has done this as a global pre-user execution of a script (dovecot) > > I don't see any bugs about a default-user-sieve-script. *BUT* > imapd.conf does offer this option [IMPLEMENTED]: > autocreate_sieve_script: <none> > The full path of a file that contains a sieve script. This script > automatically becomes a user’s initial default sieve filter script. > When this option is not defined, no default sieve filter is created. > The file must be readable by the cyrus daemon. > > Of course, the user can override this. Unfortunately that feature only addresses PROVISIONING of data, which is quite unuseful since cyrus mail admins do this with the auto-* uoa.gr patches (that's another pain that devs refused to include for a long time) - What it lacks is the ability to handle CHANGE (change of default script, or alter existing user scripts).

2 2

[Dovecot] Couple of questions about the logs
by Steve Campbell 23 Jul '12

23 Jul '12

The log entries for imap disconnection shows a "bytes = x/y" format where the x equals bytes sent from client and y equals bytes received from client. Can someone explain that a little better to me, please? In an imap account, does this "y" represent the size of the header information being returned to the client or the amount of data of the email mailbox? Also, is there a way to tell if an email has been deleted (or marked for deletion) when using an imap client? Here's the situation: I've got a user who uses imap when using his phone and webmail. When in the office, he uses a pop3 client on his desktop. He indicates he's missing some emails from the weekend when first turning on his desktop. I know of no way to discover if he's deleted and then purged email from his mailbox using imap clients. I've checked the logs and he does not access his mailbox simultaneously from any of the 3 clients. I can find 31 emails he received since his last pop login on Friday until his first pop login on Monday. The pop login indicates he received only 27 emails during the pop retrieval. I'm a little lost here. Any help would be appreciated in interpreting the logs or suggesting how this might have happened. thanks steve campbell

2 4

[Dovecot] dovecot 2.x via xinetd
by Mathieu Roy 23 Jul '12

23 Jul '12

Hello, I was using dovecot 1.2.x via xinetd with a setup like http://wiki.dovecot.org/InetdInstall Since I upgraded to Debian Wheezy, shipping dovecot 2.x, it no longer works. At best, I end up with stuff like Error: net_connect_unix(anvil) failed: No such file or directory Fatal: Couldn't connect to anvil Any clues? Regards, (add me in Cc in replies, I'm not suscribed to the list) # doveconf -n # 2.1.7: /etc/dovecot/dovecot.conf # OS: Linux 3.2.0-3-amd64 x86_64 Debian wheezy/sid ext4 mail_location = maildir:/home/%n/.Maildir:LAYOUT=fs mail_privileged_group = mail namespace inbox { inbox = yes location = prefix = } passdb { driver = pam } protocols = " imap" ssl_cert = </etc/dovecot/certs/cert-gate.crt ssl_key = </etc/dovecot/certs/cert-gate.key userdb { driver = passwd } -- Mathieu Roy

4 7

[Dovecot] about .dovecot.sieve file can't found for directory
by F.Y 23 Jul '12

23 Jul '12

Hi all : i used roundcube webmail and enable filter(managesieve) . i create some rules ,and the rule save in maildir . ok ..see my dovecot config: # 1.2.15: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-5-686 i686 Debian 6.0.5 ext3 log_path: /var/log/dovecot.log log_timestamp: %Y-%m-%d %H:%M:%S protocols: imap imaps pop3 pop3s managesieve listen(default): * listen(imap): * listen(pop3): * listen(managesieve): *:2000 disable_plaintext_auth: no login_dir: /var/run/dovecot/login login_executable(default): /usr/lib/dovecot/imap-login login_executable(imap): /usr/lib/dovecot/imap-login login_executable(pop3): /usr/lib/dovecot/pop3-login login_executable(managesieve): /usr/lib/dovecot/managesieve-login mail_privileged_group: mail mail_uid: vuser mail_gid: vgroup mail_location: maildir:/home/data/domains/%d/%n/Maildir mail_debug: yes mbox_write_locks: fcntl dotlock mail_executable(default): /usr/lib/dovecot/imap mail_executable(imap): /usr/lib/dovecot/imap mail_executable(pop3): /usr/lib/dovecot/pop3 mail_executable(managesieve): /usr/lib/dovecot/managesieve mail_plugin_dir(default): /usr/lib/dovecot/modules/imap mail_plugin_dir(imap): /usr/lib/dovecot/modules/imap mail_plugin_dir(pop3): /usr/lib/dovecot/modules/pop3 mail_plugin_dir(managesieve): /usr/lib/dovecot/modules/managesieve managesieve_logout_format(default): bytes=%i/%o managesieve_logout_format(imap): bytes=%i/%o managesieve_logout_format(pop3): bytes=%i/%o managesieve_logout_format(managesieve): bytes(in=%i/out=%o) lda: postmaster_address: fy(a)5dshu.com mail_plugins: sieve mail_plugin_dir: /usr/lib/dovecot/modules/lda auth_socket_path: /var/run/dovecot/auth-master auth default: mechanisms: plain login verbose: yes debug: yes passdb: driver: sql args: /etc/dovecot/dovecot-sql.conf socket: type: listen client: path: /var/spool/postfix/private/auth mode: 384 user: postfix group: postfix master: path: /var/run/dovecot/auth-master mode: 384 user: vuser group: vgroup plugin: sieve_dir: /home/data/domains/%d/%n/Maildir/sieve sieve: /home/data/domains/%d/%n/Maildir/.dovecot.sieve I create some rules, it can save for Maildir/sieve ,but can't found .dovecot.sieve on Maildir.. i trying for google and baidu search engine,can't found any help .

2 1

[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