- dovecot - dovecot.org

[Dovecot] How does vpopmail support works?
by Oliver Schulze L. 22 Mar '07

22 Mar '07

Hi, I'm still trying to migrate a running qmail + vpopmail to sendmail + dovecot. I need the milter stuff from sendmail. I got sendmail + dovecot running using the migrated tables from the vpopmail DB, but I'm facing the UID problem in pop3. So, now I'm following the vpopmail authdb path. My questions are: - what do I need, a running vpopmail server (lib + binary, etc)? - or only the DB? This is on Centos 4.4 Many thanks Oliver -- Oliver Schulze L. | Get my e-mail after a captcha in: Asuncion - Paraguay | http://tinymailto.com/oliver

1 0

[Dovecot] Wiki needs updating: Dovecot LDA + Dovecot Sieve + Exim
by Stephen Usher 22 Mar '07

22 Mar '07

So as to make sure that Dovecot Sieve's vacation system works Exim has to be forced to generate a "Reply-To:" header in the message (which it doesn't do by default). The current example for using the Dovecot LDA with Exim doesn't do this. Here is a replacement example for the local_delivery transport:- local_delivery: driver = pipe command = /usr/local/libexec/dovecot/deliver -d $local_part message_prefix = message_suffix = log_output delivery_date_add envelope_to_add return_path_add headers_add = Reply-To: ${if def:header_reply-to:{$h_reply-to:}{$h_from:}} #group = mail #mode = 0660 Basically, if the Reply-To: header exists than it merely gets overwritten with itself. If it doesn't then the header is created and the contents of the From header is put into it. If this is not done then the libsieve over restrictive rules (requiring a "Reply-To:" header even though the RFC doesn't require it) will not allow the vacation system to work. Steve -- --------------------------------------------------------------------------- Computer Systems Administrator, E-Mail:-steve@earth.ox.ac.uk Department of Earth Sciences, Tel:- +44 (0)1865 282110 University of Oxford, Parks Road, Oxford, UK. Fax:- +44 (0)1865 272072

3 2

[Dovecot] Doubled mails and UIDs
by Adam Lackorzynski 22 Mar '07

22 Mar '07

Hi, I'm still seeing mails being downloaded twice via POP3 in my setup, running rc27. The log file shows: dovecot: Mar 18 22:08:05 Error: POP3(joe): mbox sync: UID inserted in the middle of mailbox /home/joe/Mail/INBOX (442671 > 80, seq=10, idx_msgs=153) dovecot: Mar 18 22:08:05 Info: POP3(joe): Disconnected: Logged out top=0/0, retr=153/1069109, del=153/153, size=1066449 The next POP3 connect will fetch most of the messages again. dovecot: Mar 18 22:18:48 Info: POP3(joe): Disconnected: Logged out top=0/0, retr=147/1006204, del=147/147, size=1003647 Is there a problem if an incoming message already contains an X-UID header? Might it be worthwhile to remove this header when mails are being delivered (e.g. with procmail)? Thanks, Adam -- Adam adam(a)os.inf.tu-dresden.de Lackorzynski http://os.inf.tu-dresden.de/~adam/

2 4

[Dovecot] rc27 assert, mbox format
by Jeff A. Earickson 22 Mar '07

22 Mar '07

Timo, After several days of flawless work, rc27 gave an assert/core yesterday: Mar 19 00:10:46 karst dovecot: [ID 107833 mail.error] IMAP(user): file mbox-sync-rewrite.c: line 423: assertion failed: (need_space == (uoff_t)-mails[idx].space) Mar 19 00:10:46 karst dovecot: [ID 107833 mail.error] IMAP(user): Raw backtrace: 0x8a51c -> 0x473f4 -> 0x479b0 -> 0x41c50 -> 0x42430 -> 0x431d4 -> 0x43dac -> 0x44040 -> 0x2aa70 -> 0x2afec -> 0x2337c -> 0x23508 -> 0x235f0 -> 0x90c18 -> 0x9043c -> 0x2cfac -> 0x1dbe8 I could see nothing wrong with the user's mailbox, it was not corrupted. My setup: Solaris 10 sparc, mbox format, INBOX NFSv4 mounted from another S10 sparc system, no disk quotas, ZFS filesystem for both the INBOX filesystem and the user's home directory. Unfortunately, I compiled dovecot with Sun's cc compiler, so the gdb traceback is fairly useless. I need to go back to gcc. Jeff Earickson Colby College

2 2

Re: [Dovecot] Dovecot 'suicide'
by John Andrea 21 Mar '07

21 Mar '07

>dovecot: Time just moved backwards by 6 seconds So this will show up when systems move from daylight savings time to standard time ? >As others mentioned, using ntpd avoids this problem entirely. Not entirely. If you need to restart ntpd, the time can jump when catching up with 'step-tickers'.

3 2

[Dovecot] Double homedirs and tilde problems in case of chroot in passwd-file / static dbs.
by Michal Soltys 21 Mar '07

21 Mar '07

Recently I've made the post about "double homedir" problem, but I couldn't recreate it later. Here're the exact steps to make it happen (configuration is at the bottom): 1) set configuration as below with passwd-files 2) clean testms dir (not necessary though) 3) reload dovecot (HUP is enough) 4) access the server with any client using testms user (make sure no other user accesses server before you) - on the first access, dovecot will create /home/vmail/ppgk.com.pl/testms/Maildir under /home/vmail/ppgk.com.pl/testms/ - on every next access, dovecot will access (and create if it doesn't exist) proper Maildir under "single" home path Situation will repeat itself, if dovecot is reloaded (or killed and restarted). It happens to both imap and pop3. Note, that the a single access seems to be enough to "fix" the problem to all the other users in passwd-file, should there be any. The problem seems to be created by chroot specification in passwd-file & static (and possibly when other dbs are used). On the first access, dovecot attempts to recreate whole /home/vmail.... directory structure *after* chrooting to the homedir (or without taking earlier chroot into account), at least that's how it looks from ktrace. If I moved /./ to the left by one subdir, dovecot would attempt to do it under root owned /home/vmail/ppgk.com.pl/ and fail in the process. And so on. Tilde is another problem - if in dovecot.userdb I change - maildir:~/Maildir: to mbox:~/Mail:INBOX=~/inbox: - then single '~' directory will be created under /home/vmail/ppgk.com.pl/testms/, along the inbox file and Mail dir. If INBOX, CONTROL and/or INDEX is specified explicitely in maildir case, '~' won't be created. That leads to the questiom - is tilde allowed in INBOX under mbox storage at all ? I can't check '~' in INBOX/mbox case for system accounts atm though. If you need any more info (like ktrace), let me know. Configuration: openbsd 3.9, i386, dovecot 1.0-rc27 (no post rc27 diffs) dovecot.userdb: testms::10000:10000:Test,,,:/home/vmail/ppgk.com.pl/testms/./::userdb_mail=maildir:~/Maildir: dovecot.passdb: testms:{PLAIN}test: base_dir: /var/dovecot/ protocols: imap imaps pop3 pop3s ssl_listen: * ssl_ca_file: /etc/ssl/cert_bundle.pem ssl_cert_file: /etc/ssl/ca_ppgk/certs/fetch_crt.pem ssl_key_file: /etc/ssl/ca_ppgk/private/fetch_key.pem verbose_ssl: yes login_dir: /var/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: Dovecot IMAP server ready. login_greeting_capability(default): yes login_greeting_capability(imap): yes login_greeting_capability(pop3): no valid_chroot_dirs: /var/mail:/home/regular:/home/vmail verbose_proctitle: yes first_valid_uid: 1999 first_valid_gid: 10 mail_location: mbox:~/Mail:INBOX=/var/mail/%u mail_debug: yes fsync_disable: yes lock_method: fcntl maildir_copy_with_hardlinks: yes mbox_read_locks: fcntl mbox_write_locks: fcntl 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): outlook-idle delay-newmail imap_client_workarounds(imap): outlook-idle delay-newmail 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 debug: yes passdb: driver: passwd-file args: /etc/dovecot.passdb passdb: driver: bsdauth userdb: driver: passwd-file args: /etc/dovecot.userdb userdb: driver: passwd socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: postfix group: postfix master:

