- dovecot - dovecot.org

[Dovecot] Dovecot Top?
by Andrew Hearn 15 Jun '09

15 Jun '09

Hello, We occasional see high load peaks on our mail servers - these generally don't only last a few minutes. 'Top' show imap taking the lots of CPU resources, is there a dovecot 'top' like program to show dovecot which users are taking system resources? Or how else can this kind of thing be tracked down? (v1.1.7) Thanks. Andrew.

2 2

[Dovecot] Sendmail + Deliver as an LDA
by Natan Vermeersch 14 Jun '09

14 Jun '09

Need help with setup/config. Current situation: (dovecot version : 1.1.7) we have system users and virtual users. (with different domains) Virtual users have procmail as LDA Now we want "deliver" to become the LDA I'm confused reading http://wiki.dovecot.org/LDA/Sendmail sendmail.mc: divert(-1) divert(0)dnl include(`/usr/share/sendmail-cf/m4/cf.m4')dnl VERSIONID(`$Id: sendmail-procmail.mc,v 1.2 2004/12/07 01:59:31 g2boojum Exp $')dnl OSTYPE(linux)dnl DOMAIN(generic)dnl define(`PROCMAIL_MAILER_PATH',`/usr/bin/procmail')dnl define(`confDONT_PROBE_INTERFACES',true)dnl define(`ALIAS_FILE', `/etc/mail/aliases')dnl dnl FEATURE(`smrsh',`/usr/sbin/smrsh')dnl dnl FEATURE(`local_lmtp',`/usr/sbin/mail.local')dnl FEATURE(`local_procmail')dnl FEATURE(`redirect')dnl FEATURE(`access_db')dnl FEATURE(`virtusertable',`hash -o /etc/mail/virtusertable')dnl dnl FEATURE(`mailertable')dnl FEATURE(`always_add_domain')dnl FEATURE(`use_ct_file')dnl FEATURE(`use_cw_file')dnl FEATURE(`blacklist_recipients')dnl dnl FEATURE(`relay_entire_domain')dnl dnl MAILER(local)dnl MAILER(smtp)dnl MAILER(procmail)dnl INPUT_MAIL_FILTER(`mimedefang', `S=unix:/var/spool/MIMEDefang/mimedefang.sock, T=S:5m;R:5m')dnl What setup do we need for both system and virtual users ? Help would be appreciated ! thx Natan _________________________________________________________________ Reageer op foto’s van je vrienden en bekijk hun reacties op de jouwe. Gegarandeerd hilariteit! http://www.microsoft.com/belux/nl/windows/windowslive/products/photos.aspx

3 9

[Dovecot] dovecot-antispam and permissions
by Tom Hendrikx 14 Jun '09

14 Jun '09

hi list, I'm having trouble with a new setup. My server is running postfix (2.5.5), dovecot (1.1.7), dspam (3.8.0). These all seems to work with eachother. When I add dovecot-antispam in the mix, the following problem occurs: New mail arrives, postfix hands the mail to dspam using a content_filter, and dspam clasifies the mail, running as the dspam user. Dspam writes its data away in a sqlite database. Mail then gets reinjected into postfix and delivered to the system user by deliver. When I manually classify a mail using dovecot-antispam, dovecot runs dspam classification as the system user. This gives the error "failed to call dspam" in my client, and the message "dspam[20203]: query error: attempt to write a readonly database: see sql.errors for more details". Since the mentioned sql.errors is owned by the system user and not by the "dspam" user, it seems that the re-classification proces is run as that user, so he has no write access to the sqlite db, which is owned by dspam:dspam. I could fix this by manually changing group ownership to the database, but maybe there is a more generic way to solve this? -- Regards, Tom

1 1

[Dovecot] Error compile dovecot 1.1.16
by Yanmarshus 14 Jun '09

14 Jun '09

/* sorry, my english is bad :-( */ There's error i found while compile dovecot 1.1.16 Compiling run on Slackware 12.2 (fresh install) Error in src/dict/main.c line 85 and line 102 dict_drivers_register_all(); and dict_drivers_unregister_all(); I know C so little, and try to add these line to dict.h void dict_drivers_register_all(void) void dict_drivers_unregister_all(void) After this patch, compiling run without error My question, is that right solution ? Thanks.

2 1

[Dovecot] dovecot-1.2-managesieve sieve_dir permissions
by Pascal Volk 13 Jun '09

13 Jun '09

Hi Stephan, I've compiled the latest managesieve code from Sun May 17th 2009. ManageSieve had created the sieve directory with 0770 permissions, but the user's home directory has only 0700 permissions. With dovecot-1.{0,1}-managesieve the permissions was set properly. Regards, Pascal -- The trapper recommends today: cafebabe.0916419(a)localdomain.org

1 0

[Dovecot] Couldn't open INBOX: Timeout while waiting for lock
by Eric Sammons 12 Jun '09

12 Jun '09

Hi, So I've been through google and the dovecot source and have not yet found a reasonable explanation for the 'Timeout while waiting for lock' error. My customer's configuration is utilizes mbox with the following mbox configs. [snip] pop3_lock_session = yes mbox_read_locks = fcntl mbox_write_locks = fcntl mbox_lock_timeout = 300 [/snip] I see from the source that this error can occur in one of two places: mbox_lock_dotlock() mbox_update_locking() Given my customer is using fcntl locking I automatically assume that it is the later where they are hitting the error. While I see in the source these errors are Temporary Errors; I do wonder what is the specific cause and what should we be looking at to address the errors. One thing we have noticed is that the errors do not occur regulararly. For exapmle, there were no such errors reported on June 9 or June 10; however on June 11 and 12 the errors started to appear. Any direction / pointers are greatly appreciated. Thank you! -- Eric L. Sammons, RHCE

2 1

[Dovecot] Dovecot as a (quota) policy server for Postfix
by Wolfram Schlich 12 Jun '09

12 Jun '09

Hi guys, I'm currently experimenting with Postfix, Dovecot and OpenLDAP to setup a mail server hosting virtual users. The standard stuff works fine so far. The only thing that doesn't work as I'd like it to do is Quota. Currently, Dovecot handles/enforces quota through the deliver LDA. When Postfix tries to deliver a mail to a mailbox that is over quota, the deliver LDA bounces the mail back to the sender. I don't like that. I'd rather prefer Postfix to reject the mail right after receiving the '.' DATA termination line and having checked whether the users quota is or would be exceeded. This could work by writing a small Postfix policy server/daemon that does exactly that Dovecot does: - get the user quota limit from userdb (from LDAP in my case) - get the user quota used (from maildirsize in my case) _ check whether the current mail size + quota used exceed the quota limit and if true, reject the mail Of course this would only work for mails going to a single local recipient address, but most of the time, that's just the case. Now I can re-implement that part of functionality from Dovecot in Perl and write such a small policy daemon that does exactly fit my setup (LDAP + maildirsize). There's one thing I'd like much better, though: What about extending Dovecot by a small policy server module for Postfix? Dovecot already has all the code to do the "over quota" checks and supports a great number of combinations for quota limit and used quota storage. My Postfix instance already kinda depends on a running Dovecot due to Dovecot-SASL for SMTP-Authentication and Dovecot-deliver for mail delivery, so it wouldn't introduce a completely new dependency either. Timo (and all others), what do you think about such a Postfix policy server implemented as a part of Dovecot? -- Regards, Wolfram Schlich <wschlich(a)gentoo.org> Gentoo Linux * http://dev.gentoo.org/~wschlich/

3 2

[Dovecot] gmail pop3 fetcher sets my emails as read
by Julien Buratto 12 Jun '09

12 Jun '09

Hello, I'm testing gmail to fetch my emails via POP3 and I've noticed that on the server where I run dovecot, the emails that gmail take, are marked as read when I imap my emails with my thunderbird. As I've noticed that this is not true for the email accounts on another mail environment, I was wondering if anyone of you could sugged where I could change the behaviour. My configuration is: # 1.1.8: /etc/dovecot.conf # OS: Linux 2.6.9-67.0.4.EL i686 CentOS release 4.7 (Final) log_path: /var/log/maillog info_log_path: /var/log/maillog protocols: imap pop3 pop3s disable_plaintext_auth: no login_dir: /var/run/dovecot/login login_executable(default): /usr/libexec/dovecot/imap-login login_executable(imap): /usr/libexec/dovecot/imap-login login_executable(pop3): /usr/libexec/dovecot/pop3-login mail_location: mbox:~/mail/:INBOX=mbox mail_executable(default): /usr/libexec/dovecot/imap mail_executable(imap): /usr/libexec/dovecot/imap mail_executable(pop3): /usr/libexec/dovecot/pop3 mail_plugin_dir(default): /usr/lib/dovecot/imap mail_plugin_dir(imap): /usr/lib/dovecot/imap mail_plugin_dir(pop3): /usr/lib/dovecot/pop3 auth default: cache_size: 1024 verbose: yes passdb: driver: pam args: session=yes cache_key=%u%s dovecot userdb: driver: passwd Thank you for helping -- Julien Buratto

2 3

[Dovecot] Dovecot fails to deliver in mail clients
by Zwelabantu Ngwenya 12 Jun '09

12 Jun '09

Morning I am new to linux and have configured a Postfix + Dovecot Mail server on my SUSE Linux Server 10 SP2 Machine. Postfix works fine I assume as mail gets delivered to user's mailbox or directories. But when I configure a mail client to download mail from the server it finds no mail. When I check the user's mailbox using Webmin mail is delivered. I have also tried to telnet to the server when I do I am able to log in with user's credentials but when I type the list or stat command telnet says there is no mail 0.0Kb. I have tried everything, mail gets delivered to inboxes but telnet and mail clients don't get mail. Please let me know what I am doing wrong Zwelabantu Ngwenya

3 2

[Dovecot] unable to send mails via postfix/dovecot SASL
by Michal Szymanski 11 Jun '09

11 Jun '09

Hello, I have a freshly setup postfix/dovecot mail server (after a server upgrade I decided to change my sendmail/popper conf to something more modern :) It mostly works, there is no problem in sending/receiving mails in local network, both using text clients like mutt or pine dealing with the incoming/outcoming mail directly. Also dovecot works fine with SSL authentication from the outside world (home computers etc) but only for reading the mail. I have been struggling for several days already to get postfix/dovecot/SSL trio to work for sending (relaying) mail from the home computers (but also from local network) via my server to the final recipients, using authenticated connections. I followed http://wiki.dovecot.org/HowTo/PostfixAndDovecotSASL hints for the configuration of postfix and dovecot (see output of dovecot -n and postconf -n commands below). I also uncommented "smtps" line in /etc/postfix/master.cf file (otherwise postfix was refusing any connections to secure SMTP port). For a while, I uncommented also "submission" line there but to no success either. Now when I try to send a mail from my home PC, using Thuinderbird 2.0.0.21, with SSL connection configured for outgoing smtp server (port 465), using username/password, it shows "Connected to server..." message but after a minute or so, it fails saying that the connection to SMTP server failed. The server log shows: 11:51:24 sirius postfix/smtpd[15126]: connect from my_home_pc_name/ip Jun 11 11:52:25 sirius postfix/smtpd[15126]: lost connection after UNKNOWN from from my_home_pc_name/ip Jun 11 11:52:25 sirius postfix/smtpd[15126]: disconnect from my_home_pc_name/ip There are no dovecot-related messages in the log regarding such an attempt. I am not sure whether this is dovecot or postfix problem but, being no expert on either of those, I am asking help to resolve this annoying problem. with best regards, Michal. -------------- dovecon -n -------------------------- # 1.0.7: /etc/dovecot.conf ssl_cert_file: /etc/pki/dovecot/certs/sirius.pem ssl_key_file: /etc/pki/dovecot/private/sirius.key login_dir: /var/run/dovecot/login login_executable(default): /usr/libexec/dovecot/imap-login login_executable(imap): /usr/libexec/dovecot/imap-login login_executable(pop3): /usr/libexec/dovecot/pop3-login mail_location: mbox:~/Mail:INBOX=/var/spool/mail/%u mmap_disable: yes mail_executable(default): /usr/libexec/dovecot/imap mail_executable(imap): /usr/libexec/dovecot/imap mail_executable(pop3): /usr/libexec/dovecot/pop3 mail_plugin_dir(default): /usr/lib64/dovecot/imap mail_plugin_dir(imap): /usr/lib64/dovecot/imap mail_plugin_dir(pop3): /usr/lib64/dovecot/pop3 imap_client_workarounds(default): delay-newmail outlook-idle netscape-eoh imap_client_workarounds(imap): delay-newmail outlook-idle netscape-eoh imap_client_workarounds(pop3): outlook-idle pop3_client_workarounds(default): pop3_client_workarounds(imap): pop3_client_workarounds(pop3): outlook-no-nuls oe-ns-eoh auth default: mechanisms: plain login verbose: yes passdb: driver: pam userdb: driver: passwd socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: postfix group: postfix ----------------- postconf -n ---------------------------- alias_database = hash:/etc/mail/aliases alias_maps = hash:/etc/mail/aliases broken_sasl_auth_clients = yes command_directory = /usr/sbin config_directory = /etc/postfix daemon_directory = /usr/libexec/postfix debug_peer_level = 2 header_checks = regexp:/etc/postfix/header_checks html_directory = no inet_interfaces = all mail_owner = postfix mailbox_command = /usr/bin/procmail mailq_path = /usr/bin/mailq.postfix manpage_directory = /usr/share/man masquerade_domains = astrouw.edu.pl mydestination = $myhostname, localhost.$mydomain, localhost, $mydomain, mail.$mydomain, www.$mydomain, ftp.$mydomain, /etc/mail/local-host-names myhostname = sirius.astrouw.edu.pl newaliases_path = /usr/bin/newaliases.postfix queue_directory = /var/spool/postfix readme_directory = /usr/share/doc/postfix-2.3.3/README_FILES sample_directory = /usr/share/doc/postfix-2.3.3/samples sendmail_path = /usr/sbin/sendmail.postfix setgid_group = postdrop smtp_generic_maps = hash:/etc/postfix/generic smtpd_recipient_restrictions = check_recipient_access hash:/etc/postfix/access, permit_mynetworks, permit_sasl_authenticated, reject_unauth_destination, reject_unlisted_recipient smtpd_sasl_auth_enable = yes smtpd_sasl_path = private/auth smtpd_sasl_security_options = noanonymous smtpd_sasl_type = dovecot unknown_local_recipient_reject_code = 550 --------------------------------------------------------------- -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.

3 7