- dovecot - dovecot.org

[Dovecot] MIME Decoding Problem
by Jim Rosenberg 23 Jan '08

23 Jan '08

I am having a recurring problem with Dovecot 1.0.8 failing to MIME-decode certain messages. The client is Mulberry 4.0.8. The messages causing the problem seem to be MIME messages with "no parts". I.e. the message has some MIME encoding, but is just included as the message body. The kind of effect I will see is a proliferation of untranslated =xx codes, or in some cases an untranslated base64 block. I.e. I see the raw text from the message body with no MIME decoding at all. When this problem happens, if I close the folder, ditch the .imap directory on the server for this folder, and reopen the folder, the problem has gone away, I can view the message just fine. So, I don't believe it's a client problem. (And Mulberry is probably the most IMAP-knowledgeable client out there ...) Below is my dovecot -n listing. -Thanks, Jim ------------------ # 1.0.8: /usr/local/etc/dovecot.conf base_dir: /var/dovecot/ ssl_disable: yes ssl_cert_file: /etc/ssl/dovecotcert.pem disable_plaintext_auth: no login_dir: /var/dovecot/login login_executable: /usr/local/libexec/dovecot/imap-login login_user: _dovecot mail_location: mbox:~/mail:INBOX=/var/mail/%u mail_full_filesystem_access: yes mbox_write_locks: fcntl imap_client_workarounds: delay-newmail outlook-idle netscape-eoh tb-extra-mailbox-sep namespace: type: private separator: / inbox: yes namespace: type: private separator: / prefix: mail/ hidden: yes namespace: type: private separator: / prefix: ~/mail/ hidden: yes auth default: passdb: driver: passwd userdb: driver: passwd

2 3

[Dovecot] Slow header fetching rate over nfs mailspool.
by Dino Ming 23 Jan '08

23 Jan '08

