- dovecot - dovecot.org

[Dovecot] Convert plugin question
by Dmitry Filonov 06 Feb '08

06 Feb '08

Hi, Is it possible to change convert plugin, so it would keep old UIDVALIDITY and UIDNEXT after conversion from mbox to Maildir? As far as I can tell, this shouldn't be a big problem as this information already exists in the mbox. Well, at least for mboxes, that have that information. The problem is easy, if UIDVALIDITY changes during conversion, then client has to reload whole mailbox from the server. And this is not easy for users with 5+ Gb of mail. Thanks, FiL

5 8

[Dovecot] Sieve
by Fred Newtz 06 Feb '08

06 Feb '08

Alright, so I know I need to get sieve installed. Seems fairly easy to make happen. However, in the documentation it tells me to find dovecot-config and supply that directory into the --with-dovecot= configuration option. For some reason I do not have that file on my machine. I have used find / -name 'dovecot-config' to search for it and it is not there. Is it going to be a problem that the file is not on my machine? Thanks, Fred

2 1

[Dovecot] LDA postfix + deliver, problem lookup, accepting email for everyone
by Sylvain Viart 06 Feb '08

06 Feb '08

Hi, I'm setting up dovecot pop3 deamon for a small set of mailbox. I want to be able to set a small set of mailbox simply, so I've used "passdb passwd-file" + virtual mailboxes with "userdb static". My problem is that it seems that postfix accept and create mailbox for every address I post. It is configured to use local delivery through dovecot's deliver. How do I force deliver to retrun an error if the destination is not defined in the passwd-file? The doc said that "userdb static" should do a lookup automatically. But no luke for me. Is it really a deliver problem, or a postfix configuration problem? Any, hint? Regards, Sylvain. dovecot --version 1.0.rc15 # dovecot -n # /etc/dovecot/dovecot.conf base_dir: /var/run/dovecot/ log_path: /var/log/dovecot/dovecot.log info_log_path: /var/log/dovecot/dovecot-info.log log_timestamp: %Y-%m-%d %H:%M:%S protocols: pop3 ssl_disable: yes disable_plaintext_auth: no login_dir: /var/run/dovecot/login login_executable: /usr/lib/dovecot/pop3-login first_valid_uid: 8 last_valid_uid: 8 first_valid_gid: 8 last_valid_gid: 8 mail_extra_groups: mail mail_location: maildir:/var/mail/%u mail_executable: /usr/lib/dovecot/pop3 mail_plugin_dir: /usr/lib/dovecot/modules/pop3 pop3_uidl_format: %08Xu%08Xv auth default: verbose: yes debug: yes passdb: driver: passwd-file args: /etc/dovecot/passwd.dovecot userdb: driver: static args: uid=mail gid=mail home=/var/mail/%u allow_all_users=no socket: type: listen client: master: path: /var/run/dovecot/auth-master mode: 432 user: mail group: mail Also in postfix : dovecot_destination_recipient_limit = 1 virtual_mailbox_domains = my.domain.com virtual_transport = dovecot # UID/GID mail virtual_uid_maps = static:8 virtual_gid_maps = static:8 + master.cf # pop3 deliver dovecot dovecot unix - n n - - pipe flags=DRhu user=mail:mail argv=/usr/lib/dovecot/deliver -f ${sender} -d ${recipient}

3 4

Re: [Dovecot] LDA postfix + deliver, problem lookup, accepting email for everyone
by Sylvain Viart 06 Feb '08

06 Feb '08

Hi Charles Charles Marcus a écrit : >> dovecot --version >> 1.0.rc15 > > Please upgrade first - this is very old. Yep, you're right, but it's debian etch package version. Is it known to be broken, using this version? I've fought with other software compilation, if I can avoid to do it one more time... Thanks noticing that. Regards, Sylvain.

1 0

[Dovecot] High availability strategies?
by Ed W 06 Feb '08

06 Feb '08

