Re: [Dovecot] Dovecot LDA LDAP lookups on samba4 server ends very often in timeouts (Christian Wiese)
Dear Christian thank you very much - you got it at the very first shot: modified /etc/ openldap/ldap.conf adding REFERRALS off en everything works without issues now many thanks Marco Carcano
[Dovecot] v2.2.beta2 released
http://dovecot.org/releases/2.2/beta/dovecot-2.2.beta2.tar.gz http://dovecot.org/releases/2.2/beta/dovecot-2.2.beta2.tar.gz.sig A ton of fixes since beta1. Especially the new dsync and the replication server related to that should really work now. It also works correctly now for shared mailboxes with private \Seen flags. And the replication server uses incremental syncing after the initial full sync, so it should be pretty efficient also. I've only two things left to do before v2.2.rc1: 1. Implement dsync to work via TCP and TCP+SSL sockets. This is pretty easy to do actually, since it can use the existing doveadm-server to start up. 2. Read up all the pending mails from Dovecot mailing list and fix up the reported issues. Actually I guess most of those are for v2.1, but still I should get around to it. :) There shouldn't be any major bugs left, so I'm expecting v2.2.rc1 out in maybe a week or so, hopefully followed by the final v2.2.0 soon afterwards. Please test and report any bugs found!
Re: [Dovecot] v2.2.beta2 released
I've been running 2.2beta1 in production since it got out and I haven't had any issues. However, my setup is simply IMAP/POP3 without any complicated configurations. This is on FreeBSD 8.3-STABLE with about 100 users. I've just updated to 2.2b2... On 21 February 2013 18:34, Timo Sirainen t...@iki.fi wrote: http://dovecot.org/releases/2.2/beta/dovecot-2.2.beta2.tar.gz http://dovecot.org/releases/2.2/beta/dovecot-2.2.beta2.tar.gz.sig A ton of fixes since beta1. Especially the new dsync and the replication server related to that should really work now. It also works correctly now for shared mailboxes with private \Seen flags. And the replication server uses incremental syncing after the initial full sync, so it should be pretty efficient also. I've only two things left to do before v2.2.rc1: 1. Implement dsync to work via TCP and TCP+SSL sockets. This is pretty easy to do actually, since it can use the existing doveadm-server to start up. 2. Read up all the pending mails from Dovecot mailing list and fix up the reported issues. Actually I guess most of those are for v2.1, but still I should get around to it. :) There shouldn't be any major bugs left, so I'm expecting v2.2.rc1 out in maybe a week or so, hopefully followed by the final v2.2.0 soon afterwards. Please test and report any bugs found! -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254733744121/+254722743223 _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ I can't hear you -- I'm using the scrambler.
[Dovecot] Public folders and dsync replication Dovecot v2.1.7
Dear all
I have a few public folders setup and working fine, and one such public
folder is 'Public/General'. I'm trying to sort dsync replication out to
another server and notice that the system log is full of error messages
similar to:
dovecot: doveadm: Error: dsync-remote(username: Error: Can't update
subscription Pu
blic/General: Invalid mailbox name
The replication setup is basically as per the v2 wiki.
It seems that when a mail client subscribes to a public folder, the
folder name is put into '~/Maildir/subscriptions' and this seems to be
the cause of the error during replication. The mails are not
synchronised to the other server.
Public namespace is:
namespace {
type = public
separator = /
prefix = Public/
location = maildir:/home/shared/public
subscriptions = no
list = yes
}
Hopefully somebody can send the clue bus over?
Steve
--
Steve Brown
Operations Manager Connection Services Ltd
+44 (0)1189 711 765 Direct +44 (0)870 751 7571 Fax
www.connectionservices.com www.hotspot-directory.com
Re: [Dovecot] Public folders and dsync replication Dovecot v2.1.7
Am 21.02.2013 19:19, schrieb Steve Brown:
Dear all
I have a few public folders setup and working fine, and one such public
folder is 'Public/General'. I'm trying to sort dsync replication out to
another server and notice that the system log is full of error messages
similar to:
dovecot: doveadm: Error: dsync-remote(username: Error: Can't update
subscription Pu
blic/General: Invalid mailbox name
The replication setup is basically as per the v2 wiki.
It seems that when a mail client subscribes to a public folder, the
folder name is put into '~/Maildir/subscriptions' and this seems to be
the cause of the error during replication. The mails are not
synchronised to the other server.
Public namespace is:
namespace {
type = public
separator = /
prefix = Public/
location = maildir:/home/shared/public
subscriptions = no
list = yes
}
Hopefully somebody can send the clue bus over?
Steve
v2.1.7 is not recent have you tried 2.1.15 ?
Best Regards
MfG Robert Schetterer
--
[*] sys4 AG
http://sys4.de, +49 (89) 30 90 46 64
Franziskanerstraße 15, 81669 München
Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263
Vorstand: Patrick Ben Koetter, Axel von der Ohe, Marc Schiffbauer
Aufsichtsratsvorsitzender: Joerg Heidrich
Re: [Dovecot] Public folders and dsync replication Dovecot v2.1.7
On 21.2.2013, at 20.19, Steve Brown steve.br...@connectionservices.com wrote: I have a few public folders setup and working fine, and one such public folder is 'Public/General'. I'm trying to sort dsync replication out to another server and notice that the system log is full of error messages similar to: dovecot: doveadm: Error: dsync-remote(username: Error: Can't update subscription Pu blic/General: Invalid mailbox name I don't think v2.1 replication can handle public folders. Use v2.2.
Re: [Dovecot] v2.2.beta2 released
On 21.02.2013, at 16:34, Timo Sirainen t...@iki.fi wrote: A ton of fixes since beta1. Especially the new dsync and the replication server related to that should really work now. I am running v2.2beta1 for almost a week now (handful of users, ~1000 mails/day). And yes, I can confirm that replication works ... Please test and report any bugs found! ... there is only a feature request left: I did run a lot of stress tests as mentioned before (simultaneously injected local mail). Whenever I do run those tests with a delay of 1 second between every injection, I do observe, that not all mails injected become visible in my MUAs (Mail.app and Roundcube), immediately. All get new mail functionality or MUA restarts fails to fetch those missing messages from both servers. But, if I do restart any one of both dovecot servers involved, those remaining missing messages are fetched instantaneously. It seems to me, as if those missing messages were kept in the replicator queue and not delivered to the partner server, and as if that queue became flushed during restart. After restart all injected and replicated messages are accessible by the MUAs. I never waited longer then 10 minutes before restarting dovecot, thus I do not know if I didn't wait long enough. But I can say that an additionally injected local mail shows up in both MUAs but doesn't become replicated. Thus, if I am not mistaken that something like a flushing really takes place, I wonder if there is a doveadm flush replicator-queue functionality is available already (that I might have over-seen), and if not, would that be a big deal to implement? JFTR and with kind regards, Michael
Re: [Dovecot] v2.2.beta2 released
On 21.2.2013, at 22.12, Michael Grimm trash...@odo.in-berlin.de wrote: I am running v2.2beta1 for almost a week now (handful of users, ~1000 mails/day). And yes, I can confirm that replication works ... Please test and report any bugs found! ... there is only a feature request left: I did run a lot of stress tests as mentioned before (simultaneously injected local mail). Whenever I do run those tests with a delay of 1 second between every injection, I do observe, that not all mails injected become visible in my MUAs (Mail.app and Roundcube), immediately. All get new mail functionality or MUA restarts fails to fetch those missing messages from both servers. But, if I do restart any one of both dovecot servers involved, those remaining missing messages are fetched instantaneously. It seems to me, as if those missing messages were kept in the replicator queue and not delivered to the partner server, and as if that queue became flushed during restart. After restart all injected and replicated messages are accessible by the MUAs. Possibly a bug, see if it still happens with beta2. I never waited longer then 10 minutes before restarting dovecot, thus I do not know if I didn't wait long enough. But I can say that an additionally injected local mail shows up in both MUAs but doesn't become replicated. Thus, if I am not mistaken that something like a flushing really takes place, I wonder if there is a doveadm flush replicator-queue functionality is available already (that I might have over-seen), and if not, would that be a big deal to implement? Well, you can sync a user with e.g.: doveadm sync -d -l 30 -u user@domain or with -A parameter to sync everyone. And with -f parameter to do a full sync if needed. The -l 30 parameter adds locking so two dsyncs won't run at the same time for the user.
Re: [Dovecot] v2.2.beta2 released
On 21.02.2013, at 21:17, Timo Sirainen t...@iki.fi wrote: On 21.2.2013, at 22.12, Michael Grimm trash...@odo.in-berlin.de wrote: But, if I do restart any one of both dovecot servers involved, those remaining missing messages are fetched instantaneously. Possibly a bug, see if it still happens with beta2. Sorry, I did forget to mention that this is happening with v2.2.beta2 (3fb9a8bc35aa) as well. Thus, if I am not mistaken that something like a flushing really takes place, I wonder if there is a doveadm flush replicator-queue functionality is available already (that I might have over-seen), and if not, would that be a big deal to implement? Well, you can sync a user with e.g.: doveadm sync -d -l 30 -u user@domain or with -A parameter to sync everyone. And with -f parameter to do a full sync if needed. I needed to add that -f for full sync, and that flushed the queue. Thanks for pointing me to that. I do have a replication_full_sync_interval = 1 hours set. Does that setting equals to the same like running a doveadm dsync ... every other hour? Regards, Michael
[Dovecot] Problem with managesieve proxy
Hi folks, I'm setting up a new dovecot email service and have a proxy server running in front of it to facilitate migrating users from my very old UW-IMAP-based mail server to the new one. I have a mysql proxy table that directs inbound IMAP and LMTP connections to the correct server, works great. Managesieve connections are not working through the proxy using either with the sieverules plugin for RoundCube or the Sieve plugin for Thunderbird. If I point them directly at the actual dovecot server everything works fine, so I must have something wrong in my proxy setup. This is what I get in the maillogs when I try to connect to the managesieve proxy: PROXY machine: Feb 21 16:16:38 sortie dovecot: managesieve-login: Error: proxy: Remote x.y.z.110:4190 disconnected: Connection closed (state=0, duration=0s): user=brown, method=PLAIN, rip=x.y.z.83, lip=x.y.z.109, TLS, session=0jUal0LWswCYAxZT Feb 21 16:16:38 sortie dovecot: managesieve-login: Disconnected (internal failure, 1 succesful auths): user=brown, method=PLAIN, rip=x.y.z.83, lip=x.y.z.109, TLS, session=0jUal0LWswCYAxZT SERVER machine: Feb 21 16:16:38 postie dovecot: managesieve-login: Disconnected: Too many invalid commands. (no auth attempts in 0 secs): user=, rip=x.y.z.109, lip=x.y.z.110, session=REgal0LWnQCYAxZt Output of a 'tcpdump -A' is attached as well if needed. x.y.z.83 - Roundcube webmail server x.y.z.109 - PROXY x.y.z.110 - SERVER If I turn off TLS all-around I get an error in the roundcube log that says: [20-Feb-2013 23:02:27] No supported authentication method found. The server supports these methods: , but we want to use: PLAIN (): [20-Feb-2013 23:02:27] Not currently in AUTHORISATION state (1): I am using Pigeonhole 0.3.3 on both proxy and server. Dovecot configurations for the proxy and server are attached below. Here are the SQL files referenced in the proxy configs. Long lines broke for readability. /etc/dovecot/dovecot-sql.conf.ext driver = mysql connect = host=localhost dbname=dovecot user=dovecot password=XXX password_query = SELECT NULL AS password, 'any-cert' as 'ssl', \ 'Y' as nopassword, host, user as destuser, \ 'Y' AS proxy \ FROM proxy WHERE user = '%u' /etc/dovecot/dovecot-sql-lmtp.conf.ext driver = mysql connect = host=localhost dbname=dovecot user=dovecot password=XXX password_query = SELECT NULL AS password, 'any-cert' as 'ssl', \ 'Y' as nopassword, host, user as destuser, 'Y' AS proxy \ FROM proxy WHERE user = '%n' The proxy DB table looks like this: - -- Table structure for table `proxy` -- CREATE TABLE IF NOT EXISTS `proxy` ( `id` int(11) NOT NULL AUTO_INCREMENT, `user` varchar(255) NOT NULL, `email` varchar(64) NOT NULL, `host` varchar(16) DEFAULT NULL, PRIMARY KEY (`id`), UNIQUE KEY `user_index` (`user`) ) ENGINE=MyISAM DEFAULT CHARSET=latin1 AUTO_INCREMENT=379 ; -- -- Dumping data for table `proxy` -- INSERT INTO `proxy` (`id`, `user`, `email`, `host`) VALUES (1, 'brown', '', 'x.y.z.110'), (2, 'fizgig', '', 'x.r.z.15'), 110 is the new dovecot IMAP server, 15 is the old UW-IMAP server. Any advice on getting managesieve proxy running would be greatly appreciated. Thanks, --[Lance] -- GPG Fingerprint: 409B A409 A38D 92BF 15D9 6EEE 9A82 F2AC 69AC 07B9 CACert.org Assurer 16:24:14.079073 IP x.y.z.83.42168 x.y.z.109.sieve: Flags [S], seq 4273974283, win 14600, options [mss 1460,sackOK,TS val 533787509 ecr 0,nop,wscale 5], length 0 E.._~@.@.~w...S...m...^..9.?.. ...u 16:24:14.079103 IP x.y.z.109.sieve x.y.z.83.42168: Flags [S.], seq 165429520, ack 4273974284, win 14480, options [mss 1460,sackOK,TS val 517181158 ecr 533787509,nop,wscale 5], length 0 E@.@..m...S.^...A...8.F.. ...u 16:24:14.079206 IP x.y.z.83.42168 x.y.z.109.sieve: Flags [.], ack 1, win 457, options [nop,nop,TS val 533787509 ecr 517181158], length 0 E..4_.@.@.~~...S...m...^.A..]. ...u 16:24:14.084288 IP x.y.z.109.sieve x.y.z.83.42168: Flags [P.], seq 1:316, ack 1, win 453, options [nop,nop,TS val 517181163 ecr 533787509], length 315 E..o..@.@..m...S.^...A.^(. ...uIMPLEMENTATION Dovecot Pigeonhole SIEVE fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date ihave NOTIFY mailto SASL STARTTLS VERSION 1.0 OK Dovecot ready. 16:24:14.084420 IP x.y.z.83.42168 x.y.z.109.sieve: Flags [.], ack 316, win 490, options [nop,nop,TS val 533787514 ecr 517181163], length 0 E..4_.@.@.~}...S...m...^.BL... ...z 16:24:14.084676 IP x.y.z.83.42168 x.y.z.109.sieve: Flags [P.], seq 1:13, ack 316, win 490, options [nop,nop,TS val 533787514 ecr 517181163], length 12 E..@_.@.@.~p...S...m...^.BL'k. ...zCAPABILITY 16:24:14.084680 IP x.y.z.109.sieve
Re: [Dovecot] v2.2.beta2 released
Hello Michael, Can you post to the list your working configurations for dovecot? I've been fighting with the dsync replication a while ago and was super buggy so I've put that project on ice. If now it finally works I would like to get it moving again. Best, Andrei On 21.02.2013, at 21:17, Timo Sirainen t...@iki.fi wrote: On 21.2.2013, at 22.12, Michael Grimm trash...@odo.in-berlin.de wrote: But, if I do restart any one of both dovecot servers involved, those remaining missing messages are fetched instantaneously. Possibly a bug, see if it still happens with beta2. Sorry, I did forget to mention that this is happening with v2.2.beta2 (3fb9a8bc35aa) as well. Thus, if I am not mistaken that something like a flushing really takes place, I wonder if there is a doveadm flush replicator-queue functionality is available already (that I might have over-seen), and if not, would that be a big deal to implement? Well, you can sync a user with e.g.: doveadm sync -d -l 30 -u user@domain or with -A parameter to sync everyone. And with -f parameter to do a full sync if needed. I needed to add that -f for full sync, and that flushed the queue. Thanks for pointing me to that. I do have a replication_full_sync_interval = 1 hours set. Does that setting equals to the same like running a doveadm dsync ... every other hour? Regards, Michael !DSPAM:512687b9301841449136444!
[Dovecot] Dovecot list archives not updating
The February archive indexes of this list haven't been updating since Feb 8. The text file at http://dovecot.org/pipermail/dovecot/2013-February.txt appears to be up to date with all posts, but the index pages at http://dovecot.org/pipermail/dovecot/2013-February/thread.html, http://dovecot.org/pipermail/dovecot/2013-February/subject.html, http://dovecot.org/pipermail/dovecot/2013-February/author.html and http://dovecot.org/pipermail/dovecot/2013-February/date.html have no posts after the one at http://dovecot.org/pipermail/dovecot/2013-February/071213.html from Fri Feb 8 16:31:49 EET 2013. Subsequent posts appear to not have individual HTML pages either as URLs http://dovecot.org/pipermail/dovecot/2013-February/071214.html and http://dovecot.org/pipermail/dovecot/2013-February/071215.html return 404 errors. I suspect there is a permissions issue starting soon after Fri Feb 8 16:31:49 EET 2013 and that Mailman's error log has lots of tracebacks from this. If that is the case, the messages were probably all shunted and running Mailman's bin/unshunt after fixing the underlying issue and also making sure that any messages older than Fri Feb 8 16:31:49 EET 2013 in Mailman's 'shunt' queue that should not also be reprocessed are removed. -- Mark Sapiro m...@msapiro.netThe highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan
Re: [Dovecot] v2.2.beta2 released
On 2/21/2013 8:43 AM, Odhiambo Washington wrote: I've been running 2.2beta1 in production since it got out and I haven't had any issues. However, my setup is simply IMAP/POP3 without any complicated configurations. This is on FreeBSD 8.3-STABLE with about 100 users. I've just updated to 2.2b2... The same applies to me except it's CentOS 5 and I have only a half dozen POP3 users and a couple of IMAP users with a total of about 2 dozen mailboxes. No problems with 2.2beta2 so far. -- Mark Sapiro m...@msapiro.netThe highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan
[Dovecot] patch to fix binary attachment indexing
FTS indexing of binary attachments is broken in dovecot-2.1.15: the binary data which fts_build_mail_real() sends to fts_build_body_block() (which sends it to fts_backend_update_build_more()) is garbled. This patch ungarbles it but I’m not positive it’s the best fix. --- dovecot-2.1.15/src/plugins/fts/fts-build-mail.c 2012-11-27 02:07:27.0 -0600 +++ dovecot/src/plugins/fts/fts-build-mail.c2013-02-21 19:48:15.0 -0600 @@ -178,7 +178,8 @@ *binary_body_r = TRUE; key.type = FTS_BACKEND_BUILD_KEY_BODY_PART_BINARY; } - if (ctx-body_parser == NULL) + if (ctx-body_parser == NULL + key.type != FTS_BACKEND_BUILD_KEY_BODY_PART_BINARY) ctx-body_parser = fts_parser_text_init(); key.body_content_type = content_type; key.body_content_disposition = ctx-content_disposition;
[Dovecot] SOLVED Re: Problem with managesieve proxy
I found it. I needed to tell the sieve service to specify STARTTLS instead of SSL when connecting to the backend server in the SQL statement: /etc/dovecot/dovecot-sql-lmtp.conf.ext password_query = SELECT NULL AS password, \ 'any-cert' as 'starttls', \ ... instead of ... 'any-cert' as 'ssl', \ ... Once I got that right everything fell into place. --[Lance] -- GPG Fingerprint: 409B A409 A38D 92BF 15D9 6EEE 9A82 F2AC 69AC 07B9 CACert.org Assurer
Re: [Dovecot] v2.2.beta2 released
Hi --
On 2013-02-21 Michescu Andrei wrote:
Can you post to the list your working configurations for dovecot?
(This is based on
http://dovecot.org/list/dovecot/2012-March/064513.html)
My design:
single user vmail to run dsync over ssh
(one may use root instead)
Thus, my prerequisites are:
create vmail user accounts at both servers (example: mx1 and
mx2)
exchange ssh-keys for ssh authentication between both servers
involved
My relevant parts from dovecot.conf, identical for both servers:
## --- DSYNC REPLICATION
# ssh command line used in dsync replication
# added:
# -p xxx (ssh port)
# -o mail_plugins=(omit mail_log plugins for
dsync)
#
dsync_remote_cmd = ssh -p 44488 -l%{login} %{host} doveadm
-omail_plugins= dsync-server -u%u -n%{namespace}
# aggregator, replicator, doveadm, and config needed, and
dsync_remote_cmd (see above)
#
service aggregator {
# give enough permissions for mail processes
#
fifo_listener replication-notify-fifo {
user = vmail
mode = 0600
}
unix_listener replication-notify {
user = vmail
mode = 0600
}
}
service replicator {
# start replication at startup
#
process_min_avail = 1
}
service doveadm {
# if you're using a single virtual user, set this to
start ssh as vmail (not root)
#
user = vmail
}
service config {
# needed to grant access to /var/run/dovecot/config for
service doveadm
#
unix_listener config {
user = vmail
}
}
The following part is for server mx1, only:
---
# dsync replication plugin
#
plugin {
# this host replicates to remote host
#
mail_replica = remote:vm...@mx2.fqdn
# run full synchronization mode every other hour
#
replication_full_sync_interval = 1 hours
}
The following part is for server mx2, only:
---
# dsync replication plugin
#
plugin {
# this host replicates to remote host
#
mail_replica = remote:vm...@mx1.fqdn
# run full synchronization mode every other hour
#
replication_full_sync_interval = 1 hours
}
HTH,
Michael
Re: [Dovecot] Crash in dsync [dovecot 2.1.7]
On 22.2.2013, at 0.54, Joe Beaubien joe.beaub...@gmail.com wrote: dsync(document): Error: Mailbox INBOX/Julie: Corrupted index, uidvalidity=0 dsync(document): Warning: mdbox /backup_hdd/current/emails/document/storage: rebuilding indexes dsync(document): Panic: file mdbox-storage-rebuild.c: line 66 (mdbox_storage_rebuild_init): assertion failed: (!storage-rebuilding_storage) Fixed: http://hg.dovecot.org/dovecot-2.1/rev/9cb64709dd8c
