March 2011 - dovecot - dovecot.org

[Dovecot] Bug: Creating mbox folders
by Kelly Stephens 23 Mar '11

23 Mar '11

Hey, I had trouble this morning creating a folder to contain sub-folders. I am using the mbox format. Turns out that the .imap directory in the new folder (directory) was not being created. Anytime I tried to view a sub-folder (using Thunderbird) dovecot would dump. Once I manually created the .imap directory, it works fine. dovecot --version -> 2.0.9 dovecot -n # 2.0.9: /etc/dovecot/dovecot.conf # OS: Linux 2.6.35.11-83.fc14.i686 i686 Fedora release 14 (Laughlin) listen = * mbox_write_locks = fcntl passdb { driver = pam } protocols = imap ssl_cert = </etc/pki/dovecot/certs/dovecot.pem ssl_key = </etc/pki/dovecot/private/dovecot.pem userdb { driver = passwd } The maillog dump... Mar 16 08:50:22 brinn dovecot: imap(kms): Panic: file mailbox-list.c: line 324 (mailbox_list_get_unexpanded_path): assertion failed: (*location == SETTING_STRVAR_UNEXPAND ED[0]) Mar 16 08:50:22 brinn dovecot: imap(kms): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0() [0x994051] -> /usr/lib/dovecot/libdovecot.so.0() [0x9940c0] -> /usr/lib /dovecot/libdovecot.so.0(i_fatal+0) [0x96a690] -> /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_list_get_unexpanded_path+0x138) [0xa086d8] -> /usr/lib/dovecot/libdovec ot-storage.so.0(mailbox_list_mkdir+0x52) [0xa09b32] -> /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_list_create_missing_index_dir+0x129) [0xa09fb9] -> /usr/lib/doveco t/libdovecot-storage.so.0(index_storage_mailbox_open+0xa4) [0xa23c24] -> /usr/lib/dovecot/libdovecot-storage.so.0() [0xa485de] -> /usr/lib/dovecot/libdovecot-storage.so.0 () [0xa04d25] -> dovecot/imap(cmd_select_full+0x1cf) [0x805310f] -> dovecot/imap(cmd_select+0x1a) [0x8053b3a] -> dovecot/imap() [0x80560ed] -> dovecot/imap() [0x80561ca] -> dovecot/imap(client_handle_input+0x12d) [0x805640d] -> dovecot/imap(client_input+0x60) [0x8056d10] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x52) [0x9a18e2] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0xd3) [0x9a2b43] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_run+0x40) [0x9a1860] -> /usr/lib/dovecot/libdovecot.so.0(master_service_run+0x2b) [0x98cfcb] -> dovecot/imap(main+0x33d) [0x805faad] -> /lib/libc.so.6(__libc_start_main+0xe6) [0x732e36] -> dovecot/imap() [0x804e111] Mar 16 08:50:22 brinn dovecot: master: Error: service(imap): child 9753 killed with signal 6 (core dumps disabled)

2 4

[Dovecot] different users with different quota
by Jim Knuth 23 Mar '11

23 Mar '11

Hello, How can one assign different users different Quota? So properly? quota_rule1 = userONE:storage=1G quota_rule2 = Trash:storage=100M quota_rule3 = SPAM:ignore quota_rule4 = userTWO:storage=5M quota_rule5 = Trash:storage=50M quota_rule6 = SPAM:ignore and so on ... Right or how? -- Mit freundlichen Grüßen, Jim Knuth P.S.: Bitte senden Sie KEINE HTML-Mails! Zufallszitat: Die Geschichte wird freundlich mit mir umgehen, denn ich habe vor, sie zu schreiben. [Churchill]

3 8

[Dovecot] FETCH got too little data (+ wrong W value) with 1 byte offset
by Vincent Artzner 23 Mar '11

23 Mar '11

