Re: [Dovecot] 1.11 bug?: file client-common.c: line 25 (client_unlink): assertion failed: (clients_count 0)
Yes Timo, found Warning: Killed with signal 15 in the log. What can be something that killed dovecot? Mar 26 17:18:43 Info: pop3-login: Login: user=xxx, method=PLAIN, rip=x.x.x.x, lip=y.y.y.y Mar 26 17:18:43 Info: POP3(xxx): Disconnected: Logged out top=0/0, retr=0/0, del=0/207, size=35162343 Mar 26 17:18:43 Warning: Killed with signal 15 Mar 26 17:18:43 Info: pop3-login: Disconnected: Shutting down (no auth attempts): rip=x.x.x.x, lip=y.y.y.y Mar 26 17:18:43 Info: pop3-login: Disconnected: Shutting down (auth failed, 11997592 attempts): user=??�, method=??� Mar 26 17:18:43 Panic: pop3-login: file client-common.c: line 25 (client_unlink): assertion failed: (clients_count 0) Mar 26 17:18:46 Info: dovecot v1.1.11 starting up (core dumps disabled) Thanks, - Long Le On Mon, 2009-03-30 at 01:54 -0400, Timo Sirainen wrote: Well. There are two problems: First is that it's crashing, which is clearly a bug. It just shouldn't happen. If you upgraded to v1.1.13 you would probably get a core dump, and that might be useful in figuring out the crash (http://dovecot.org/bugreport.html), but the real problem appears to be in the Disconnected reason. Shutting down means that the whole Dovecot is being shut down. Which most likely means that something killed dovecot master process. Do you see such a line in logs? Probably Warning: killed with signal something. On Mar 29, 2009, at 11:41 PM, Long Le Dinh wrote: Any help on this? It happens more frequently :(. Is this related to LDAP authen? Thanks, - Long Le On Fri, 2009-03-27 at 13:14 +0700, Long Le Dinh wrote: Hi, I got below log in last 2 days, I have to restart dovecot as pop3- login failed and service cannot respond. Mar 26 14:19:31 Info: pop3-login: Disconnected: Shutting down (auth failed, 1 attempts): method=PLAIN, rip=x.x.x.x Mar 26 14:19:31 Info: pop3-login: Disconnected: Shutting down (tried to use disabled plaintext auth): method=??B7 Mar 26 14:19:31 Panic: pop3-login: file client-common.c: line 25 (client_unlink): assertion failed: (clients_count 0) Mar 26 14:19:31 Error: child 31902 (login) killed with signal 6 (ip=x.x.x.x) My system info: dovecot -n # 1.1.11: /etc/dovecot.conf # OS: Linux 2.6.18-8.el5 i686 CentOS release 5 (Final) ext3 log_path: /var/log/dovecot.log 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 mail_gid: 100 mail_location: maildir:/home/%u/Maildir 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 auth default: verbose: yes debug: yes passdb: driver: ldap args: /etc/dovecot-ldap.conf userdb: driver: passwd userdb: driver: ldap args: /etc/dovecot-ldap.conf We're using Maildir format, no NFS. Any help/clue is appreciated. Thanks, - Long Le
Re: [Dovecot] [Help] How get the complete CAPABILITY list?
Michael, I think you are referring to the list returned by CAPABILITY command to be seen as the list of CAPABILITIES AFTER usr1 login. To my surprise, the PLAIN are supported for a email user account even if it is not listed, but PLAIN is natually supported if you don't specify use secure authentication at your email client. However, there can be the following error for specific user created, like this when doing the connection from email client to Dovecot Email server It's like the following in the log of Email server log, imap(user1): stat(/home/user1/Maildir/cur) failed: Permission denied However, when creating user1 and related Maildir, it is given 766 access right already like the following, sudo cp -r /etc/skel/Maildir /home/myuser/ sudo chown -R myuser:usergroup /home/myuser/Maildir sudo chmod -R 700 /home/myuser/Maildir so what's the problem? Why do I still get a Permission denied? -Original Message- From: ext Michael M. Slusarz [mailto:slus...@curecanti.org] Sent: 30 March 2009 13:39 To: Yang Tao.6 (Nokia-D/Beijing); dovecot@dovecot.org Subject: Re: [Dovecot] [Help] How get the complete CAPABILITY list? Whatever is returned by the CAPABILITY command. I guess I am not understanding your question. When in an unauthenticated state, the server doesn't need to broadcast the capabilities of commands/features that the client *can't* use yet. i.e. knowing the server supports UIDPLUS at the authentication stage is pointless. Same thing after authenticating - the client could care less what authentication options are available after logged in. RFC 3501 states that the list of capabilities can change after the STARTTLS or AUTHENTICATE/LOGIN commands are successful. Thus, the only way to ensure that you have the correct list of capabilities is to re-issue the command after each of these events, although recent IMAP servers (i.e. Dovecot 1.2) will automatically list capabilities in the response codes after these events so that the client doesn't need to send an explicit CAPABILITY command. I believe this behavior is suggested in the Lemonade profile. michael
[Dovecot] outlook problem if TLS mailsettings are off
Dear List, I dont know if its a dovecot config problem or whatever else issue. Behaviour: If I set /etc/dovecot/dovecot.conf: Following is valid with IMAP mailboxes only: disable_plaintext_auth = yes # outlook 2007 with TLS in/out enabled can show index of mails and klick on mail does preview / doubleklick opens mail PERFECT AS INTENDED disable_plaintext_auth = no# outlook 2007 with TLS/SSL OFF can show index of mails, but (double)-/klick on mail gives me sandwatch-mouspointer and I've to restart outlook again (and enable TLS again to get it work again) with POP3 mailbox both variants are working smoothly. Other ssl/tls settings: ssl_disable = no login_process_per_connection = yes using or not using following makes no difference... imap_client_workarounds(default): outlook-idle delay-newmail imap_client_workarounds(imap): outlook-idle delay-newmail pop3_client_workarounds(pop3): outlook-no-nuls oe-ns-eoh I'm sad - but I can't force SSL/TLS for my users - so I can't solve this by using disable_plaintext_auth = yes Is there any way out of the dark? my data: gentoo linux dovecot 1.1.7 postfix 2.5.5 postfixadmin-2.2.1.1 mysql 5.0.70-r1 php 5.2.8-pl12 dovecot -n # 1.1.7: /etc/dovecot/dovecot.conf # OS: Linux 2.6.26-gentoo-r3 i686 Gentoo Base System release 1.12.11.1 ext3 protocols: pop3 pop3s imap imaps ssl_cert_file: /etc/ssl/dovecot/server.pem ssl_key_file: /etc/ssl/dovecot/server.key 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 mail_max_userip_connections(default): 10 mail_max_userip_connections(imap): 10 mail_max_userip_connections(pop3): 30 first_valid_uid: 8 last_valid_uid: 8 first_valid_gid: 12 last_valid_gid: 12 mail_privileged_group: mail mail_uid: mail mail_gid: mail mail_location: maildir:/var/mail/%d/%n/Maildir/:INDEX=/var/mail/%d/%n/indexes mail_executable(default): /usr/libexec/dovecot/imap mail_executable(imap): /usr/libexec/dovecot/imap mail_executable(pop3): /usr/libexec/dovecot/pop3 mail_plugins(default): quota imap_quota mail_plugins(imap): quota imap_quota mail_plugins(pop3): quota mail_plugin_dir(default): /usr/lib/dovecot/imap mail_plugin_dir(imap): /usr/lib/dovecot/imap mail_plugin_dir(pop3): /usr/lib/dovecot/pop3 imap_client_workarounds(default): outlook-idle delay-newmail imap_client_workarounds(imap): outlook-idle delay-newmail imap_client_workarounds(pop3): pop3_client_workarounds(default): pop3_client_workarounds(imap): pop3_client_workarounds(pop3): outlook-no-nuls oe-ns-eoh auth default: mechanisms: plain login passdb: driver: sql args: /etc/dovecot/dovecot-sql.conf userdb: driver: prefetch 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: 384 user: mail group: mail regards, Georg Kaefer
Re: [Dovecot] [Help] How get the complete CAPABILITY list?
Sorry, that was a very stupid question. Fixed the chown and chmod, and it passed the connection for user1. Thanks guys. -Original Message- From: dovecot-bounces+tao.6.yang=nokia@dovecot.org [mailto:dovecot-bounces+tao.6.yang=nokia@dovecot.org] On Behalf Of Yang Tao.6 (Nokia-D/Beijing) Sent: 30 March 2009 16:38 To: slus...@curecanti.org; dovecot@dovecot.org Subject: Re: [Dovecot] [Help] How get the complete CAPABILITY list? Importance: High Michael, I think you are referring to the list returned by CAPABILITY command to be seen as the list of CAPABILITIES AFTER usr1 login. To my surprise, the PLAIN are supported for a email user account even if it is not listed, but PLAIN is natually supported if you don't specify use secure authentication at your email client. However, there can be the following error for specific user created, like this when doing the connection from email client to Dovecot Email server It's like the following in the log of Email server log, imap(user1): stat(/home/user1/Maildir/cur) failed: Permission denied However, when creating user1 and related Maildir, it is given 766 access right already like the following, sudo cp -r /etc/skel/Maildir /home/myuser/ sudo chown -R myuser:usergroup /home/myuser/Maildir sudo chmod -R 700 /home/myuser/Maildir so what's the problem? Why do I still get a Permission denied? -Original Message- From: ext Michael M. Slusarz [mailto:slus...@curecanti.org] Sent: 30 March 2009 13:39 To: Yang Tao.6 (Nokia-D/Beijing); dovecot@dovecot.org Subject: Re: [Dovecot] [Help] How get the complete CAPABILITY list? Whatever is returned by the CAPABILITY command. I guess I am not understanding your question. When in an unauthenticated state, the server doesn't need to broadcast the capabilities of commands/features that the client *can't* use yet. i.e. knowing the server supports UIDPLUS at the authentication stage is pointless. Same thing after authenticating - the client could care less what authentication options are available after logged in. RFC 3501 states that the list of capabilities can change after the STARTTLS or AUTHENTICATE/LOGIN commands are successful. Thus, the only way to ensure that you have the correct list of capabilities is to re-issue the command after each of these events, although recent IMAP servers (i.e. Dovecot 1.2) will automatically list capabilities in the response codes after these events so that the client doesn't need to send an explicit CAPABILITY command. I believe this behavior is suggested in the Lemonade profile. michael
[Dovecot] Sieve Rule for Folders
Hello! Is it possible with sieve to do the following: When a new message is added to a folder (e.g. dovecot folder and not INBOX) then an action like forwarding it per E-Mail should be triggered. Is this possible? If yes, how does the sieve script look like? If possible, can a shell script also be triggered as action? Thanx. Ciao, Gerhard -- http://www.wiesinger.com/
Re: [Dovecot] Upgrade from 1.0 to 1.1, plus migration from Maildir to dbox
On 3/29/2009, Daniel L. Miller (dmil...@amfes.com) wrote: So - time to make the leap. I want to upgrade a live version 1.0 server to version 1.1 (from Ubuntu repositories, using version 1.0.10 to 1.1.4). Why? Current version is 1.1.13, and 1.2 is close to RC... Personally, unless you have an uncommon setup, I'd go straight to 1.2b4... -- Best regards, Charles
Re: [Dovecot] [Help] How get the complete CAPABILITY list?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Mon, 30 Mar 2009, tao.6.y...@nokia.com wrote: However, there can be the following error for specific user created, like this when doing the connection from email client to Dovecot Email server It's like the following in the log of Email server log, imap(user1): stat(/home/user1/Maildir/cur) failed: Permission denied However, when creating user1 and related Maildir, it is given 766 access right already like the following, sudo cp -r /etc/skel/Maildir /home/myuser/ sudo chown -R myuser:usergroup /home/myuser/Maildir sudo chmod -R 700 /home/myuser/Maildir so what's the problem? Why do I still get a Permission denied? /home or /home/myuser (/home/user1) is missing the correct permissions. Bye, - -- Steffen Kaiser -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iQEVAwUBSdCNjXWSIuGy1ktrAQLz7ggAw48OsEEpZOylBKbj53pHSWIpryPhsyuA WQQfX4xPjYzDEXjf40m93zDzrJRGP3Ih0YbYi8Ko0IsuZ9S4W1kBkL56kjSbWhlS vUN3IfakVMGJx5b1tanp2oIFZLwzRFcn/WfnrrjaYU5gPxI3ycq7DhXgAbxuZe4k T4BBl7Dko9MmkmrGO524egUKPPGCsEp6Gpnm7OF8H3zmIuMM0SEMtrd+E2qOeHkY bzA0+3sXreL6EyXFZRqwsMqFMb8Xl7yxvFHYysPTb3J3MWeAxFrF7D6XsBNn7bU9 UB36RgTwDjsDXYbUYvkZcsLxhNJ9hSTNFmYzdr/h9KQyhx0zfRMflA== =2Ygx -END PGP SIGNATURE-
[Dovecot] Empty To: Header and message_address_parse
Using dovecot 1.2beta (but earlier versions should behave similarly) we have a problem in conjunction with empty To: headers and the RT request tracker. RT sends mail out using Bcc: and no To: header at all. To make some mailers happy one can configure to send a dummy To: header, which we do. Our To header looks like: To: AdminCc of rt Ticket #123456:; The message_address_parse function called with the TRUE flag (triggers add_fixed_address) in dovecot changes that to To: AdminCc of rt Ticket #123456: missing_mail...@missing_domain ; and then at least alpine does use that invalid address as Cc: address when replying. If the mail is stored in a local folder, i.e. does not get fetched via IMAP then the To: line is displayed as is and a reply does not result in an errorneous Cc: This behaviour is at least inconsistent from a user point of view. Is there some advice other than change the RT mail header generation? (other mailers seem to copy the To: line unaltered which results in an invalid address as well, therefore I admit that the real problem is with RT) -- Wolfgang Friebel Deutsches Elektronen-Synchrotron DESY Phone/Fax: +49 33762 77372/216Platanenallee 6 Mail: Wolfgang.Friebel AT desy.de D-15738 Zeuthen Germany
[Dovecot] Double mysql auth problem
Hello ,
I am forced to use 2 DBs to auth users. First one is for our CRM system
(new user=mail from him/her) , second is for other (cannot user CRM DB :( )
Postfix have no problem to deliver mails to both DBs but I've some
problems with reciveing mails from second (not CRM) DB.
The dovecot.conf :
protocols = imap pop3 imaps
disable_plaintext_auth = no
mail_location = maildir:/home/vmail/%d/%n
log_path = /var/log/dovecot
ssl_disable = no
ssl_cert_file = /etc/ssl/certs/dovecot.pem
ssl_key_file = /etc/ssl/private/dovecot.pem
auth_verbose = yes
auth_debug = yes
auth_debug_passwords = yes
auth default {
passdb sql {
args = /etc/dovecot/dovecot-mysql.conf
}
userdb static {
args = uid=5000 gid=5000 home=/home/vmail/%d/%n allow_all_users=yes
}
}
auth secondary {
passdb sql {
args = /etc/dovecot/dovecot-mysql2.conf
}
userdb static {
args = uid=5000 gid=5000 home=/home/vmail/%d/%n allow_all_users=yes
}
}
dovecot-mysql.conf :
driver = mysql
connect = host=127.0.0.1 dbname= user= password=
default_pass_scheme = CRYPT
password_query = SELECT email as user, haslo as password FROM users WHERE
email='%u';
dovecot-mysql2.conf :
driver = mysql
connect = host=127.0.0.1 dbname= user= password=
default_pass_scheme = CRYPT
password_query = SELECT email as user, password FROM poczta WHERE
email='%u';
I could log on mail located in dovecot-mysql.conf (CRM) but when I try
to log on second DB I got errors :
dovecot: Mar 30 14:41:01 Info: auth(default): client in:
AUTH1 PLAIN service=imapsecured lip=127.0.0.1
rip=127.0.0.1 lport=993 rport=32930
resp=AGdyb21AZXVyaW1hZ2UucGwANzEyMA==
dovecot: Mar 30 14:41:01 Info: auth-worker(default):
sql(g...@eurimage.pl,127.0.0.1): query: SELECT email as user, haslo as
password FROM users WHERE email='g...@eurimage.pl';
dovecot: Mar 30 14:41:01 Info: auth-worker(default):
sql(g...@eurimage.pl,127.0.0.1): unknown user
dovecot: Mar 30 14:41:01 Info: auth(default): new auth connection:
pid=19560
dovecot: Mar 30 14:41:01 Info: auth(secondary): new auth connection:
pid=19560
dovecot: Mar 30 14:41:03 Info: auth(default): client out:
FAIL1 user=g...@eurimage.pl
dovecot: Mar 30 14:41:03 Info: imap-login: Disconnected (auth failed, 1
attempts): user=g...@eurimage.pl, method=PLAIN, rip=127.0.0.1,
lip=127.0.0.1, TLS
I see query for auth default but got no isea why there's no query for
auth secondary ?
Waiting for some help :)
Re: [Dovecot] Sieve Rule for Folders
Gerhard Wiesinger wrote: Hello! Is it possible with sieve to do the following: When a new message is added to a folder (e.g. dovecot folder and not INBOX) then an action like forwarding it per E-Mail should be triggered. Is this possible? If yes, how does the sieve script look like? If you want to do this using Sieve through IMAP (i.e. when appending new messages): currently no. There is work in progress to produce an IMAP extension that allows setting such scripts for specific folders and operations on those folders. This is nowhere near finished however and implementing this is not trivial. If possible, can a shell script also be triggered as action? Not with Sieve. Perhaps there is a plugin for IMAP that allows triggering shell scripts when accessing certain folders, but I really wouldn't know. PS: if you are trying to build a spam learning folder: there is a plugin for that called antispam. Regards, Stephan.
Re: [Dovecot] Panic: Trying to allocate 2147483648 bytes
Timo Sirainen wrote: On Mar 26, 2009, at 1:00 PM, David Halik wrote: Any thoughts on this Timo? Just wondering if you were able to reproduce the problem and saw the same behavior. We can look into it more if need be, but since I can replicate it on both Fedora and Solaris, I'm guessing it's a fundamental bug with how certain malformed emails are searched. Interesting that the only two people who reported this were running on Solaris. Anyway, fixed: http://hg.dovecot.org/dovecot-1.1/rev/a2013dedbad0 In my case the error occured only sometimes. I made several tests with the patch applied and the errror seems to be gone. Thanks. Martin I suppose that could be thought of as a DoS attack, but since it requires user to search messages and have a very special kind of email, and by default imap process size is limited to 256 MB, I don't think I'll bother releasing v1.1.14 because of it. --- Martin Preen, Universität Freiburg, Institut für Informatik Georges-Koehler-Allee 52, Raum 00-006, 79110 Freiburg, Germany phone: ++49 761 203-8250 pr...@informatik.uni-freiburg.de fax: ++49 761 203-8242www.informatik.uni-freiburg.de
Re: [Dovecot] v1.2: can't access other users shared INBOX
On 25.03.2009, Bernhard Herzog wrote:
On 19.03.2009, Bernhard Herzog wrote:
The reason for that is maildir_fill_readdir always adds the virtual name
of the INBOX even when MAILBOX_LIST_ITER_VIRTUAL_NAMES isn't set. In
lines 260ff of mailbox-list-maildir-iter.c, rev. 5284f45c249a it
unconditionally adds the prefix to INBOX when adding it to the tree:
node = mailbox_tree_get(ctx-tree_ctx,
t_strconcat(ns-prefix, INBOX, NULL), NULL);
The patch below fixes this, by only adding the virtual name of the INBOX
if virtual_names is true, basically in the same way as earlier in the
loop. I'm not sure whether it's really the correct fix, but in my tests
so far it seems to work correctly.
As it turns out, there is one problem the patch doesn't address.
There's one other problem that the patch doesn't fix. If user fred gives dave
read permission on INBOX but not on any other folder and the inbox has
children, the INBOX is not always listed for dave. OTOH, if dave has read
permissions on one of the children, or the INBOX does not have children at
all, the INBOX is listed.
What happens is that if INBOX has children maildir_fill_readdir will add INBOX
to the tree indirectly when it encounters the children and later when the
INBOX special cases are handled, INBOX is already in the tree and it won't be
matched against the mailbox name pattern and thus it's MAILBOX_MATCHED flag
will not be set. If INBOX is the only visible mailbox that would match the
search pattern, no mailbox in the tree has the MAILBOX_MATCHED flag, and
dovecot will consider the whole users/fred namespace invisible to dave.
The patch below addresses this.
Bernhard
diff -r 643a96aec996 src/lib-storage/list/mailbox-list-maildir-iter.c
--- a/src/lib-storage/list/mailbox-list-maildir-iter.c Thu Mar 26 18:36:36
2009 -0400
+++ b/src/lib-storage/list/mailbox-list-maildir-iter.c Fri Mar 27 17:46:53
2009 +0200
@@ -250,16 +250,29 @@ maildir_fill_readdir(struct maildir_list
if (!update_only)
node-flags |= MAILBOX_MATCHED;
}
- } else if (mailbox_tree_lookup(ctx-tree_ctx, INBOX) == NULL
- imap_match(glob, INBOX) == IMAP_MATCH_YES) {
+ } else {
+ const char * inbox_name;
+ if (!virtual_names) {
+ inbox_name = INBOX;
+ } else {
+ inbox_name = mail_namespace_get_vname(ns, mailbox,
+ INBOX);
+ }
+
/* see if INBOX exists. */
ret = ctx-ctx.list-v.
- iter_is_mailbox(ctx-ctx, ctx-dir, , INBOX,
- MAILBOX_LIST_FILE_TYPE_UNKNOWN, flags);
- if (ret 0) {
- node = mailbox_tree_get(ctx-tree_ctx,
- t_strconcat(ns-prefix, INBOX, NULL), NULL);
- node-flags = MAILBOX_NOCHILDREN | MAILBOX_MATCHED;
+ iter_is_mailbox(ctx-ctx, ctx-dir, ,
+ INBOX,
+ MAILBOX_LIST_FILE_TYPE_UNKNOWN,
+ flags);
+ if (ret 0 imap_match(glob, inbox_name) == IMAP_MATCH_YES) {
+
+ node = mailbox_tree_get(ctx-tree_ctx, inbox_name,
+ created);
+ if (created)
+ node-flags = MAILBOX_NOCHILDREN;
+
+ node-flags |= MAILBOX_MATCHED;
}
}
return 0;
--
Bernhard Herzog | ++49-541-335 08 30 | http://www.intevation.de/
Intevation GmbH, Neuer Graben 17, 49074 Osnabrück | AG Osnabrück, HR B 18998
Geschäftsführer: Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner
signature.asc
Description: This is a digitally signed message part.
[Dovecot] MAILBOXDIR question
I'm unclear about where and how this is to be used. I gather it is to be a new standard, but I didn't seem to find anything about it in the Dovecot Wiki Mail Location page. There are some words about it in the 1.1.12/3 release notes, but perhaps I'm thick, but they're meta-ambiguous to me. Is it meant to be used like this: mail_location = mbox:MAILBOXDIR=~/mail:INBOX=/var/mail/%u instead of the current mail_location = mbox:~/mail:INBOX=/var/mail/%u ??? Sorry to be so dense. -- Once upon a time, the Internet was a friendly, neighbors-helping-neighbors small town, and no one locked their doors. Now it's like an apartment in Bed-Stuy: you need three heavy duty pick-proof locks, one of those braces that goes from the lock to the floor, and bars on the windows Stewart Dean, Unix System Admin, Bard College, New York 12504 sd...@bard.edu voice: 845-758-7475, fax: 845-758-7035
[Dovecot] dbox benchmarks
http://hg.dovecot.org/dovecot-dbox-redesign/ Looks like multi-dbox scales pretty nicely. Even after 100k messages the peak saved msgs/sec is the same as the initial saved msgs/sec, even if the average slows down somewhat. I tested this by first deleting mailbox, then running imaptest for a second to get saving to start writing several fields to dovecot.index.cache file. Then ran imaptest for 60 seconds that did nothing but save messages using IMAP APPEND commands. The summary is that multi-dbox is almost 10x as fast as maildir when fsync is disabled and 2,5 faster with fsyncing: fsync_disable=yes: multi-dbox : ~1700 - ~1500 msgs/sec, 90842 msgs/60 sec single-dbox: ~1700 - ~1400 msgs/sec, 86149 msgs/60 sec maildir: ~330 - ~110 msgs/sec, 9789 msgs/60 sec fsync_disable=no: multi-dbox : ~220 - ~170 msgs/sec, 10113 msgs/60 sec maildir: ~100 - ~70 msgs/sec, 4123 msgs/60 sec Also I just noticed that saving messages with two clients gets a peak of 2200 msgs/sec, most likely because two CPU cores can be used then. Hmm. I guess if there were no locking it should have reached 3400 msgs/sec, but it's better than no performance increase. And the raw data: multi-dbox, fsync_disable=yes imaptest clients=1 secs=1;imaptest clients=1 msgs=100 - logout=0 append=100,0 secs=60 Logi Sele Appe 100% 100% 100% 11 1759 1/ 1 00 1424 1/ 1 00 1734 1/ 1 ... 00 1701 1/ 1 00 1640 1/ 1 00 778 1/ 1 00 1305 1/ 1 00 1598 1/ 1 Totals: Logi Sele Appe 100% 100% 100% 11 90842 multi-dbox, fsync_disable=no imaptest clients=1 secs=1;imaptest clients=1 msgs=100 - logout=0 append=100,0 secs=60 Logi Sele Appe 100% 100% 100% 11 209 1/ 1 00 227 1/ 1 00 208 1/ 1 ... 00 203 1/ 1 00 145 1/ 1 00 156 1/ 1 00 180 1/ 1 00 162 1/ 1 Totals: Logi Sele Appe 100% 100% 100% 11 10113 maildir, fsync_disable=yes Logi Sele Appe 100% 100% 100% 11 331 1/ 1 00 311 1/ 1 00 288 1/ 1 ... 00 96 1/ 1 00 119 1/ 1 00 111 1/ 1 Totals: Logi Sele Appe 100% 100% 100% 11 9789 maildir, fsync_disable=no Logi Sele Appe 100% 100% 100% 11 77 1/ 1 00 101 1/ 1 00 45 1/ 1 ... 00 52 1/ 1 00 67 1/ 1 00 89 1/ 1 Totals: Logi Sele Appe 100% 100% 100% 11 4123 single-dbox, fsync_disable=yes imaptest clients=1 secs=1;imaptest clients=1 msgs=100 - logout=0 append=100,0 secs=60 Logi Sele Appe 100% 100% 100% 11 1765 1/ 1 00 1715 1/ 1 00 1764 1/ 1 ... 00 1722 1/ 1 00 1679 1/ 1 00 1678 1/ 1 00 828 1/ 1 00 1467 1/ 1 00 1469 1/ 1 00 1149 1/ 1 00 1135 1/ 1 Totals: Logi Sele Appe 100% 100% 100% 11 86149 signature.asc Description: This is a digitally signed message part
Re: [Dovecot] dbox benchmarks
On Mon, 2009-03-30 at 18:26 -0400, Timo Sirainen wrote: maildir: ~330 - ~110 msgs/sec, 9789 msgs/60 sec With maildir_very_dirty_syncs=yes (just committed to v1.2 hg): ~1100 - ~110 msgs/sec, 11904 msgs/60 sec. signature.asc Description: This is a digitally signed message part
[Dovecot] Convert from maildir to dbox
Ok...I made the leap. Compiled a copy of 1.2b4 (very pleasant compile BTW - almost no warnings, nice code Timo!)...tweaked a config...had a few false starts... 1.2b4 seems to working quite nicely. Now...for my next magical trick... I would like to migrate from maildir to dbox. I've tried using the convert plugin, but it kept failing during the conversion. I should mention my paths: home (old new) = /var/mail/%d/%n old mail = maildir:/var/mail/%d/%n new mail = dbox:/var/mail/%d/%n/dbox Note that home was defined as the same path as mail in my old config - I'm looking to fix that as well during the migration. I found entries in my mail log after the convert execution similar to: Mar 30 19:00:52 bubba dovecot: IMAP(s...@amfes.com): rename(/var/mail/amfes.com/sfox/.dovecot.convert.lock/cur, /var/mail/amfes.com/sfox/dbox/mailboxes/dovecot/convert/lock/dbox-Mails) failed: Not a directory Mar 30 19:01:41 bubba dovecot: IMAP(s...@amfes.com): Mailbox conversion failed for mailbox dovecot.convert.lock Now that I'm staring at that line...I'm wondering if that home=mail configuration is part of the problem. I currently have about a dozen users on this box - but with very large mailboxes (I still have archived mailing lists in mine!). If there's a few manual steps I need to perform to condition this setup prior to conversion please advise. Should I manually shift the mailboxes into a /var/mail/%d/%n/maildir folder? -- Daniel
Re: [Dovecot] Empty To: Header and message_address_parse
On Mar 30, 2009, at 8:29 AM, wolfgang.frie...@desy.de wrote: Our To header looks like: To: AdminCc of rt Ticket #123456:; The message_address_parse function called with the TRUE flag (triggers add_fixed_address) in dovecot changes that to To: AdminCc of rt Ticket #123456: missing_mail...@missing_domain ; That's a bug. Fixed: http://hg.dovecot.org/dovecot-1.2/rev/e5658894cd13
Re: [Dovecot] Common sasl master [Was: sendmail with dovecot sasl]
Mario Pavlov wrote, On 3/28/09 8:36 AM: Hi, so sendmail can use only cyrus-sasl ? Right. SASL is only standardized in the network-facing parts: a collection of named and specified authentication mechanisms. Cyrus and Dovecot offer extremely different interfaces to different sets of back-end services for other software to use. Supporting Dovecot SASL in an MTA requires creating a completely different interface than is used for Cyrus, and Dovecot does not provide all of the functionality that Cyrus does. ok, thank you Mario Pavlov wrote: I was wondering if I can make sendmail use dovecot's SASL implementation...maybe I should somehow compile it against dovecot's SASL ? My idea is to make sendmail and dovecot authenticate against one central user/password repository. Is this possible ? thank you. P.S. I want to use virtual users Sendmail uses cyrus-sasl (only?). You can make cyrus-sasl and dovecot-sasl use common master e.g. LDAP or PAM. LDAP centric approach is a standard recommendation if you plan multi server mail system with multiple mailbox servers/filtering gateways. -- [plen: Andrew] Andrzej Adam Filip : a...@onet.eu While there's life, there's hope. -- Publius Terentius Afer (Terence)
Re: [Dovecot] Convert from maildir to dbox
On Mar 30, 2009, at 10:21 PM, Daniel L. Miller wrote: I currently have about a dozen users on this box - but with very large mailboxes (I still have archived mailing lists in mine!). If there's a few manual steps I need to perform to condition this setup prior to conversion please advise. Should I manually shift the mailboxes into a /var/mail/%d/%n/maildir folder? Yes. convert plugin really doesn't like it when home dir = mail dir.
Re: [Dovecot] MAILBOXDIR question
On Mar 30, 2009, at 3:15 PM, Stewart Dean wrote: I'm unclear about where and how this is to be used. I gather it is to be a new standard, but I didn't seem to find anything about it in the Dovecot Wiki Mail Location page. There are some words about it in the 1.1.12/3 release notes, but perhaps I'm thick, but they're meta-ambiguous to me. Is it meant to be used like this: mail_location = mbox:MAILBOXDIR=~/mail:INBOX=/var/mail/%u instead of the current mail_location = mbox:~/mail:INBOX=/var/mail/%u No, don't use MAILBOXDIR with mbox or maildir. It's primarily useful with dbox. But the correct syntax would have been: mail_location = mbox:~/mail:MAILBOXDIR=mailboxes:INBOX=/var/mail/%u