Anyone here trying any "high availability" strategies for mail servers? (Ralph what do you do?) I am reading up a little on DRBD + OCFS for a master/master setup but this doesn't seem to address how to avoid having a single master proxy process (assuming that we are running on rented equip and don't have ability to shift IP addresses around servers). It appears to be possible to play games with DNS and short expiries, but this causes extra DNS traffic for the general case when we are up and running? We had some bad ram in a server recently and it's the worst possible situation. Server locking up, downtime, but it's not easy to repro and fix... (only happens every few days. Memcheck found nothing...) How could we redesign our setup to be resilient against this? (How does Google or Yahoo do it?) For reference I am using vservers to host dovecot and this is working very nicely and makes it real simple to chuck the config onto another host and test things (upgrades, etc). Highly recommended. Any suggestions (from people who have tried stuff)? Cheers Ed W

1 0

[Dovecot] ssl-parameters.dat.tmp missing
by Zbigniew Szalbot 05 Feb '08

05 Feb '08

Hello, My dovecot works well but I have noticed in logs the following line: Feb 5 09:19:51 lists dovecot: ssl-build-param: Can't create temporary SSL parameters file /var/lib/dovecot/ssl-parameters.dat.tmp: No such file or directory I am not sure when it first appeared but I have not seen it before (and I am using dovecot for more almost 2 years now). $ dovecot -n # 1.0.10: /usr/local/etc/dovecot.conf base_dir: /var/run/dovecot/ protocols: imap imaps pop3 pop3s ssl_cert_file: /etc/ssl/certs/cert.pem ssl_key_file: /etc/ssl/certs/key.pem disable_plaintext_auth: no shutdown_clients: no login_dir: /var/run/dovecot/login login_executable(default): /usr/local/libexec/dovecot/imap-login login_executable(imap): /usr/local/libexec/dovecot/imap-login login_executable(pop3): /usr/local/libexec/dovecot/pop3-login login_greeting: Welcome. Dovecot is ready. login_max_processes_count: 200 verbose_proctitle: yes first_valid_uid: 26 first_valid_gid: 0 mail_extra_groups: mailnull default_mail_env: maildir:/var/spool/virtual/%d/%n/Maildir mail_location: maildir:/var/spool/virtual/%d/%n/Maildir mail_executable(default): /usr/local/libexec/dovecot/imap mail_executable(imap): /usr/local/libexec/dovecot/imap mail_executable(pop3): /usr/local/libexec/dovecot/pop3 mail_plugin_dir(default): /usr/local/lib/dovecot/imap mail_plugin_dir(imap): /usr/local/lib/dovecot/imap mail_plugin_dir(pop3): /usr/local/lib/dovecot/pop3 imap_client_workarounds(default): delay-newmail outlook-idle netscape-eoh tb-extra-mailbox-sep imap_client_workarounds(imap): delay-newmail outlook-idle netscape-eoh tb-extra-mailbox-sep imap_client_workarounds(pop3): outlook-idle pop3_uidl_format(default): pop3_uidl_format(imap): pop3_uidl_format(pop3): %08Xu%08Xv 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: sql args: /usr/local/etc/dovecot-sql.conf userdb: driver: sql args: /usr/local/etc/dovecot-sql.conf socket: type: listen client: path: /var/run/dovecot/auth-client mode: 432 master: path: /var/run/dovecot/auth-master mode: 384 user: root group: wheel Thank you for pointers as to what to do to fix that warning. Zbigniew Szalbot

3 4

[Dovecot] proxy logging
by diego 05 Feb '08

05 Feb '08