We are setting up a Dovecot over a pair of NFS which mirrored with DRBD +Heartbeat, under Debian Etch AMD64 with Kernel 2.6.22-5. The problem was slow header downloading rate. We had tried to use postal to inject 500 emails which are under 5KB each, but when ever we start up Mail.app, Thunderbird or even OE6, the header download rate is terrible slow. Its look like a few sec for just 1 header download from the strace of the dovecot process, sometime, it maybe longer and this leading to the MUA hang. We had tried dove 1.0.rc15-2etch3, 1.1beta13... and the following configuration is for 1.1beta13. Mount options on Dovecot frontend -------------------------------------------- nfs4 rsize=8192,wsize=8192,hard,fg,proto=tcp,retrans=0,noatime Export option on NFS backend -------------------------------------------- /dap/mail 192.168.2.0 /24(rw,no_subtree_check,no_root_squash,no_all_squash,sync,fsid=0) /dap/mail/mstorage 192.168.2.0/24(rw,no_subtree_check,no_root_squash,no_all_squash,sync) Dovecot Config dump. -------------------------------------------- base_dir = /var/run/dovecot/ protocols = pop3 imap disable_plaintext_auth = no log_path = /var/log/dovecot.log info_log_path = /var/log/dovecot-info.log log_timestamp = "%Y-%m-%d %H:%M:%S " ssl_disable = yes login_dir = /var/run/dovecot/login login_chroot = yes login_user = dovecot login_processes_count = 10 login_max_processes_count = 20 login_process_per_connection = yes mail_debug = yes max_mail_processes = 1024 mail_process_size = 256 mail_location = maildir:~/Maildir:INDEX=/var/indexes/%u (Indexes is putting on local disk, but same with no luck) auth_process_size = 128 auth_cache_size = 32 auth_cache_ttl = 3600 auth_verbose = yes auth_debug = no auth_debug_passwords = no auth_worker_max_count = 50 namespace private { separator = / prefix = INBOX/ inbox = yes } mail_extra_groups = mail mmap_disable = no lock_method = fcntl mail_nfs_storage = yes mail_nfs_index = no dotlock_use_excl = no fsync_disable = no Strace Log file of dovecot during thunderbird download those headers. -------------------------------------------- 17:19:27.670428 open("/dap/mstorage/example.com/dino/Maildir/cur/ 1201079181.H112920P11724.mx01.example.com,S=3841:2,", O_RDONLY) = 11 17:19:27.670631 fstat(11, {st_mode=S_IFREG|0600, st_size=3841, ...}) = 0 17:19:27.670691 pread(11, "Return-path: <dino(a)example.com>\nE"..., 4096, 0) = 3841 17:19:31.725525 pread(11, "", 255, 3841) = 0 17:19:31.725624 pread(11, "Return-path: <dino(a)example.com>\nE"..., 4096, 0) = 3841 17:19:31.725729 pread(11, "Return-path: <dino(a)example.com>\nE"..., 4096, 0) = 3841 17:19:31.725798 close(11) = 0 17:19:31.725887 open("/dap/mstorage/example.com/dino/Maildir/cur/ 1201079181.H210436P11742.mx01.example.com,S=2263:2,", O_RDONLY) = 11 17:19:31.726127 fstat(11, {st_mode=S_IFREG|0600, st_size=2263, ...}) = 0 17:19:31.726193 pread(11, "Return-path: <dino(a)example.com>\nE"..., 4096, 0) = 2263 17:19:38.973282 pread(11, "", 1833, 2263) = 0 17:19:38.973382 pread(11, "Return-path: <dino(a)example.com>\nE"..., 4096, 0) = 2263 17:19:38.973488 pread(11, "Return-path: <dino(a)example.com>\nE"..., 4096, 0) = 2263 17:19:38.973559 close(11) = 0 17:19:38.973645 open("/dap/mstorage/example.com/dino/Maildir/cur/ 1201079181.H210590P11751.mx01.example.com,S=3764:2,", O_RDONLY) = 11 17:19:38.973900 fstat(11, {st_mode=S_IFREG|0600, st_size=3764, ...}) = 0 17:19:38.973967 pread(11, "Return-path: <dino(a)example.com>\nE"..., 4096, 0) = 3764 17:19:39.013845 pread(11, "", 332, 3764) = 0 17:19:39.013906 pread(11, "Return-path: <dino(a)example.com>\nE"..., 4096, 0) = 3764 17:19:39.013999 pread(11, "Return-path: <dino(a)example.com>\nE"..., 4096, 0) = 3764 17:19:39.014066 close(11) = 0 17:19:39.014129 open("/dap/mstorage/example.com/dino/Maildir/cur/ 1201079181.H297801P11758.mx01.example.com,S=6890:2,", O_RDONLY) = 11 17:19:39.014331 fstat(11, {st_mode=S_IFREG|0600, st_size=6890, ...}) = 0 17:19:39.014391 pread(11, "Return-path: <dino(a)example.com>\nE"..., 4096, 0) = 4096 17:19:39.053878 pread(11, "~b_])!5b\'8rIwz/mmG31A}yr*9\'uC!$<"..., 4095, 4096) = 2794 17:19:39.053963 pread(11, "", 1301, 6890) = 0 17:19:39.054022 pread(11, "Return-path: <dino(a)example.com>\nE"..., 4096, 0) = 4096 17:19:39.054115 pread(11, "Return-path: <dino(a)example.com>\nE"..., 4096, 0) = 4096 17:19:39.054182 close(11) = 0 17:19:39.054245 open("/dap/mstorage/example.com/dino/Maildir/cur/ 1201079181.H308343P11761.mx01.example.com,S=2510:2,", O_RDONLY) = 11 17:19:39.054448 fstat(11, {st_mode=S_IFREG|0600, st_size=2510, ...}) = 0 17:19:39.054508 pread(11, "Return-path: <dino(a)example.com>\nE"..., 4096, 0) = 2510 17:19:42.805170 pread(11, "", 1586, 2510) = 0 17:19:42.805271 pread(11, "Return-path: <dino(a)example.com>\nE"..., 4096, 0) = 2510 17:19:42.805376 pread(11, "Return-path: <dino(a)example.com>\nE"..., 4096, 0) = 2510 17:19:42.805441 write(1, "* 272 FETCH (UID 3838 RFC822.SIZ"..., 2146) = 2146 17:19:42.805503 close(11) = 0

2 1

