- dovecot - dovecot.org

[Dovecot] Calculation of suggested vsz_limit values
by Nikolaos Milas 20 Dec '11

20 Dec '11

Hello, I would like to ask on suggested vsz_limit values. Is there any way of calculating such values? How should we determine them? I don't want to risk wrong values (and possible errors) on a production system, if I upgrade to 2.0.16 where vsz_limit values are enforced (I read release notes)! If there is no standard way of calculation, could someone please check the following info and suggest some values? I am running dovecot-2.0.13-1_128.el5 x86_64 RPM on CentOS 5.7 (as a VM on a KVM Host). All accounts are virtual, hosted on LDAP Server. We have about 250 mailboxes of 4GB each (in practice, only a couple of mailboxes ever reach 1GB so we are "over-booking"). It is a relatively low-load server. Memory status and config follows below. Thanks, Nick The server memory condition is as follows: # vmstat procs -----------memory---------- ---swap-- -----io---- --system-- -----cpu------ r b swpd free buff cache si so bi bo in cs us sy id wa st 0 0 92 62400 212324 1299604 0 0 397 235 70 39 4 2 89 4 0 # free -m total used free shared buffers cached Mem: 2010 1951 59 0 207 1269 -/+ buffers/cache: 474 1536 Swap: 2015 0 2015 ---------- Config Start ------------- # 2.0.13: dovecot.conf protocols = imap pop3 mail_location = maildir:~/Maildir/ mail_gid = 500 mail_uid = 500 auth_mechanisms = plain login auth_username_format = %Lu auth_verbose = yes disable_plaintext_auth = no mail_plugins = quota protocol imap { imap_client_workarounds = "delay-newmail " mail_plugins = quota imap_quota } protocol pop3 { mail_max_userip_connections = 3 mail_plugins = quota pop3_client_workarounds = outlook-no-nuls oe-ns-eoh pop3_uidl_format = %08Xu%08Xv } protocol lda { auth_socket_path = /var/run/dovecot/auth-master info_log_path = log_path = mail_plugins = quota postmaster_address = sysadmin(a)example.com sendmail_path = /usr/lib/sendmail } userdb { args = /etc/dovecot/dovecot-usrdb-ldap.conf driver = ldap } passdb { args = /etc/dovecot/dovecot-passdb-ldap.conf driver = ldap } plugin { quota = maildir:User quota quota_rule = *:storage=4G quota_rule2 = Trash:storage=+3%% quota_warning = storage=75%% quota-warning 75 %u quota_warning2 = storage=90%% quota-warning 90 %u } service quota-warning { executable = script /opt/mail1.sh user = vmail unix_listener quota-warning { user = vmail } } service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } unix_listener auth-master { group = vmail mode = 0660 user = vmail } user = root } service imap-login { service_count = 1 vsz_limit = 64 M } service pop3-login { service_count = 1 vsz_limit = 64 M } ssl_ca = </etc/pki/CA/certs/chain.pem ssl_cert = </etc/pki/CA/certs/cert.pem ssl_key = </etc/pki/CA/private/key.pem syslog_facility = local1 ---------- Config End -------------

3 4

[Dovecot] Strange Login / Timeout Sessions
by Carlos Mennens 20 Dec '11

20 Dec '11

I have my webmail application tied to Postfix / Dovecot server & now for some reason the IMAP sessions oddly time out throughout the day and then logging back into the mail system over the web is painfully slow. The only thing I've seen that fixes it is to reload the Dovecot daemon in Linux: /etc/init.d/dovecot reload Once that command is ran, my webmail login is super fast and moving from folder to folder is extremely fast again. Then in about a few hours, the session will time out and this problem repeats. The problem is the same for everyone and not just a few user accounts. Anyone have any idea what I should be looking for or looking at? My Dovecot logs or mixed in /var/log/maillog which is extremely hard to watch live & gets mixed with Postfix, Amavisd, and Postgrey. Any ideas or suggestions to narrow this problem out? I'm running Dovecot-1.0.7-7.el5_7.1. I saw this load on the console today: Error: Dovecot is already running with PID 2334 (read from /var/run/dovecot/master.pid) Fatal: Invalid configuration in /etc/dovecot.conf Below is my configuration file: [root@mail ~]# dovecot -n # 1.0.7: /etc/dovecot.conf protocols: imap ssl_ca_file: /etc/ssl/certs/digicert.crt ssl_cert_file: ***OMIT*** ssl_key_file: ***OMIT*** login_dir: /var/run/dovecot/login login_executable: /usr/libexec/dovecot/imap-login mail_location: maildir:~/Maildir auth default: mechanisms: plain login passdb: driver: pam userdb: driver: passwd socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: postfix group: postfix

