- dovecot - dovecot.org

[Dovecot] mbox inbox default
by bhayden＠umn.edu 01 Aug '07

01 Aug '07

HI Timo & all. We're an mbox environment, inboxes in /var/mail/$USER (I'll include dovecot -n output at the bottom of this mail). mail_location is set accordingly for deliver. I'd assumed that if the /var/mail/$USER file doesn't exist, dovecot would create it, but we've discovered from experience (and I verified it in mbox-storage.c) that if access(path, R_OK|W_OK) fails--as it does if the file doesn't exist--that dovecot defaults then to delivering in root_dir/inbox. I'm curious why this is. It seems like if the configured INBOX file doesn't exist, dovecot should create it if possible; it's a different case than if, say, the user doesn't have write access to that directory, in which case it of course would be appropriate to fall back to some other location rather than rejecting mail. Is there something I'm missing that makes my idea wrong? Thanks, -Brian Hayden OIT Internet Services University of MN # ./dovecot -n # /etc/opt/dovecot/dovecot.conf syslog_facility: local6 protocols: imap imaps pop3 pop3s listen(default): *:143 listen(imap): *:143 listen(pop3): *:110 ssl_listen(default): *:993 ssl_listen(imap): *:993 ssl_listen(pop3): *:995 ssl_cert_file: /etc/opt/openssl/certs/dovecot.pem ssl_key_file: /etc/opt/openssl/private/dovecot.pem shutdown_clients: no login_dir: /var/opt/dovecot/run/dovecot/login login_executable(default): /opt/dovecot/libexec/dovecot/imap-login login_executable(imap): /opt/dovecot/libexec/dovecot/imap-login login_executable(pop3): /opt/dovecot/libexec/dovecot/pop3-login login_log_format_elements: user=<%u> pid=<%p> method=%m rip=%r lip=%l %c login_processes_count: 32 login_max_processes_count: 6000 max_mail_processes: 8192 first_valid_uid: 100 mail_location: mbox:~:INBOX=/var/mail/%u:INDEX=/var/mail/.dovecot-index/%1u/%u/ mail_debug: yes mbox_lazy_writes: no mail_executable(default): /opt/dovecot/libexec/dovecot/mail_path.sh mail_executable(imap): /opt/dovecot/libexec/dovecot/mail_path.sh mail_executable(pop3): /opt/dovecot/libexec/dovecot/pop3 mail_plugins(default): acl mail_plugins(imap): acl mail_plugins(pop3): mail_plugin_dir(default): /opt/dovecot/lib/dovecot/imap mail_plugin_dir(imap): /opt/dovecot/lib/dovecot/imap mail_plugin_dir(pop3): /opt/dovecot/lib/dovecot/pop3 mail_log_prefix: [%p] %Us(%u): mail_log_max_lines_per_sec: 0 imap_client_workarounds(default): delay-newmail outlook-idle tb-extra-mailbox-sep imap_client_workarounds(imap): delay-newmail outlook-idle tb-extra-mailbox-sep imap_client_workarounds(pop3): outlook-idle pop3_uidl_format(default): pop3_uidl_format(imap): pop3_uidl_format(pop3): %08Xu%08Xv namespace: type: private separator: / location: mbox:~:INBOX=/var/mail/%u:INDEX=/var/mail/.dovecot-index/%1u/%u/ inbox: yes namespace: type: private separator: / prefix: mail/ location: mbox:~/mail/:INDEX=/var/mail/.dovecot-index/%1u/%u/ hidden: yes namespace: type: private separator: / prefix: ~/mail/ location: mbox:~/mail/:INDEX=/var/mail/.dovecot-index/%1u/%u/ hidden: yes namespace: type: private separator: / prefix: ~%u/mail/ location: mbox:~/mail/:INDEX=/var/mail/.dovecot-index/%1u/%u/ hidden: yes namespace: type: private separator: / prefix: Shared/ location: maildir:~/Maildir/Shared/:INDEX=/var/mail/.dovecot-index/%1u/%u/shared:CONTROL=/var/mail/.dovecot-index/%1u/%u/shared-control auth default: username_format: %Lu passdb: driver: pam args: session=yes * userdb: driver: passwd plugin: acl: vfile:

2 2

[Dovecot] High cpu usage OpenSolaris
by Gary Gendel 01 Aug '07

01 Aug '07

All, Nevermind... I discovered the problem. It was in the Solaris Sun Studio 12 compiler. I created a debug version to begin testing, but that version worked without sucking up the cpu. So it looks like the optimizer messed up. If I used the -fast optimization, it sucks up cpu, but with -xO5 all is well. Gary --------------------------------------------------------------------- Hi, I've built 64-bit dovecot 1.0.2 on Opensolaris to replace version 1.0.0rc10. It functions fine, but when I connect, it eats up all available cpu. My guess is that the poll thread is running continuously. Any ideas on what I should do to verify this or does anyone know of a fix? Thanks, Gary

4 4

[Dovecot] RFE: please include quota waning patch
by Farkas Levente 01 Aug '07

01 Aug '07

hi, it'd be very useful to include the quota warning patch in official release. without it the quota support is not really useful since mail simple dropped when quota is over. and most enduser never know what happend, they just recognize mails are not coming:-( thanks. -- Levente "Si vis pacem para bellum!"

4 5

[Dovecot] Missing MIME-Version header in e-mails.
by Tan Shao Yi 01 Aug '07

01 Aug '07

Hi, I notice that in src/lib-mail/message-parser.c, there is a section of code that checks for the presence of MIME-Version before allowing processing of the Content-* headers. Is there a possibility of relaxing this rule? There are some broken mailers, in particular newsletter mailers that do not seem to honour the MIME-Version header, though they do send the Content-Type. Cheers.

2 1

[Dovecot] Mount options and NFS: just checking...
by Mike Brudenell 01 Aug '07

01 Aug '07

