- dovecot - dovecot.org

[Dovecot] Upgrade 1.0->1.2 dbox mysql
by Bradley Giesbrecht 29 Dec '09

29 Dec '09

Hi, I just upgraded to from dovecot v1.1.15 to v1.2.9 so I can use dovecot- sieve. Most everything seems to work but my webmail (roundcube) clients are not seeing their subscribed folders. Reading over the upgrade docs at http://wiki.dovecot.org/Upgrading/1.2 I'm wondering if I have the two settings below configured correctly. dovecot.conf: mail_location = dbox:/opt/local/var/mail/%d/%n/dbox dovecot_mysql.conf user_query homedir result: /opt/local/var/mail/example.com/foo bash-3.2# dovecot -n # 1.2.9: /opt/local/etc/dovecot/dovecot.conf # OS: Darwin 9.8.0 Power Macintosh hfs log_path: /opt/local/var/serveza/log/mail/dovecot.log protocols: imap imaps pop3 pop3s disable_plaintext_auth: no verbose_ssl: yes login_dir: /opt/local/var/run/dovecot/login login_executable(default): /opt/local/libexec/dovecot/imap-login login_executable(imap): /opt/local/libexec/dovecot/imap-login login_executable(pop3): /opt/local/libexec/dovecot/pop3-login login_greeting: now what? mail_location: dbox:/opt/local/var/serveza/mail/%d/%n/dbox mail_debug: yes mail_executable(default): /opt/local/etc/dovecot/bin/log_imap_login.sh mail_executable(imap): /opt/local/etc/dovecot/bin/log_imap_login.sh mail_executable(pop3): /opt/local/etc/dovecot/bin/log_pop3_login.sh mail_plugin_dir(default): /opt/local/lib/dovecot/imap mail_plugin_dir(imap): /opt/local/lib/dovecot/imap mail_plugin_dir(pop3): /opt/local/lib/dovecot/pop3 lda: log_path: /opt/local/var/serveza/log/mail/dovecot-deliver.log auth_socket_path: /opt/local/var/run/dovecot/auth-master postmaster_address: postmaster(a)pixilla.com auth default: mechanisms: plain login cram-md5 ntlm apop verbose: yes debug: yes debug_passwords: yes passdb: driver: sql args: /opt/local/etc/dovecot/dovecot_mysql.conf userdb: driver: prefetch userdb: driver: sql args: /opt/local/etc/dovecot/dovecot_mysql.conf socket: type: listen client: path: /opt/local/var/spool/postfix/private/auth mode: 432 user: _postfix group: _postfix master: path: /opt/local/var/run/dovecot/auth-master mode: 384 user: _vmail Thanks for any clues, Bradley Giesbrecht

3 3

[Dovecot] Install fails when libdir and libexecdir are the same directory
by River Tarnell 29 Dec '09

29 Dec '09

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I'm using Dovecot 1.2.9. I configured it like this: % ./configure --prefix=/opt/rt --libdir=/opt/rt/lib \ --libexecdir=/opt/rt/lib [other args...] It compiled fine, but failed to install, because it tries to install a directory called <libdir>/dovecot/imap, and a file called <libexecdir>/dovecat/imap, which obviously doesn't work when libdir and libexecdir are the same directory: gmake[5]: Entering directory `/home/river/hp-pkg/mail/dovecot/work/dovecot-1.2.9/src/plugins/imap-acl' gmake[5]: Nothing to be done for `install-exec-am'. test -z "/opt/rt/lib/dovecot/imap" || /opt/rt/bin/gmkdir -p "/home/river/hp-pkg/mail/dovecot/install/opt/rt/lib/dovecot/imap" /opt/rt/bin/gmkdir: cannot create directory `/home/river/hp-pkg/mail/dovecot/install/opt/rt/lib/dovecot/imap': File exists gmake[5]: *** [install-imap_moduleLTLIBRARIES] Error 1 As a workaround I used --libexecdir=/opt/rt/lib/dovecot/libexec, but perhaps one of the conflicting files could be moved or renamed. (On System Vish platforms, e.g. Solaris and HP-UX, 'libexec' isn't used -- files that other systems put into 'libexec' go into 'lib'.) - river. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (HP-UX) iEYEARECAAYFAks6OpgACgkQIXd7fCuc5vJ2IACfSXNKUbHi1r0mRWIvfTgl6ATk HMEAn1uAhwdFn+yQMAnAP/RrYx07wlIv =t1pG -----END PGP SIGNATURE-----

2 1

[Dovecot] multiple attribute templates?
by Mariano Absatz 29 Dec '09

29 Dec '09

Hi, I've been using an attribute template for some time without any problems. My accounts are on an LDAP server and I have an attribute maildropPath which is the maildir path for the user relative to /home/vmail That is, user "mabsatz(a)example.org" has, in attribute maildropPath the string "example.org/mabsatz", meaning that the maildir is in /home/vmail/example.org/mabsatz This is configured like this (taken from http://wiki.dovecot.org/AuthDatabase/LDAP/Userdb) user_attrs = maildropPath=mail=maildir:/home/vmail/%$ pass_attrs = uid=user,userPassword=password,maildropPath=userdb_mail=maildir:/home/vmail/%$ and it works OK. Now I want to start using sieve and, since all accounts are virtual, I want to use a subdirectory "sieve" within the maildir to hold the scripts, so I need (I think) a userdb home to point to the same path... being a monkey I tried to imitate (or rather, extend) the previous configuration like this: user_attrs = maildropPath=mail=maildir:/home/vmail/%$,maildropPath=home=/home/vmail/%$ pass_attrs = uid=user,userPassword=password,maildropPath=userdb_mail=maildir:/home/vmail/%$,maildropPath=userdb_home=/home/vmail/%$ Alas... this didn't work... that is, apparently, the "home" attribute works OK (I got my scripts on the /home/vmail/example.org/mabsatz/sieve directory), but the "mail" attribute got lost and mail is being delivered to /home/vmail/mabsatz. Is there a way to use more than one attribute template AND that both use the same LDAP attribute? Otherwise, can someone think of a better way to do what I'm trying to do? I'm using dovecot 1.1.11 from the standard ubuntu 9.04 package (dovecot-imapd_1.1.11-0ubuntu4.1). -- Mariano Absatz - "El Baby" el.baby(a)gmail.com www.clueless.com.ar -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Real programmers use: cat > a.out http://xkcd.com/378/ -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- * TagZilla 0.066 * http://tagzilla.mozdev.org

2 1

[Dovecot] Deliver EX_TEMPFAIL's without giving any information
by Denis Khromov 29 Dec '09

29 Dec '09

Hi all. I've had a hard time trying to find out why deliver isn't working after I've updated dovecot from v1.11 to v1.2.8. It just gave me EX_TEMPFAIL without any info in the logs. My deliver was setuid-root. Once I've made a simple shell wrapper script for the deliver executable which saves deliver's stdout+stderr, I've found the reason: /usr/local/libexec/dovecot/deliver must not be both world-executable and setuid-root. This allows root exploits. See http://wiki.dovecot.org/LDA#multipleuids Did a 'chmod o-x deliver' and fixed groups/owners and now everything works as it should. I think this error message should go to log files, not just to stdout/stderr. And it's worth to describe this behaviour in the Wiki. Cheers, Denis

2 1

[Dovecot] dovecot -n output of (default) is confusing me
by john.blue＠cox.net 29 Dec '09

29 Dec '09

Hello, I'm new to dovecot and I've been taking my time examining what makes dovecot work. If I have imap and pop3 listed as protocols, dovecot -n outputs: mail_executable(default): /usr/local/libexec/dovecot/imap mail_executable(imap): /usr/local/libexec/dovecot/imap mail_executable(pop3): /usr/local/libexec/dovecot/pop3 I don't understand why imap is listed twice once as (default), and the other without (default). As a secondary question, why would you want a default of imap as opposed to pop3? Thanks. John

2 1

[Dovecot] Log rotation?
by Beto Moreno 29 Dec '09

29 Dec '09

Hi people. I had read dovecot logging info, they say something about using log rotation to help us rotate our log, with this setup: # dovecot SIGUSR1: Re-opens the log files. /var/log/dovecot*.log { missingok notifempty delaycompress sharedscripts postrotate /bin/kill -USR1 `cat /var/run/dovecot/master.pid 2>/dev/null` 2> /dev/null || true endscript } Well, my question is simple, Do we need to restart the service each time logrotation runs? In my case, is wrong this? var/log/dovecot*.log { weekly rotate 8 notifempty missingok copytruncate create 600 root start 0 } I have 2 dovecot logs: dovecot-info.log dovecot.log dovecot-info.log is the biggest, 5MB by week, is to much? Do I have to change our log rotation to "daily"? Centos 5.4 updated, dovecot 1.0.7-7.el5, thanks!!!

3 3

[Dovecot] Retrieve Physical Message Filename
by Tony Rutherford 29 Dec '09

29 Dec '09

Hi,Using Dovecot 1.2.9 with Maildir and Layout=FS.In a plugin, i'm overriding "update_flags":void my_mail_update_flags(struct mail *_mail, enum modify_type modify_type, enum mail_flags flags)For this email which is having its flags updated, I need to retrieve the physical filename of the message. I see where using:mail_get_special(_mail, MAIL_FETCH_UIDL_FILE_NAME, &fname);...I can retrieve part of the filename, but without the ":2" and the flags part.Is there a method I can use to get the whole filename (without having to reassemble it myself). I've looked around, and I'm guessing it exists, but I don't see it offhand.Thanks,...Tony RutherfordSoftware EngineerBlueTie Inc.arutherford(a)bluetie.com(585) 586-2000 x1040 This message is intended solely for the individual(s) to whom it is addressed. If you are not the intended recipient, any dissemination or copying is strictly prohibited. If you believe you received this message in error, please notify the sender and delete from your system. Thank you.

2 1

[Dovecot] Design: Optimizations for high-latency storage backend
by Timo Sirainen 29 Dec '09

29 Dec '09

Mainly intended for future support of key-value (etc.) databases, but this is probably useful even for regular disk I/O. By using async I/O for disk access, the OS could more intelligently do seeks on disk to read the wanted data with less latency. Problem #1: Accessing message body while searching (e.g. SEARCH BODY). The idea is that searching wouldn't block. Caller would typically use mailbox_search_next_nonblock() function, which can return "try again later" result. Whenever search sees a query that could potentially block (e.g. SEARCH BODY, or searching a header that might not be cached), it goes into a slightly different search mode: - the whole search would typically be run from beginning to end immediately, and the search result state would be stored for each message. - whenever search runs into a situation where the result can't be determined without opening message body, it issues a prefetch command for that message, marks the result for the message as "incomplete", and continues to the next message - once the search is done with all messages, it starts replying to the caller. if the next search result is incomplete at the time, the search returns "try again later". optimizations: - probably there should be prefetch limit (a queue) so that only maybe 10 requests are actually pending at a time. - probably the whole search shouldn't run immediately. maybe it should stop after having 10 requests pending. - prefetch could return only the needed parts of the message, such as "only header" or "only body" (or in future something like "message without attachments") There would be a new call, something like mailbox_search_set_nonblock_callback() that specifies a function to be called when next search result is available. The callback then would continue the search. This is similar to how IMAP SEARCH is already implemented, except currently when mailbox_search_next_nonblock() returns "try again later", Dovecot simply adds a 0 second timeout after which it's called again (that's enough for Dovecot to do some other pending work). Problem #2: Accessing index cache while searching. Cache file is typically in memory or in low-latency disk already. Anyway something similar to #1 could be implemented for it. "Make sure cache x..y bytes in cache file have been read to memory" call or something. Problem #3: Fetching message body (and uncached fields). The nice thing about lib-storage's fetching API is that the caller already specifies what fields it intends to access in mailbox_search_init(). So this code can use a similar technique than searching: - callers only use mailbox_search_next_nonblock() - which keeps returning "try again later" until the message body has been read to memory - trying to access a field that's not specified in wanted_fields in mailbox_search_init() could be (optionally) treated as a programming error and cause a crash instead of a blocking wait. Problem #4: How to drop latencies between IMAP commands? For example a (stupid) client issues commands: a FETCH 1 BODY.PEEK[] a FETCH 2 BODY.PEEK[] ..etc.. You really don't want to a delay between each command. So what Dovecot code needs to happen is to start processing the next command while waiting for previous one to finish reading the body to memory. A lot of this actually already works as intended, but there are some cases that don't, such as FETCH + SELECT (see #5). Problem #5: Opening mailbox index. So if your indexes are also stored in high-latency disk, how do you optimize getting STATUS for each mailbox? Again, a similar idea than before: Create a new mailbox_open_nonblock() function that calls a given callback function when the indexes are read to memory. During the wait it can continue processing more STATUS commands (hopefully client sends them all at once, instead of waiting for each reply before sending next STATUS). .. I think that's all of the problematic cases that could cause blocking. And the solution is always the same: Use prefetching and "try again later" status code with a callback function to be called when it's ready. Luckily there are only two functions that need the above behavior, implementing async callbacks for all functions would have made programming it horrible. The main problem will then be to optimize what and how much to prefetch. For example in the cache file case, should the cache be read to memory when mailbox is opened, or should it be delayed until something is actually wanted to be read from it? Should all of it be read, or should Dovecot attempt to be smarter to reduce memory usage and I/O bandwidth, so e.g. if the cache is wanted to be accessed to 3rd last message, maybe just read the cache file beginning from that message to EOF? Transaction log files have a similar problem. Actually all of this is similar to how Dovecot attempts to cache them to memory when using mmap_disable=yes, so it's not really a new problem.

2 2

[Dovecot] Design: Mailbox list indexes
by Timo Sirainen 29 Dec '09

29 Dec '09

I drove over 2000 miles in recent days, so I had some time to think about future Dovecot things. :) Maybe for v2.1 or v3.0, whichever I happen to release next. Here's the first thought: The main idea behind mailbox list indexes was to make getting STATUS information for mailboxes from a single index file. The code was already written for Dovecot v1.1, but it was disabled because of bugs I never got around to fixing. It also was maybe a bit overdesigned to make it fast with thousands of mailboxes. There were two indexes: Mailbox UID -> name map index, and UID -> status info index. I don't think most people have that many mailboxes. Using two index files just makes the common case slower. So the new mailbox list index could be a single index (read/written to using the same index file API as for mails). Index's header would contain an ID -> string map. So basically an array of {uint32_t id, char nul-terminated-name[]} records. Each index record would contain: - mailbox UID number (32 bit) - ID number (32 bit), pointing to a string in the header. That'll be this mailbox's name. - parent mailbox UID (e.g. if parent's name is "foo" and our name is "bar", the mailbox is "foo/bar") - mailbox global UID (128 bit) - mailbox flags (\Noselect, \Nonexistent) - STATUS information: message/unseen counts, last-non-recent-uid (for recent count), uidvalidity, uidnext, highest-modseq - storage backend specific timestamps So typically the whole index would be read into memory and the mailbox tree would be generated based on the parent UID pointers. If there are any \Noselect or \Nonexistent mailboxes, they just have their GUIDs and STATUS info zeroed out. Each time a mailbox is created or renamed, a new name ID is added to the header with the given name. I don't think it's worth it to try to reuse old IDs. Unused names (after delete/rename) will be dropped sometimes later. Whenever STATUS information changes while accessing mailbox, the STATUS info is updated in mailbox list index. Also unless mailbox_list_index_dirty_syncs=yes (or something similar), the index can't be trusted by itself. So before trusting the index, Dovecot needs to check if the index is up to date by comparing the timestamps to what exists in filesystem. For example with Maildir there would be new/ and cur/ directories' mtimes. Then there's the problem of how to notice externally added/deleted/renamed mailboxes. It'll be immediately noticed if such mailbox is tried to be opened, but what about LIST replies? One possibility would be to refresh the list once when session begins and after that just have LIST return indexed mailboxes. Another would be to keep track of directory mtimes and keep stat()ing the dirs to see if something changes. The latter is probably more trouble than worth.. Besides caching LIST and STATUS replies, there's one additional thing I thought of that the mailbox list indexes will be useful for: atomic mailbox list updates. Even if the backend doesn't support e.g. atomic RENAME (such as Maildir++), this can be made practically atomic using the list index. CREATE, RENAME and DELETE commands begin by writing and committing a record to the mailbox list index about the change. Then they'll start the actual change, and finally write to the index that the change is complete. If it crashed in the middle, the next session would finish it. If another session tries to do a conflicting change before the change is finished, it would wait for the previous one to finish. (Probably practically the index would be write-locked and all changes would wait for previous ones to finish.) And the final functionality of this mailbox list index is for the future support of key-value (etc.) databases: The mailbox list index would be the authoritative list of mailboxes. It wouldn't be stored anywhere else.