2 1

[Dovecot] Index files in .imap directory
by Steven F Siirila 21 Mar '07

21 Mar '07

A few RC releases ago we had a problem where a user's restored home directory contained a .imap folder either from a previous RC release or perhaps it was a different server. In any event, restoration of the user caused problems since Dovecot choked on the restored .imap index files. Removing those index files cleared the problem. I'm wondering if this is still an issue, and therefore whether we need to find and remove all .imap folders prior to archiving users, so that they are not restored with potentially old/bad index files. I would like to NOT have to worry about them, but rather have Dovecot be smart about when to simply re-create them if it detects something it does not like about them. -- Steven F. Siirila Office: Lind Hall, Room 130B Internet Services E-mail: sfs(a)umn.edu Office of Information Technology Voice: (612) 626-0244 University of Minnesota Fax: (612) 626-7593

2 2

[Dovecot] Exceptions to MyNetworks
by chandler.lists＠chapman.edu 21 Mar '07

21 Mar '07

The mynetworks setting is defined here in CIDR notation. I'd like to make an exception for one of our (insecure) machines that shouldn't be allowed to relay through our box, and only attempt local delivery. What's the best way to do this?

2 2

[Dovecot] connection refused
by Steven F Siirila 21 Mar '07

21 Mar '07

We have been increasing our user count and have only run across these errors so far (dovecot-1.0.rc27): Mar 18 02:50:14 myhost.mydomain dovecot: pop3-login: Can't connect to auth server at default: Connection refused Mar 18 04:07:13 myhost.mydomain dovecot: imap-login: Can't connect to auth server at default: Connection refused Mar 18 05:43:14 myhost.mydomain dovecot: pop3-login: Can't connect to auth server at default: Connection refused Mar 18 07:39:38 myhost.mydomain dovecot: imap-login: Can't connect to auth server at default: Connection refused Mar 18 07:58:44 myhost.mydomain dovecot: imap-login: Can't connect to auth server at default: Connection refused Mar 18 09:55:20 myhost.mydomain dovecot: imap-login: Can't connect to auth server at default: Connection refused I presume that the changes Timo made in response to my previous inquiry about refused connections at reboot will fix these. My question is: what do clients see when this situation arises? Is it transparent, or does the client/user end up having to re-connect? -- Steven F. Siirila Office: Lind Hall, Room 130B Internet Services E-mail: sfs(a)umn.edu Office of Information Technology Voice: (612) 626-0244 University of Minnesota Fax: (612) 626-7593