Greetings - I'm now in the last couple of weeks before going live with Dovecot (v1.0.3) on our revamped IMAP service. I'd like to double-check about the best mount options to use; could someone advise, please? I have three separate directory trees for the message store, the control files and the index files. These are arranged as follows: Message Store Mounted over NFS from a NetApp filer; filestore quotas are ENABLED. Control Files Mounted over NFS from the NetApp filer; filestore quotas are DISABLED. Index Files Mounted on local disk; filestore quotas are DISABLED. We will have a pair of Solaris 10 servers on which Dovecot 1.0.3 is running. Users are normally directed to their "preferred" server but, if it is unavailable, will go via the other server. Q1. Am I right in thinking that for the Message Store and Control Files I should NFS-mount both of them with the "actimeo=0"? (Or would "noac" be better, which also turns off client write- caching as well as the attribute cache?) Q2. Should I NFS-mount either or both of the Message Store and Control Files with the "noxattr" option to turn off extended attributes? Q3. Which of the filestores should I mount with the "noatime" option? (I understand that for the filer-based NFS mounts this can be done on the filer, as the option isn't available with "mount" for NFS-monted filestores.) Q4. Any other options to use/miss out? Currently my understanding from the list and the NFS page at the Wiki is: A1. Use "actimeo=0" for both Message Store and Control Files. No idea about the need for/impact of using "noac". A2. No idea. A3. Safe to use "noatime" for all three filestores. (I understand Dovecot will use utime() when needed on such filestores, but am not sure if it will work on the NFS-mounted filestores from the filer if access times are turned off at the filer end.) Any thoughts, please? Cheers, Mike B-) -- The Computing Service, University of York, Heslington, York Yo10 5DD, UK Tel:+44-1904-433811 FAX:+44-1904-433740 * Unsolicited commercial e-mail is NOT welcome at this e-mail address. *

2 3

[Dovecot] mbox bug in 1.0.0
by bhayden＠umn.edu 01 Aug '07

01 Aug '07

Hi folks. We're moving users from rc24 and 27 to 1.0.0. On four mailboxes so far we've seen these errors after the move (quick and dirty anonymizing follows): Apr 23 13:22:41 server.umn.edu dovecot: [ID 107833 local6.info] imap-login: Login: user=<USER>, pid=<9046>, method=PLAIN, rip=***.***.***.***, lip=***.***.***.***, TLS Apr 23 13:22:41 server.umn.edu dovecot: [ID 107833 local6.error] [9073] IMAP(USER): mbox /var/mail/user: seq=1 uid=8808 uid_broken=0 originally needed 10 bytes, now needs 23 bytes Apr 23 13:22:41 server.umn.edu dovecot: [ID 107833 local6.error] [9073] IMAP(USER): Raw backtrace: 0x7b800 -> 0x43434 -> 0x3e018 -> 0x3fc34 -> 0x40080 -> 0x6d3cc -> 0x29a88 -> 0x21324 -> 0x214c0 -> 0x22f48 -> 0x22ec0 -> 0x230c0 -> 0x81c18 -> 0x814e4 -> 0x2b5cc -> 0x1dc58 Points of interest: 1. I can't reproduce this. It still happens after the user's .imap directories are removed. If I make a copy of the mailbox on another machine running the same version of Dovecot with the same config, the problem doesn't occur. Weird. 2. So far, have only seen it on quite large mailboxes (close to or over 100MB). Most large boxes have not had the problem, but the ones that have are all large. Any thoughts? Dovecot -n output below. -Brian Hayden OIT Internet Services U of Minnesota # dovecot -n # /etc/opt/dovecot/dovecot.conf syslog_facility: local6 protocols: imap imaps pop3 pop3s listen(default): *:143 listen(imap): *:143 listen(pop3): *:110 ssl_listen(default): *:993 ssl_listen(imap): *:993 ssl_listen(pop3): *:995 ssl_cert_file: /etc/opt/openssl/certs/dovecot.pem ssl_key_file: /etc/opt/openssl/private/dovecot.pem shutdown_clients: no login_dir: /var/opt/dovecot/run/dovecot/login login_executable(default): /opt/dovecot/libexec/dovecot/imap-login login_executable(imap): /opt/dovecot/libexec/dovecot/imap-login login_executable(pop3): /opt/dovecot/libexec/dovecot/pop3-login login_log_format_elements: user=<%u> pid=<%p> method=%m rip=%r lip=%l %c login_processes_count: 32 login_max_processes_count: 4096 max_mail_processes: 8192 first_valid_uid: 100 default_mail_env: mbox:~/:INBOX=/var/mail/%u mail_location: mbox:~/:INBOX=/var/mail/%u mail_full_filesystem_access: yes mbox_lazy_writes: no mail_executable(default): /opt/dovecot/libexec/dovecot/imap mail_executable(imap): /opt/dovecot/libexec/dovecot/imap mail_executable(pop3): /opt/dovecot/libexec/dovecot/pop3 mail_plugin_dir(default): /opt/dovecot/lib/dovecot/imap mail_plugin_dir(imap): /opt/dovecot/lib/dovecot/imap mail_plugin_dir(pop3): /opt/dovecot/lib/dovecot/pop3 mail_log_prefix: [%p] %Us(%u): imap_client_workarounds(default): delay-newmail outlook-idle tb-extra-mailbox-sep imap_client_workarounds(imap): delay-newmail outlook-idle tb-extra-mailbox-sep imap_client_workarounds(pop3): outlook-idle pop3_uidl_format(default): pop3_uidl_format(imap): pop3_uidl_format(pop3): %08Xu%08Xv namespace: type: private separator: / location: mbox:~/:INBOX=/var/mail/%u inbox: yes hidden: yes auth default: username_format: %Lu verbose: yes debug: yes passdb: driver: pam args: session=yes * userdb: driver: passwd

2 4

[Dovecot] dovecot-uidlist locking
by Tony Tsang 01 Aug '07

01 Aug '07

Hi all, I've a dovecot server setup and occassionally clients cannot get mails from their inbox. When I inspect the maildir for that user, there is stale dovecot-uidlist.lock file, and imap process keeps waiting for release of the lock. Is there any other method to perform locking on dovecot-uidlist instead of using dotlock mechanism? It is creating maintenance problems if I need to remove those stale lock files everytime clients hit this problem Tony.

2 2

[Dovecot] user name before and after authentication
by François Wautier 01 Aug '07

01 Aug '07

Hi, I am new to dovecot and spend the last few hours trying to configure it to my liking. I am using version 1.0.2 I have a setup where I only have "virtual" mailboxes in various domain ( mydomain.com, mydomain.biz,...). I setup Exim to deliver the email into <some path>/domains/<domainname>/<user> Now I am trying to get dovecot to access those mailboxes I setup LDAP bind authentication against an AD server. it works fine... but I have a problem getting the correct path to the mailboxes. The user logs in as user(a)domain.ext The mailbox path being at <some path>/domains/%n/%u The LDAP module gets the DN for my user and verify that it can binds, and in the process changes the "user" to cn=<real name>,cn=Users,dc=domain,dc=ext There goes my path To make matter worse, the uid and gid are the same for all users and are fixed (exim user and group). Hence cannot be retrieved from AD I tried to use userdb static, but I can't seem to be able to reset "user" to its pre-authentication value userdb prefetch/ldap but I can't set the uid/gid So here are my request for help... Is there a way to set home dir/ mail dir before authentication? Is there a way to reference the pre-auth user name? Is there a way to create arbitrary variables and used them? Is there a way to fix the uid/gid to use to access the mailboxes? Any one of these could probably solve my problem. Any suggestion is most welcome. François

2 1

[Dovecot] IMAPs and POP3s poxying
by Jason Russler 01 Aug '07

01 Aug '07

Hi All, I have a polotical situation at work that requires that I off-load mail access to a host other than the one our users have configured in their clients. I don't have access to any of the switching or routing to our hosts, and there's only a 1 to 1 relationship between the proxy I want to set up and the actual mail handler. I was looking at the proxying Howto in the Wiki and was presented with an SQL server requirement to do user/ip address look-ups. In my case, it will always be proxying the same host. How would I configure Dovecot to proxy another single system without doing the SQL look-up? Is there a port-forwarding solution that would work better (for POP3s and IMAPS)? These are RedHat 5 hosts so Netfilter is fair game if the protocols allow. Thanks, -Jason

2 1

[Dovecot] apparent bug with filesystem quota and message lists
by Stewart Dean 01 Aug '07

01 Aug '07

Don't know if anyone else uses Berkeley derived filesystem quota, but IBM's AIX does. A little over a week after migrating from UWIMAP to DC (with mbox format unchanged) everything is clean except for this one problem: When users go over quota, when they login the next time, the folder list is blank. You can imagine the panicked calls to the Helpdesk. If their quotas are raised or re-graced, Get Mail returns the expected list. This behavior happens with a variety of clients: Pine, MacMail,TBird, Horde Webmail, etc. The index filesystem has no quota on it. I would have to imagine the Dovecot is using (or trying to use) some space in the quota'ed filesystems which the operating system won't allow, and this results in there being an empty file that DC uses for the message list sent to the client. There are NO messages in syslog (other than the expected login and logout) indicating any problems. Our legacy setup has the inboxes in /var/spool/mail, and the folders in ~/mail. The problem can happen either place. dovecot -n returns: > # 1.0.1: /usr/local/etc/dovecot.conf > listen: *:143 > ssl_listen: *:993 > disable_plaintext_auth: no > login_dir: /var/run/dovecot/login > login_executable: /usr/local/libexec/dovecot/imap-login > login_processes_count: 12 > login_max_processes_count: 774 > verbose_proctitle: yes > first_valid_uid: 200 > mail_location: mbox:~/mail:INBOX=/var/spool/mail/%u:INDEX=/var/dcindx/%u > mbox_dirty_syncs: no > mbox_lazy_writes: no > auth default: > passdb: > driver: pam > userdb: > driver: passwd Suggestions? -- ==== Stewart Dean, Unix System Admin, Henderson Computer Resources Center of Bard College, Annandale-on-Hudson, New York 12504 sdean(a)bard.edu voice: 845-758-7475, fax: 845-758-7035

2 2