Re: [Dovecot] Virtual Users and permission denied on POP3 Authentication - cur directory
by Iain M Conochie 23 Jan '08

23 Jan '08

John Dubchak wrote: > > On Jan 23, 2008, at 4:27 AM, Iain M Conochie wrote: > >> Then I am a bit stuck. That was how I got it working for LDAP to be >> honest. >> >> What kind of usernames are your users using to login with? Is it >> user@domain or just user? > > user@domain > > Thanks, > John What do you have as your user_query then? You may need to use WHERE userid = '%n' AND domain = '%d' instead of WHERE userid = '%u' perhaps? Iain

1 0

[Dovecot] Create IMAP folders on first login?
by Andreas Ntaflos 23 Jan '08

23 Jan '08

Hello list, I am currently playing around with a virtual domain/virtual user setup and thanks to the documentation on both the Dovecot and the Postfix websites things are going swimmingly (apart from an oddity I will post separately about). On trying things out with different newly created virtual users I wondered if it was possible for Dovecot to create certain IMAP folders on the first login of the user? So that folders such "Drafts", "Sent" and "Trash" are created automatically for each new user (upon login). Or is this a job for the mail client, or for the admin who creates the new users? TIA! Andreas -- Andreas Ntaflos Vienna, Austria GPG Fingerprint: 6234 2E8E 5C81 C6CB E5EC 7E65 397C E2A8 090C A9B4

2 2

[Dovecot] Problem with quota support on debian etch
by Sascha Bendix 22 Jan '08

22 Jan '08

Hi, sorry but I'm new to dovecot and this list and don't know how to proceed with my dovecot installation. I was trying to set up an Mailserver with Postfix, Dovecot and PostgreSQL. Everything was working fine till I wanted to integrate quota support. When I activate it by adding quota to the the imap plugin section (like described in the wiki) I get the following error every time I try to login: Jan 20 19:32:07 kauket dovecot: IMAP(user(a)dmain.de): Unknown quota backend: quota=maildir Jan 20 19:32:07 kauket dovecot: child 11288 (imap) returned error 89 Jan 20 19:32:07 kauket dovecot: imap-login: Login:user=<user(a)domain.de>, method=plain, rip=::ffff:1.2.3.4, lip=::ffff:1.2.3.5, TLS I tried to set quota = maildir:storage=10240 in the plugin section, too and got the same error. I already talked to some dovecot users bot nobody could help me and I hope you can give me an advice what could be the mistake. Here is my Config: # /etc/dovecot/dovecot.conf log_timestamp: %Y-%m-%d %H:%M:%S protocols: imaps listen: [::] ssl_cert_file: /etc/ssl/certs/kauket.maedness.de.crt ssl_key_file: /etc/ssl/certs/kauket.maedness.de.key login_dir: /var/run/dovecot/login login_executable: /usr/lib/dovecot/imap-login login_user: dovecot-auth mail_extra_groups: mail mail_location: maildir:/var/mail/%h mail_plugins: quota imap_quota auth default: user: dovecot passdb: driver: sql args: /etc/dovecot/dovecot-sql.conf userdb: driver: sql args: /etc/dovecot/dovecot-sql.conf # grep -ve '^[ ]*#' -e '^$' dovecot-sql.conf driver = pgsql connect = host=localhost dbname=postfix user=postfix password=password default_pass_scheme = MD5 password_query = SELECT password FROM mailbox WHERE username = '%u' user_query = SELECT maildir, 10000 AS uid, 8 AS gid, quota=maildir:storage=' || quota AS quota, maildir AS home FROM mailbox WHERE username = '%u' The system is a debian stable (etch) with package version 1.0.rc15-2etch1 and dovecot --version tells 1.0.rc15. I know the this version of dovecot is a little bit ancient but I hope you can still help me. I even don't know if it's only a bug in the package or if it's a bug in dovecot itself. I thank you for all clues and advices. Sincerly yours, Sascha

2 2

[Dovecot] Virtual Users and permission denied on POP3 Authentication - cur directory
by John Dubchak 22 Jan '08

22 Jan '08