Hi there, I juste set up dovecot as local imap server last week, with maildir format. Things went fine with two "low volume" accounts, until I added another one. Then I see two different things with connected clients: 1/ Quite oftent well formed messages that appear... and disappear quite immediately. On the server, the messages concerned by 2/ seem to be there, I can open the files and it looks ok (header, content). The only error log I get is this: 2011-03-18 14:43:14 IMAP(info): Info: Disconnected: FETCH failed bytes=109363/174063195 2011-03-18 14:43:14 imap-login: Info: Login: user=<info>, method=PLAIN, rip=192.168.0.191, lip=192.168.0.10, TLS 2011-03-18 14:43:15 IMAP(info): Error: FETCH [] for mailbox Envois UID 11572 got too little data: 63454 vs 63455 2011-03-18 14:43:15 IMAP(info): Error: Maildir filename has wrong W value: /home/info/Maildir/.Envois/cur/1300450349.M120256P3108.Serveurlinux,S=460764,W=460768:2,S 2011-03-18 14:43:15 IMAP(info): Error: Corrupted index cache file /home/info/Maildir/.Envois/dovecot.index.cache: Broken virtual size for mail UID 11572 Please note the size: 63454 vs 63455: it's always like that: one byte difference. Here is the dovecot -n result: # 1.2.9: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-24-generic-pae i686 Ubuntu 10.04.2 LTS ext4 log_path: /home/dovecot.log log_timestamp: %Y-%m-%d %H:%M:%S listen: *:144 ssl_listen: *:10943 login_dir: /var/run/dovecot/login login_executable: /usr/lib/dovecot/imap-login login_process_per_connection: no mail_max_userip_connections: 20 mail_privileged_group: mail mail_location: maildir:/home/%u/Maildir:INBOX=/home/%u/Maildir/ mbox_write_locks: fcntl dotlock auth default: passdb: driver: pam userdb: driver: passwd The imap client used is thunderbird under windows XP/7. I also reproduced it with opera mail client. I tried to rename/delete dovecot.index.cache files as I have read about it, but doesn't changed anything. The incoming mails are provided to dovecot by procmail, so I think dovecot is responsible for settings the S, W params in the filenames. No other process should alter the messages (i still have to fully check this). I am a bit lost (not a system administrator at all) and would be grateful for any advice. Vincent

3 6

[Dovecot] DoveCot 2.0.9: Problem with some Clients and separator (migrate from Cyrus)
by Denny Schierz 23 Mar '11

23 Mar '11

hi, we had to move from a old dieing Sparc very quickly our Cyrus IMAP Users to Dovecot. Most things works, but some Clients (like Evolution or Thunderbird) are strange. Our separator in Dovecot2 is "^", the mailboxes on the filesystem are something like "INBOX.subfolder1.subfolder2", but in TB and Evo I see INBOX^subfolder1^subfolder^ In Roundcube Webmail, I have just a normal tree, as I expected. I used cyrus2dovecot.pl for converting. On Evolution I deleted the IMAP Profile and recreated it, and that was working, but it isn't a workaround for TB So, how can I fix it? namespace { type = private separator = ^ prefix = inbox = yes hidden = no subscriptions = yes } cu denny

3 6

[Dovecot] Master user creds for proxy stored statically/locally?
by Edward Carraro 22 Mar '11

22 Mar '11

I have successfully set up the master user on the destination server (2.0.11) and tests have worked. now I'm working on the proxy Before I had the proxy just forward everything to the backend and had the destination server do the authentication. My authentication is done via LDAP but not really sure how to append the master user and password to the users credentials after authentication is done. id rather not have the master user/pass in each users ldap entry and returned after doing a lookup or add a destuser field for each user... basically i prefer not having to add any new attributes to LDAP Can the information be stored locally in a file on the proxy? do i just make the same master user file that I have on the backend? Thanks!

3 14

[Dovecot] Change password cheme
by Pascal Nobus 22 Mar '11

22 Mar '11

We want to update our password scheme from crypt to SHA256. Because usernames/passwords are in MySQL I thought this wouldn't be a problem. We have about 3000 users that need to be updated, so make a new password for them isn't possible. I was thinking of an automated script that would update the database after every login. So we did this: dovecot.conf: mail_executable = /usr/local/etc/updatepwd.sh updatepwd.sh: #!/bin/sh $USER $PASSWORD|/usr/local/etc/do_updatepwd.pl exec /usr/local/libexec/dovecot/imap "$@" (do_updatepwd.pl is a perl script that makes a sha256 from the second argument, and then update the mysql-query) However: the password is not in the ENVIROMENT anymore. I changed in dovecot the settings: auth_debug = yes auth_debug_passwords = yes Anyone a solution for this? Best regards, Pascal

2 1

[Dovecot] Problem with sieve and delivery to folders with german umlauts.
by Micha Krause 22 Mar '11

22 Mar '11