2 1

[Dovecot] One important question!
by I M 19 Dec '11

19 Dec '11

Hello!Please, give me a feedback as soon as you can! I need some advice regarding "dovecot self signed certificate" configuration!If you have any experience in working with php IMAP-module that would be useful for me to know what would you say about below: Problem: I can connect to my INBOX through telnet, but I cannot do it through imap-functions (Certificate failure for ...)? My best,Edward.

3 3

[Dovecot] Two important new Pigeonhole v0.3 features
by Stephan Bosch 19 Dec '11

19 Dec '11

Hello Dovecot users, Pigeonhole v0.3 for Dovecot v2.1 has two new features I would like you to play with before I make a first release: 1) The new Sieve editheader extension (http://tools.ietf.org/html/rfc5293) This allows modifying the headers of the message before delivery. This is actually the first implemented extension that can modify the message itself in any way. This feature adds quite a bit of new code that I'd like to see tested more thoroughly. 2) The new sieve-filter tool (documented in the sieve-filter(1) man page upon installation). This allows (re-)filtering messages that are already stored in a particular mailbox. It preserves the assigned IMAP flags and keywords and using the imap4flags extension these can also be modified. It also plays nice with the editheader extension. Judging by postings in this mailing list from the last few years, this is a highly-demanded feature and I'm glad that I finally got around to finish this thing. If the new sieve-filter tool is lacking certain features in your opinion, just let me know. Needless to say: read the man page carefully and watch out with important mail. This is currently only available from the mercurial repository, but if you prefer to have an .rc1 release first, just tell me and I'll make one. The automatic Debian repository already includes these features. Regards, Stephan.

3 4

[Dovecot] IMAP and sieve
by moozer 19 Dec '11

19 Dec '11

I am currently setting up an IMAP server for archiving purposes. The goal is to drag an email to the IMAP folder, and then have a server-side sieve script to put it in the right folder. One of the sources used was this wiki entry http://wiki.dovecot.org/LDA/Sieve/Dovecot I added the mail_plugins = sieve to /etc/dovecot/15-lda.conf and after some exim4 fiddling, mails delivered are filtered by my sieve script. Doing the same for imap delivery (in /etc/dovecot/20-imap.conf) give the following error Dec 19 10:22:09 leon dovecot: imap: Error: dlopen(/usr/lib/dovecot/modules/lib90_sieve_plugin.so) failed: /usr/lib/dovecot/libdovecot-sieve.so.0: undefined symbol: mail_deliver_save_open Dec 19 10:22:09 leon dovecot: imap: Error: Can't load plugin sieve_plugin: Plugin is intended to be used only by binaries: lda lmtp (we're imap) Dec 19 10:22:09 leon dovecot: imap: Fatal: Couldn't load required plugins Dec 19 10:22:10 leon dovecot: imap: Error: dlopen(/usr/lib/dovecot/modules/lib90_sieve_plugin.so) failed: /usr/lib/dovecot/libdovecot-sieve.so.0: undefined symbol: mail_deliver_save_open Dec 19 10:22:10 leon dovecot: imap: Error: Can't load plugin sieve_plugin: Plugin is intended to be used only by binaries: lda lmtp (we're imap) Dec 19 10:22:10 leon dovecot: imap: Fatal: Couldn't load required plugins I notice this part: "plugin is intended to be used only by binaries: lda lmtp (we're imap)" So the question is if it is possible to run sieve server-side sieve scripts on emails copied using IMAP. Suggestions are most welcome. Moozer -- I am running debian testing # dovecot --version 2.0.15

2 2

[Dovecot] DKIM Verification failures
by Nikolaos Milas 18 Dec '11

18 Dec '11

Hi, -- This message refers to the maillist itself rather than to dovecot software -- I have noticed that when I post to this list (only), I get DKIM Verification failure reports from: root(a)moncton.sidefx.com (e.g. for my last post: "DKIM failure report for job 4D27B5DC4E on mail.sidefx.com") root(a)mail.rmacd.com (e.g. for my last post: "DKIM failure report for job B69B3187F1 on mail.rmacd.com") root(a)mx0.roessner-net.de (e.g. for my last post: "DKIM failure report for job 6103B52092 on mx0.roessner-net.de") I have not had other DKIM failure reports from anywhere and I know that we should not have issues with it. An example from gmail: Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of nmilas(a)noa.gr designates 195.251.204.235 as permitted sender) smtp.mail=nmilas(a)noa.gr; dkim=pass header.i=(a)noa.gr So, whom should I contact to investigate this problem? Thanks, Nick