Hi, I've been working on configuring a new Postfix+Dovecot+Cyrus-SASL +Postgres server to perform multi-domain virtual hosting with non-unix accounts. I believe I have everything working correctly and have tested both the SASL portion and POP authentication through telnet and all works as expected, with one exception. When I authenticate using POP3: # telnet mail.host 110 Trying 192.168.XXX.XXX... Connected to mail.host. Escape character is '^]'. +OK Dovecot ready. user user1(a)domain1.com +OK pass secret +OK Logged in. -ERR No INBOX for user. And the maillog reports the following: Jan 21 13:42:32 mail.host dovecot: pop3-login: Login: user=<user1>, method=PLAIN, rip=192.168.XXX.XXX, lip=192.168.XXX.XXX Jan 21 13:42:32 mail.host dovecot: POP3(user1): mkdir(/var/spool/ virtual_mailbox/domain1.com/user1/cur) failed: Permission denied Jan 21 13:42:32 mail.host dovecot: POP3(user1): mkdir(/var/spool/ virtual_mailbox/domain1.com/user1/cur) failed: Permission denied Jan 21 13:42:32 mail.host dovecot: POP3(user1): Couldn't open INBOX: Internal error occurred. Refer to server log for more information. [2008-01-21 13:42:32] Jan 21 13:42:32 mason dovecot: POP3(user1): No INBOX for user top=0/0, retr=0/0, del=0/0, size=0 The directory structures for the virtual mailboxes are: /var/spool/virtual_mailbox/domain1.com/user1 /var/spool/virtual_mailbox/domain2.com/user1 And the entire tree from virtual_mailbox down is owned by vuser:vuser. The directories have permissions 700. What I believe is happening is that Dovecot is trying to use the uid and gid of user1, who doesn't have a system account, rather than vuser's when writing to the virtual_mailbox folders. I'm not sure how I can configure Dovecot to use the vuser information. Here is my dovecot.conf: ------------------------------------------------------------------------- protocols = imap pop3 listen = [*] disable_plaintext_auth = no syslog_facility = mail mail_location = maildir:/var/spool/virtual_mailbox/%h # Default umask to use for mail files and directories. #umask = 0077 protocol imap { } protocol pop3 { } protocol lda { postmaster_address = postmaster(a)example.com } auth_debug_passwords = yes auth_debug = yes auth_verbose = yes auth default { # SQL database passdb sql { args = /etc/dovecot-sql.conf } userdb sql { args = /etc/dovecot-sql.conf } user = root } ------------------------------------------------------------------------- Any insight will be appreciated, I've been working on this non-stop for several days now and can't seem to figure it out. Thanks, John

2 3

[Dovecot] Problem downloading mail with "large" attachment using Thunderbird....
by Bjørn T Johansen 22 Jan '08

22 Jan '08

We have a user that is using Thunderbird on Windows to read mail over IMAP and it works ok, except for downloading mail with "large" attachment.. When opening a mail with a attachment with a size of 14-15MB, TB downloads the attachment seemingly ok, but TB stops when reaching 99%. After TB has stopped, if the user tries to select another mail, TB just hangs and it has to be closed and started again to work again... I have checked the dovecot log, but I can't find anything there... We have also tried to create a log in TB but everything looks ok there also... Is there a known problem with TB and "large" attachment or does anyone know how to fix this, if possible? Regards, BTJ -- ----------------------------------------------------------------------------------------------- Bjørn T Johansen btj(a)havleik.no ----------------------------------------------------------------------------------------------- Someone wrote: "I understand that if you play a Windows CD backwards you hear strange Satanic messages" To which someone replied: "It's even worse than that; play it forwards and it installs Windows" -----------------------------------------------------------------------------------------------

4 6

[Dovecot] Maildrop script to sieve
by Raphael Bittencourt S. Costa 21 Jan '08

21 Jan '08

Hi, I'm working on a system that have about 350K e-mail users and 100k users that uses maildrop scripts to make filters on their delivery. So, changing scripts by hand can't be a choice. I "googled" so much and I wasn't able to find any script that converts maildrop scripts to sieve. Does anyone knows where can I find it? By the way, does anyone uses dovecot-1.1-beta on a production system with sieve+maildir+lda? Thanks, Raphael Costa