Hi, I'm testing dovecot 1.1.beta14 on two debian etch with drbd+ocfs2[active/active], I use qmail+vpopmail(userdb) and three front-end with openbsd 4.2 with dovecot 1.1.beta14 as proxy with passdb sql through vpopmail database. Is posible to add logs into vpopmail.vlog from proxys?, like "update vlog blah blah..." or in other sql database? I tried with post login scripting but I don't recibe any variable. Please, sorry my poor english. Regards,. debian backend servers: # 1.1.beta14: /etc/dovecot.conf log_path: /var/log/dovecot.log info_log_path: /var/log/dovecot.log protocols: imap pop3 ssl_disable: yes disable_plaintext_auth: no login_dir: /usr/local/dovecot/var/run/dovecot/login login_executable(default): /usr/local/dovecot/libexec/dovecot/imap-login login_executable(imap): /usr/local/dovecot/libexec/dovecot/imap-login login_executable(pop3): /usr/local/dovecot/libexec/dovecot/pop3-login login_process_per_connection: no mail_max_userip_connections: 2048 verbose_proctitle: yes mail_debug: yes mmap_disable: yes mail_executable(default): /usr/local/dovecot/libexec/dovecot/imap mail_executable(imap): /usr/local/dovecot/libexec/dovecot/imap mail_executable(pop3): /usr/local/dovecot/libexec/dovecot/pop3 mail_plugins(default): quota imap_quota mail_plugins(imap): quota imap_quota mail_plugins(pop3): mail_plugin_dir(default): /usr/local/dovecot/lib/dovecot/imap mail_plugin_dir(imap): /usr/local/dovecot/lib/dovecot/imap mail_plugin_dir(pop3): /usr/local/dovecot/lib/dovecot/pop3 imap_client_workarounds(default): delay-newmail netscape-eoh tb-extra-mailbox-sep imap_client_workarounds(imap): delay-newmail netscape-eoh tb-extra-mailbox-sep imap_client_workarounds(pop3): pop3_client_workarounds(default): pop3_client_workarounds(imap): pop3_client_workarounds(pop3): outlook-no-nuls oe-ns-eoh auth default: verbose: yes debug: yes debug_passwords: yes passdb: driver: vpopmail userdb: driver: vpopmail plugin: quota: maildir openbsd frontend servers: # 1.1.beta14: /etc/dovecot.conf log_path: /var/log/dovecot.log info_log_path: /var/log/dovecot.log protocols: imaps pop3s ssl_cert_file: /etc/ssl/dovecot.pem verbose_ssl: yes login_dir: /usr/local/dovecot/var/run/dovecot/login login_executable(default): /usr/local/dovecot/libexec/dovecot/imap-login login_executable(imap): /usr/local/dovecot/libexec/dovecot/imap-login login_executable(pop3): /usr/local/dovecot/libexec/dovecot/pop3-login login_user: _dovecot verbose_proctitle: yes mail_debug: yes fsync_disable: yes mail_drop_priv_before_exec: yes mail_executable(default): /usr/local/dovecot/libexec/dovecot/imap mail_executable(imap): /usr/local/dovecot/libexec/dovecot/imap mail_executable(pop3): /usr/local/dovecot/libexec/dovecot/pop3 mail_plugin_dir(default): /usr/local/dovecot/lib/dovecot/imap mail_plugin_dir(imap): /usr/local/dovecot/lib/dovecot/imap mail_plugin_dir(pop3): /usr/local/dovecot/lib/dovecot/pop3 mail_log_max_lines_per_sec: 0 imap_client_workarounds(default): delay-newmail netscape-eoh tb-extra-mailbox-sep imap_client_workarounds(imap): delay-newmail netscape-eoh tb-extra-mailbox-sep imap_client_workarounds(pop3): pop3_client_workarounds(default): pop3_client_workarounds(imap): pop3_client_workarounds(pop3): outlook-no-nuls oe-ns-eoh auth default: user: nobody verbose: yes debug: yes debug_passwords: yes passdb: driver: sql args: /etc/dovecot-sql.conf userdb: driver: static args: uid=0 gid=0 plugin: quota: maildir mail_log_events: delete undelete expunge copy mailbox_delete mailbox_rename mail_log_fields: uid box msgid size /etc/dovecot-sql.conf: password_query = SELECT pw_clear_passwd AS password, pw_domain AS domain, '192.168.224.2' AS host, 'Y' AS nologin, 'Y' AS nodelay, 'Y' AS proxy FROM vpopmail WHERE pw_name = '%n' AND pw_domain = '%d' limit 1

3 3

[Dovecot] IMAP quotas - Reasonable size?
by Tobias Balle-Petersen 05 Feb '08

05 Feb '08

Hello... I'm setting up dovecot (IMAP only) at an ad-agency (Lots of big files attached to mails). I'm wondering... What would you consider to be reasonable mail quota? My concern is, that some client-software will have problems with huge mailboxes. I was going to give everyone 2GB, but some users demand 15GB+. Does dovecot "prefer" mailboxes within a certain size? Looking forward to hear your thoughts on the subject. Thanks, Tobias Balle-Petersen