3 3

[Dovecot] logging deletion of emails through IMAP?
by John Brock 16 Dec '11

16 Dec '11

Version 1.2.16: Is there some way to enable logging for when emails are deleted via IMAP? All I see are log entries for users logging in/logging out. It would be nice to know when an email is deleted, and from which IP address the user was logged in when s/he deleted the email. -- John Brock Adeptive Software 303-554-0301 x1

2 1

[Dovecot] simultaneous scripts not running via sieve_before
by Scott Lewis 16 Dec '11

16 Dec '11

Hi again everyone, So I've finally got sieve integration happening on my REHL Postfix/Dovecot server, with private user scripts happily running when users create them. (we user SquirrelMail, so the avelsieve plugin runs the sieve integration). Now I'd like to utilise additional per-user scripts (probably via sieve_before), but I've not been able to get my additional scripts to execute. I am doing the following: a) getting avelsieve to write my redirect script (ie. logging on as user, completing private script wizard, and activating it) b) compiling .dovecot.sieve with sievec c) copying the resultant .dovecot.svbin to sieve/ directory (and renaming it eg redirect.svbin still, it appears that each /home/%u/.dovecot.sieve file is the only one taking effect. Any thoughts on how to make the other ones active? (The idea behind this is to automatically forward all of joeuser@mydomain's incoming mail to somewhere like joeusersbackup(a)gmail.com, for backup reasons. One day, I'll work out how to configure postfix to do this for all outgoing email too, but that's for another day :) Below are what my .conf files look like. Thanks in advance, Scott /etc/dovecot.conf: [code] protocols = imap imaps managesieve listen = * protocol imap { #mail_plugins = sieve quota } ## ## ManageSieve specific settings ## protocol managesieve { # debugging mail_debug = yes #login_executable = /usr/libexec/dovecot/managesieve-login #mail_executable = /usr/libexec/dovecot/managesieve #managesieve_max_line_length = 65536 #managesieve_logout_format = bytes ( in=%i : out=%o ) #managesieve_implementation_string = Cyrus timsieved v2.2.13 } protocol lda { mail_plugins = sieve quota sieve=~/.dovecot.sieve sieve_extentions = +include sieve_dir=~/sieve sieve_before = /home/%u/sieve/redirect.svbin sieve_global_path = /etc/globalsieverc.svbin [/code]

3 3

[Dovecot] Autosubscribe new folders
by For＠ll 15 Dec '11

15 Dec '11

Hi, I have a sieve filter: require ["fileinto","reject","body"]; if header :contains "subject" "NOTE" { if body :content "application/pdf" :contains "" { redirect "notes(a)domena.com"; } else { reject text: Lack attachment PDF! . ; stop; } } When I get a new message, in user folder is automaticly created folder like subject but is not subscribed. What I must settings in dovecot to automaticly subscribe folders to subscriptions files.?

3 4

[Dovecot] dovecot-antispam: pipe backend with spamc failing to parse args
by Micah Anderson 15 Dec '11

15 Dec '11

I'm trying to get the pipe backend to work with the new dovecot-antispam (I was very pleased to see the new version, thanks Johannes!) Before I would run the following over the maildir: spamc -d 10.0.1.109 -L ham < $file 2>&1 > /dev/null now, i'm using dovecot-antispam and mdbox and have the following configured: antispam_backend = pipe antispam_signature = X-Spam-Flag antispam_signature_missing = error antispam_trash_pattern = trash;Trash;Deleted * antispam_spam_pattern_ignorecase = SPAM antispam_pipe_tmpdir = /var/tmp antispam_pipe_program_spam_arg = -L spam antispam_pipe_program_notspam_arg = -L ham antispam_pipe_program = /usr/bin/spamc antispam_pipe_program_args = -d 10.0.1.109 Now, when I move a message to Spam, dovecot-antispam detects it and attempts to run, but it fails: Dec 14 16:22:45 grosbeak [username 10.0.1.74 uid]: antispam: run program failed with exit code 64 Exit code 64 is spamc's exit code for "command line usage error" - but I can't see exactly the command that is being constructed by dovecot-antispam to know where the error is. Any ideas? micah --

2 1