Re: [Dovecot] [OT] DRBD
On Mon, Nov 23, 2009 at 10:25 PM, Rodolfo Gonzalez Gonzalez rgonza...@gnt.cc wrote: Hello all, has someone worked with DRBD (http://www.drbd.org) for HA of mail storage? if so, does it have stability issues? comments and experiences are thanked :) Thanks, Rodolfo. We have deployed active/passive DRBD Mailserver for a customer with ~ 5000 mailboxes. runs nice without any problems. CentOS 5.3 Heartbeat 1 ! DRBD 8.3.x LVM If you try to use LVM/ext3 with DRBD and you want to use consistend snapshots, use this setup http://www.drbd.org/users-guide-emb/s-lvm-drbd-as-pv.html Storage layer: disks/hwraid/softwareraid - drbd - LVM - fs this way lvm can trigger the fs with a freezecall before the blocklevel snapshot. We currently migrate our 1 Mailcluster from a netapp storage to multiple storage server with drbd. Our other project the webcluster runs with about 1000 sites (Typo3/Joomla) on a CentOS nfs-server backed with the drbd. The failover time is about 4 seconds and no pending write ist lost.
[Dovecot] 2.0.alpha3 typo patch
--- a/src/lib-storage/mail-storage-service.c
+++ b/src/lib-storage/mail-storage-service.c
@@ -269,7 +269,7 @@
}
}
if (*set-mail_privileged_group != '\0') {
- if (!parse_uid(set-mail_privileged_group,
rset.privileged_gid))
+ if (!parse_gid(set-mail_privileged_group,
rset.privileged_gid))
i_fatal(Unknown mail_gid group: %s, set-mail_gid);
}
if (*set-mail_access_groups != '\0')
[Dovecot] restrictions on folder length?
Greetings all, After migrating a few dozen people to our departmental mailserver, we've run into a problem with one user who makes extensive use of folders and nesting them. I've seen as many as 8 levels. The longest resulting folder name is 113 characters, which results in a total path length of 137 characters (/var/spool/mail/**). Their old mail server handled this fine, but dovecot is choking on it; imapsync reports invalid mailbox name, and he gets the same error clicking on the mailboxes in Thunderbird (they seem to have been created, despite the error messages.) Mail was imported over using imapsync, and did so flawlessly for all the other accounts. Are we running up against a soft (configuration file) or hard (source) limit? Or is this a bug? Thanks! Brett
Re: [Dovecot] restrictions on folder length?
On Wed, 2009-11-25 at 11:59 -0500, Brett Dikeman wrote: Greetings all, After migrating a few dozen people to our departmental mailserver, we've run into a problem with one user who makes extensive use of folders and nesting them. I've seen as many as 8 levels. The longest resulting folder name is 113 characters, which results in a total path length of 137 characters (/var/spool/mail/**). mbox or maildir? What OS? What filesystem? Their old mail server handled this fine, but dovecot is choking on it; imapsync reports invalid mailbox name, and he gets the same error clicking on the mailboxes in Thunderbird (they seem to have been created, despite the error messages.) Try talking IMAP protocol directly: 1 login user pass 2 create mailbox/name Are you sure it's because of the mailbox name length? Maybe there's something else wrong in the name? The hardcoded mailbox length is 512 characters. With Maildir++ it's typically 255 characters because of OS/filesystem limits. signature.asc Description: This is a digitally signed message part
Re: [Dovecot] Acl Groups
On Wed, 2009-11-25 at 09:36 +0200, Dimitrios Karapiperis wrote: I have a corpus of virtual users ( us...@domain.tld , us...@domain.tld, us...@domain.tld,..., us...@domain.tld ... ) authenticated against Active Directory. Is it possible to group some users (virtual) and give appropriate ACLs on a shared imap public folder using an ACL vfile? Yes, with v1.1+. You'll need to have your userdb lookup (or some other way, e.g. with post-login scripting) return a comma-separated acl_groups field. http://wiki.dovecot.org/ACL signature.asc Description: This is a digitally signed message part
Re: [Dovecot] Acl Groups
O/H Timo Sirainen έγραψε: On Wed, 2009-11-25 at 09:36 +0200, Dimitrios Karapiperis wrote: I have a corpus of virtual users ( us...@domain.tld , us...@domain.tld, us...@domain.tld,..., us...@domain.tld ... ) authenticated against Active Directory. Is it possible to group some users (virtual) and give appropriate ACLs on a shared imap public folder using an ACL vfile? Yes, with v1.1+. You'll need to have your userdb lookup (or some other way, e.g. with post-login scripting) return a comma-separated acl_groups field. http://wiki.dovecot.org/ACL Thanks for the reply. //return a comma-separated acl_groups field. What does this mean, sorry I cannot usnderstand it. Is there somewhere some bits of configuration lines, so that it will be more clear. Thanks Dimitrios
Re: [Dovecot] init-script update for v2.0
Pascal Volk user+dove...@localhost.localdomain.org wrote: * Added LSB-compliant info block (for insserv and friends) [...] +# Required-Start:$local_fs $syslog +# Required-Stop: $local_fs $syslog +# Should-Start: $time I think this should be $remote_fs, as according to http://refspecs.freestandards.org/LSB_3.1.0/LSB-Core-generic/LSB-Core-generic/facilname.html and http://wiki.debian.org/LSBInitScripts /usr (where dovecot probably is located) could be mounted from remote. Also I guess $network is a good idea in Required-Start/Stop. Bernhard
Re: [Dovecot] 1.2.7: recs[i]-uid rec- uid
Timo, -Original Message- I'm not really sure why these are happening. I anyway changed them from being assert-crashes to just logged errors. I'm interested to find out what it logs now and if there are any user-visible errors. http://hg.dovecot.org/dovecot-1.2/rev/e47eb506eebd FWIW, I'm seeing this on 1.2.8 as well - just for one user so far. I'll try applying this patch, and report if I see anything else logged. The user who encountered an assert crash prior to this patch now seems to be working properly. I am not aware of any errors presented to the client, but the logs show the following on the first login after application of the patch: Nov 25 07:51:28 oh-popmap1p dovecot: imap: user=youm, rip=x.x.x.x, pid=13702: /home6/youm/Maildir/.Deleted Messages/dovecot-uidlist: uid=24464 exists in index, but not in uidlist Nov 25 07:51:28 oh-popmap1p dovecot: imap: user=youm, rip=x.x.x.x, pid=13702: /home6/youm/Maildir/.Deleted Messages/dovecot-uidlist: uid=24520 exists in index, but not in uidlist Nov 25 07:51:28 oh-popmap1p dovecot: imap: user=youm, rip=x.x.x.x, pid=13702: /home6/youm/Maildir/.Deleted Messages/dovecot-uidlist: uid=24532 exists in index, but not in uidlist I have not seen it repeated since. -Brad
[Dovecot] Release candidates for Sieve v0.1.14 and ManageSieve v0.11.10 for Dovecot v1.2.8
Hello Dovecot users, I am getting closer to new releases for Sieve and ManageSieve for Dovecot v1.2.8. However, the release for Sieve includes a large restructuring of the sources to improve extension handling and to remove global state. That is why I first provide a few pre-releases for you to check first: Sieve http://www.rename-it.nl/dovecot/1.2/dovecot-1.2-sieve-0.1.14pre.tar.gz http://www.rename-it.nl/dovecot/1.2/dovecot-1.2-sieve-0.1.14pre.tar.gz.sig ManageSieve http://www.rename-it.nl/dovecot/1.2/dovecot-1.2-managesieve-0.11.10pre.tar.gz http://www.rename-it.nl/dovecot/1.2/dovecot-1.2-managesieve-0.11.10pre.tar.gz.sig Check the NEWS files in the respective repositories for other changes included in these releases: http://hg.rename-it.nl/dovecot-1.2-sieve/file/216f58aae5c1/NEWS http://hg.rename-it.nl/dovecot-1.2-managesieve/file/a44ca0d89875/NEWS Feel free to test these release candidates and please notify me when you incur any problems. The real releases will follow this weekend. Regards, -- Stephan Bosch step...@rename-it.nl
Re: [Dovecot] init-script update for v2.0
On 11/25/2009 10:17 PM Bernhard Schmidt wrote: Pascal Volk user+dove...@localhost.localdomain.org wrote: +# Required-Start:$local_fs $syslog +# Required-Stop: $local_fs $syslog +# Should-Start: $time I think this should be $remote_fs, as according to http://refspecs.freestandards.org/LSB_3.1.0/LSB-Core-generic/LSB-Core-generic/facilname.html and http://wiki.debian.org/LSBInitScripts /usr (where dovecot probably is located) could be mounted from remote. Also I guess $network is a good idea in Required-Start/Stop. My excuse: When I modified the init script, it was very urgent. ;-) Yes, mails could also be located on a $remote_fs. Many Dovecot installations uses SQL backends from the same host for passdb/userdb lookups. So I'll add postgresql and mysql. BTW: There is an interesting request for Postfix in the Debian BTS, 'Some proposal for init sequence' http://bugs.debian.org/543472 Regards, Pascal -- The trapper recommends today: 5e1f1e55.0932...@localdomain.org # HG changeset patch # User Pascal Volk u...@localhost.localdomain.org # Date 1259210088 0 # Branch HEAD # Node ID 31c202ba1e1f11059562c0e31bff69641d7373d0 # Parent f8151445662effc240b68903ab9bc42a60c04cc9 doc/dovecot-initd.sh extended LSB run-time dependencies diff -r f8151445662e -r 31c202ba1e1f doc/dovecot-initd.sh --- a/doc/dovecot-initd.sh Wed Nov 25 13:19:42 2009 -0500 +++ b/doc/dovecot-initd.sh Thu Nov 26 04:34:48 2009 + @@ -1,8 +1,8 @@ #!/bin/sh ### BEGIN INIT INFO # Provides: dovecot -# Required-Start:$local_fs $syslog -# Required-Stop: $local_fs $syslog +# Required-Start:$local_fs $remote_fs $syslog $network postgresql mysql +# Required-Stop: $local_fs $remote_fs $syslog $network postgresql mysql # Should-Start: $time # Default-Start: 2 3 4 5 # Default-Stop: 0 1 6
Re: [Dovecot] init-script update for v2.0
After repeated reading about {Required,Should}-{Start,Stop} I've
refreshed the patch, it replaces my last patch. Sorry.
Regards,
Pascal
--
The trapper recommends today: deadbeef.0933...@localdomain.org
# HG changeset patch
# User Pascal Volk u...@localhost.localdomain.org
# Date 1259213472 0
# Branch HEAD
# Node ID 2b33f2ef69eb23cb1a496c9ed5223604e43821ff
# Parent f8151445662effc240b68903ab9bc42a60c04cc9
doc/dovecot-initd.sh extended LSB run-time dependencies
diff -r f8151445662e -r 2b33f2ef69eb doc/dovecot-initd.sh
--- a/doc/dovecot-initd.sh Wed Nov 25 13:19:42 2009 -0500
+++ b/doc/dovecot-initd.sh Thu Nov 26 05:31:12 2009 +
@@ -1,9 +1,10 @@
#!/bin/sh
### BEGIN INIT INFO
# Provides: dovecot
-# Required-Start:$local_fs $syslog
-# Required-Stop: $local_fs $syslog
-# Should-Start: $time
+# Required-Start:$local_fs $syslog $network
+# Required-Stop: $local_fs $syslog $network
+# Should-Start: $remote_fs $time postgresql mysql
+# Should-Stop: $remote_fs $time postgresql mysql
# Default-Start: 2 3 4 5
# Default-Stop: 0 1 6
# Short-Description: Dovecot init script
