Re: [Dovecot] v2.0.alpha1 released
On 14.10.2009 2:30, Ed W wrote: Actually, here's the original Nokia paper - just reading it now, seems quite interesting: http://research.nokia.com/files/NRCTR2008002.pdf I wonder whats difference between WM phones which connects to Exchange servers using same TCP socket via HTTP(S) and push messages while doing seems fine for battery life.
[Dovecot] Some errors with sieve
Hello all. I found some errors in logs like this: Oct 14 05:51:47 IMAP(ch...@khb.fxclub.org): Error: stat(/var/spool/dovecot/domains/khb.fxclub.org/chief/.dovecot.sieve/tmp) failed: Not a directory Oct 14 06:17:01 IMAP(m...@fxclub.org): Error: stat(/var/spool/dovecot/domains/fxclub.org/msa/.dovecot.sieve/tmp) failed: Not a directory Oct 14 06:17:28 IMAP(stolchnev...@soft-expert.biz): Error: stat(/var/spool/dovecot/domains/soft-expert.biz/stolchnev-vk/.dovecot.sieve/tmp) failed: Not a directory Filter seems to work normal. Dovecot -n: # 1.2.4: /usr/local/etc/dovecot.conf # OS: FreeBSD 7.1-RELEASE-p7 i386 ufs base_dir: /var/run/dovecot/ log_path: /var/log/dovecot/dovecot.log info_log_path: /var/log/dovecot/dovecot-debug.log protocols: imap imaps pop3 pop3s managesieve listen(default): * listen(imap): * listen(pop3): * listen(managesieve): *:2000 ssl_ca_file: /usr/local/etc/certs/GlobalSignCA.crt ssl_cert_file: /usr/local/etc/certs/fxclub_org.crt ssl_key_file: /usr/local/etc/certs/fxclub_org.key ssl_cipher_list: ALL:!LOW:!SSLv2 login_dir: /var/run/dovecot/login login_executable(default): /usr/local/libexec/dovecot/imap-login login_executable(imap): /usr/local/libexec/dovecot/imap-login login_executable(pop3): /usr/local/libexec/dovecot/pop3-login login_executable(managesieve): /usr/local/libexec/dovecot/managesieve-login login_process_size: 128 login_processes_count: 20 login_max_processes_count: 512 mail_max_userip_connections(default): 256 mail_max_userip_connections(imap): 256 mail_max_userip_connections(pop3): 20 mail_max_userip_connections(managesieve): 10 verbose_proctitle: yes first_valid_gid: 0 mail_privileged_group: mail mail_uid: dmail mail_gid: dmail mail_location: maildir:/var/spool/dovecot/domains/%d/%n mail_debug: yes mail_executable(default): /usr/local/libexec/dovecot/imap mail_executable(imap): /usr/local/libexec/dovecot/imap mail_executable(pop3): /usr/local/libexec/dovecot/pop3 mail_executable(managesieve): /usr/local/libexec/dovecot/managesieve mail_process_size: 512 mail_plugins(default): quota imap_quota autocreate mail_log mail_plugins(imap): quota imap_quota autocreate mail_log mail_plugins(pop3): quota mail_plugins(managesieve): mail_plugin_dir(default): /usr/local/lib/dovecot/imap mail_plugin_dir(imap): /usr/local/lib/dovecot/imap mail_plugin_dir(pop3): /usr/local/lib/dovecot/pop3 mail_plugin_dir(managesieve): /usr/local/lib/dovecot/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_client_workarounds(default): pop3_client_workarounds(imap): pop3_client_workarounds(pop3): outlook-no-nuls oe-ns-eoh pop3_client_workarounds(managesieve): lda: postmaster_address: postmas...@fxclub.org hostname: mail.fxclub.org mail_plugins: sieve quota mail_plugin_dir: /usr/local/lib/dovecot/lda quota_full_tempfail: yes deliver_log_format: msgid=%m: %$ %f %s log_path: /var/log/dovecot/deliver.log info_log_path: /var/log/dovecot/deliver.log sendmail_path: /usr/sbin/sendmail rejection_reason: Your message to %t was automatically rejected:%n%r auth_socket_path: /var/run/dovecot/auth-master auth default: mechanisms: plain login user: dovecot-auth username_format: %Lu worker_max_count: 100 passdb: driver: ldap args: /usr/local/etc/dovecot-ldap.conf userdb: driver: ldap args: /usr/local/etc/dovecot-ldap.conf socket: type: listen client: path: /var/run/dovecot/auth-client mode: 432 user: exim master: path: /var/run/dovecot/auth-master mode: 384 user: dmail plugin: quota: maildir quota_rule: *:storage=1024M quota_rule2: Trash:storage=1256M quota_rule3: SPAM:ignore quota_warning: storage=95%% /usr/local/bin/quota-warning.sh 95 quota_warning2: storage=80%% /usr/local/bin/quota-warning.sh 80 autocreate: Trash autocreate2: Sent autocreate3: Spam autosubscribe: Trash autosubscribe2: Sent autosubscribe3: Spam sieve_dir: ~/sieve sieve: ~/.dovecot.sieve sieve_global_path: /var/spool/dovecot/global.sieve mail_location: /var/spool/dovecot/domains/%d/%n/ mail_log_events: delete undelete expunge copy mailbox_delete mailbox_rename mail_log_fields: uid box msgid size mail_log_max_lines_per_sec: 0 -- С уважением, Проскурин Кирилл +7(495)727-06-26 доб. 1070
Re: [Dovecot] Some errors with sieve
Proskurin Kirill wrote: Hello all. I found some errors in logs like this: Oct 14 05:51:47 IMAP(ch...@khb.fxclub.org): Error: stat(/var/spool/dovecot/domains/khb.fxclub.org/chief/.dovecot.sieve/tmp) failed: Not a directory Oct 14 06:17:01 IMAP(m...@fxclub.org): Error: stat(/var/spool/dovecot/domains/fxclub.org/msa/.dovecot.sieve/tmp) failed: Not a directory Oct 14 06:17:28 IMAP(stolchnev...@soft-expert.biz): Error: stat(/var/spool/dovecot/domains/soft-expert.biz/stolchnev-vk/.dovecot.sieve/tmp) failed: Not a directory Filter seems to work normal. Don't place the .dovecot.sieve file in a Maildir directory. I is recognized as a folder and when an attempt is made to access it through IMAP, errors like the one above will be reported in the logs. Regards, Stephan
Re: [Dovecot] backup using rsync
to...@tuxteam.de wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tue, Oct 13, 2009 at 04:15:02PM +0200, Robert Schetterer wrote: to...@tuxteam.de schrieb: On Fri, Oct 09, 2009 at 03:41:40PM +0200, Robert Schetterer wrote: [...] i ll do backups with rsync on maildirs with courier ( which has also : in filenames ) Stupid question: with CIFS as target filesystem? no never, why should i do this, nfs , ssh etc should be faster and more secure etc Nor would I, for that. But I can afford the luxury to see CIFS once a couple of years :) My experience is that cifs is *faster* than nfs... Also, I personally find it simpler to administrate than NFS. Probably this is due to ignorance of how to setup NFS to do user based ID mappings, etc, but there you go... (Much as it pains me to like an MS derived product, I have to stick up for it here... I think you will find a bunch of benchmarks in favour of either solution if you search the net, but the point being that at least some benchmarks also put cifs ahead of nfs in terms of performance...) The end result is still in favour or rsync+ssh though... Do have a look at snapback2 for a fairly simple backup solution which works very nicely for me Ed W
Re: [Dovecot] v2.0.alpha1 released
Nikolay Shopik wrote: On 14.10.2009 2:30, Ed W wrote: Actually, here's the original Nokia paper - just reading it now, seems quite interesting: http://research.nokia.com/files/NRCTR2008002.pdf I wonder whats difference between WM phones which connects to Exchange servers using same TCP socket via HTTP(S) and push messages while doing seems fine for battery life. I'm not sure I understand the question, but bear in mind that WM phones are usually massively hungry for power even at idle and usually have fairly short battery lives (and big batteries) and so the *incremental* cost of using the network may be much less apparent in that case? Note how the author finds that his radio card consumes something like 33mA at idle, compared with his notes that other authors measure 200-400mA from various WM device radios - he notes something about perhaps there being some more research needed on choose a good radio card... Actually for those not reading the news, CE6.5 is getting panned in reviews right now, MS have fumbled this Sidekick/Danger device thing big time (spent half a billion dollars buying the company and then lost all the data and likely all the customers in one day...) and it looks like their ipod killer (Pink?) is stillborn and they are getting beaten up for effectively spending the money twice building a phone + a zune when both basically do similar things. Looks like WM devices may get passed over quite a bit until CE7 is released in a blaze of glory... Oh also in the news this month is that the LSE is to move away from it's Microsoft .Net platform, plus a slew of massive bug fixes for all their platforms. All in all a tough month for MS, but to their credit they seem to have avoided many of them making the major news channels apart from the fairly anti-MS end of the geek press... Ed W
[Dovecot] Questions regarding dbox migration
It has been my wish to move to dbox for a long time hoping to reduce the number of writes which is really killing us. Now I wonder what may be the best way of doing so. I'm considering some sort of intermediate migration where the existing Maildir users are changed to single-dbox and then later upgraded to 2.0 and changed to multi-dbox when it becomes stable. But is this a reasonable task to perform on a production system or at all? The alternative is to wait for 2.0 to become completely stable and then go all the way at once. I would however much prefer to take it one step at a time and I think it would be safer to start out with single-dbox as it appears less complex. Now the big question is whether multi-dbox and single-dbox are compatible formats. If a Maildir-dbox migration is made on a system running dovecot v. 1.1, would it then be trivial later changing to multi-dbox after upgrading to 2.0 or is a completely new migration then needed? Would this scenario be much different if the system is upgraded to version 1.2 before the change to single-dbox? Kind regards, Mikkel
[Dovecot] quota error dovecot 1.1.13
Hi all, I've troubles with dovecot and quota. Sometimes mails to users are bounced because quota is full. I'm reading quota_rules from LDAP. One du -h . from maildir show user is under quota ( at 70 % more or less), less than 99%, i delete maildirsize and dovecot recreate it with ldap-quota value at first line and second line is current-quota mails. Current-quota is near quota max value so dovecot execute quota_warning (99%). Why is dovecot thinking quota is at 99% when du -h show me its value is near 70% ? any guess? My conf: syslog_facility: local1 protocols: imap pop3 managesieve listen(default): * listen(imap): * listen(pop3): *:110 listen(managesieve): *:2000 ssl_disable: yes disable_plaintext_auth: no login_dir: /usr/local/dovecot//var/run/dovecot/login login_executable(default): /usr/local/dovecot/libexec/dovecot/imap-login login_executable(imap): /usr/local/dovecot/libexec/dovecot/imap-login login_executable(pop3): /usr/local/dovecot/libexec/dovecot/pop3-login login_executable(managesieve): /usr/local/dovecot/libexec/dovecot/managesieve-login login_process_per_connection: no login_process_size: 1200 login_processes_count: 20 login_max_processes_count: 2048 login_max_connections: 512 max_mail_processes: 4096 mail_max_userip_connections(default): 1000 mail_max_userip_connections(imap): 1000 mail_max_userip_connections(pop3): 10 mail_max_userip_connections(managesieve): 10 mail_location: maildir:%h/Maildir mmap_disable: yes dotlock_use_excl: no mail_nfs_storage: yes mail_nfs_index: yes mail_executable(default): /usr/local/dovecot/libexec/dovecot/imap mail_executable(imap): /usr/local/dovecot/libexec/dovecot/imap mail_executable(pop3): /usr/local/dovecot/libexec/dovecot/pop3 mail_executable(managesieve): /usr/local/dovecot/libexec/dovecot/managesieve mail_plugins(default): quota imap_quota mail_plugins(imap): quota imap_quota mail_plugins(pop3): quota mail_plugins(managesieve): mail_plugin_dir(default): /usr/local/dovecot/lib/dovecot/imap mail_plugin_dir(imap): /usr/local/dovecot/lib/dovecot/imap mail_plugin_dir(pop3): /usr/local/dovecot/lib/dovecot/pop3 mail_plugin_dir(managesieve): /usr/local/dovecot//lib/dovecot/managesieve imap_client_workarounds(default): outlook-idle imap_client_workarounds(imap): outlook-idle imap_client_workarounds(pop3): imap_client_workarounds(managesieve): sieve(default): sieve(imap): sieve(pop3): sieve(managesieve): ~/.dovecot.sieve auth default: cache_size: 512000 cache_ttl: 1800 executable: /usr/local/dovecot/libexec/dovecot/dovecot-auth failure_delay: 5 debug: yes worker_max_count: 4096 worker_max_request_count: 4096 process_size: 4096 passdb: driver: ldap args: /etc/dovecot/dovecot-ldap.conf userdb: driver: ldap args: /etc/dovecot/dovecot-ldap.conf socket: type: listen master: path: /var/run/dovecot/auth-master mode: 511 plugin: sieve: %h/.dovecot.sieve quota_warning: storage=99%% /usr/local/bin/quota-full.sh %u quota_warning2: storage=95%% /usr/local/bin/quota-warning.sh 95 %u quota_warning3: storage=70%% /usr/local/bin/quota-warning.sh 70 %u quota: maildir thanks in advance, Regards.
Re: [Dovecot] quota error dovecot 1.1.13
Brightblade skrev: Hi all, I've troubles with dovecot and quota. Sometimes mails to users are bounced because quota is full. I'm reading quota_rules from LDAP. One du -h . from maildir show user is under quota ( at 70 % more or less), less than 99%, i delete maildirsize and dovecot recreate it with ldap-quota value at first line and second line is current-quota mails. Current-quota is near quota max value so dovecot execute quota_warning (99%). Why is dovecot thinking quota is at 99% when du -h show me its value is near 70% ? any guess? You should read the file named maildirsize in the specific user's homedir. I'll tell you whether this is caused by a wrong interpretation of your ldap values or whether dovecot didn't count the usage right. The first line in the maildirsize file tells what values it got from the database and the subsequent lines are counting the actual usage. Comparing the values on the first line to your ldap database is the first thing you should do. Getting what dovecot considers the actual usage from the maildirsize file requires that you know how it works. One in a while dovecot saves the current usage to the second line of the maildirsize file. Then afterwards every time the there is a change (mail arrives or is deleted) one line showing that change is appended to the file. When a certain limit is reached all the lines are summed together and the second line of the file is updates (while all subsequent lines are deleted). This means that just reading the second line of the file will give you a pretty good indication of whether dovecot has counted the usage correctly. If dovecot has made an error just delete the maildirsize which will cause dovecot to recount the usage. Regards, Mikkel
[Dovecot] pop3-login process
Hi, I would like to know if the pop3-login process would be create more than one while a user connection is established. http://wiki.dovecot.org/RunningDovecot imap-login and pop3-login processes handle new IMAP and POP3 connections until user has logged in. I'm sorry to ask you this kind of question... Regards, -- GyaO! - Anime, Dramas, Movies, and Music videos [FREE] http://pr.mail.yahoo.co.jp/gyao/
Re: [Dovecot] Some errors with sieve
On Oct 14, 2009, at 3:55 AM, Stephan Bosch wrote: Proskurin Kirill wrote: Hello all. I found some errors in logs like this: Oct 14 05:51:47 IMAP(ch...@khb.fxclub.org): Error: stat(/var/spool/ dovecot/domains/khb.fxclub.org/chief/.dovecot.sieve/tmp) failed: Not a directory Oct 14 06:17:01 IMAP(m...@fxclub.org): Error: stat(/var/spool/ dovecot/domains/fxclub.org/msa/.dovecot.sieve/tmp) failed: Not a directory Oct 14 06:17:28 IMAP(stolchnev...@soft-expert.biz): Error: stat(/ var/spool/dovecot/domains/soft-expert.biz/stolchnev- vk/.dovecot.sieve/tmp) failed: Not a directory Filter seems to work normal. Don't place the .dovecot.sieve file in a Maildir directory. I is recognized as a folder and when an attempt is made to access it through IMAP, errors like the one above will be reported in the logs. And if you really can't help doing it, set maildir_stat_dirs=yes.
[Dovecot] [Off-Topic] Dovecot and Maildrop
Hello, I need to know : What is the best way to use Postfix (Virtual User on Mysql) + Dovecot + Maildrop ? Is there some documentation that you can indicate to me? Thanks !!
Re: [Dovecot] Questions regarding dbox migration
On Oct 14, 2009, at 7:03 AM, Mikkel wrote: It has been my wish to move to dbox for a long time hoping to reduce the number of writes which is really killing us. BTW. Have you tried maildir_very_dirty_syncs=yes setting? That should reduce disk i/o, and I'm really interested in hearing how much.
Re: [Dovecot] [Off-Topic] Dovecot and Maildrop
* Darvin Denmian [2009-10-14 12:27]: Hello, I need to know : What is the best way to use Postfix (Virtual User on Mysql) + Dovecot + Maildrop ? Is there some documentation that you can indicate to me? Thanks !! http://wiki.dovecot.org/HowTo http://wiki.dovecot.org/maildrop -- -- Kirill Miazine k...@krot.org
Re: [Dovecot] pop3-login process
Hello! * ogu...@yahoo.co.jp [2009-10-14 21:47]: Hi, I would like to know if the pop3-login process would be create more than one while a user connection is established. I appologize if I don't understand your question correctly: There will be login_processes_count login processes listening for new connections. And there will be a new pop3-login process for each new established user connection until the number of login processes reach the value defined in login_max_processes_count. http://wiki.dovecot.org/RunningDovecot imap-login and pop3-login processes handle new IMAP and POP3 connections until user has logged in. I'm sorry to ask you this kind of question... -- -- Kirill Miazine k...@krot.org
Re: [Dovecot] Autocreate plugin for some domains
Dear Timo, I added the line you mentioned echo yeah i got here /tmp/autocreate and did not create the file /tmp/autocreate This is the script with the real domain: #!/bin/bash DOMAIN=`echo $USER|sed s/^.*@//` if [ $DOMAIN = operaciones.qnet.com.pe ]; then export USERDB_AUTOCREATE=INBOX.spam1 export USERDB_AUTOCREATE2=INBOX.spam2 export EXTRA=USERDB_AUTOCREATE USERDB_AUTOCREATE2 echo yeah i got here /tmp/autocreate fi unset USER exec $* What could be happening? Thanks Jose Luis From: t...@iki.fi To: jolumape...@hotmail.com Date: Tue, 13 Oct 2009 20:58:47 -0400 CC: dovecot@dovecot.org Subject: Re: [Dovecot] Autocreate plugin for some domains On Oct 13, 2009, at 6:32 PM, Jose Luis Marin Perez wrote: Additionally I have made this modification: #!/bin/bash DOMAIN=`echo $USER|sed s/^.*@//` if [ $DOMAIN = domain2.com ]; then export USERDB_AUTOCREATE=INBOX.box1 export USERDB_AUTOCREATE2=INBOX.box2 export EXTRA=USERDB_AUTOCREATE USERDB_AUTOCREATE2 Are you sure this code gets called? Maybe add something here such as: echo yeah i got here /tmp/autocreate fi unset USER exec $* But it does not work, and dovecot.log not log any information about the plugin autocreate What does it log with auth_debug=yes enabled? _ Invite your mail contacts to join your friends list with Windows Live Spaces. It's easy! http://spaces.live.com/spacesapi.aspx?wx_action=createwx_url=/friends.aspxmkt=en-us
Re: [Dovecot] Autocreate plugin for some domains
On Tue, 2009-10-13 at 22:53 -0500, Jose Luis Marin Perez wrote: I added the line you mentioned echo yeah i got here /tmp/autocreate and did not create the file /tmp/autocreate Then it needs more debugging. Try: This is the script with the real domain: #!/bin/bash DOMAIN=`echo $USER|sed s/^.*@//` echo $USER /tmp/autocreate echo $DOMAIN /tmp/autocreate signature.asc Description: This is a digitally signed message part
Re: [Dovecot] Questions regarding dbox migration
On 10/14/2009, Timo Sirainen (t...@iki.fi) wrote: I'm trying to get v2.0.0 out pretty quickly though. v2.0.beta1 should hopefully be out in less than a month. Great news on how fast 2.0 is coming along! I finally got the go ahead to convert my biggest client, but he wants to hold off (political reasons) for a few months, so I think I'll just plan on starting to test 2.0 soon, and making that the target for his installation. The main problem with it is actually how to make it enough backwards compatible that everyone won't start hating me. I honestly don't see that ever happening Timo - and please, don't go down the same road Microsoft did with Windows. Not that you need any help, but I would suggest to just focus on making the conversion tools (mbox/maildir (m)dbox, old config new config, etc) rock solid, and document any incompatibilities really well. -- Best regards, Charles
Re: [Dovecot] Questions regarding dbox migration
On 10/14/2009, Timo Sirainen (t...@iki.fi) wrote: BTW. Have you tried maildir_very_dirty_syncs=yes setting? That should reduce disk i/o, and I'm really interested in hearing how much. What are the downsides? Also, I'm guessing maybe there are certain conditions where you definitely don't want to do it? -- Best regards, Charles
Re: [Dovecot] quota error dovecot 1.1.13
On Wed, 2009-10-14 at 11:43 +, Brightblade wrote: Why is dovecot thinking quota is at 99% when du -h show me its value is near 70% ? any guess? Messages copied with hard links. Try du -l instead. signature.asc Description: This is a digitally signed message part
Re: [Dovecot] Questions regarding dbox migration
On Wed, 2009-10-14 at 12:18 -0400, Charles Marcus wrote: The main problem with it is actually how to make it enough backwards compatible that everyone won't start hating me. I honestly don't see that ever happening Timo - and please, don't go down the same road Microsoft did with Windows. Not that you need any help, but I would suggest to just focus on making the conversion tools (mbox/maildir (m)dbox, old config new config, etc) rock solid, and document any incompatibilities really well. Well, the old config - new config tool is probably the way I'm going, but that still needs to be written. :) signature.asc Description: This is a digitally signed message part
Re: [Dovecot] Questions regarding dbox migration
On Wed, 2009-10-14 at 12:18 -0400, Charles Marcus wrote: On 10/14/2009, Timo Sirainen (t...@iki.fi) wrote: BTW. Have you tried maildir_very_dirty_syncs=yes setting? That should reduce disk i/o, and I'm really interested in hearing how much. What are the downsides? Also, I'm guessing maybe there are certain conditions where you definitely don't want to do it? The only reason you wouldn't want to set it is if cur/ directory is modified outside Dovecot. Or Dovecot is used without index files (or e.g. with NFS and local index files). The point being: Dovecot trusts index files to be up-to-date with cur/ directory's contents. Although even then it still checks the cur/'s mtime to see if it had changed. The only problem is if Dovecot changes it at the same time as non-Dovecot. Then it doesn't know that there was a change. Unless the filesystem supports nano/microsecond mtimes, that'll make it very unlikely for Dovecot to miss this. signature.asc Description: This is a digitally signed message part
Re: [Dovecot] Questions regarding dbox migration
On 10/14/2009 12:24 PM, Timo Sirainen wrote: BTW. Have you tried maildir_very_dirty_syncs=yes setting? That should reduce disk i/o, and I'm really interested in hearing how much. What are the downsides? Also, I'm guessing maybe there are certain conditions where you definitely don't want to do it? The only reason you wouldn't want to set it is if cur/ directory is modified outside Dovecot. Or Dovecot is used without index files (or e.g. with NFS and local index files). The point being: Dovecot trusts index files to be up-to-date with cur/ directory's contents. Although even then it still checks the cur/'s mtime to see if it had changed. The only problem is if Dovecot changes it at the same time as non-Dovecot. Then it doesn't know that there was a change. Unless the filesystem supports nano/microsecond mtimes, that'll make it very unlikely for Dovecot to miss this. Perfect explanation, thanks. :)
Re: [Dovecot] Autocreate plugin for some domains
Hi Timo, These are the results: more /tmp/autocreate jmarin jmarin I'm using the mail account jma...@operaciones.qnet.com.pe vchkpw-wrapper.sh #!/bin/bash DOMAIN=`echo $USER|sed s/^.*@//` echo $USER /tmp/autocreate echo $DOMAIN /tmp/autocreate if [ $DOMAIN = operaciones.qnet.com.pe ]; then export USERDB_AUTOCREATE=INBOX.spam1 export USERDB_AUTOCREATE2=INBOX.spam2 export EXTRA=USERDB_AUTOCREATE USERDB_AUTOCREATE2 echo yeah i got here /tmp/autocreate fi unset USER exec $* Thanks Jose Luis From: t...@iki.fi To: jolumape...@hotmail.com Date: Wed, 14 Oct 2009 12:18:17 -0400 CC: dovecot@dovecot.org Subject: Re: [Dovecot] Autocreate plugin for some domains On Tue, 2009-10-13 at 22:53 -0500, Jose Luis Marin Perez wrote: I added the line you mentioned echo yeah i got here /tmp/autocreate and did not create the file /tmp/autocreate Then it needs more debugging. Try: This is the script with the real domain: #!/bin/bash DOMAIN=`echo $USER|sed s/^.*@//` echo $USER /tmp/autocreate echo $DOMAIN /tmp/autocreate _ Explore the seven wonders of the world http://search.msn.com/results.aspx?q=7+wonders+worldmkt=en-USform=QBRE
Re: [Dovecot] Autocreate plugin for some domains
On Wed, 2009-10-14 at 11:37 -0500, Jose Luis Marin Perez wrote: These are the results: more /tmp/autocreate jmarin jmarin Oh, right, that's because of vchkpw that drops the @domain out of $USER. What if you simply comment out: DOMAIN=`echo $USER|sed s/^.*@//` Maybe it sets $DOMAIN internally? If not, find out where the domain is: set /tmp/environment signature.asc Description: This is a digitally signed message part
[Dovecot] dovecot + ldap
Hi, I have a configuration with dovecot authenticating to AD. I would like to authenticate using the user logon name in AD. and mail box were created according to the field mail in AD anyone have any idea about this? my dovecot-ldap: hosts = xx.xx.xx.xx base = dc=domain,dc=com ldap_version = 3 auth_bind = yes auth_bind_userdn = domain\%u thanks. -- Bely Silva Junior
Re: [Dovecot] Better APPEND performance
On Wed, 2009-10-07 at 17:53 -0500, Mike Abbott wrote: What can be done to make maildir_uidlist_refresh_fast_init() choose the fast path more often? Pretty simple bug. Fixed: http://hg.dovecot.org/dovecot-1.2/rev/ebdba086e3b1 This makes the performance pretty good when appending to maildirs with large number of messages. In my desktop the append speed stays pretty constant at ~500 msgs/sec after 20k messages, while without the patch it crawls at ~30-40 msgs/sec. signature.asc Description: This is a digitally signed message part
[Dovecot] dovecot + ldap
Hi, I have a configuration with dovecot authenticating to AD. I would like to authenticate using the user logon name in AD. and mail box were created according to the field mail in AD anyone have any idea about this? my dovecot-ldap: hosts = xx.xx.xx.xx base = dc=domain,dc=com ldap_version = 3 auth_bind = yes auth_bind_userdn = domain\%u thanks. -- Bely Silva Junior
Re: [Dovecot] @2.0 IMAP login, Error: ...//lib20_fts_plugin.so: undefined symbol: fts_next_hook_mailbox_allocated
I'm, as yet, still unable to load any fts plugin ... any advice here? Thx.
On Mon, Oct 12, 2009 at 9:15 PM, PGNet Dev pgnet.dev+dove...@gmail.com wrote:
hi,
@ imap login to 2.0/head,
Oct 12 21:06:53 master: Info: Dovecot v2.0.alpha1 starting up (core
dumps disabled)
Oct 12 21:07:16 imap-login: Info: Login:
user=testu...@my.domain.com, method=PLAIN, rip=192.168.1.100,
lip=192.168.1.101, TLS
Oct 12 21:07:16 IMAP(testu...@my.domain.com): Info: Loading modules
from directory: /usr/local/lib/dovecot
Oct 12 21:07:16 IMAP(testu...@my.domain.com): Info: Module loaded:
/usr/local/lib/dovecot/lib10_quota_plugin.so
Oct 12 21:07:16 IMAP(testu...@my.domain.com): Info: Module loaded:
/usr/local/lib/dovecot/lib11_imap_quota_plugin.so
Oct 12 21:07:16 IMAP(testu...@my.domain.com): Info: Module loaded:
/usr/local/lib/dovecot/lib20_autocreate_plugin.so
Oct 12 21:07:16 IMAP(testu...@my.domain.com): Error:
dlopen(/usr/local/lib/dovecot/lib20_fts_plugin.so) failed:
/usr/local/lib/dovecot/lib20_fts_plugin.so: undefined symbol:
fts_next_hook_mailbox_allocated
Oct 12 21:07:16 IMAP(testu...@my.domain.com): Fatal: Couldn't load
required plugins
also, after install, i note,
cd /usr/local/lib
ls dovecot/{imap,lda,pop3}
dovecot/imap:
lib15_notify_plugin.so
dovecot/lda:
lib15_notify_plugin.so lib90_sieve_plugin.a lib90_sieve_plugin.la
lib90_sieve_plugin.so
dovecot/pop3:
lib15_notify_plugin.so
shouldn't, e.g., dovecot/imap have auto-populated symlinks to
autocreate, fts, etc plugins? or for 2.0 do they need to be manually
created?
thx.
Re: [Dovecot] Autocreate plugin for some domains
Hi Timo, This is the content of /tmp/Environment: [r...@ml110c ~]# more environment ANONYMOUS_USERNAME=anonymous AUTH_1_MASTER=/usr/local/var/run/dovecot/auth-master AUTH_1_MASTER_GROUP=vchkpw AUTH_1_MASTER_MODE=600 AUTH_1_MASTER_USER=vpopmail AUTH_NAME=default AUTH_WORKER_MAX_COUNT=30 AUTH_WORKER_MAX_REQUEST_COUNT=0 AUTH_WORKER_PATH=/usr/local/var/run/dovecot/auth-worker.13415 BASH=/bin/bash BASH_ARGC=([0]=1) BASH_ARGV=([0]=/usr/local/libexec/dovecot/checkpassword-reply) BASH_LINENO=([0]=0) BASH_SOURCE=([0]=/usr/local/bin/vchkpw-wrapper.sh) BASH_VERSINFO=([0]=3 [1]=00 [2]=15 [3]=1 [4]=release [5]=i686-redhat-linux-gnu) BASH_VERSION='3.00.15(1)-release' CACHE_NEGATIVE_TTL=3600 CACHE_SIZE=0 CACHE_TTL=3600 DEFAULT_REALM= DIRSTACK=() DOMAIN=jmarin DOVECOT_MASTER=1 DOVECOT_VERSION=1.1.16 EUID=89 FAILURE_DELAY=2 GROUPS=() HOME=/usr/vpopmail/domains/operaciones.qnet.com.pe/jmarin HOSTNAME=ml110c.qnet.com.pe HOSTTYPE=i686 IFS=$' \t\n' LOCAL_IP=127.0.0.1 LOG_TO_MASTER=1 MACHTYPE=i686-redhat-linux-gnu MASTER_USER_SEPARATOR= MECHANISMS=plain OPTERR=1 OPTIND=1 OSTYPE=linux-gnu PASSDB_1_ARGS='/usr/vpopmail/bin/vchkpw /usr/local/bin/vchkpw-wrapper.sh' PASSDB_1_DRIVER=checkpassword PATH=/usr/local/bin:/bin:/usr/bin PIPESTATUS=([0]=0) PPID=13415 PROTO=TCP PS4='+ ' PWD=/usr/vpopmail/domains/operaciones.qnet.com.pe/jmarin REALMS= REMOTE_IP=127.0.0.1 RESTRICT_CHROOT= RESTRICT_GID_FIRST= RESTRICT_GID_LAST= RESTRICT_SETEXTRAGROUPS= RESTRICT_SETGID= RESTRICT_SETGID_PRIV= RESTRICT_SETUID= RESTRICT_USER= SERVICE=imap SHELL=NOLOGIN SHELLOPTS=braceexpand:hashall:interactive-comments SHLVL=1 SYSLOG_FACILITY=16 TCPLOCALIP=127.0.0.1 TCPLOCALPORT=10143 TCPREMOTEIP=127.0.0.1 TCPREMOTEPORT=38229 TERM=dumb UID=89 USER=jmarin USERDB_1_ARGS='uid=89 gid=89 home=/usr/vpopmail/domains/%d/%u' USERDB_1_DRIVER=prefetch USERDB_2_DRIVER=vpopmail USERNAME_CHARS=abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890.-_@ USERNAME_FORMAT= USERNAME_TRANSLATION= VERBOSE_DEBUG=1 vpopuser=jma...@operaciones.qnet.com.pe WINBIND_HELPER_PATH=/usr/bin/ntlm_auth _=jmarin and I noticed that where the mail account is in the variable VPOPUSER so I modified the script to: #!/bin/bash DOMAIN=`echo $VPOPUSER|sed s/^.*@//` echo $USER /tmp/autocreate echo $DOMAIN /tmp/autocreate if [ $DOMAIN = operaciones.qnet.com.pe ]; then export USERDB_AUTOCREATE=INBOX.spam1 export USERDB_AUTOCREATE2=INBOX.spam2 export EXTRA=USERDB_AUTOCREATE USERDB_AUTOCREATE2 fi unset USER exec $* working correctly, just wanted to ask if I use the variable VPOPUSER not bring trouble? Thanks Jose Luis From: t...@iki.fi To: jolumape...@hotmail.com Date: Wed, 14 Oct 2009 12:39:10 -0400 CC: dovecot@dovecot.org Subject: Re: [Dovecot] Autocreate plugin for some domains On Wed, 2009-10-14 at 11:37 -0500, Jose Luis Marin Perez wrote: These are the results: more /tmp/autocreate jmarin jmarin Oh, right, that's because of vchkpw that drops the @domain out of $USER. What if you simply comment out: DOMAIN=`echo $USER|sed s/^.*@//` Maybe it sets $DOMAIN internally? If not, find out where the domain is: set /tmp/environment _ Explore the seven wonders of the world http://search.msn.com/results.aspx?q=7+wonders+worldmkt=en-USform=QBRE
Re: [Dovecot] Better APPEND performance
On Wed, 2009-10-14 at 12:48 -0400, Timo Sirainen wrote: On Wed, 2009-10-07 at 17:53 -0500, Mike Abbott wrote: What can be done to make maildir_uidlist_refresh_fast_init() choose the fast path more often? Pretty simple bug. Fixed: http://hg.dovecot.org/dovecot-1.2/rev/ebdba086e3b1 This makes the performance pretty good when appending to maildirs with large number of messages. In my desktop the append speed stays pretty constant at ~500 msgs/sec after 20k messages, while without the patch it crawls at ~30-40 msgs/sec. This is also useful for maildir_very_dirty_syncs=yes, otherwise dovecot-uidlist never shrinks: http://hg.dovecot.org/dovecot-1.2/rev/7956cc1086e1 signature.asc Description: This is a digitally signed message part
Re: [Dovecot] Questions regarding dbox migration
Timo Sirainen skrev: On Oct 14, 2009, at 7:03 AM, Mikkel wrote: It has been my wish to move to dbox for a long time hoping to reduce the number of writes which is really killing us. BTW. Have you tried maildir_very_dirty_syncs=yes setting? That should reduce disk i/o, and I'm really interested in hearing how much. I don't think I've tried that one. Earlier on I experimented with fsync_disable=yes (which made a huge difference by the way) but that was before I started using mail_nfs_storage=yes and mail_nfs_index=yes I would like to try using maildir_very_dirty_syncs=yes but is it advisable in combination with NFS? Regards, Mikkel
Re: [Dovecot] Questions regarding dbox migration
Timo Sirainen skrev: On Oct 14, 2009, at 7:03 AM, Mikkel wrote: Now the big question is whether multi-dbox and single-dbox are compatible formats. Kind of, but not practically. If a Maildir-dbox migration is made on a system running dovecot v. 1.1, would it then be trivial later changing to multi-dbox after upgrading to 2.0 or is a completely new migration then needed? Would this scenario be much different if the system is upgraded to version 1.2 before the change to single-dbox? Migrating from single-dbox to multi-dbox isn't any easier than maildir - multi-dbox. From your comments it appears like dbox and mdbox are quite different in many ways. Is mdbox going to replace dbox completely or are you expecting to keep both formats? My point is: what's going to be the difference between dbox and mbox with mdbox_rotate_size set small enough to allow only one mail per file? I'm trying to get v2.0.0 out pretty quickly though. v2.0.beta1 should hopefully be out in less than a month. The main problem with it is actually how to make it enough backwards compatible that everyone won't start hating me. That is great news. I'm looking very much forward to make the shift to dbox/mdbox. A new mail storage format is really, really, really interesting from my point of view. CPU and RAM are both very cheap by now but disk I/O remains as expensive as always and really is the only limiting factor these days and is what's driving up the costs of running any larger mail system. The performance gains you mentioned previously this year would probably cut the total datacenter costs in half and that is quite an accomplishment. How stable do you think dbox and mdbox are at the moment? Regards, Mikkel
Re: [Dovecot] Questions regarding dbox
Timo Sirainen t...@iki.fi wrote: [...] Do you play to support both ways migration tools? dbox - maildir(s) -- [plen: Andrew] Andrzej Adam Filip : a...@onet.eu Unlike most net.puritans, however, I feel that what OTHER consenting computers do in the privacy of their own phone connections is their own business. -- John Woods, j...@eddie.mit.edu
[Dovecot] Two passwords: One for Dovecot IMAP and One for Dovecot SASL? Is it possible?
Greetings, Can Dovecot can handle separate authentication for receiving mail (IMAPS) and sending mail (SMTPS)? In the past, we used Dovecot IMAP for the receiving part and Cyrus SASL for the sending part. This allowed us to use two passwords with mail. Cyrus has grown too old and isn't useful anymore. Can Dovecot give us this functionality: two passwords, one for IMAP authentication and one for SASL authentication? If so, could you point me in the right direction to get this working? Thanks in advance, A
Re: [Dovecot] Questions regarding dbox migration
On Wed, 2009-10-14 at 21:14 +0200, Mikkel wrote: It has been my wish to move to dbox for a long time hoping to reduce the number of writes which is really killing us. BTW. Have you tried maildir_very_dirty_syncs=yes setting? That should reduce disk i/o, and I'm really interested in hearing how much. I don't think I've tried that one. Earlier on I experimented with fsync_disable=yes (which made a huge difference by the way) but that was before I started using mail_nfs_storage=yes and mail_nfs_index=yes I would like to try using maildir_very_dirty_syncs=yes but is it advisable in combination with NFS? It should be fine with NFS if indexes are also on NFS. Although I just fixed a bug related to it: http://hg.dovecot.org/dovecot-1.2/rev/7956cc1086e1 Indexes on NFS are problematic now though if multiple servers can access the mailbox at the same time. mail_nfs_index=yes is supposed to help with that, but it's not perfect either. Long term solution would be for Dovecots in different machines to talk to each others directly instead of through NFS. signature.asc Description: This is a digitally signed message part
Re: [Dovecot] Questions regarding dbox migration
On Wed, 2009-10-14 at 21:28 +0200, Mikkel wrote: From your comments it appears like dbox and mdbox are quite different in many ways. Is mdbox going to replace dbox completely or are you expecting to keep both formats? My point is: what's going to be the difference between dbox and mbox with mdbox_rotate_size set small enough to allow only one mail per file? The main difference is that mdbox needs to lock files when saving messages. That's not especially nice with NFS. Single-dbox currently locks index files, but it can be made entirely lockless eventually. There are also some other differences like: - in mdbox all messages exist in storage/ directory, while in dbox messages exist in separate mailbox directories - mdbox has a separate storage/dovecot.map.index that needs to be updated - in mdbox message can be copied by doing a couple of small appends to index files, while with dbox the file needs to be hard linked (and currently even that's not done) How stable do you think dbox and mdbox are at the moment? mdbox passed 16 hours of imaptest stress testing with zero errors. I'm thinking about starting to use it at some point for my own mails. dbox in v1.2 should also be stable, but in v2.0 last I tried imaptest could break it, I should fix it someday soon. signature.asc Description: This is a digitally signed message part
Re: [Dovecot] Questions regarding dbox
On Wed, 2009-10-14 at 21:39 +0200, Andrzej Adam Filip wrote: Timo Sirainen t...@iki.fi wrote: [...] Do you play to support both ways migration tools? dbox - maildir(s) convert plugin can already do that. In v2.0 I'm planning on getting rid of convert plugin and relying on dsync program. It can do two-way sync between any mailbox formats and between different machines if wanted (e.g. via ssh). signature.asc Description: This is a digitally signed message part
[Dovecot] Dovecot deliver with AD LDAP userdb
Good Afternoon,
I have my virtual users stored in an Active Directory database. As far
as mail info goes the 2 important fields are: mail (their primary
email address) and otherMailbox (a multivalue attribute containing
their mail aliases). Right now all email addresses belong in the same
domain and there are no immediate plans to change this.
If I use Postfix to do the lookups and delivery only using Dovecot for
passdb Pam driver and a static userdb then everything delivers fine to
mail and otherMailbox addresses. I have been working on switching over
to Dovecot's deliver process in order to integrate sieve capability. I
have configured userdb ldap and passdb ldap in Dovecot and have set up
master and client sockets. Before I describe my problem let me show
you my configuration (as I think the dovecot-ldap.conf in particular
needs to be explained). Here are the important parts of dovecot.conf:
auth default {
socket listen {
master {
path = /usr/var/run/dovecot/auth-master
mode = 0666
user = vmail
group = vmail
}
client {
path = /var/spool/postfix/private/auth
mode = 0666
user = postfix
group = postfix
}
}
passdb ldap {
args = /etc/dovecot-ldap.conf
}
userdb ldap {
# Path for LDAP configuration file, see doc/dovecot-ldap-example.conf
args = /etc/dovecot-ldap.conf
}
and my dovecot -n:
lda:
postmaster_address: postmas...@sau24.org
mail_plugins: sieve
auth default:
mechanisms: plain login
debug: yes
passdb:
driver: ldap
args: /etc/dovecot-ldap.conf
userdb:
driver: ldap
args: /etc/dovecot-ldap.conf
socket:
type: listen
client:
path: /var/spool/postfix/private/auth
mode: 438
user: postfix
group: postfix
master:
path: /usr/var/run/dovecot/auth-master
mode: 438
user: vmail
group: vmail
plugin:
sieve: ~/.dovecot.sieve
sieve_dir: ~/sieve
sieve_storage: ~/sieve
Further, here is my dovecot-ldap.conf:
hosts = delldb.sau24.org:3268
base = dc=sau24, dc=org
ldap_version = 3
dn = cn=Mail User,cn=Users,dc=sau24,dc=org
dnpass = secret
auth_bind = yes
scope = subtree
user_attrs = sAMAccountName=home=/home/vmail/%$,=uid=501,=gid=501
pass_attrs = sAMAccountName=user
user_filter =
((objectclass=person)(|(sAMAccountName=%n)(mail...@sau24.org)(othermailbox...@sau24.org)))
pass_filter =
((objectclass=person)(|(sAMAccountName=%n)(mail...@sau24.org)(othermailbox...@sau24.org)))
Now, you'll notice that the user_filter and pass_filter have the
domain statically placed after the mail and othermailbox attributes.
This reason for this is that this ldap configuration is used for both
authentication purposes and local delivery, so its not always being
passed the domain info (for authentication it gets the users IP
address). Since all my users are on the same domain I can statically
set this here. This setup authenticates users to imap and pop (users
use their sAMAccountName as their username when they log in), and
pulls their correct home directory. Checking mail is not a problem at
all.
Further, this setup will deliver mail correctly to mail addressed to
the value in the mail attribute. The problem seems to be in the
otherMailbox attribute, it cannot lookup the users sAMAccountName
based off of the otherMailbox field. Here is what it looks like in the
logs for mail sent to my mail attribute (mark.sch...@sau24.org):
Oct 14 12:36:19 auth(default): Info: master in: USER1
mark.sch...@sau24.org service=deliver
Oct 14 12:36:19 auth(default): Info: ldap(mark.sch...@sau24.org): user
search: base=dc=sau24, dc=org scope=subtree
filter=((objectclass=user)(|(sAMAccountName=mark.schaub)(mail=mark.sch...@sau24.org)(othermailbox=mark.sch...@sau24.org)))
fields=sAMAccountName
Oct 14 12:36:19 auth(default): Info: ldap(mark.sch...@sau24.org):
result: sAMAccountName(home=/home/vmail/%$)=/home/vmail/mschaub
Oct 14 12:36:19 auth(default): Info: master out: USER 1
mark.sch...@sau24.org home=/home/vmail/mschaubuid=501
gid=501
Oct 14 12:36:19 deliver(mark.sch...@sau24.org): Info: sieve:
msgid=6b71e3a70910140936v4e8cd6fdwd847a1721a9d9...@mail.gmail.com:
stored mail into mailbox 'INBOX'
But this is what I get when I try to send to an address listed in my
otherMailbox field (t...@sau24.org):
Oct 14 12:30:58 auth(default): Info: master in: USER1
t...@sau24.org service=deliver
Oct 14 12:30:58 auth(default): Info: ldap(t...@sau24.org): user
search: base=dc=sau24, dc=org scope=subtree
filter=((objectclass=user)(|(sAMAccountName=tech)(mail=t...@sau24.org)(othermailbox=t...@sau24.org)))
fields=sAMAccountName
Oct 14 12:30:58 auth(default): Info: ldap(t...@sau24.org): Unknown user
Oct 14 12:30:58 auth(default): Info: master out: NOTFOUND 1
As a test I tried modifying my dovecot-ldap.conf to use different
fields instead of otherMailbox. Sending to some of those attributes
worked, others didnt. I could use the sn and givenName
[Dovecot] Investigating suspected cache corruption
Hi All, I'm running Dovecot 1.1.11 for a site of about 7000 active users with a Squirrelmail frontend. We migrated from Courier (big shout to everyone who worked on the wonderful part of the Dovecot wiki that deals with Courier migration) and I have been extremely happy with the performance gains Dovecot has given us. Not only is the IMAP part of Squirrelmail faster, but our same hardware is under far less stress than it was before the migration. To date, the only problem we have experienced is a seemingly random but significant slowdown in Squirrelmail's loading of the messages in a user's Inbox. Each time, I have been able to fix the problem by deleting the user's dovecot.index, dovecot.index.cache and dovecot.index.log files in the user's INDEX directory for their dovecot Inbox. I tried having users experiencing this problem log in to a test Squirrelmail box with mail_debug on, but I didn't see anything out of the ordinary and they report the same slowness on the test server. I don't see anything but normal login/logout IMAP lines in the production dovecot logs. I have hesitated a bit in posting to the list since this seems to be happening to a small percentage of users and it technically may be a problem with Squirrelmail, but the fact that I'm able to fix the problem by nuking Dovecot's index files has me concerned - does anyone have any suggestions for troubleshooting? My first idea when I get another one of these is to do a telnet IMAP session to Dovecot on one of the Squirrelmail boxes and see if I can get it to slow down when retrieving messages from the Inbox. We are using Maildir over NFS with the control/index files stored on NFS as well. We're doing FS quota over NFS using rquotad to query the NFS server for each user's quota. Here's the output of dovecot -n: # 1.1.11: /etc/dovecot.conf Warning: fd limit 1024 is lower than what Dovecot can use under full load (more than 1536). Either grow the limit or change login_max_processes_count and max_mail_processes settings # OS: Linux 2.6.18-128.1.1.0.1.el5 x86_64 Red Hat Enterprise Linux Server release 5.3 (Tikanga) 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_process_per_connection: no login_processes_count: 10 login_max_processes_count: 512 verbose_proctitle: yes first_valid_uid: 0 mail_location: maildir:~/Maildir:CONTROL=/Mail/mailhome/ %u/.dovecot:INDEX=/Mail/mailhome/%u/.dovecot mmap_disable: yes mail_nfs_storage: yes mail_nfs_index: yes mail_drop_priv_before_exec: yes 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): mail_plugin_dir(default): /usr/lib64/dovecot/imap mail_plugin_dir(imap): /usr/lib64/dovecot/imap mail_plugin_dir(pop3): /usr/lib64/dovecot/pop3 imap_client_workarounds(default): outlook-idle delay-newmail imap_client_workarounds(imap): outlook-idle delay-newmail imap_client_workarounds(pop3): imap_logout_format(default): bytes(in/out)=%i/%o imap_logout_format(imap): bytes(in/out)=%i/%o imap_logout_format(pop3): bytes=%i/%o pop3_uidl_format(default): %08Xu%08Xv pop3_uidl_format(imap): %08Xu%08Xv pop3_uidl_format(pop3): UID%u-%v pop3_client_workarounds(default): pop3_client_workarounds(imap): pop3_client_workarounds(pop3): outlook-no-nuls oe-ns-eoh pop3_logout_format(default): top=%t/%p, retr=%r/%b, del=%d/%m, size=%s pop3_logout_format(imap): top=%t/%p, retr=%r/%b, del=%d/%m, size=%s pop3_logout_format(pop3): top(count/bytes)=%t/%p, retr(count/bytes)=%r/ %b, del(deleted/pre-deleted)=%d/%m, mailbox-size(bytes)=%s namespace: type: private prefix: INBOX. inbox: yes list: yes subscriptions: yes auth default: mechanisms: plain login passdb: driver: pam userdb: driver: passwd plugin: quota: fs:Mail Quota:user Many thanks, David Warden
Re: [Dovecot] Investigating suspected cache corruption
On Wed, 2009-10-14 at 16:17 -0400, David Warden wrote: To date, the only problem we have experienced is a seemingly random but significant slowdown in Squirrelmail's loading of the messages in a user's Inbox. Each time, I have been able to fix the problem by deleting the user's dovecot.index, dovecot.index.cache and dovecot.index.log files in the user's INDEX directory for their dovecot Inbox. First thing to try next time: Does it help if you only delete dovecot.index.cache file? How large is the cache file? And take a copy of the dovecot.index* files before doing that, I can then ask a few more questions about them. I tried having users experiencing this problem log in to a test Squirrelmail box with mail_debug on, but I didn't see anything out of the ordinary and they report the same slowness on the test server. I don't see anything but normal login/logout IMAP lines in the production dovecot logs. mail_debug doesn't really help with performance debugging. My first idea when I get another one of these is to do a telnet IMAP session to Dovecot on one of the Squirrelmail boxes and see if I can get it to slow down when retrieving messages from the Inbox. That sounds like a good idea to try. And use the exact same IMAP commands as Squirrelmail to do it. strace -tt output of of the slow imap process could also show something interesting. signature.asc Description: This is a digitally signed message part
Re: [Dovecot] Questions regarding dbox migration
Timo Sirainen skrev: The main difference is that mdbox needs to lock files when saving messages. That's not especially nice with NFS. Single-dbox currently locks index files, but it can be made entirely lockless eventually. There are also some other differences like: - in mdbox all messages exist in storage/ directory, while in dbox messages exist in separate mailbox directories - mdbox has a separate storage/dovecot.map.index that needs to be updated - in mdbox message can be copied by doing a couple of small appends to index files, while with dbox the file needs to be hard linked (and currently even that's not done) So basically you prefer mdbox but are maintaining dbox because of its almost lockless design which is better for NFS users? Do you consider it to be viable having two different dbox formats or are you planning to keep only one of them in a long term perspective? Regards, Mikkel
Re: [Dovecot] Questions regarding dbox migration
On Wed, 2009-10-14 at 23:04 +0200, Mikkel wrote: So basically you prefer mdbox but are maintaining dbox because of its almost lockless design which is better for NFS users? Do you consider it to be viable having two different dbox formats or are you planning to keep only one of them in a long term perspective? I'm planning on keeping both of them. And it's not necessarily only because of NFS users. Multi-dbox was done mainly because filesystems suck (mailbox gets fragmented all around the disk). Maybe if filesystems in future suck less, single-dbox will be better. Or perhaps SSDs make the fragmentation problem mostly irrelevant. And note that there are no real world statistics on how much faster multi-dbox is compared to single-dbox (or maildir). Maybe the difference isn't all that big after all. Or maybe it's a lot bigger than I thought. I've no idea. signature.asc Description: This is a digitally signed message part
Re: [Dovecot] Questions regarding dbox migration
Timo Sirainen skrev: On Wed, 2009-10-14 at 21:14 +0200, Mikkel wrote: It has been my wish to move to dbox for a long time hoping to reduce the number of writes which is really killing us. BTW. Have you tried maildir_very_dirty_syncs=yes setting? That should reduce disk i/o, and I'm really interested in hearing how much. I don't think I've tried that one. Earlier on I experimented with fsync_disable=yes (which made a huge difference by the way) but that was before I started using mail_nfs_storage=yes and mail_nfs_index=yes I would like to try using maildir_very_dirty_syncs=yes but is it advisable in combination with NFS? It should be fine with NFS if indexes are also on NFS. Although I just fixed a bug related to it: http://hg.dovecot.org/dovecot-1.2/rev/7956cc1086e1 The system is currently running dovecot version 1.1.19. Would you consider it safe to try it on that version as well? Indexes on NFS are problematic now though if multiple servers can access the mailbox at the same time. mail_nfs_index=yes is supposed to help with that, but it's not perfect either. Long term solution would be for Dovecots in different machines to talk to each others directly instead of through NFS. Is worse now than previously? I have been running at production setup with two servers accessing the same Maildir data from NFS without any problems for quite a while now. Load is spread randomly between the two servers so I can only assume that by coincidence they sometimes try to access the same mailbox. This has functioned quote well with many versions of the 1.1.x dovecot releases so unless some new issues have been introduced I don't think I should fear anything in that regard :-) Regards, Mikkel
Re: [Dovecot] Questions regarding dbox migration
On Wed, 2009-10-14 at 23:18 +0200, Mikkel wrote: I don't think I've tried that one. Earlier on I experimented with fsync_disable=yes (which made a huge difference by the way) but that was before I started using mail_nfs_storage=yes and mail_nfs_index=yes I would like to try using maildir_very_dirty_syncs=yes but is it advisable in combination with NFS? It should be fine with NFS if indexes are also on NFS. Although I just fixed a bug related to it: http://hg.dovecot.org/dovecot-1.2/rev/7956cc1086e1 The system is currently running dovecot version 1.1.19. Would you consider it safe to try it on that version as well? Yes. v1.2.6 + these two patches should make the performance better: http://hg.dovecot.org/dovecot-1.2/rev/ebdba086e3b1 http://hg.dovecot.org/dovecot-1.2/rev/7956cc1086e1 Indexes on NFS are problematic now though if multiple servers can access the mailbox at the same time. mail_nfs_index=yes is supposed to help with that, but it's not perfect either. Long term solution would be for Dovecots in different machines to talk to each others directly instead of through NFS. Is worse now than previously? With dbox index corruption becomes a worse problem than with maildir, because index is the only location where message flags are kept. v2.0 creates dovecot.index.backup files every once in a while though. I have been running at production setup with two servers accessing the same Maildir data from NFS without any problems for quite a while now. Load is spread randomly between the two servers so I can only assume that by coincidence they sometimes try to access the same mailbox. This has functioned quote well with many versions of the 1.1.x dovecot releases so unless some new issues have been introduced I don't think I should fear anything in that regard :-) And you've actually been looking at Dovecot's error log? Good if it doesn't break, most people seem to complain about random errors. signature.asc Description: This is a digitally signed message part
Re: [Dovecot] Autocreate plugin for some domains
Hi Timo, This is the content of /tmp/Environment: [r...@ml110c ~]# more environment ANONYMOUS_USERNAME=anonymous AUTH_1_MASTER=/usr/local/var/run/dovecot/auth-master AUTH_1_MASTER_GROUP=vchkpw AUTH_1_MASTER_MODE=600 AUTH_1_MASTER_USER=vpopmail AUTH_NAME=default AUTH_WORKER_MAX_COUNT=30 AUTH_WORKER_MAX_REQUEST_COUNT=0 AUTH_WORKER_PATH=/usr/local/var/run/dovecot/auth-worker.13415 BASH=/bin/bash BASH_ARGC=([0]=1) BASH_ARGV=([0]=/usr/local/libexec/dovecot/checkpassword-reply) BASH_LINENO=([0]=0) BASH_SOURCE=([0]=/usr/local/bin/vchkpw-wrapper.sh) BASH_VERSINFO=([0]=3 [1]=00 [2]=15 [3]=1 [4]=release [5]=i686-redhat-linux-gnu) BASH_VERSION='3.00.15(1)-release' CACHE_NEGATIVE_TTL=3600 CACHE_SIZE=0 CACHE_TTL=3600 DEFAULT_REALM= DIRSTACK=() DOMAIN=jmarin DOVECOT_MASTER=1 DOVECOT_VERSION=1.1.16 EUID=89 FAILURE_DELAY=2 GROUPS=() HOME=/usr/vpopmail/domains/operaciones.qnet.com.pe/jmarin HOSTNAME=ml110c.qnet.com.pe HOSTTYPE=i686 IFS=$' \t\n' LOCAL_IP=127.0.0.1 LOG_TO_MASTER=1 MACHTYPE=i686-redhat-linux-gnu MASTER_USER_SEPARATOR= MECHANISMS=plain OPTERR=1 OPTIND=1 OSTYPE=linux-gnu PASSDB_1_ARGS='/usr/vpopmail/bin/vchkpw /usr/local/bin/vchkpw-wrapper.sh' PASSDB_1_DRIVER=checkpassword PATH=/usr/local/bin:/bin:/usr/bin PIPESTATUS=([0]=0) PPID=13415 PROTO=TCP PS4='+ ' PWD=/usr/vpopmail/domains/operaciones.qnet.com.pe/jmarin REALMS= REMOTE_IP=127.0.0.1 RESTRICT_CHROOT= RESTRICT_GID_FIRST= RESTRICT_GID_LAST= RESTRICT_SETEXTRAGROUPS= RESTRICT_SETGID= RESTRICT_SETGID_PRIV= RESTRICT_SETUID= RESTRICT_USER= SERVICE=imap SHELL=NOLOGIN SHELLOPTS=braceexpand:hashall:interactive-comments SHLVL=1 SYSLOG_FACILITY=16 TCPLOCALIP=127.0.0.1 TCPLOCALPORT=10143 TCPREMOTEIP=127.0.0.1 TCPREMOTEPORT=38229 TERM=dumb UID=89 USER=jmarin USERDB_1_ARGS='uid=89 gid=89 home=/usr/vpopmail/domains/%d/%u' USERDB_1_DRIVER=prefetch USERDB_2_DRIVER=vpopmail USERNAME_CHARS=abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890.-_@ USERNAME_FORMAT= USERNAME_TRANSLATION= VERBOSE_DEBUG=1 vpopuser=jma...@operaciones.qnet.com.pe WINBIND_HELPER_PATH=/usr/bin/ntlm_auth _=jmarin and I noticed that where the mail account is in the variable VPOPUSER so I modified the script to: #!/bin/bash DOMAIN=`echo $VPOPUSER|sed s/^.*@//` echo $USER /tmp/autocreate echo $DOMAIN /tmp/autocreate if [ $DOMAIN = operaciones.qnet.com.pe ]; then export USERDB_AUTOCREATE=INBOX.spam1 export USERDB_AUTOCREATE2=INBOX.spam2 export EXTRA=USERDB_AUTOCREATE USERDB_AUTOCREATE2 fi unset USER exec $* working correctly, just wanted to ask if I use the variable VPOPUSER not bring trouble? Thanks Jose Luis From: t...@iki.fi To: jolumape...@hotmail.com Date: Wed, 14 Oct 2009 12:39:10 -0400 CC: dovecot@dovecot.org Subject: Re: [Dovecot] Autocreate plugin for some domains On Wed, 2009-10-14 at 11:37 -0500, Jose Luis Marin Perez wrote: These are the results: more /tmp/autocreate jmarin jmarin Oh, right, that's because of vchkpw that drops the @domain out of $USER. What if you simply comment out: DOMAIN=`echo $USER|sed s/^.*@//` Maybe it sets $DOMAIN internally? If not, find out where the domain is: set /tmp/environment _ Connect to the next generation of MSN Messenger http://imagine-msn.com/messenger/launch80/default.aspx?locale=en-ussource=wlmailtagline
Re: [Dovecot] Autocreate plugin for some domains
On Wed, 2009-10-14 at 16:33 -0500, Jose Luis Marin Perez wrote: working correctly, just wanted to ask if I use the variable VPOPUSER not bring trouble? Anything that works is fine. signature.asc Description: This is a digitally signed message part
Re: [Dovecot] Autocreate plugin for some domains
Thanks Timo. From: t...@iki.fi To: jolumape...@hotmail.com Date: Wed, 14 Oct 2009 17:37:25 -0400 CC: dovecot@dovecot.org Subject: Re: [Dovecot] Autocreate plugin for some domains On Wed, 2009-10-14 at 16:33 -0500, Jose Luis Marin Perez wrote: working correctly, just wanted to ask if I use the variable VPOPUSER not bring trouble? Anything that works is fine. _ News, entertainment and everything you care about at Live.com. Get it now! http://www.live.com/getstarted.aspx
Re: [Dovecot] Questions regarding dbox migration
Timo Sirainen wrote: And you've actually been looking at Dovecot's error log? Good if it doesn't break, most people seem to complain about random errors. Well, it does complain once in a while but it has never resulted in data being lost in any way. But I guess your point is that this might happen with dbox under the same circumstances. A very good reason to wait for 2.0 I guess... Regards, Mikkel
Re: [Dovecot] Questions regarding dbox migration
On Wed, 2009-10-14 at 23:41 +0200, Mikkel wrote: Timo Sirainen wrote: And you've actually been looking at Dovecot's error log? Good if it doesn't break, most people seem to complain about random errors. Well, it does complain once in a while but it has never resulted in data being lost in any way. But I guess your point is that this might happen with dbox under the same circumstances. A very good reason to wait for 2.0 I guess... Well, the NFS caching issues aren't going away in v2.0 yet. v2.1 or so perhaps.. signature.asc Description: This is a digitally signed message part
Re: [Dovecot] Questions regarding dbox migration
Timo Sirainen wrote: On Wed, 2009-10-14 at 23:41 +0200, Mikkel wrote: Timo Sirainen wrote: And you've actually been looking at Dovecot's error log? Good if it doesn't break, most people seem to complain about random errors. Well, it does complain once in a while but it has never resulted in data being lost in any way. But I guess your point is that this might happen with dbox under the same circumstances. A very good reason to wait for 2.0 I guess... Well, the NFS caching issues aren't going away in v2.0 yet. v2.1 or so perhaps.. But it should be able to heal itself using the backup files in version 2.0, right? How often are they created anyway? Regards, Mikkel
Re: [Dovecot] Questions regarding dbox migration
On Wed, 2009-10-14 at 23:52 +0200, Mikkel wrote: Timo Sirainen wrote: On Wed, 2009-10-14 at 23:41 +0200, Mikkel wrote: Timo Sirainen wrote: And you've actually been looking at Dovecot's error log? Good if it doesn't break, most people seem to complain about random errors. Well, it does complain once in a while but it has never resulted in data being lost in any way. But I guess your point is that this might happen with dbox under the same circumstances. A very good reason to wait for 2.0 I guess... Well, the NFS caching issues aren't going away in v2.0 yet. v2.1 or so perhaps.. But it should be able to heal itself using the backup files in version 2.0, right? That's the theory anyway. :) How often are they created anyway? Whenever dovecot.index file would normally get recreated, the old one is first link()ed to dovecot.index.backup. So that depends on various things. You could compare timestamp differences between dovecot.index and dovecot.index.log in your current system. Perhaps I should add some extra code that guarantees that .backup gets created at least once .. a day? week? .. (assuming there have been changes) signature.asc Description: This is a digitally signed message part
Re: [Dovecot] Questions regarding dbox migration
Timo Sirainen skrev: On Wed, 2009-10-14 at 23:04 +0200, Mikkel wrote: So basically you prefer mdbox but are maintaining dbox because of its almost lockless design which is better for NFS users? Do you consider it to be viable having two different dbox formats or are you planning to keep only one of them in a long term perspective? I'm planning on keeping both of them. And it's not necessarily only because of NFS users. Multi-dbox was done mainly because filesystems suck (mailbox gets fragmented all around the disk). Maybe if filesystems in future suck less, single-dbox will be better. Or perhaps SSDs make the fragmentation problem mostly irrelevant. You are talking about directories being fragmented right? In case of mdbox wouldn't you have the very same problem since larger files may be fragmented all over the disk just like many small files in a directory might? And note that there are no real world statistics on how much faster multi-dbox is compared to single-dbox (or maildir). Maybe the difference isn't all that big after all. Or maybe it's a lot bigger than I thought. I've no idea. I think the impact on imap operations and mail delivery probably would very little due to bigger files. But pop3 users just download everything once in a while and should benefit tremendously from just having to read one file sequentially as opposed to read many small files. So I can definitely see the point in mdbox but I better stay away from it, using NFS... :/ Regards, Mikkel
Re: [Dovecot] Questions regarding dbox migration
Timo Sirainen wrote: On Wed, 2009-10-14 at 23:52 +0200, Mikkel wrote: But it should be able to heal itself using the backup files in version 2.0, right? That's the theory anyway. :) How often are they created anyway? Whenever dovecot.index file would normally get recreated, the old one is first link()ed to dovecot.index.backup. So that depends on various things. You could compare timestamp differences between dovecot.index and dovecot.index.log in your current system. Perhaps I should add some extra code that guarantees that .backup gets created at least once .. a day? week? .. (assuming there have been changes) I would like it to happen as often as possible unless you expect a lot of I/O to happen on this account. In that case perhaps it could be made a configurable option so the system administrator could decide for himself which risk/performance profile would fit in the specific situation? Regards, Mikkel
[Dovecot] Dovecot 1.2.6 segfault in imap_fetch_begin
We recently upgraded from Dovecot 1.2.4 to 1.2.6 (with the sieve patches of course). Everything has been running quite well since the upgrade. The occasional issue with assert-crashing when expunging has gone away. However, one of our users seems to have triggered a new issue. She's been the only one to see it, but whenever she logs in, her imap process segfaults immediately. It appears that the crash is a null pointer deref in the array library, but I'm not sure what code is at fault for calling in without checking array validity... or even if I'm on the right track. Backtraces and some further information are available here. Cores available on request. http://uoregon.edu/~brandond/dovecot-1.2.6/bt.txt Thanks, -Brad
Re: [Dovecot] Dovecot 1.2.6 segfault in imap_fetch_begin
On Wed, 2009-10-14 at 17:14 -0700, Brandon Davidson wrote: Backtraces and some further information are available here. Cores available on request. http://uoregon.edu/~brandond/dovecot-1.2.6/bt.txt -O2 compiling has dropped one stage from the backtrace, but I think this will fix the crash: http://hg.dovecot.org/dovecot-1.2/rev/352eab3d6ade There are also a few other bugs in QRESYNC handling that get fixed by these: http://hg.dovecot.org/dovecot-1.2/rev/f7f0bff8438a http://hg.dovecot.org/dovecot-1.2/rev/51329696ecf5 http://hg.dovecot.org/dovecot-1.2/rev/73c4a7d325fe I guess it would be time for 1.2.7 somewhat soon.. signature.asc Description: This is a digitally signed message part
Re: [Dovecot] Questions regarding dbox migration
On Wed, 2009-10-14 at 23:59 +0200, Mikkel wrote: I'm planning on keeping both of them. And it's not necessarily only because of NFS users. Multi-dbox was done mainly because filesystems suck (mailbox gets fragmented all around the disk). Maybe if filesystems in future suck less, single-dbox will be better. Or perhaps SSDs make the fragmentation problem mostly irrelevant. You are talking about directories being fragmented right? Files in a directory written to different parts of disk, yes. In case of mdbox wouldn't you have the very same problem since larger files may be fragmented all over the disk just like many small files in a directory might? I guess this depends on filesystem. But the files would typically be about 2 MB of size. I think filesystems usually copy more data around to avoid fragmentation. In any case if there are expunged messages, files containing them would be recreated (nightly or something). That'll unfragment the files. And finally one thing I've also been thinking about has been that perhaps new mails could be created into separate individual files. A nightly run would then gather them together into a larger file. So I can definitely see the point in mdbox but I better stay away from it, using NFS... :/ What kind of index related errors have you seen in logs? Dovecot can handle most index corruptions without losing much (if any) data. Everything related to dovecot.index.cache can at least be ignored. signature.asc Description: This is a digitally signed message part
Re: [Dovecot] pop3-login process
Hello, Thank you for the reply. So it means like this? A established connection = A pop3-login process I'm having a strange phenomenon that there are 5000 established connections, but pop3-login processes are more than 5000. Regards, --- Kirill Miazine k...@krot.org wrote: Hello! * ogu...@yahoo.co.jp [2009-10-14 21:47]: Hi, I would like to know if the pop3-login process would be create more than one while a user connection is established. I appologize if I don't understand your question correctly: There will be login_processes_count login processes listening for new connections. And there will be a new pop3-login process for each new established user connection until the number of login processes reach the value defined in login_max_processes_count. http://wiki.dovecot.org/RunningDovecot imap-login and pop3-login processes handle new IMAP and POP3 connections until user has logged in. I'm sorry to ask you this kind of question... -- -- Kirill Miazine k...@krot.org -- GyaO! - Anime, Dramas, Movies, and Music videos [FREE] http://pr.mail.yahoo.co.jp/gyao/
Re: [Dovecot] pop3-login process
On Thu, 2009-10-15 at 09:49 +0900, ogu...@yahoo.co.jp wrote: So it means like this? A established connection = A pop3-login process It should be about that. I'm having a strange phenomenon that there are 5000 established connections, but pop3-login processes are more than 5000. How much more? Anyway, with that many connections you should probably switch to running login_process_per_connection=no. http://wiki.dovecot.org/LoginProcess signature.asc Description: This is a digitally signed message part
Re: [Dovecot] Dovecot 1.2.6 segfault in imap_fetch_begin
Timo, -Original Message- -O2 compiling has dropped one stage from the backtrace, but I think this will fix the crash: snip I guess it would be time for 1.2.7 somewhat soon.. Thanks! As always, you're one step ahead of us with the bug fixes! I've got one more for you that just popped up. I'm guessing that it's also due to expunging causing sequence numbers to mixed up, and one of the existing patches will fix it? The error from the logs is: Panic: file mail-transaction-log-view.c: line 108 (mail_transaction_log_view_set): assertion failed: (min_file_seq = max_file_seq) Raw backtrace: imap [0x49e4a0] - imap [0x49e503] - imap [0x49db66] - imap(mail_transaction_log_view_set+0x4ac) [0x48651c] - imap(mail_index_view_sync_begin+0xe5) [0x480055] - imap(index_mailbox_sync_init+0x7f) [0x45e84f] - imap(maildir_storage_sync_init+0x100) [0x43cd30] - imap(imap_sync_init+0x67) [0x428257] - imap(cmd_sync_delayed+0x174) [0x4284a4] - imap(client_handle_input+0x19e) [0x420aee] - imap(client_input+0x5f) [0x4214df] - imap(io_loop_handler_run+0xf8) [0x4a61f8] - imap(io_loop_run+0x1d) [0x4a530d] - imap(main+0x620) [0x428da0] - /lib64/libc.so.6(__libc_start_main+0xf4) [0x31d5a1d994] - imap [0x419a89] dovecot: child 11758 (imap) killed with signal 6 (core dumped) Backtrace and such here: http://uoregon.edu/~brandond/dovecot-1.2.6/bt2.txt Thanks again, -Brad
Re: [Dovecot] ldap quota dovecot
HI All I'm having this exact problem but I call deliver this way in Postfix virtual_transport = dovecot mailbox_transport = dovecot Should I remove these and use the mailbox_command directive instead as you suggested? or is there a mailbox_transport alternative? On Mon, Sep 28, 2009 at 4:26 PM, Timo Sirainen t...@iki.fi wrote: On Mon, 2009-09-28 at 23:20 +0200, Mathieu BALCERAK wrote: Timo Sirainen a écrit : On Sun, 2009-09-27 at 16:26 +0200, Mathieu BALCERAK wrote: I have the same issue, when i upgrade to 1.2.5 the quota per user work only if i remove the directive quota_rule=*:storage=2G I set this rules as default for all my users except for 3 users. The imap_quota report perfectly the quota but dovecot lda take the quota_rule, per user quota not apply. How are you calling deliver? I call the deliver in postfix : mailbox_command = /usr/lib/dovecot/deliver That's the problem. I've tested with mailbox_command = /usr/lib/dovecot/deliver -d $USER This will solve your problem. but i have this error : deliver($USER): Error: userdb lookup: connect(/var/run/dovecot/auth-master) failed: Permission denied Change the permissions so that it does have access. You can specify the auth-master permissions in dovecot.conf. I guess you'll have to use mode=0666.
[Dovecot] Per User Quotas
Hi All I have not been able to get per user quotas going. A general quota works fine. My LDAP server is windows 2000. Here is my config mail# dovecot -n # 1.1.3: /usr/local/etc/dovecot.conf log_path: /var/log/dovecot.log protocols: imaps pop3s lda managesieve listen(default): * listen(imap): * listen(pop3): * listen(managesieve): *:2000 ssl_cert_file: /usr/local/etc/dovecot/ssl/certs/dovecot.pem ssl_key_file: /usr/local/etc/dovecot/ssl/private/dovecot.pem ssl_cipher_list: ALL:!ADH!LOW:!SSLv2:!EXP:+HIGH:+MEDIUM disable_plaintext_auth: no login_dir: /var/run/dovecot/login login_executable(default): /usr/local/libexec/dovecot/imap-login login_executable(imap): /usr/local/libexec/dovecot/imap-login login_executable(pop3): /usr/local/libexec/dovecot/pop3-login login_executable(managesieve): /usr/local/libexec/dovecot/managesieve-login login_greeting: Mail Server ready. login_greeting_capability(default): yes login_greeting_capability(imap): yes login_greeting_capability(pop3): no login_greeting_capability(managesieve): no verbose_proctitle: yes first_valid_uid: 1000 first_valid_gid: 1000 mail_privileged_group: mail mail_location: maildir:~/Maildir:INBOX=~/Maildir/:INDEX=~/Maildir/tmp/index mail_debug: yes maildir_copy_preserve_filename: yes mail_executable(default): /usr/local/libexec/dovecot/imap mail_executable(imap): /usr/local/libexec/dovecot/imap mail_executable(pop3): /usr/local/libexec/dovecot/pop3 mail_executable(managesieve): /usr/local/libexec/dovecot/managesieve mail_plugins(default): quota imap_quota mail_plugins(imap): quota imap_quota mail_plugins(pop3): quota mail_plugins(managesieve): mail_plugin_dir(default): /usr/local/lib/dovecot/imap mail_plugin_dir(imap): /usr/local/lib/dovecot/imap mail_plugin_dir(pop3): /usr/local/lib/dovecot/pop3 mail_plugin_dir(managesieve): /usr/local/lib/dovecot/managesieve imap_client_workarounds(default): delay-newmail netscape-eoh tb-extra-mailbox-sep imap_client_workarounds(imap): delay-newmail netscape-eoh tb-extra-mailbox-sep imap_client_workarounds(pop3): imap_client_workarounds(managesieve): pop3_enable_last(default): no pop3_enable_last(imap): no pop3_enable_last(pop3): yes pop3_enable_last(managesieve): no 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 sieve_storage(default): sieve_storage(imap): sieve_storage(pop3): sieve_storage(managesieve): ~/sieve sieve(default): sieve(imap): sieve(pop3): sieve(managesieve): ~/.dovecot.sieve auth default: mechanisms: plain login username_format: %Ln verbose: yes debug: yes passdb: driver: ldap args: /usr/local/etc/dovecot-ldap.conf userdb: driver: static args: uid=1002 gid=1002 home=/home/vmail/%u allow_all_users=yes userdb: driver: passwd args: blocking=yes socket: type: listen client: path: /var/run/dovecot/auth-client mode: 432 master: path: /var/run/dovecot/auth-master mode: 384 user: vmail group: vmail plugin: quota_warning: storage=95%% /usr/local/etc/dovecot/quota-warning.sh 95 quota_warning2: storage=80%% /usr/local/etc/dovecot/quota-warning.sh 80 quota: maildir quota2: maildir:user quota quota_rule: *:storage=512M quota_rule2: Trash:storage=10M quota_rule3: SPAM:ignore sieve: /home/vmail/%u/.dovecot.sieve I have this in dovecot-ldap.conf hosts = 192.168.1.97 192.168.1.76 base = dc=atlas,dc=local auth_bind = yes auth_bind_userdn = atlas\%u pass_filter = ((objectclass=person)(uid=%u)) user_attrs = homeDirectory=/home/vmail/%u,uidNumber=1002,gidNumber=1002,streetAddress=quota_rule=*:storage=%$M I then put this in the streetAddress area of the user info in AD *:storage=256M But no go. When I log in either in thunderbird or squirrelmail, I see the general quota for that user which is 512M and not 256M I'm at a loss, any help would be appreciated. By the way, after reading another thread, I added this to postfix but still no go. mailbox_command = /usr/local/libexec/dovecot/deliver -d $USER
Re: [Dovecot] Questions regarding dbox migration
At 12:18 PM 10/14/2009, Charles Marcus wrote: Not that you need any help, but I would suggest to just focus on making the conversion tools (mbox/maildir (m)dbox, old config new config, etc) rock solid, and document any incompatibilities really well. It'd be nice to think you were kidding, but I'll be you're not. I'd guess that there's no two the same configs of dovecot out there. I can't see any way to test for all of them. Heck, documentation for any particular environment/config, while abundant, is never quite exactly right because of that. (and for that matter I never could find one set of docs that covered everything I needed for a complete setup - I hate to merge dozens of docs on implementation). Dovecot is just a component of a larger mail infrastructure that's part of the zillions of choices in open source. And that's going to suck. Mail is probably the most critical business app out there. Upgrading with incompatibilities is going to be a nightmare for me, and that's even considering that I have a parallel pre-production environment. But it comes with using open source software (and quality code at that), so I live with it. Rick -- Best regards, Charles