Hi, I have a problem with sieve and german umlauts: error: msgid=unspecified: failed to store into mailbox 'INBOX.t&AOQ-st' (INBOX.t&-AOQ-st): Mailbox doesn't exist: t&-AOQ-st. The folder name is "täst", the filesystem folder is ".t&AOQ-st" , but sieve seems to look for a folder named ".t&-AOQ-st" Dovecot verstion is: 2.0.9 (7ecc5e10da57) Micha Krause

3 3

[Dovecot] http://wiki2.dovecot.org/MailServerOverview contains poppycock
by William Blunn 22 Mar '11

22 Mar '11

Just having another look at http://wiki2.dovecot.org/MailServerOverview , it seems to have some statements in it which are misleading, and some which are really ... well ... wrong. Quote: "With the possible, optional, exception of the deliver MDA, Dovecot is not involved with reception, delivery, and storage of mail. That function is provided by a MTA such as postfix <http://www.postfix.org>. It is the MTA that determines where and how mail is stored - Dovecot must then be configured to retrieve the mail accordingly." (Entered by user "amfes".) This contains a significant proportion of poppycock. Dovecot includes extensive functionality for the storage (as in the action of storing) of e-mail as well as retrieval, in the shape of the LDA. Using Dovecot's LDA is /required/ in the case of Dovecot-specific mail storage formats (sdbox, mdbox). With mbox, use of the Dovecot LDA is advisable since it will guarantee a locking strategy which is compatible with Dovecot's mail retrieval functionality. And in any case, use of the Dovecot LDA has merit in that it should guarantee line-up between the mailstore configurations used for storage and retrieval. It is NOT the MTA that determines where and how mail is stored. It is the PERSON who configures the system who decides this, and codifies that configuration into whatever systems carry out local delivery and retrieval. It IS true that use of Dovecot's LDA is optional, but to say that it is a "possible exception" is misleading. People /should/ use the Dovecot LDA if they are using Dovecot IMAP/POP, and the /option/ is to use the MTA's local delivery system /if/ it is so indicated on a particular system. Quote: "Again, it bears repeating, Dovecot /is not responsible for mail delivery or storage/. Any questions on these issues involve your MTA and MDA. Get those working first." (Entered by user "DanielMiller".) Again, contains quite a lot of misleading nonsense. "Mail delivery" includes the hand-off of the message by the MTA to the LDA, and the storage of the message by the LDA. The LDA should probably be Dovecot, so really Dovecot /is/ partially responsible for mail delivery. "Storage" involves that placing of message into the message store. This should be done by Dovecot, so Dovecot is responsible for this. Bill

2 2

[Dovecot] dsync inbox conversion problem (mbox -> mdbox)
by Sergiy Kyrylkov 22 Mar '11

22 Mar '11

Hi, We are trying to convert all mbox mail on our systems to mdbox using dsync, in order to be able to use email sub-folders in Thunderbird. Everything works fine for non-inbox folders, however the inbox folders are not getting converted. We used: *dsync -v convert mbox:~/mail:INBOX=/var/mail/%u* *dovecot --version* 2.0.beta6 (3156315704ef) (shipping with RHEL6/SL6) *dovecot -n* # 2.0.beta6 (3156315704ef): /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-71.18.2.el6.i686 i686 Scientific Linux release 6.0 (Carbon) mail_location = mdbox:~/mdbox mbox_write_locks = fcntl passdb { driver = pam } protocols = imap service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0666 user = postfix } } ssl = required ssl_cert = </etc/pki/dovecot/certs/dovecot.pem ssl_key = </etc/pki/dovecot/private/dovecot.pem userdb { driver = passwd } Sergiy

3 3

[Dovecot] Request - please uncomment !include_try /etc/dovecot/local.conf in example config
by Ng Oon-Ee 22 Mar '11

22 Mar '11

Hi, could I request that the example config in doc/dovecot/example-config/dovecot.conf be slightly altered to uncomment the last line? The point of include_try is that it only includes if such a file exists, and doesn't break anything if the file does not exist. My distro (Arch) has a policy not to apply non-essential patches, rather asking users to forward requests upstream, hence this email. It allows users to simply keep a local.conf with all their settings and not have to worry that it would not be used when the dovecot package gets upgraded (which mostly means /etc/dovecot/dovecot.conf gets replaced, depending on packaging standards). Thanks.

2 2