2 1

[Dovecot] pop3 seems to be down sometimes
by Thomas Balsfulland 21 Mar '07

21 Mar '07

hello guys, i am using dovecot v1.0.rc15-1~bpo1 from backports.org on a debian sarge machine as pop3 pop3s imap and imaps server. since some days it seems the pop-server will stop randomly. noone is able get mails, but imap is still working. the logfile says: dovecot: 2007-03-19 16:44:19 Info: auth(default): password(user1(a)domain.de,212.100.55.y): Requested HMAC-MD5 scheme, but we have only MD5 dovecot: 2007-03-19 16:44:20 Info: pop3-login: Login: user=<user1(a)domain.de>, method=PLAIN, rip=212.100.55.y, lip=x.x.x.x, TLS dovecot: 2007-03-19 16:44:23 Info: POP3(user1(a)domain.de): Disconnected: Logged out top=0/0, retr=0/0, del=0/0, size=0 dovecot: 2007-03-19 16:44:24 Info: auth(default): password(user2(a)domain.de,212.100.55.y): Requested HMAC-MD5 scheme, but we have only MD5 dovecot: 2007-03-19 16:44:26 Info: pop3-login: Login: user=<user2(a)domain.de>, method=PLAIN, rip=212.100.55.y, lip=x.x.x.x, TLS dovecot: 2007-03-19 16:44:29 Info: POP3(user2(a)domain.de): Disconnected: Logged out top=0/0, retr=0/0, del=0/0, size=0 dovecot: 2007-03-19 16:47:09 Info: pop3-login: Disconnected: Inactivity: rip=84.181.7.y, lip=x.x.x.x dovecot: 2007-03-19 16:48:51 Info: pop3-login: Disconnected: Inactivity: rip=84.135.196.y, lip=x.x.x.x dovecot: 2007-03-19 16:49:51 Info: pop3-login: Disconnected: Inactivity: rip=84.135.196.y, lip=x.x.x.x dovecot: 2007-03-19 16:50:36 Info: pop3-login: Disconnected: Inactivity: rip=212.100.55.y, lip=x.x.x.x dovecot: 2007-03-19 16:50:51 Info: pop3-login: Disconnected: Inactivity: rip=84.135.196.y, lip=x.x.x.x dovecot: 2007-03-19 16:50:52 Info: pop3-login: Disconnected: Inactivity: rip=84.181.7.y, lip=x.x.x.x dovecot: 2007-03-19 18:06:58 Info: imap-login: Disconnected: rip=195.71.y.z, lip=x.x.x.x, TLS dovecot: 2007-03-19 18:06:58 Info: IMAP(user3): Disconnected: Logged out dovecot: 2007-03-19 18:08:12 Info: pop3-login: Disconnected: Inactivity: rip=84.181.80.y, lip=x.x.x.x dovecot: 2007-03-19 18:08:31 Info: pop3-login: Disconnected: Inactivity: rip=84.135.196.y, lip=x.x.x.x dovecot: 2007-03-19 18:09:02 Info: pop3-login: Disconnected: Inactivity: rip=212.100.55.y, lip=x.x.x.x i dont know when and why this problem occurs. here is my config: protocols = imaps imap pop3s pop3 protocol imap { listen = 127.0.0.1 ssl_listen = x.x.x.x } protocol pop3 { listen = x.x.x.x ssl_listen = x.x.x.x } disable_plaintext_auth = no log_path = /var/log/dovecot.log info_log_path = /var/log/dovecot.log log_timestamp = "%Y-%m-%d %H:%M:%S " ssl_disable = no ssl_cert_file = /etc/ssl/certs/dovecot.pem ssl_key_file = /etc/ssl/private/dovecot.pem mail_location = mbox:/home/vmail/%d/%n:INBOX=/home/vmail/%d/%n:INDEX=/home/vmail/index/%u protocol imap { mail_plugins = quota imap_quota imap_client_workarounds = outlook-idle delay-newmail } protocol pop3 { pop3_uidl_format = %08Xu%08Xv pop3_client_workarounds = outlook-no-nuls oe-ns-eoh } auth_verbose = yes auth default { mechanisms = plain digest-md5 cram-md5 passdb passwd-file { args = /etc/dovecot/mailuser } userdb passwd-file { args = /etc/dovecot/mailuser } user = root } are there any ideas? regards thomas -- thomas balsfulland tbals(a)ctrl-c.de zwischen mut und dummheit liegt nur ein grat der sich durch das vorbereitetsein unterscheidet

2 1