3 2

[Dovecot] Quota + MySQL
by Matt Rude 05 Feb '08

05 Feb '08

Hello, Im having problems getting Dovecot to read the quota info from MySQL. My current dovecot.conf file is below. If I run the user_query of: user_query = SELECT 1000 AS uid, 1000 AS gid, maildir AS home FROM mailbox WHERE username = '%u' AND active = '1' Everything works fine but if I run the user_query of: user_query = SELECT 1000 AS uid, 1000 AS gid, maildir AS home, concat('quota=maildir:storage=', floor( mailbox.quota / 1024 )) AS quota FROM mailbox WHERE username = '$u' AND active = '1' if I were to run the query from MySQL the I get: +------+------+----------------------------------+------------------------------+ | uid | gid | home | quota | +------+------+----------------------------------+------------------------------+ | 1000 | 1000 | mattrude.com/lists@mattrude.com/ | quota=maildir:storage=512000 | +------+------+----------------------------------+------------------------------+ If I run the above query I am unable to log into the server: Feb 4 20:06:11 dovecot: imap-login: Internal login failure: user=<lists(a)mattrude.com mythtv(a)mattrude.com From=akstcaloprestimnsdgs(a)alopresti.com File=/tmp/clamav/virus.7Q >, method=PLAIN, rip=192.168.1.10, lip=192.168.1.1, TLS ## Dovecot configuration file #protocols = imap imaps pop3 pop3s protocols = imap imaps login_user = postfix listen = ssl_listen = ssl_disable = no ssl_cert_file = /etc/pki/dovecot/certs/dovecot.pem ssl_key_file = /etc/pki/dovecot/private/dovecot.pem auth_cache_size = 128 auth_cache_ttl = 600 mail_location = maildir:/var/spool/virtualmailboxes/%d/%u/imap/:INBOX=/var/spool/virtualmailboxes/%d/%u/:INDEX=/var/spool/virtualmailboxes/%d/%u/imap/index/ protocol imap { mail_plugins = quota imap_quota } protocol pop3 { mail_plugins = quota } protocol lda { postmaster_address = postmaster(a)mattrude.com hostname = samantha.mattrude.com mail_plugins = cmusieve mail_plugins = quota sieve_global_path = /var/spool/sieve/dovecot.sieve mail_plugin_dir = /usr/lib/dovecot/lda auth_socket_path = /var/run/dovecot/auth-master } auth default { mechanisms = plain digest-md5 cram-md5 userdb sql { args = /etc/dovecot-mysql.conf } passdb sql { args = /etc/dovecot-mysql.conf } user = root count = 2 } dict { } plugin sql { quota = maildir:storage=1048576 quota = maildir:ignore=Trash } If anyone sees what im missing please let me know Thanks -Matt

1 1

[Dovecot] NULL for password and proxy fields
by bill-dovecot＠carpenter.ORG 04 Feb '08

04 Feb '08

In the course of experimenting with getting dovecot proxying to work, I took a guess at two things. These work fine for me, but now I'm wondering if they are "as designed" or just a lucky accident that might stop working in the future. (I'm using dovecot 1.0.rc17, which is the included version in Ubuntu Feisty. (I am aware that some details change in v1.1, and I'm not worried about that right now.) http://wiki.dovecot.org/PasswordDatabase/ExtraFields/Proxy 1. The wiki page says about password forwarding, "Make sure that the authentication succeeds with any given password. You can do this by using empty passwords." I didn't know exactly now to interpret that last part, so I tried returning NULL as the value of the "password" field for proxy cases. That seems to make dovecot skip the password check will forwarding the user-submitted password to the proxy target host. Is that the intent of that part of that wiki page? 2. It looks like any value at all for the "proxy" field in the passdb lookup turns proxying on. The one exception is a value of NULL for "proxy", in which case proxying is not turned on and proxy-related other fields are ignored. Is that how it's intended to work? If someone can give and informend confirmation that this is as-designed, I can add some clarifying remarks on those points on the wiki page. Thanks. -- bill-dovecot(a)carpenter.ORG (WJCarpenter) PGP 0x91865119 38 95 1B 69 C9 C6 3D 25 73 46 32 04 69 D6 ED F3

4 5