3 4

[Dovecot] Dovecot marks messages read using pop3
by Steve Annessa 21 Jan '08

21 Jan '08

Hello, When I use pop3 and the option "leave messages on server" it marks all emails read. How do I stop this? dovecot version: 1.0.rc15 (Debian etch) dovecot config: # /etc/dovecot/dovecot.conf log_timestamp: %Y-%m-%d %H:%M:%S protocols: imap imaps pop3 pop3s ssl_cert_file: /etc/postfix/ssl/mail_cpcug_org.crt ssl_key_file: /etc/postfix/ssl/cpcug_org.key 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 mail_extra_groups: mail mail_location: mbox:/users/mail/%u:INDEX=/users/indexes/%u mail_executable(default): /usr/lib/dovecot/imap mail_executable(imap): /usr/lib/dovecot/imap mail_executable(pop3): /usr/lib/dovecot/pop3 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 pop3_uidl_format(default): pop3_uidl_format(imap): pop3_uidl_format(pop3): %08Xu%08Xv 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 master: path: /var/run/dovecot/auth-master mode: 384 user: nobody

2 1

[Dovecot] Exim Dovecot Authentication Problem
by Marc Perkel 21 Jan '08

21 Jan '08

Having a hard time figuring out something that is supposed to be easy. Tryiong to configure Dovecot so that it provides authentication to Exim for outgoing smtp. Tried different things and getting authentication socket protocol error dovecot_plain: driver = dovecot public_name = PLAIN server_socket = /var/run/dovecot/auth-client server_set_id = $auth1 auth default { # Space separated list of wanted authentication mechanisms: # plain digest-md5 cram-md5 apop anonymous mechanisms = plain # # Password database is used to verify user's password (and nothing more). # You can have multiple passdbs and userdbs. This is useful if you want to # allow both system users (/etc/passwd) and virtual users to login without # duplicating the system users into virtual database. # # http://wiki.dovecot.org/Authentication # # PAM authentication. Preferred nowadays by most systems. # Note that PAM can only be used to verify if user's password is correct, # so it can't be used as userdb. If you don't want to use a separate user # database (passwd usually), you can use static userdb. passdb passwd-file { # Master users that can log in as anyone args = /etc/dovecot.masterusers master = yes pass =yes } # Linuxconf passwd-like file with specified location passdb passwd-file { args = /etc/exim/control/vmail/shadow.%d } # Linuxconf passwd-like file with specified location userdb passwd-file { args = /etc/exim/control/vmail/passwd.%d } # User to use for the process. This user needs access to only user and # password databases, nothing else. Only shadow and pam authentication # requires roots, so use something else if possible. Note that passwd # authentication with BSDs internally accesses shadow files, which also # requires roots. Note that this user is NOT used to access mails. # That user is specified by userdb above. user = root # Number of authentication processes to create count = 10 } # It's possible to export the authentication interface to other programs, # for example SMTP server which supports talking to Dovecot. Client socket # handles the actual authentication - you give it a username and password # and it returns OK or failure. So it's pretty safe to allow anyone access to # it. Master socket is used to a) query if given client was successfully # authenticated, b) userdb lookups. # listener sockets will be created by Dovecot's master process using the # settings given inside the auth section auth default_with_listener { mechanisms = plain passdb passwd-file { # Master users that can log in as anyone args = /etc/dovecot.masterusers master = yes pass =yes } passdb passwd-file { # Path for passwd-file args = /etc/exim/control/vmail/shadow.%d } userdb passwd-file { # Path for passwd-file args = /etc/exim/control/vmail/passwd.%d } socket listen { master { path = /var/run/dovecot/auth-master mode = 0666 } } } auth external { mechanisms = plain passdb passwd-file { # Master users that can log in as anyone args = /etc/dovecot.masterusers master = yes pass =yes } passdb passwd-file { # Path for passwd-file args = /etc/exim/control/vmail/shadow.%d } userdb passwd-file { # Path for passwd-file args = /etc/exim/control/vmail/passwd.%d } socket listen { client { path = /var/run/dovecot/auth-client mode = 0666 } } }

3 6