1 0

[Dovecot] checking all folders for new mail (IMAP STATUS command)
by Florian Effenberger 29 Dec '09

29 Dec '09

Hello, I use Thunderbird as IMAP client and do a lot of server-side filtering with Sieve scripts. To be notified of new mails, I want to check all folders (a lot of them...) at once for new mails, and not only the inbox. According to http://kb.mozillazine.org/Checking_for_new_messages_in_other_folders_-_Thun… it should be sufficient to enable one setting -- given that the IMAP server returns the STATUS command correctly. I still run Dovecot 1.0 (from Debian 4.0), and it seems this version doesn't support the IMAP STATUS command, as I have to explictly query each folder with the second mentioned setting. What is the recommended way of checking all folders for new mails? Is there any server-side setting I can activate? Do newer versions of Dovecot support the STATUS command in the way Thunderbird expects it? Or does Dovecot even offer an option like the mentioned IMAP_CHECK_ALL_FOLDERS=1 and IMAP_ENHANCEDIDLE=1 in Courier? Sorry for my maybe dumb question... :-) Thanks, Florian

6 13

Re: [Dovecot] Dovecot-deliver sometimes fails when message set to discard via sieve
by Tobias Lang 29 Dec '09

29 Dec '09

Am 28.12.2009 um 21:51 schrieb Steve Wagner: > Sorry it took some time to get in to this failing situation. > > Procmail log--> > > procmail: [29952] Mon Dec 28 21:36:33 2009 > procmail: Match on "< 256000" > procmail: Locking "spamassassin.lock" > procmail: Executing "/usr/bin/spamc,-U,/var/run/spamd.sock" > procmail: [29952] Mon Dec 28 21:36:35 2009 > procmail: Unlocking "spamassassin.lock" > procmail: No match on "^X-Spam-Level: \*\*\*\*\*\*\*\*\*\*" > procmail: No match on "^X-Spam-Status: YES" > procmail: No match on "^List-Id: .*debian-arm.lists.debian.org" > procmail: No match on "^^rom[ ]" > procmail: Executing "/opt/dovecot/libexec/dovecot/deliver" > procmail: Error while writing to "/opt/dovecot/libexec/dovecot/deliver" > procmail: Assigning "LASTFOLDER=/opt/dovecot/libexec/dovecot/deliver" > procmail: Assigning > "LASTFOLDER=/home/lanwin/Maildir/new/1262032593.29952_2.vs5923" > procmail: Notified comsat: > "lanwin@0:/home/lanwin/Maildir/new/1262032593.29952_2.vs5923" > From KeineAntwortAdresse(a)web.de Mon Dec 28 21:36:33 2009 > Subject: discoTEL > =?ISO-8859-1?Q?Tarif=3A_F=FCr_7=2C5_Cent=2FMin=2E_telefonier > Folder: /home/lanwin/Maildir/new/1262032593.29952_2.vs5923 > 41096 > procmail: Unlocking "/home/lanwin/Maildir/.lockmail" > > Dovecot Deliver Log--> > > 2009-12-28 21:36:35 deliver(lanwin): Info: sieve: > msgid=<E1NPMKF-00014k-00(a)mxnl04.web.de>: marked message to be discarded > if not explicitly delivered (discard action) Does it always fail, if you try to do a discard, just sometimes? I am using Dovecot 1.2.9 "dovecot-1.2-sieve-0.1.14" and discarding email seems to work fine. The things I can think of are: 1) Wrong privileges for deleting. What user does procmail / deliver run as? 2) Old Bug in Sieve (http://www.dovecot.org/list/dovecot/2007-July/024290.html) 3) If it fails just sometimes, what is the difference between discarded and nondiscarded mails. If this does not turn up something, I do not have an idea what is going wrong. Only bugfix I then can you provide with, is not to discard but to move those files to a folder 'SPAM' and delete them by hand. Tobi

1 0

[Dovecot] Shared mailboxes do not support subfolders
by Nick Rosier 29 Dec '09

29 Dec '09

Hi, I'm currently running Dovecot 1.2.8 with dbox mailboxes. I've configured the use of shared mailboxes. I'm able to only see the top-level mailboxes: e.g. Inbox LogWatch Trash Sent but not LogWatch/Server1 LogWatch/Server2 Is this a know limitation of a bug? Rgds, N.

2 3

[Dovecot] sieve vs deliver -m
by Frank Cusack 29 Dec '09

29 Dec '09

I'm invoking deliver through postfix with a dovecot transport in master.cf, using the -m ${extension} argument. If I have no sieve script, or a sieve script with an implicit keep, the mail gets correctly filed into the -m mailbox. However if the sieve script has an explicit discard, this gets honored if it doesn't match another sieve action. Shouldn't -m take precedence? I would say that if an extension is present any other sieve action should be ignored, perhaps just sieve_before should be run then the message filed per the extension. -frank

2 7

[Dovecot] Fwd: Dovecot-deliver sometimes fails when message set to discard via sieve
by Tobias Lang 28 Dec '09

28 Dec '09

Anfang der weitergeleiteten E-Mail: > Von: Steve Wagner <lanwin(a)lanwin.de> > Datum: 28. Dezember 2009 21:51:39 MEZ > An: Tobias Lang <tobias.lang(a)evoscout.de> > Betreff: Re: [Dovecot] Dovecot-deliver sometimes fails when message set to discard via sieve > > Sorry it took some time to get in to this failing situation. > > Procmail log--> > > procmail: [29952] Mon Dec 28 21:36:33 2009 > procmail: Match on "< 256000" > procmail: Locking "spamassassin.lock" > procmail: Executing "/usr/bin/spamc,-U,/var/run/spamd.sock" > procmail: [29952] Mon Dec 28 21:36:35 2009 > procmail: Unlocking "spamassassin.lock" > procmail: No match on "^X-Spam-Level: \*\*\*\*\*\*\*\*\*\*" > procmail: No match on "^X-Spam-Status: YES" > procmail: No match on "^List-Id: .*debian-arm.lists.debian.org" > procmail: No match on "^^rom[ ]" > procmail: Executing "/opt/dovecot/libexec/dovecot/deliver" > procmail: Error while writing to "/opt/dovecot/libexec/dovecot/deliver" > procmail: Assigning "LASTFOLDER=/opt/dovecot/libexec/dovecot/deliver" > procmail: Assigning > "LASTFOLDER=/home/lanwin/Maildir/new/1262032593.29952_2.vs5923" > procmail: Notified comsat: > "lanwin@0:/home/lanwin/Maildir/new/1262032593.29952_2.vs5923" > From KeineAntwortAdresse(a)web.de Mon Dec 28 21:36:33 2009 > Subject: discoTEL > =?ISO-8859-1?Q?Tarif=3A_F=FCr_7=2C5_Cent=2FMin=2E_telefonier > Folder: /home/lanwin/Maildir/new/1262032593.29952_2.vs5923 > 41096 > procmail: Unlocking "/home/lanwin/Maildir/.lockmail" > > Dovecot Deliver Log--> > > 2009-12-28 21:36:35 deliver(lanwin): Info: sieve: > msgid=<E1NPMKF-00014k-00(a)mxnl04.web.de>: marked message to be discarded > if not explicitly delivered (discard action) > > Dose not look better to me. > > Steve > > Am 28.12.2009 18:06, schrieb Tobias Lang: >> >> Am 28.12.2009 um 15:09 schrieb Steve Wagner: >> >>> [snip] >>> >>> :0 w >>> | /opt/dovecot/libexec/dovecot/deliver >> >> Looks uncritical to me. Although there is no default rule at the end of >> .procmailrc, Dovecot deliver and Sieve should reroute everything not >> catched by a rule to INBOX. >> >> Did Procmails "VERBOSE=on" reveal something? >> >> Tobi >>

1 0

[Dovecot] managesieve error
by Lampa 26 Dec '09

26 Dec '09

Hello, when using sieve-php and using LOGIN auth, getting: 2009-11-21T15:13:48+0100 managesieve-login: Panic: file client.c: line 449 (client_set_auth_waiting): assertion failed: (client->to_auth_waiting == NULL) 2009-11-21T15:13:48+0100 dovecot: Error: child 8474 (login) killed with signal 6 (core dumps disabled) (latest ip=127.0.0.1) I'm using dovecot 1.2.6 from package debian testing (1:1.2.6-1) -- Lampa

2 1

[Dovecot] basic understanding of imap in dovecot
by dovecot＠paz.bz 24 Dec '09

24 Dec '09

I have always used a pop3 daemon, and switching to dovecot has been my introduction to imap. Imap is foreign to me. I am wondering if I am a little off-track here, and would like some clarification. My MTA (exim) delivers email to: /mail/user dovecot, sucks that mail from /mail/user TO /home/user/mail/<filenamesoffolders> dovecot IMAP further uses /home/user/mail/.imap/folders/{.index / .index.cache / .index.log} the mail folder which exim uses doesn't seem to get emptied by dovecot when it sucks the email into /home/user/mail/<filenamesoffolders> when using IMAP. If POP3 is used via dovecot, then it appears that the interaction is directly to the original exim folder and that it does indeed empty (or at least it has the "FOLDER INTERNAL DATA" entry). I suppose my question is, is there a way to have dovecot empty/parse the original exim mailbox so that the customer email isn't sitting in two spots, taking up double the space. This would be in the IMAP environment only, as POP3 seems to be fine. Any online references available to help a newbee understand IMAP? Thanks!

3 2

[Dovecot] 2.0.beta1/07e688afe81b imap crash
by Pascal Volk 24 Dec '09

24 Dec '09

Hi Timo, I've replaced a mdbox, as long Thunderbird was connected. The result is attached. Regards, Pascal -- The trapper recommends today: face1e55.0935803(a)localdomain.org #0 0x00007f0caa42ea18 in mail_namespace_get_vname (ns=0x0, dest=0x145d460, name=0x14bf1f9 "INBOX") at mail-namespace.c:418 No locals. #1 0x00007f0caa48eec0 in index_storage_mailbox_alloc (ibox=0x14b7890, name=0x14bf1f9 "INBOX", input=0x0, flags=265, index_prefix=0x7f0caa4e67b2 "dovecot.index") at index-storage.c:461 box = 0x14b7890 path = 0x14b7890 "x{K\001" dir_gid = 0 origin = 0x14b7828 "" dir_origin = 0x2d8 <Address 0x2d8 out of bounds> vname = 0x145d460 __PRETTY_FUNCTION__ = "index_storage_mailbox_alloc" #2 0x00007f0caa4cdd89 in mdbox_mailbox_alloc (storage=0x1462a20, list=0x0, name=0x14bf1f9 "INBOX", input=0x0, flags=265) at mdbox-storage.c:126 mbox = 0x14b7890 pool = 0x14b7828 #3 0x00007f0caa4cc84d in rebuild_restore_msg (ctx=0x14c4cf0, msg=0x151a098) at mdbox-storage-rebuild.c:545 storage = 0x1462a20 file = 0x0 hdr = 0x7fffc4a037c0 dbox_rec = {map_uid = 0, save_date = 0} mailbox = 0x14bf1f9 "INBOX" box = 0x0 mbox = 0x100000009 error = MAIL_ERROR_NONE deleted = false created = false size = 834 ret = 1 seq = 0 __PRETTY_FUNCTION__ = "rebuild_restore_msg" #4 0x00007f0caa4ccb73 in rebuild_handle_zero_refs (ctx=0x14c4cf0) at mdbox-storage-rebuild.c:632 msgs = 0x14ed000 i = 0 count = 1 #5 0x00007f0caa4ccdbe in rebuild_finish (ctx=0x14c4cf0) at mdbox-storage-rebuild.c:685 No locals. #6 0x00007f0caa4cd13e in mdbox_storage_rebuild_scan (ctx=0x14c4cf0) at mdbox-storage-rebuild.c:762 hdr = 0x14a3910 dir = 0x1475f70 d = 0x0 path = 0x145d298 dir_len = 24 uid_validity = 1261521073 ret = 0 __PRETTY_FUNCTION__ = "mdbox_storage_rebuild_scan" #7 0x00007f0caa4cd226 in mdbox_storage_rebuild (storage=0x1462a20) at mdbox-storage-rebuild.c:788 ctx = 0x14c4cf0 st = {st_dev = 2305, st_ino = 4562950, st_nlink = 2, st_mode = 16832, st_uid = 1000, st_gid = 1000, __pad0 = 0, st_rdev = 0, st_size = 4096, st_blksize = 4096, st_blocks = 8, st_atim = { tv_sec = 1261522332, tv_nsec = 0}, st_mtim = {tv_sec = 1261522325, tv_nsec = 0}, st_ctim = {tv_sec = 1261522325, tv_nsec = 0}, __unused = {0, 0, 0}} ret = 32524 #8 0x00007f0caa4cdc42 in mdbox_storage_destroy (_storage=0x1462a20) at mdbox-storage.c:93 storage = 0x1462a20 #9 0x00007f0caa43416f in mail_storage_unref (_storage=0x14a4ec0) at mail-storage.c:327 storage = 0x1462a20 __PRETTY_FUNCTION__ = "mail_storage_unref" #10 0x00007f0caa42db3a in mail_namespace_free (ns=0x14a4e70) at mail-namespace.c:50 No locals. #11 0x00007f0caa42e7df in mail_namespaces_deinit (_namespaces=0x14c0100) at mail-namespace.c:349 ns = 0x14a4e70 namespaces = 0x0 #12 0x00007f0caa436c9c in mail_user_deinit_base (user=0x14c0090) at mail-user.c:28 No locals. #13 0x00007f0ca91a22e8 in quota_user_deinit (user=0x14c0090) at quota-storage.c:463 quser = 0x14c0e10 #14 0x00007f0caa437257 in mail_user_unref (_user=0x14c8ef8) at mail-user.c:128 user = 0x14c0090 __PRETTY_FUNCTION__ = "mail_user_unref" #15 0x00000000004121e1 in client_destroy (client=0x14c8ea0, reason=0x0) at imap-client.c:197 cmd = 0x7fffc4a03ac8 __PRETTY_FUNCTION__ = "client_destroy" #16 0x0000000000413991 in client_input (client=0x14c8ea0) at imap-client.c:802 cmd = 0xc4a03b0c output = 0x0 bytes = 170 __PRETTY_FUNCTION__ = "client_input" #17 0x00007f0caa1ca9d6 in io_loop_handler_run (ioloop=0x1465f60) at ioloop-epoll.c:208 ctx = 0x1469fc0 events = 0x146a800 event = 0x146a800 list = 0x1466e80 io = 0x1467980 tv = {tv_sec = 4, tv_usec = 997221} events_count = 4 t_id = 2 msecs = 4998 ret = 1 i = 0 j = 0 call = true #18 0x00007f0caa1c9681 in io_loop_run (ioloop=0x1465f60) at ioloop.c:350 No locals. #19 0x00007f0caa1b3aef in master_service_run (service=0x1464ee0, callback=0x41f55f <client_connected>) at master-service.c:473 No locals. #20 0x000000000041f76a in main (argc=1, argv=0x146d010) at main.c:307 set_roots = {0x4234a0, 0x0} service_flags = MASTER_SERVICE_FLAG_KEEP_CONFIG_OPEN storage_service_flags = MAIL_STORAGE_SERVICE_FLAG_DISALLOW_ROOT postlogin_socket_path = 0x0

1 0

[Dovecot] Permissions errors while reading messages via IMAP
by Geoff Sweet 24 Dec '09

24 Dec '09

Greetings all, I have been trying to setup a new system using Postfix and Dovecot to manage email for a bunch of virtual domains. So far everything is great, and I am now at the point where I am trying to build a webmail interface for the system. I'm using RoundCube for now. The tutorial I have been working from is here: http://workaround.org/articles/ispmail-etch/ Which seems to be a decent enough read. At this point I can login without issue but I can't see any mail messages. When I login, dovecot throws errors like this: Dec 23 12:08:49 mail1 dovecot: auth(default): client out: OK 1 user=geoff.sweet(a)test.com Dec 23 12:08:49 mail1 dovecot: auth(default): master in: REQUEST 1 4312 1 Dec 23 12:08:49 mail1 dovecot: auth(default): master out: USER 1 geoff.sweet(a)test.com uid=5000 gid=5000 home=/home/vmail/test.com/geoff.sweet Dec 23 12:08:49 mail1 dovecot: IMAP(geoff.sweet(a)test.com): Effective uid=5000, gid=5000, home=/home/vmail/test.com/geoff.sweet Dec 23 12:08:49 mail1 dovecot: IMAP(geoff.sweet(a)test.com): maildir: data=/home/vmail/test.com/geoff.sweet/Maildir Dec 23 12:08:49 mail1 dovecot: IMAP(geoff.sweet(a)test.com): maildir++: root=/home/vmail/test.com/geoff.sweet/Maildir, index=, control=, inbox=/home/vmail/test.com/geoff.sweet/Maildir Dec 23 12:08:49 mail1 dovecot: imap-login: Login: user=<geoff.sweet(a)test.com>, method=PLAIN, rip=192.168.20.11, lip=192.168.20.12 Dec 23 12:08:49 mail1 dovecot: IMAP(geoff.sweet(a)test.com): Disconnected: Logged out bytes=39/431 Dec 23 12:08:49 mail1 dovecot: auth(default): new auth connection: pid=4315 Dec 23 12:08:49 mail1 dovecot: auth-worker(default): sql(geoff.sweet(a)test.com,192.168.20.11): query: SELECT email as user, password FROM view_mailboxes WHERE email='geoff.sweet(a)test.com'; Dec 23 12:08:49 mail1 dovecot: auth(default): client in: AUTH 1 PLAIN service=imap lip=192.168.20.12 rip=192.168.20.11 lport=143 rport=43878 resp=AGdlb2ZmLnN3ZWV0QHdob290aXMuY29tAGJvYjEyMzQ1 Dec 23 12:08:49 mail1 dovecot: auth(default): client out: OK 1 user=geoff.sweet(a)test.com Dec 23 12:08:49 mail1 dovecot: auth(default): master in: REQUEST 2 4311 1 Dec 23 12:08:49 mail1 dovecot: auth(default): master out: USER 2 geoff.sweet(a)test.com uid=5000 gid=5000 home=/home/vmail/test.com/geoff.sweet Dec 23 12:08:49 mail1 dovecot: imap-login: Login: user=<geoff.sweet(a)test.com>, method=PLAIN, rip=192.168.20.11, lip=192.168.20.12 Dec 23 12:08:49 mail1 dovecot: IMAP(geoff.sweet(a)test.com): Effective uid=5000, gid=5000, home=/home/vmail/test.com/geoff.sweet Dec 23 12:08:49 mail1 dovecot: IMAP(geoff.sweet(a)test.com): maildir: data=/home/vmail/test.com/geoff.sweet/Maildir Dec 23 12:08:49 mail1 dovecot: IMAP(geoff.sweet(a)test.com): maildir++: root=/home/vmail/test.com/geoff.sweet/Maildir, index=, control=, inbox=/home/vmail/test.com/geoff.sweet/Maildir Dec 23 12:08:49 mail1 dovecot: IMAP(geoff.sweet(a)test.com): Namespace : Using permissions from /home/vmail/test.com/geoff.sweet/Maildir: mode=0700 gid=-1 Dec 23 12:08:49 mail1 dovecot: IMAP(geoff.sweet(a)test.com): open(/home/vmail/test.com/geoff.sweet/Maildir/dovecot.index.log) failed: Permission denied (euid=5000(vmail) egid=5000(vmail) missing +r perm: /home/vmail/test.com/geoff.sweet/Maildir/dovecot.index.log) Dec 23 12:08:49 mail1 dovecot: IMAP(geoff.sweet(a)test.com): open(/home/vmail/test.com/geoff.sweet/Maildir/dovecot-uidlist) failed: Permission denied Dec 23 12:08:49 mail1 last message repeated 2 times There is some permission issue that allows dovecot to deliver email to the /home/vmail location (I dislike this location and want to change it) via the dovecot LDA process, but then not be able to read it when accessed via IMAP. I'm very confused lol. Dovecot version 1.2.9 dovecot -n: # 1.2.9: /etc/dovecot.conf # OS: Linux 2.6.18-164.6.1.el5 i686 CentOS release 5.4 (Final) ext3 login_dir: /var/run/dovecot/login login_executable(default): /usr/libexec/dovecot/imap-login login_executable(imap): /usr/libexec/dovecot/imap-login login_executable(pop3): /usr/libexec/dovecot/pop3-login login_greeting: Dovecot ready. mail_location: maildir:/home/vmail/%d/%n/Maildir mail_debug: yes mail_executable(default): /usr/libexec/dovecot/imap mail_executable(imap): /usr/libexec/dovecot/imap mail_executable(pop3): /usr/libexec/dovecot/pop3 mail_plugin_dir(default): /usr/lib/dovecot/imap mail_plugin_dir(imap): /usr/lib/dovecot/imap mail_plugin_dir(pop3): /usr/lib/dovecot/pop3 lda: log_path: /home/vmail/dovecot-deliver.log auth_socket_path: /var/run/dovecot/auth-master postmaster_address: postmaster(a)test.com mail_plugins: global_script_path: /home/vmail/globalsieverc auth default: mechanisms: plain login debug: yes debug_passwords: yes passdb: driver: sql args: /etc/dovecot/dovecot-sql.conf userdb: driver: static args: uid=5000 gid=5000 home=/home/vmail/%d/%n allow_all_users=yes 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: vmail

2 4

[Dovecot] virtual plugin: Broken mailbox list
by e-frog 23 Dec '09

23 Dec '09

Hello Timo, I'm testing the latest hg version from the 1.2 series and get the following in dovecot's error log as soon as I try to access the virtual mailbox Dec 11 18:23:07 ubuntu-test dovecot: IMAP(xxxxx): virtual index /etc/dovecot/virtual/unseen: Broken mailbox list $ cat dovecot-virtual * unseen $ dovecot -n # 1.2.8: /etc/dovecot/dovecot.conf # OS: Linux 2.6.31-16-generic-pae i686 Ubuntu 9.10 protocols: imap imaps managesieve 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(managesieve): /usr/lib/dovecot/managesieve-login verbose_proctitle: yes mail_location: maildir:~/.maildir mail_debug: yes mail_drop_priv_before_exec: yes mail_executable(default): /usr/lib/dovecot/rawlog /usr/lib/dovecot/wrapper.sh mail_executable(imap): /usr/lib/dovecot/rawlog /usr/lib/dovecot/wrapper.sh mail_executable(managesieve): /usr/lib/dovecot/managesieve mail_plugins(default): expire fts fts_squat virtual quota imap_quota mail_log acl mail_plugins(imap): expire fts fts_squat virtual quota imap_quota mail_log acl mail_plugins(managesieve): mail_plugin_dir(default): /usr/lib/dovecot/modules/imap mail_plugin_dir(imap): /usr/lib/dovecot/modules/imap mail_plugin_dir(managesieve): /usr/lib/dovecot/modules/managesieve mail_log_max_lines_per_sec: 0 namespace: type: private separator: / inbox: yes list: yes subscriptions: yes namespace: type: private separator: / prefix: virtual/ location: virtual:/etc/dovecot/virtual:INDEX=~/.maildir/control:CONTROL=~/.maildir/control list: children lda: postmaster_address: postmaster@ubuntu hostname: ubuntu mail_plugins: sieve virtual expire quota acl mail_plugin_dir: /usr/lib/dovecot/modules/lda deliver_log_format: msgid=%m: from=%f: %$ log_path: /var/log/deliver.log info_log_path: /var/log/deliver.log sendmail_path: /usr/lib/sendmail rejection_subject: Rejected: %s rejection_reason: Your message to <%t> was automatically rejected:%n%r auth_socket_path: /var/run/dovecot/auth-master auth default: passdb: driver: sql args: /etc/dovecot/dovecot-sql.conf userdb: driver: sql args: /etc/dovecot/dovecot-sql.conf socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: postfix group: postfix master: path: /var/run/dovecot/auth-master mode: 438 plugin: quota: dict:user::proxy::dictionary expire: Trash 1 "INBOX/log check" 1 expire_dict: proxy::dictionary mail_log_events: delete undelete expunge copy mailbox_delete mailbox_rename flag_change mail_log_fields: uid box msgid size flags sieve: ~/.dovecot.sieve sieve_dir: ~/sieve deliver_log_format: msgid=%m: from=%f: %$ fts: squat fts_squat: partial=4 full=10 dict: dictionary: mysql:/etc/dovecot/dovecot-dict-sql.conf

2 2

[Dovecot] imap-login crashes after upgrade to Dovecot 1.2.8 Linux 64-bit
by Chris Wakelin 23 Dec '09

23 Dec '09

Hi all, We moved our Dovecot installation first of all to have all folders and inboxes on NetApps via NFS (with indexes local) then from a physical Solaris 8 4-way UltraSparc server running Dovecot 1.2.5 (32-bit) to a virtualised Ubuntu 8.04 64-bit server with a single virtual processor (in VMWare ESX 3.5) running Dovecot 1.2.8 (64-bit). Since the change, many of our users have experienced random disconnections when proxied in imap-login (either using the internal SSL proxy, or to an external IMAP server) and the error logs contain things like: > Dec 18 00:27:58 imap-login: Info: Disconnected: Connection queue full (auth failed, 1 attempts): user=<user0>, method=PLAIN, rip=<ip0>, lip=134.225.32.156, TLS > Dec 18 00:27:58 imap-login: Panic: file ioloop.c: line 39 (io_add): assertion failed: (fd >= 0) > Dec 18 00:27:58 IMAP 9486 <user1> <ip1> : Info: Connection closed bytes=224/1753 > Dec 18 00:27:58 IMAP 10116 <user2> <ip2> : Info: Connection closed bytes=82/707 ... > Dec 18 00:27:58 IMAP 10296 <user3> <ip3> : Info: Disconnected in IDLE bytes=44/435 > Dec 18 00:27:58 IMAP 10298 <user3> <ip3> : Info: Disconnected in IDLE bytes=263/1662 > Dec 18 00:27:58 dovecot: Error: child 5124 (login) killed with signal 6 (core dumped) (latest ip=<ip0>) > Dec 18 00:27:58 imap-login: Info: Aborted login (no auth attempts): rip=<ip0>, lip=134.225.32.156, TLS: Disconnected and a backtrace gives: > (gdb) bt > #0 0x00007ff1030ad095 in raise () from /lib/libc.so.6 > #1 0x00007ff1030aeaf0 in abort () from /lib/libc.so.6 > #2 0x00000000004112d5 in default_fatal_finish (type=<value optimized out>, status=0) at failures.c:160 > #3 0x0000000000411333 in i_internal_fatal_handler (type=LOG_TYPE_PANIC, status=0, fmt=<value optimized out>, args=<value optimized out>) at failures.c:443 > #4 0x0000000000410996 in i_panic (format=0x6 <Address 0x6 out of bounds>) at failures.c:207 > #5 0x000000000041420e in io_add (fd=-1, condition=IO_READ, callback=0x404db0 <client_input>, context=0x6af000) at ioloop.c:39 > #6 0x00000000004059db in client_auth_failed (client=0x6af000, nodelay=true) at client-authenticate.c:103 > #7 0x0000000000405e07 in client_handle_args (client=0x6af000, args=<value optimized out>, success=true, nodelay_r=0x7fff571009af) > at client-authenticate.c:198 > #8 0x0000000000406214 in sasl_callback (_client=0x6af000, reply=SASL_SERVER_REPLY_SUCCESS, data=0x0, args=0x6361d0) at client-authenticate.c:277 > #9 0x000000000040eb13 in auth_client_input_ok (conn=0x75b6c8, args=<value optimized out>) at auth-server-request.c:196 > #10 0x000000000040dbf3 in auth_client_input (conn=0x75b6c8) at auth-server-connection.c:136 > #11 0x0000000000414aa8 in io_loop_handler_run (ioloop=<value optimized out>) at ioloop-epoll.c:208 > #12 0x0000000000413b9d in io_loop_run (ioloop=0x6552b0) at ioloop.c:335 > #13 0x0000000000408e81 in main (argc=2, argv=0x7fff57100c58, envp=0x7fff57100c70) at main.c:494 Up until this afternoon we had "login_process_per_connection = yes", and login_max_connections at the default (256). This evening I tried with "login_process_per_connection = no" with no problems, except more CPU load and needing to increase login_max_processes_count (and strictly speaking the max fds set with ulimit -n would need to be increased, though I didn't do that as it would have involved killing and restarting the master process - come back Solaris plimit!) Just after midnight, I switched back to "login_process_per_connection = no" and set "login_max_connections = 32" and managed to get core dumps enabled, hence the above! Apart from this problem, the virtual machine has been doing extremely well, so it's not CPU or I/O load related. I'm not sure whether the problem is caused by the switch from Dovecot 1.2.5 to 1.2.8, Solaris to Linux, physical to virtual, or 32-bit to 64-bit! Perhaps we changed too much at once, but it did mean we kept the service going while power was turned off in our main machine room last weekend ... Best Wishes, Chris -- --+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+- Christopher Wakelin, c.d.wakelin(a)reading.ac.uk IT Services Centre, The University of Reading, Tel: +44 (0)118 378 8439 Whiteknights, Reading, RG6 2AF, UK Fax: +44 (0)118 975 3094

2 6

[Dovecot] expire db(s)?
by ben＠electricembers.net 23 Dec '09

23 Dec '09

with two separate dovecot/backend servers accessing one central mysql server, will it be ok to have them both use the same expires table? Or will that confuse the actual dovecot --exec-mail ext /usr/local/libexec/dovecot/expire-tool.sh cronjob since some of the entries mailboxes won't exist locally? Ben

2 3

[Dovecot] qpopper to dovecot migration
by Jernej Porenta 23 Dec '09

23 Dec '09

Heya, We are in the process of migrating from qpopper to dovecot as POP3 server (and IMAP as well) and we hit the UIDL issue with dovecot. Qpopper uses its own algorithm to create UIDL values and if you set it up to write them down in the mbox file as X-UIDL, then dovecot can use them (pop_uidl_reuse = yes). But if you don't use that feature from qpopper, than X-UIDLs are missing and there is no way to create the same UIDL values. So, I was wondering if anyone else hit that issue and maybe knows how to address it (writing an extension or something)? Thanks in advance, regards, Jernej

2 1

[Dovecot] Dovecot Deliver CPU usage
by Aravind Divakaran 23 Dec '09

23 Dec '09

Hi All, We have upgraded the dovecot from 1.0 to 1.2.8. After upgradation we have noticed that dovecot deliver process is utilizing a lot of CPU. As a result the mailsystem will stop working. When we limit the no of procs in postfix for dovecot deliver the CPU usage will come down. But we are not facing this problem with the previous version. Below is the log files for dovecot when the error occurs write_full(/home/vmail/dhanbank.co.in/vinukumarvm/temp.server.be3e5a849a909847) failed: No space left on device dovecot: deliver(user(a)example.com): stat(/tmp/Dovecot Delivery Mail) failed: No space left on device But my system has 54gb of free space for root filesystem where tmp residing. Can anyone help me to solve this issue. Rgds, Aravind

5 17

[Dovecot] Panic: file maildir-uidlist.c: line 1242 (maildir_uidlist_records_drop_expunges): assertion failed
by Anton Dollmaier 23 Dec '09

23 Dec '09

Hi all, after inserting another sieve-rule, I get the following backtrace on deliver. The mail gets delivered into the Mailbox, but as deliver does not exit with 0, postfix bounces the mail. The additional rule is the same as all others in my .dovecot-sieve: > require ["fileinto", "include"]; > > if header :contains ["From"] ["@terra.a1a-server.de"] { > fileinto "Server.ADITSystems.terra"; > (...) > } elsif header :contains ["From"] ["@neon.a1a-server.de"] { > fileinto "Server.ADITSystems.neon"; > } else { > include :global "shared.sieve"; > fileinto "Server.Serveradmin"; > } > Dec 23 11:23:37 deliver(serveradmin(a)aditsystems.de): Panic: file > maildir-uidlist.c: line 1242 (maildir_uidlist_records_drop_expunges): > assertion failed: (recs[i]->uid < rec->uid) > Dec 23 11:23:37 deliver(serveradmin(a)aditsystems.de): Error: Raw backtrace: > /usr/lib/dovecot/deliver [0x80e52a1] -> > /usr/lib/dovecot/deliver(default_fatal_handler+0x3a) [0x80e53ca] -> > /usr/lib/dovecot/deliver [0x80e4c79] -> /usr/lib/dovecot/deliver > [0x807e097] -> > /usr/lib/dovecot/deliver(maildir_uidlist_sync_finish+0x29f) > [0x807f10f] -> > /usr/lib/dovecot/deliver(maildir_uidlist_sync_deinit+0xa8) > [0x807f458] -> > /usr/lib/dovecot/deliver(maildir_transaction_save_commit_pre+0x399) > [0x80820c9] -> /usr/lib/dovecot/deliver [0x807bbb2] -> > /usr/lib/dovecot/deliver(index_transaction_commit+0x4e) [0x80a472e] > -> /usr/lib/dovecot/deliver(mailbox_transaction_commit+0x26) > [0x80a9716] -> /usr/lib/dovecot/modules/lda/lib90_sieve_plugin.so > [0xb7d30b84] -> > /usr/lib/dovecot/modules/lda/lib90_sieve_plugin.so(sieve_result_execute+0x244) > [0xb7d2a024] -> > /usr/lib/dovecot/modules/lda/lib90_sieve_plugin.so(sieve_execute+0x87) > [0xb7d37fa7] -> /usr/lib/dovecot/modules/lda/lib90_sieve_plugin.so > [0xb7d1bcde] -> /usr/lib/dovecot/deliver(main+0x1108) [0x8061618] -> > /lib/i686/cmov/libc.so.6(__libc_start_main+0xe5) [0xb7d8a455] -> > /usr/lib/dovecot/deliver [0x805f3c1] Following output of "dovecot -n": > # 1.2.8: /etc/dovecot/dovecot.conf > # OS: Linux 2.6.26-2-686-bigmem i686 Debian 5.0.3 > protocols: imap imaps managesieve pop3 pop3s > listen: [::], * > ssl_cert_file: /etc/dovecot/dovecot.pem > ssl_key_file: /etc/dovecot/dovecot.pem > 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 > login_executable(managesieve): /usr/lib/dovecot/managesieve-login > login_process_per_connection: no > login_processes_count: 5 > mail_privileged_group: vmail > mail_location: maildir:~/Maildir > mail_executable(default): /usr/lib/dovecot/imap > mail_executable(imap): /usr/lib/dovecot/imap > mail_executable(pop3): /usr/lib/dovecot/pop3 > mail_executable(managesieve): /usr/lib/dovecot/managesieve > mail_plugins(default): autocreate expire quota imap_quota > mail_plugins(imap): autocreate expire quota imap_quota > mail_plugins(pop3): > mail_plugins(managesieve): > 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 > mail_plugin_dir(managesieve): /usr/lib/dovecot/modules/managesieve > imap_client_workarounds(default): delay-newmail tb-extra-mailbox-sep > imap_client_workarounds(imap): delay-newmail tb-extra-mailbox-sep > imap_client_workarounds(pop3): > imap_client_workarounds(managesieve): > pop3_save_uidl(default): no > pop3_save_uidl(imap): no > pop3_save_uidl(pop3): yes > pop3_save_uidl(managesieve): no > pop3_uidl_format(default): %08Xu%08Xv > pop3_uidl_format(imap): %08Xu%08Xv > pop3_uidl_format(pop3): UID%u-%v > pop3_uidl_format(managesieve): %08Xu%08Xv > pop3_client_workarounds(default): > pop3_client_workarounds(imap): > pop3_client_workarounds(pop3): outlook-no-nuls oe-ns-eoh > pop3_client_workarounds(managesieve): > managesieve_implementation_string(default): dovecot > managesieve_implementation_string(imap): dovecot > managesieve_implementation_string(pop3): dovecot > managesieve_implementation_string(managesieve): Cyrus timsieved v2.2.13 > namespace: > type: private > separator: . > prefix: INBOX. > inbox: yes > list: yes > subscriptions: yes > namespace: > type: public > separator: . > prefix: Server. > location: maildir:/var/mail/vmail/%d/shared/Server:INDEX=~/indexes/Server > list: yes > subscriptions: yes > lda: > postmaster_address: postmaster(a)terra.a1a-server.de > mail_plugins: quota sieve autocreate > deliver_log_format: %m:%$:%f:%s > log_path: /var/log/dovecot-deliver.log > info_log_path: /var/log/dovecot-deliver.log > auth default: > mechanisms: plain login > passdb: > driver: sql > args: /etc/dovecot/dovecot-sql.conf > passdb: > driver: sql > args: /etc/dovecot/dovecot-sql-master.conf > userdb: > driver: sql > args: /etc/dovecot/dovecot-sql.conf > socket: > type: listen > client: > path: /var/spool/postfix/private/auth > mode: 432 > user: postfix > group: postfix > master: > path: /var/run/dovecot/auth-master > mode: 438 > plugin: > sieve: ~/.dovecot.sieve > sieve_global_dir: /etc/dovecot/sieve/ > sieve_dir: %h/sieve > autocreate: INBOX.Trash > autocreate2: INBOX.Spam > autocreate3: INBOX.Sent > autosubscribe: INBOX.Trash > autosubscribe2: INBOX.Spam > autosubscribe3: INBOX.Sent Best regards & merry christmas! Anton Dollmaier

2 1

[Dovecot] Openbsd Postfix-Dovecot-SASL
by thekat 22 Dec '09

22 Dec '09

Greetings all, I have a OpenBSD /Dovecot server at home running and sending / receiving email "internally" without issue.. Recently, I set up the same at our Parish, but one of our users wants to get their email externally. The user can read their email but has to "send" via the local ISP server.. The problem After much searching I have not found an answer to my question. I would like the user to authenticate to be able to "send" email "through" the server.. OpenBSD uses bsdauth by default in Dovecot. After reading the Postfix http://www.postfix.org/SASL_README.html and the Dovecot Wiki http://wiki.dovecot.org/HowTo/PostfixAndDovecotSASL I have tried multiple configurations but I can't seem to get this to work.. It may be something very simple that I am missing.. All users on the Server have accounts in /etc/passwd (just no shell) Postfix - main.cf mailbox_command = /usr/local/libexec/dovecot/deliver mynetworks = 127.0.0.0/8 smtpd_sasl_type = dovecot smtpd_sasl_path = private/auth smtpd_sasl_auth_enable = yes smtpd_recipient_restrictions = permit_mynetworks, permit_sasl_authenticated, reject_unauth_destination dovecot --version 1.1.16 dovecot -n # OS: OpenBSD 4.6 i386 base_dir: /var/dovecot/ protocols: imaps listen: *, [::] 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 login_max_processes_count: 256 max_mail_processes: 32 mail_location: maildir:~/Maildir mbox_write_locks: fcntl imap_client_workarounds: delay-newmail netscape-eoh tb-extra-mailbox-sep auth default: cache_size: 1024 passdb: driver: bsdauth args: cache_key=%u userdb: driver: passwd socket: type: listen client: path: /var/run/auth-client mode: 432 user: _postfix master: path: /var/run/auth-master mode: 384 user: _postfix Error using bsdauth Dec 21 15:07:09 aml000t3 dovecot: dovecot v1.1.16 starting up Dec 21 15:07:09 aml000t3 dovecot: Panic: auth(default): file passdb.c: line 190 (passdb_init): assertion failed: (passdb->passdb->default_pass_scheme != NULL || passdb->passdb->cache_key == NULL) Dec 21 15:07:09 aml000t3 dovecot: child 18954 (auth) killed with signal 6 (core not dumped) Dec 21 15:07:09 aml000t3 dovecot: Fatal: Auth process died too early - shutting down It looks like bsdauth has a bug and even though this thread "lists" a patch, I haven't been able to find it.. http://old.nabble.com/bsdauth-with-cache_key-failed-ts25800484.html#a258004… so I guess I am looking for an alternative to be able to allow users to "send through the server" Thx for any pointers tk -- View this message in context: http://old.nabble.com/Openbsd-Postfix-Dovecot-SASL-tp26890148p26890148.html Sent from the Dovecot mailing list archive at Nabble.com.

2 4

[Dovecot] Remove From Server When Deleted From Deleted Items
by Matt 21 Dec '09

21 Dec '09

In Windows Live Mail I have this setting enabled: "Remove From Server When Deleted From Deleted Items". It does not seem to remove them even when the trash is emptied though. Am using POP3 access. Anyone else see this? Matt

1 0

[Dovecot] Dovecot v2.0 wiki
by Timo Sirainen 21 Dec '09

21 Dec '09

I forked the wiki to http://wiki1.dovecot.org/ is the old docs for v1.x http://wiki2.dovecot.org/ is the new docs for v2.0 For now wiki.dovecot.org points to wiki1, but once v2.0 is released I'll change it to point to wiki2. I symlinked the user directory, so users should stay synced between the wikis. The main reason for wiki2 is to be able to describe Dovecot v2.0's actual behavior everywhere and get rid of all the old v1.x specific settings. The wiki1 is already annoyingly bloated and confusing with information about v1.0 and then v1.1 and maybe even how it's still different in v1.2.. Now would be a good time to do any other larger changes, if anyone has suggestions. :) (Oh, and I haven't yet done any actual changes to wiki2..)

3 5

Re: [Dovecot] [exim] Exim + Dovecot deliver overquota problems
by Nikita Koshikov 21 Dec '09

21 Dec '09

On Mon, 21 Dec 2009 13:44:42 +0100 Joan <aseques(a)gmail.com> wrote: > > > > You need to check user's quota on routing stage, not transport. > > > It'd be much better, because I would allow me to mix overquota and > no-overquota recipients. > But the problem in my case is that I am using some hashing to > distribute the users' mailboxes, dovecot can handle this easily > because it supports some interesting stuff > (http://wiki.dovecot.org/Variables) Exim have much more variables and functions http://exim.org/exim-html-4.69/doc/html/spec_html/ch11.html#SECTexpvar, so if you don't use any special dovecot variable data, than it shouldn't be a problem. > With a perl script I could also do that, I would like only if it's the > last resort (too much overhead I would think) > > Parsing file and counting quota value - is trivial stuff. The main disadvantage of this way is executing external aplication on every RCPT TO command. If you'll decide to use perl consider using option perl_at_start to minimize aplication starting time.

1 0

[Dovecot] Released Pigeonhole Sieve v0.1.14 and ManageSieve v0.11.10 for Dovecot v1.2.9
by Stephan Bosch 21 Dec '09

21 Dec '09

Hello Dovecot users, Due to personal matters I haven't had time to do anything in the last few weeks. Before that I provided some pre-releases and since nobody indicated problems with those, I release them definitively now. I hope the shit storm has blown over, so that I can dedicate more of my time towards Pigeonhole development. The Sieve release involves a large architectural change, but also fixes quite a few small problems. The ManageSieve release is necessary to match Sieve API changes. Changelog Sieve v0.1.14: * Made the imposed limits on the number of redirects and the number of actions configurable. The settings are called sieve_max_actions and sieve_max_redirects. * Did a major rework of extension handling, making sure that no global state is maintained. This change was triggered by problems that global state info would cause for Dovecot v2.0, but it is also important for v1.2 as it significantly cleans up the library implementation. + Made LDA Sieve plugin recognize the deliver_log_format setting. + Message headers produced from user-supplied data are now RFC2047-encoded if necessary for outgoing messages. This is for example important for the :subject argument of the vacation action. + Added support for the $text$ substitution in the deprecated notify extension. + The subaddress extension now also accepts recipient_delimiter setting as an alias for sieve_subaddress_sep setting. This anticipates the recipient_delimiter setting in v2.0. - Fixed logging of mailbox names. It logged the converted mUTF7 version in stead of the original UTF8 version supplied by the user. - Fixed a minor memory leak in the multiscript support. - Fixed a bug in the recompilation of Sieve scripts. Made sure that scripts are only recompiled when the script file - or the symlink pointing to it - is strictly newer. Changelog ManageSieve v0.11.10: * This release contains adjustments to match changes in the Sieve API. This means that this release will only compile against Pigeonhole Sieve v0.1.14. - Fixed compilation of ManageSieve against CMUSieve. The releases are available as follows: Sieve: http://www.rename-it.nl/dovecot/1.2/dovecot-1.2-sieve-0.1.14.tar.gz http://www.rename-it.nl/dovecot/1.2/dovecot-1.2-sieve-0.1.14.tar.gz.sig ManageSieve (package + patch): http://www.rename-it.nl/dovecot/1.2/dovecot-1.2-managesieve-0.11.10.tar.gz http://www.rename-it.nl/dovecot/1.2/dovecot-1.2-managesieve-0.11.10.tar.gz.… http://www.rename-it.nl/dovecot/1.2/dovecot-1.2.9-managesieve-0.11.10.diff.… http://www.rename-it.nl/dovecot/1.2/dovecot-1.2.9-managesieve-0.11.10.diff.… Refer to http://pigeonhole.dovecot.org for more information. Have fun testing the new releases and don't hesitate to notify me when there are problems. Releases for Dovecot v2.0 are still under development... Regards, -- Stephan Bosch stephan(a)rename-it.nl

2 4

[Dovecot] Dovecot vs Exim file locking
by Daniel Campos 21 Dec '09

21 Dec '09

Hi all: We're planning to deploy a large e-mail system storing maildirs in a NAS system through NFS. One of the options we're thinking on is using Dovecot+EXIM. As far as I've read in both project's documentation, both services implement locking allowing multiple servers to access the same maildirs in order to distribute the service load. However, I can't find any information explaining whether both locking mechanisms are compatible, whether any additional configuration is needed both in Dovecot and/or EXIM, or even whether any locking synchronization between both services is needed/recommendable at all. The only remote clue I've found is that, according to Dovecot docs: "Because Dovecot uses its own non-standard locking (dovecot-uidlist.lock dotlock file), other MUAs accessing the maildir don't support it." (but EXIM is not a MUA, anyway) Anyhow theoretically MailDir could even be considered free of locking problems, but I'm not sure of the real implications of putting together several Exim and Dovecot installations pointing to the same NFS filesystem. Any knowledge/experience/link/clue on this would be greatly appreciated. Thanks in advance, Daniel Campos

4 4

[Dovecot] deliver panics when handling mails bigger than some kByte
by Leon Meßner 19 Dec '09

19 Dec '09

Hi, i've just upgraded to dovecot-1.2.8 (from 1.2.4) and do now get the following errors when deliver gets hands on mails with some attachments. # tail -n 1 /var/log/messages Dec 14 19:00:36 mail3 dovecot: deliver(user): Panic: file istream.c: line 96 (i_stream_read): assertion failed: (stream->eof) The MTA is postfix running inside a FreeBSD 7.2-STABLE jail. The homes where deliver should put mails are mounted via NFS. As it works with small attachments perhaps this is related to the message size. However i don't get the "stale NFS file handle" error any more which i did under 1.2.4 (See thread that begins with: Message-ID: <20091016122519.GC6309(a)emmi.physik-pool.tu-berlin.de> ) Greetings, Leon

2 2

[Dovecot] "Filename keeps changing" issue
by Paul Ezvan 19 Dec '09

19 Dec '09

Hello, I have been experiencing a issue for a while with dovecot 1.2.8 : Dec 4 12:54:00 gen1 dovecot: IMAP(paul): maildir_file_do(/home/paul/Maildir/.Travail.Linux.Arch Linux/cur/1224250603.M73770P8724.gen0:2,): Filename keeps changing Dec 4 12:54:01 gen1 dovecot: IMAP(paul): Disconnected: Internal error occurred. Refer to server log for more information. [2009-12-04 12:53:59] bytes=4445/26986 So I can't get the messages in this directory neither with Evolution neither with Horde neither with Squirrelmail, but it works with roundcubemail. How can I debug this ? dovecot -n # 1.2.8: /etc/dovecot/dovecot.conf # OS: Linux 2.6.31-ARCH i686 protocols: imap imaps pop3 pop3s managesieve ssl_cert_file: /etc/ssl/certs/ezvan.fr.pem ssl_key_file: /etc/ssl/private/ezvan.fr.key 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 login_executable(managesieve): /usr/lib/dovecot/managesieve-login login_process_per_connection: no mail_location: maildir:~/Maildir mail_executable(default): /usr/lib/dovecot/imap mail_executable(imap): /usr/lib/dovecot/imap mail_executable(pop3): /usr/lib/dovecot/pop3 mail_executable(managesieve): /usr/lib/dovecot/managesieve mail_process_size: 0 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/pop3 mail_plugin_dir(managesieve): /usr/lib/dovecot/modules/managesieve imap_client_workarounds(default): outlook-idle imap_client_workarounds(imap): outlook-idle imap_client_workarounds(pop3): imap_client_workarounds(managesieve): lda: postmaster_address: postmaster(a)ezvan.fr mail_plugins: sieve sieve_global_path: /var/sieve/global auth default: passdb: driver: pam userdb: driver: passwd socket: type: listen client: path: /var/run/dovecot/auth-client mode: 432 master: path: /var/run/dovecot/auth-master mode: 384 plugin: sieve: ~/.dovecot.sieve sieve_storage: ~/sieve Thanks for help ! Paul Ezvan

6 11

[Dovecot] dovecot: pipe() failed: Too many open files
by JW 19 Dec '09

19 Dec '09

In the past few months we've been having increasing problems with dovecot timing out pop3 logins. As best I can tell it gets to the point where it won't accept any new pop3 logins. The error in the mail log is: dovecot: pipe() failed: Too many open files I've researched this problem a number of times, usually I see suggestions to increase ulimit. I've done this a number of times, all the way up to: ulimit -n 8192 I've put that in the init script right above the daemon start line. So far it hasn't helped. In addition, when looking at lsof, it doesn't seem like we're anywhere near the actual limit. for example, last time dovecot only had 1032 files open. Does anyone have any idea what could be causing the error? Or what else I can try to figure this out? Thank you, JW -- ---------------------- System Administrator - Cedar Creek Software http://www.cedarcreeksoftware.com

5 7

[Dovecot] Release candidates for Sieve v0.1.14 and ManageSieve v0.11.10 for Dovecot v1.2.8
by Stephan Bosch 19 Dec '09

19 Dec '09

Hello Dovecot users, I am getting closer to new releases for Sieve and ManageSieve for Dovecot v1.2.8. However, the release for Sieve includes a large restructuring of the sources to improve extension handling and to remove global state. That is why I first provide a few pre-releases for you to check first: Sieve http://www.rename-it.nl/dovecot/1.2/dovecot-1.2-sieve-0.1.14pre.tar.gz http://www.rename-it.nl/dovecot/1.2/dovecot-1.2-sieve-0.1.14pre.tar.gz.sig ManageSieve http://www.rename-it.nl/dovecot/1.2/dovecot-1.2-managesieve-0.11.10pre.tar.… http://www.rename-it.nl/dovecot/1.2/dovecot-1.2-managesieve-0.11.10pre.tar.… Check the NEWS files in the respective repositories for other changes included in these releases: http://hg.rename-it.nl/dovecot-1.2-sieve/file/216f58aae5c1/NEWS http://hg.rename-it.nl/dovecot-1.2-managesieve/file/a44ca0d89875/NEWS Feel free to test these release candidates and please notify me when you incur any problems. The real releases will follow this weekend. Regards, -- Stephan Bosch stephan(a)rename-it.nl

3 5

[Dovecot] Maildir on NFS - attribute caching question
by Brandon Davidson 18 Dec '09

18 Dec '09

Hi Timo, We've been running Dovecot with Maildir on NFS for quite a while - since back in the 1.0 days I believe. I'm somewhat new here. Anyway... The Wiki article on NFS states that 1.1 and newer will flush attribute caches if necessary with mail_nfs_storage=yes. We're running 1.2.8 with that set, as well as mail_nfs_index=yes, mmap_disable=yes and fsync_disable=no. We have a pool of POP/IMAP and SMTP machines that are accessing the maildirs, and can't guarantee any sort of user session affinity to a particular host. We also mount our NFS shares with 'noac', which is what I'm writing to ask about. I'd like to stop doing that for performance reasons. Do you see any issues with taking that out of the mount options, given our environment? Thanks, -Brad

2 1

[Dovecot] lot's of timeouts
by Götz Reinicke - IT-Koordinator 18 Dec '09

18 Dec '09

Hi, since some time ago we do have a lot of "timeouts" connecting to our imap/po3 server. This week I switched the whole system to a new dual quadcore xeon, 24GB RAM, SAS2 RAID-10. (SUN Fire 4170) But the mailclients (mostly thunderbird and apple mail) still reporte the timeouts by accessing the mailboxes. The server is doing smtp, imap/pop3, webmailsystem and spam/antivirus-checking all together. (RH EL 5, sendmail, horde, mysql, mailscanner, spamassassin) We use the original RH dovecot-1.0.7, mbox-format and mailboxes up to 4 GB ... (historicaly grown ...) So where to start debugging the imap/pop3 timeouts? What information may I provide, which doc may I read? Thanks for helping me to find and fix the problem. Best regards Götz -- Götz Reinicke IT-Koordinator Tel. +49 7141 969 420 Fax +49 7141 969 55 420 E-Mail goetz.reinicke(a)filmakademie.de Filmakademie Baden-Württemberg GmbH Akademiehof 10 71638 Ludwigsburg www.filmakademie.de Eintragung Amtsgericht Stuttgart HRB 205016 Vorsitzende des Aufsichtsrats: Prof. Dr. Claudia Hübner Staatsrätin für Demographischen Wandel und für Senioren im Staatsministerium Geschäftsführer: Prof. Thomas Schadt

2 4

[Dovecot] v2.0.beta1 released
by Timo Sirainen 18 Dec '09

18 Dec '09

http://dovecot.org/releases/2.0/beta/dovecot-2.0.beta1.tar.gz http://dovecot.org/releases/2.0/beta/dovecot-2.0.beta1.tar.gz.sig Now that v2.0 is in beta stage I don't expect anything big to change anymore. The configuration and the APIs shouldn't change in non-backwards compatible ways. There are still bugs left to be fixed and some small features to be implemented, but I'd like to have people start testing it more. The biggest unimplemented "feature" is how to convert v1.x configuration easily/automatically to v2.0. Either the old config file should be translated to new one, or Dovecot should be able to read the old config file as-is. I think I like the translation better, so that people won't still be using v1.x configuration when v2.1 arrives and drops v1.x support. Largest changes since alpha3: - if some IP address is failing authentications, all auth attempts from the IP are delayed increasingly. a successful auth drops the delay. max delay is 15 seconds. this is enforced by auth process, so it works across different connections/processes/protocols. - lib-storage plugin API changed. processes handling multiple users now support different plugins for different users. - expire plugin's settings work a bit differently now: http://hg.dovecot.org/dovecot-2.0/rev/46691becc45e - post-login scripting works again, see http://dovecot.org/list/dovecot/2009-December/045139.html - Tons of fixes

7 20

[Dovecot] Upgrade 1.0->1.2 dbox mysql
by Bradley Giesbrecht 17 Dec '09

17 Dec '09

Seems to work but it's weird that I lost my subscribed folders. Also the perl script imapsync is only seeing an inbox and no other folders. I seem to be creating a lot of name mailboxes where my INBOX and other folders are located. /opt/local/var/mail/domain.com/username/dbox/mailboxes This dir is getting populated with new INBOX and default folders. (domain.com and username are substitutes for the real users domain and username) dovecot.log: Dec 17 12:29:17 IMAP(username(a)domain.com): Info: Effective uid=5000, gid=5000, home=/opt/local/var/mail/domain.com/username Dec 17 12:29:17 IMAP(username(a)domain.com): Info: dbox: data=/opt/local/ var/mail/domain.com/username/dbox Dec 17 12:29:17 IMAP(username(a)domain.com): Info: fs: root=/opt/local/ var/mail/username.com/username/dbox, index=, control=, inbox= dovecot-deliver.log: Dec 17 12:35:08 deliver(username(a)domain.com): Info: auth input: home=/ opt/local/var/mail/domain.com/username Dec 17 12:35:08 deliver(username(a)domain.com): Info: auth input: uid=5000 Dec 17 12:35:08 deliver(username(a)domain.com): Info: auth input: gid=5000 Dec 17 12:35:08 deliver(username(a)domain.com): Info: dbox: data=/opt/ local/var/mail/domain.com/username/dbox Dec 17 12:35:08 deliver(username(a)domain.com): Info: fs: root=/opt/ local/var/mail/domain.com/username/dbox, index=, control=, inbox= Dec 17 12:35:08 deliver(username(a)domain.com): Info: msgid=<E5136D91-256C-4FD8-87AE-065C95DEAA58(a)gmail.com >: saved mail to INBOX Could someone confirm that this looks right? Thank you, Bradley Giesbrecht

2 2

[Dovecot] Upgrade 1.0->1.2 dbox mysql
by Bradley Giesbrecht 17 Dec '09

17 Dec '09

Hi, I just upgraded to from dovecot v1.1.15 to v1.2.9 so I can use dovecot- sieve. Most everything seems to work but my webmail (roundcube) clients are not seeing their subscribed folders. Reading over the upgrade docs at http://wiki.dovecot.org/Upgrading/1.2 I'm wondering if I have the two settings below configured correctly. dovecot.conf: mail_location = dbox:/opt/local/var/mail/%d/%n/dbox dovecot_mysql.conf user_query homedir result: /opt/local/var/mail/example.com/foo bash-3.2# dovecot -n # 1.2.9: /opt/local/etc/dovecot/dovecot.conf # OS: Darwin 9.8.0 Power Macintosh hfs log_path: /opt/local/var/serveza/log/mail/dovecot.log protocols: imap imaps pop3 pop3s disable_plaintext_auth: no verbose_ssl: yes login_dir: /opt/local/var/run/dovecot/login login_executable(default): /opt/local/libexec/dovecot/imap-login login_executable(imap): /opt/local/libexec/dovecot/imap-login login_executable(pop3): /opt/local/libexec/dovecot/pop3-login login_greeting: now what? mail_location: dbox:/opt/local/var/serveza/mail/%d/%n/dbox mail_debug: yes mail_executable(default): /opt/local/etc/dovecot/bin/log_imap_login.sh mail_executable(imap): /opt/local/etc/dovecot/bin/log_imap_login.sh mail_executable(pop3): /opt/local/etc/dovecot/bin/log_pop3_login.sh mail_plugin_dir(default): /opt/local/lib/dovecot/imap mail_plugin_dir(imap): /opt/local/lib/dovecot/imap mail_plugin_dir(pop3): /opt/local/lib/dovecot/pop3 lda: log_path: /opt/local/var/serveza/log/mail/dovecot-deliver.log auth_socket_path: /opt/local/var/run/dovecot/auth-master postmaster_address: postmaster(a)pixilla.com auth default: mechanisms: plain login cram-md5 ntlm apop verbose: yes debug: yes debug_passwords: yes passdb: driver: sql args: /opt/local/etc/dovecot/dovecot_mysql.conf userdb: driver: prefetch userdb: driver: sql args: /opt/local/etc/dovecot/dovecot_mysql.conf socket: type: listen client: path: /opt/local/var/spool/postfix/private/auth mode: 432 user: _postfix group: _postfix master: path: /opt/local/var/run/dovecot/auth-master mode: 384 user: _vmail Thanks for any clues, Bradley Giesbrecht

1 0

Re: [Dovecot] Sieve Plugin Help
by Oli Schacher 17 Dec '09

17 Dec '09

Asai wrote: > Thanks, Oli. So, what about the ATrpms Dovecot-Sieve plugin? > http://atrpms.net/dist/el5/dovecot-sieve/ > > Is this different? AFAIK this is the CMU Sieve (Cyrus) plugin for dovecot 1.1. I don't think there are atrpm packages for the dovecot sieve version.

4 8

[Dovecot] Upgrade 1.0->1.2 dbox mysql
by Bradley Giesbrecht 17 Dec '09

17 Dec '09

Hi, I just upgraded to from dovecot v1.1.15 to v1.2.9 so I can use dovecot- sieve. Most everything seems to work but my webmail (roundcube) clients are not seeing their subscribed folders. Reading over the upgrade docs at http://wiki.dovecot.org/Upgrading/1.2 I'm wondering if I have the two settings below configured correctly. dovecot.conf: mail_location = dbox:/opt/local/var/mail/%d/%n/dbox dovecot_mysql.conf user_query homedir result: /opt/local/var/mail/example.com/foo bash-3.2# dovecot -n # 1.2.9: /opt/local/etc/dovecot/dovecot.conf # OS: Darwin 9.8.0 Power Macintosh hfs log_path: /opt/local/var/serveza/log/mail/dovecot.log protocols: imap imaps pop3 pop3s disable_plaintext_auth: no verbose_ssl: yes login_dir: /opt/local/var/run/dovecot/login login_executable(default): /opt/local/libexec/dovecot/imap-login login_executable(imap): /opt/local/libexec/dovecot/imap-login login_executable(pop3): /opt/local/libexec/dovecot/pop3-login login_greeting: now what? mail_location: dbox:/opt/local/var/serveza/mail/%d/%n/dbox mail_debug: yes mail_executable(default): /opt/local/etc/dovecot/bin/log_imap_login.sh mail_executable(imap): /opt/local/etc/dovecot/bin/log_imap_login.sh mail_executable(pop3): /opt/local/etc/dovecot/bin/log_pop3_login.sh mail_plugin_dir(default): /opt/local/lib/dovecot/imap mail_plugin_dir(imap): /opt/local/lib/dovecot/imap mail_plugin_dir(pop3): /opt/local/lib/dovecot/pop3 lda: log_path: /opt/local/var/serveza/log/mail/dovecot-deliver.log auth_socket_path: /opt/local/var/run/dovecot/auth-master postmaster_address: postmaster(a)pixilla.com auth default: mechanisms: plain login cram-md5 ntlm apop verbose: yes debug: yes debug_passwords: yes passdb: driver: sql args: /opt/local/etc/dovecot/dovecot_mysql.conf userdb: driver: prefetch userdb: driver: sql args: /opt/local/etc/dovecot/dovecot_mysql.conf socket: type: listen client: path: /opt/local/var/spool/postfix/private/auth mode: 432 user: _postfix group: _postfix master: path: /opt/local/var/run/dovecot/auth-master mode: 384 user: _vmail Thanks for any clues, Bradley Giesbrecht

1 0

[Dovecot] Upgrade 1.0->1.2
by Ivica Glavocic 17 Dec '09

17 Dec '09

Hi all We are planning to upgrade Dovecot from production version 1.0.10 to latest version 1.2.9 Users are using maildir style mailboxes with ~20 GB of messages on SLES10 server. Upgrade will be done by installing new server and then migrating mailboxes from old on new server. Since dovecot-uidlist file have new format and index files have changed in v1.1, what must be done to have new Dovecot v1.2 working properly with old v1.0 maildirs? Thanks, regards Ivica Glavocic

2 1

[Dovecot] force PLAIN auth mech?
by Frank Cusack 17 Dec '09

17 Dec '09

I have auth_default { mechanisms = plain } yet clients are able to login using cram-md5. how can i force use of plain?

2 2

[Dovecot] How to let people change their password ?
by Edi Stojicevic 17 Dec '09

17 Dec '09

Hi, I would like to know what do you use to let people change their email password ? I have a dedicated server with postfix and dovecot on it for a couple of web sites and I need to be able to let them change their mail password ... but I havent found any documentation on that :( If you have any feedbacks, tutorials, website, ... let me know ;) ++ -- .''`. Edi Stojicevic : :' : Debian GNU/Linux user, admin & developer - http://www.debian.org `. `~' French speaking Debian website founder - http://www.debianworld.org `- GPG Key Id : 0x1237B032

4 3

Re: [Dovecot] CRAM-MD5 in Python
by Andrea Mistrali 17 Dec '09

17 Dec '09

On 16/dic/2009, at 20.01, Nick Douma wrote: > On 16-12-2009 17:11, Andre wrote: >> Hi to all! >> I’m writing a python module (python+sqlalchemy) to manage user and domain configuration on my system (I hope to get a CLI tool, a Web app and even a native Mac app, via PyObjc, from my lib). >> I’m implementing password crypto, but I have some problem in generating CRAM-MD5 password, dovecot style. >> I’ve found an old discussion on this mailing list and a piece of Perl that works, but I need to implement it in Python; I’ve even read code (hmac-md5.c), but before start hard coding (hard from my POV at least, since I’ve never worked with crypto algorithms in a deep way), is there anyone that have had solved the problem or has any idea on how to approach it? >> >> TIA >> Andre > > If the module is always going to run on a machine with dovecot > installed, you could call from your script: > > $ dovecotpw -s CRAM-MD5 -p <password> > I know, I thought to do in this way, but it introduces an unnecessary and strong dependency. Imagine of a web server running the administration interface, that is not even the IMAP server (I know I can install only common dovecot components) or imagine to write a OSX/Windows Administration tool (I would like to write a Xcode/PyOBjc tool). Anyway, I’ll give a try to module hmac. Andre

1 0

[Dovecot] Why dovecot does not want to read my acl file?
by Lukas Haase 17 Dec '09

17 Dec '09

Hi, Simple Scenario: Shared namespace and a specific UNIX group should have access to it. System is Debian lenny (stable). # cat /etc/dovecot/dovecot.conf [...] namespace public { separator = . prefix = Shared. location = maildir:/var/mail/shared } mail_executable = /usr/local/sbin/dovecot-imap-fix.sh mail_drop_priv_before_exec = no #just to make sure [...] # dpkg -l | grep dovecot ii dovecot-common 1:1.0.15-2.3+lenny1 secure mail server that ii dovecot-imapd 1:1.0.15-2.3+lenny1 secure IMAP server that # cat /usr/local/sbin/dovecot-imap-fix.sh #!/bin/sh cat /var/mail/shared/.Office/dovecot-acl > /tmp/dovecot-$USER env >> /tmp/dovecot-$USER ACL_GROUPS=`groups $USER | tr ' ' ','` export ACL_GROUPS exec /usr/lib/dovecot/imap $* # ls -la -R /var/mail/shared/ # (cut the .,.. in output) /var/mail/shared/: total 28 drwxrwx--- 5 root office 4096 Dec 15 15:53 .Office drwxr-xr-x 2 root root 4096 Dec 14 16:55 cur -rw-r--r-- 1 root root 23 Dec 15 07:46 dovecot-acl -rw-r--r-- 1 root root 0 Dec 15 07:42 dovecot-shared drwxr-xr-x 2 root root 4096 Dec 14 16:55 new drwxr-xr-x 2 root root 4096 Dec 14 16:55 tmp /var/mail/shared/.Office: total 24 drwxrwx--- 2 root office 4096 Dec 15 09:53 cur -rw-r--r-- 1 root root 52 Dec 15 15:53 dovecot-acl -rw-rw---- 1 root office 0 Dec 15 07:42 dovecot-shared drwxrwx--- 2 root office 4096 Dec 15 09:53 new drwxrwx--- 2 root office 4096 Dec 15 09:53 tmp # id peter uid=1000(peter) gid=100(users) groups=51683(office),25783(ssh_users),100(users) # Now I log in as peter but I my client (latest TB 2) does not display the office folder. In the log it claimes that it is not able to open the acl file what really can NOT be true: Dec 15 15:56:05 mail dovecot: IMAP(peter): acl vfile: no access to file /var/mail/shared/.Office/dovecot-acl I tried: * su peter: Access no problem! * ps aux: The process is running as peter * As you can see I have debugging code in my dovecot-imap-fix.sh which successfully prints out the content of the ACL file to /tmp/user-peter I can't image that, it seems as if it is not true. By the way: As soon as I change the mail_executable to /usr/local/sbin/dovecot-imap-fix.sh I get this message and have absolutely no clue why: # /etc/init.d/dovecot restart Restarting IMAP/POP3 mail server: dovecotid: dump-capability: No such user . # Which dump-capability? Which user? Does anybody have an idea what could be wrong here? Thank you very much, Luke

4 12

[Dovecot] lib-storage API docs
by Timo Sirainen 17 Dec '09

17 Dec '09

I wrote lots of more stuff about lib-storage to http://wiki.dovecot.org/Design Still few FIXMEs to fix. Comments welcome. :) Anything else that you're interested in reading about?

1 0

[Dovecot] Filing to public folders
by Cajus Pollmeier 17 Dec '09

17 Dec '09

Hi all, I'm currently playing with a setup which might replace my current cyrus imapd one with dovecot. Currently I'm stuck with trying to file messages that got to the user "lists" to the public namespace' System folder (public/System) with sieve. Dovecot claims "Permission denied", and I tried several debugging techniques to get the cause - without a result right now :-( Thanks, Cajus 8<-------- /var/log/mail.info Dec 16 21:40:51 ferdi dovecot: deliver(lists): sieve: using sieve path for user's script: /home/lists/.dovecot.sieve Dec 16 21:40:51 ferdi dovecot: deliver(lists): sieve: opening script /home/lists/.dovecot.sieve Dec 16 21:40:51 ferdi dovecot: deliver(lists): sieve: executing compiled script /home/lists/.dovecot.sieve Dec 16 21:40:51 ferdi dovecot: deliver(lists): acl vfile: reading file /var/dovecot/public/.System/dovecot-acl Dec 16 21:40:51 ferdi dovecot: deliver(lists): sieve: msgid=<3044.1260989392(a)ferdi.test.net>: failed to store into mailbox 'public/System': Permission denied Dec 16 21:40:51 ferdi dovecot: deliver(lists): Namespace : Using permissions from /var/dovecot/mails/lists: mode=0700 gid=-1 Dec 16 21:40:51 ferdi dovecot: deliver(lists): sieve: msgid=<3044.1260989392(a)ferdi.test.net>: stored mail into mailbox 'INBOX' Dec 16 21:40:51 ferdi dovecot: deliver(lists): sieve: execution of script /home/lists/.dovecot.sieve failed, but implicit keep was successful 8<-------- /home/lists/.dovecot.sieve require ["fileinto"]; if header :contains "From" [ "root(a)test.net", "logcheck(a)test.net", "root(a)ferdi.test.net", "logcheck(a)ferdi.test.net" ] { fileinto "public/System"; stop; } 8<------- /var/dovecot/public/.System/dovecot-acl user=lists lrwstiekxa authenticated lr 8<-------- dovecot information Dovecot version 1.2.8 (Backport on debian lenny 1:1.2.8-1~bpo50+1) system> dovecot -n # 1.2.8: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-trunk-amd64 x86_64 Debian 5.0.3 ext3 log_timestamp: %Y-%m-%d %H:%M:%S ssl_cert_file: /etc/cert/ferdi.cert.pem ssl_key_file: /etc/cert/ferdi.key.pem login_dir: /var/run/dovecot/login login_executable: /usr/lib/dovecot/imap-login mail_access_groups: publicmail mail_privileged_group: mail mail_location: maildir:/var/dovecot/mails/%u mail_debug: yes mbox_write_locks: fcntl dotlock mail_plugins: acl namespace: type: private separator: / inbox: yes list: yes subscriptions: yes namespace: type: public separator: / prefix: public/ location: maildir:/var/dovecot/public:INDEX=/var/dovecot/mails/%u/public list: children lda: postmaster_address: postmaster(a)test.net mail_plugins: acl sieve auth_socket_path: /var/run/dovecot/auth-master debug: yes auth default: passdb: driver: ldap args: /etc/dovecot/dovecot-ldap.conf userdb: driver: ldap args: /etc/dovecot/dovecot-ldap.conf socket: type: listen client: path: /var/run/dovecot/auth-client mode: 432 master: path: /var/run/dovecot/auth-master mode: 432 user: root group: mail plugin: acl: vfile sieve: ~/.dovecot.sieve sieve_dir: ~/sieve antispam_signature: X-DSPAM-Signature antispam_signature_missing: error antispam_spam: SPAM antispam_dspam_binary: /usr/bin/dspam antispam_dspam_args: --deliver=;--user;%u antispam_mail_tmpdir: /tmp antispam_mail_sendmail: /usr/sbin/sendmail antispam_crm_binary: /bin/false antispam_signature: X-CRM114-CacheID

2 1

[Dovecot] Dovecot 1.2.+
by Tom Mihalicek 16 Dec '09

16 Dec '09

The Dovecot version is 1.2.8 and i am using an LDAP for a user database. The problem is following... i would like to use a quota dictionary backend from file rather than sql proxy for some reasons. Is it possible to get the full path for dovecot-quota file location from LDAP like from mail variable (/mailboxes/storage_01/domain.org/u/us/use/user/dbox/dovecot-quota)? /etc/dovecot/dovecot-ldap.conf user_attrs = storageBase=home,mailMessageStore=mail=dbox:~/%$/dbox/,mailQuota=quota_rule=*:bytes=%$,mailQuotaMessageLimit=quota_rule2=*:messages=%$ Also is it also possible the same for sieve location? I can solve the problem by adding in dovecot.conf sieve = /var/sieve/%Ld/%Ln/dovecot.sieve but i would like to have it all in one place ... t -- View this message in context: http://old.nabble.com/Dovecot-1.2.%2B-tp26803721p26803721.html Sent from the Dovecot mailing list archive at Nabble.com.

2 4

[Dovecot] v1.2.9 released
by Timo Sirainen 16 Dec '09

16 Dec '09

http://dovecot.org/releases/1.2/dovecot-1.2.9.tar.gz http://dovecot.org/releases/1.2/dovecot-1.2.9.tar.gz.sig Hopefully this release will be enough bug-free that I don't need to make v1.2 releases for next few months. * maildir: When saving, filenames now always contain ,S=<size>. Previously this was done only when quota plugin was loaded. It's required for zlib plugin and may be useful for other things too. + lazy-expunge: Support a single-namespace configuration. If a mailbox is deleted, its messages are merged with its old expunged messages (if there were any). + expire: Settings now support spaces in mailbox names by using quoted strings. - maildir: v1.2.7 and v1.2.8 caused assert-crashes in maildir_uidlist_records_drop_expunges() - maildir_copy_preserve_filename=yes could have caused crashes. - Maildir++ quota: % limits weren't updated when limits were read from maildirsize. - virtual: v1.2.8 didn't fully fix the "lots of mailboxes" bug - virtual: Fixed updating virtual mailbox based on flag changes. - fts-squat: Fixed searching multi-byte characters.

2 1