Re: Thanks for Dovecot

On Tue, 13 Oct 2015, Steve Litt wrote: Thanks for making Dovecot. +1 I just transitioned from Debian Wheezy to Void Linux. It was fairly easy to get Dovecot working on my Void box, and having Dovecot makes all of my email activities easier by doing one thing and doing it right. I'm just

Re: fts solr ignores new mailboxes until fts rescan

Hi, On 2015-10-12 18:39, Giorgio Paolucci wrote: Hello, on my debian wheezy installation, I implemented fts plugin with solr as indexing system. I noticed that if a user creates a new folder, that folder it is ignored by dovecot indexing until a doveadm fts rescan is performed for that user.

Problems sync with mail client MAC and dovecot-2.2.10-4.el7_0.1.el7_0.1.x86_64

Hello, i have installed Centos 7.1.1503 with Dovecot 2.2.10-4.el7_0.1. With Thunderbird all works fine, but when i configure the email client of Mac (Yosemite) with IMAP i can see a error in the log and the client not see the emails: Oct 9 14:31:34 localhost dovecot: imap(xxx@xxx):

Re: Problems sync with mail client MAC and dovecot-2.2.10-4.el7_0.1.el7_0.1.x86_64

On 2015-10-13 09:20, grupo correo wrote: Hello, i have installed Centos 7.1.1503 with Dovecot 2.2.10-4.el7_0.1. With Thunderbird all works fine, but when i configure the email client of Mac (Yosemite) with IMAP i can see a error in the log and the client not see the emails: Oct 9

Re: fts solr ignores new mailboxes until fts rescan

Hi Christian, may be the issue is related to this other post: http://dovecot.org/pipermail/dovecot/2015-September/102094.html Anyway, what I can tell you is that for every  user account,  for every folders created after the last doveadm fts rescan for that user, dovecot does not invoke indexer.

Re: fts solr ignores new mailboxes until fts rescan

On 2015-10-13 12:51, Giorgio Paolucci wrote: Hi Christian, may be the issue is related to this other post: http://dovecot.org/pipermail/dovecot/2015-September/102094.html Looks like the same problem and Timo wrote 2.2.19 should fix this ->

Dovecot - Postfix with HAproxy

Hi Everyone, I wouldlike to set up a postfix-dovecot with HA using HAproxy but im facing issues. I've followed this documentation : http://wiki2.dovecot.org/HAProxy (pour dovecot) http://blog.haproxy.com/2012/06/30/efficient-smtp-relay-infrastructure-with-postfix-and-load-balancers/

Re: TLS communication director -> backend with X.509 cert checks?

On 13 Oct 2015, at 22:18, Heiko Schlittermann wrote: > > Timo Sirainen (Di 13 Okt 2015 21:02:59 CEST): > … >>> On connection setup from a client the director connects to the >>> selected backend. But it seems (not checked in the source yet), >>> that for SSL

Re: TLS communication director -> backend with X.509 cert checks?

Timo Sirainen (Di 13 Okt 2015 21:36:40 CEST): … > > I see: > > > >a) pass the host *names* to the director too, for CN verification > > purpose > > > > May be in struct mail_host could be a field for the original > > hostname we used to obtain the adress(es)?

Re: TLS communication director -> backend with X.509 cert checks?

Timo Sirainen (Di 13 Okt 2015 21:02:59 CEST): > > the IP address the director connects to. > > Right. The hostnames are lost immediately at director startup. I've never > really thought about needing this functionality for director, since they're > usually in the same trusted

Dualstack IPv4/IPv6 setup with directors

Hi, still using 2.2.9, I've two directors, and these directors use both IPv4/IPv6 addresses. `host directors.` returns one A and AAA for each of the two directors: directors. has address 149.x.y.96 (director1) directors. has address 149.x.y.97 (director2)

Storage Design (Regligious War, Whatever)

We've been running dovecot director setup using MAILDIR++ spools on NFS served by 4 (aging) Netapp clustered filers and are considering modernizing our storage. There's nothing particularly wrong with the existing storage except the age, density and power consumption don't compare well when

Re: Dualstack IPv4/IPv6 setup with directors

On 13 Oct 2015, at 22:31, Heiko Schlittermann wrote: > > Hi, > > still using 2.2.9, I've two directors, and these directors > use both IPv4/IPv6 addresses. > > `host directors.` returns one A and AAA for each > of the two directors: > >directors. has address

Thanks for Dovecot

Hi all, Thanks for making Dovecot. I just transitioned from Debian Wheezy to Void Linux. It was fairly easy to get Dovecot working on my Void box, and having Dovecot makes all of my email activities easier by doing one thing and doing it right. Thank you for such great software. SteveT

Re: Indexing fails with .. FIELDS_INDEX_EXTENSION).c_str() )' failed

On 13 Oct 2015, at 23:25, Akash wrote: > > Hi, > > Mailing list archives suggest that this problem has been fixed in the > older versions itself but I am getting the error still while trying to > doveadm index a large folder of emails. Sometimes it throws error > after

Re: TLS communication director -> backend with X.509 cert checks?

Timo Sirainen (Di 13 Okt 2015 21:02:59 CEST): … > > On connection setup from a client the director connects to the > > selected backend. But it seems (not checked in the source yet), > > that for SSL certificate verification the director doesn't know the > > original host name

Re: TLS communication director -> backend with X.509 cert checks?

> On 13 Oct 2015, at 22:21, Heiko Schlittermann wrote: > > Timo Sirainen (Di 13 Okt 2015 21:02:59 CEST): >>> the IP address the director connects to. >> >> Right. The hostnames are lost immediately at director startup. I've never >> really thought about

Re: Dualstack IPv4/IPv6 setup with directors

Timo Sirainen (Di 13 Okt 2015 21:42:41 CEST): … > > Oct 13 21:23:29 director1 dovecot: director: Error: > > director(149.x.y.97:9090/out): connect() failed: Connection refused > > Oct 13 21:23:29 director1 dovecot: director: Warning: net_connect_ip(): > > ip->family !=

Re: Dovecot - Postfix with HAproxy

Op 10/13/2015 om 5:15 PM schreef Michael JOIGNY: (For some reason Thunderbird messes up this e-mail). You could try to do pre-login rawlog to see what HAProxy is sending to Dovecot. http://wiki2.dovecot.org/Debugging/Rawlog Regards, Stephan.

Indexing fails with .. FIELDS_INDEX_EXTENSION).c_str() )' failed

Hi, Mailing list archives suggest that this problem has been fixed in the older versions itself but I am getting the error still while trying to doveadm index a large folder of emails. Sometimes it throws error after 3, something 4, the latest it gave up after 111000. But it just never

Re: dovecot as proxy and verification of the backends certificate

Timo Sirainen (Di 13 Okt 2015 20:27:25 CEST): … > ># followed by the matching CRL(s). (e.g. ssl_ca = ># ssl_ca = > >ssl_ca = > > > Bug or feature? Mainly I'm asking because the comments do not indicate > > that I should have used ssl_ca for this type of operation

Re: Dovecot auth-ldap ignores tls_* settings when using ldaps://

On 08 Oct 2015, at 22:46, Heiko Schlittermann wrote: > > Hi, > > I'm using dovecot 2.2.9 (but after checking src/auth/db-ldap.c in 2.2.13 > there seems to be the same bug/feature). > > The userdb and passdb use LDAP. All further configuration is done in >

Re: Dovecot auth-ldap ignores tls_* settings when using ldaps://

Timo Sirainen (Di 13 Okt 2015 20:19:54 CEST): .. > > --- dovecot-2.2.9/src/auth/db-ldap.c2013-11-24 14:37:39.0 +0100 > > +++ dovecot-2.2.9.hs12/src/auth/db-ldap.c 2015-10-08 > > 21:24:47.051446465 +0200 > > @@ -1043,7 +1043,7 @@ > > > > static void

Re: doveadm index assertion failed

On 05 Oct 2015, at 22:05, Nick Rosier wrote: > > Hi, > > one of my mailboxes returns following error when I run doveadm index on it: > > Panic: file charset-iconv.c: line 85 (charset_to_utf8_try): assertion failed: > (srcleft <= CHARSET_MAX_PENDING_BUF_SIZE) > > OS:

Re: TLS communication director -> backend with X.509 cert checks?

On 13 Oct 2015, at 21:44, Heiko Schlittermann wrote: > > Hello, > > using Dovecot 2.2.9 and a setup with directors and backends. > The communication between directors and backends needs to be TLS > secured. > > The director config contains a list of hostnames for the

Re: bug report: dovecot-imapd core dump

On 10 Oct 2015, at 20:34, Tamas Papp wrote: > > Hi, > > Since I did not get any specific suggestions about this bug, I am > attaching another backtrace. Any suggestions for workarounds etc would > be appreciated -- should I regenerate the index? Or install a dovecot > from the

TLS communication director -> backend with X.509 cert checks?

Hello, using Dovecot 2.2.9 and a setup with directors and backends. The communication between directors and backends needs to be TLS secured. The director config contains a list of hostnames for the backends. (implicit list because of multiple A/ records for a single hostname or explicit

Re: dovecot as proxy and verification of the backends certificate

On 11 Oct 2015, at 20:04, Heiko Schlittermann wrote: > > Hello, > > I'm using a dovecot as proxy, connecting to one or more backends. > The backends use X.509 certificates. > > The proxy's passdb returns > >extra fields: >user=foo >proxy >host=backend1.

Re: Multiple core solr support

> On 11 Oct 2015, at 08:42, Daniel Miller wrote: > > Is it possible to use variables, such as domain or username, in the plugin > url declaration? This would allow using multiple cores to separate the > stored indexes. So when my own giant mailbox gets corrupt...I don't

Re: Unknown cache fields?

On 05 Oct 2015, at 17:43, Larry Rosenman wrote: > > I assume this is expected, but just checking. I do NOT use POP3. > > Oct 5 09:41:20 thebighonker dovecot: indexer-worker(mrm): Debug: Ignoring > unknown cache field: pop3.order > Oct 5 09:41:20 thebighonker dovecot:

Re: Thanks for Dovecot

On 10/13/2015 04:00 PM, Steve Litt wrote: Hi all, Thanks for making Dovecot. I just transitioned from Debian Wheezy to Void Linux. It was fairly easy to get Dovecot working on my Void box, and having Dovecot makes all of my email activities easier by doing one thing and doing it right. Thank

Re: Thanks for Dovecot

Dave McGuire writes: > On 10/13/2015 05:04 PM, Gedalya wrote: >>> Thanks for making Dovecot. >>> >>> I just transitioned from Debian Wheezy to Void Linux. It was fairly >>> easy to get Dovecot working on my Void box, and having Dovecot makes >>> all of my email activities

Re: TLS communication director -> backend with X.509 cert checks?

Timo Sirainen (Di 13 Okt 2015 23:49:20 CEST): … > > Proxying in general does check that hostname matches the SSL certificate, > because both the hostname and IP address are sent to login process. So it > should work in a way that host= and hostip= is sent. I thought > my patch

Re: iterate users with passwd-file passdb?

Eric Abrahamsen writes: Simply: Is it possible to iterate over users if I'm using the passwd-file passdb driver? Do I need a SQL-based driver if I want to iterate? What do you mean by "iterate"? If you mean whether you can look up a password entry in a multi-entry file, then yes, definitely.

Re: iterate users with passwd-file passdb?

Joseph Tam writes: > Eric Abrahamsen writes: > >> Simply: Is it possible to iterate over users if I'm using the >> passwd-file passdb driver? Do I need a SQL-based driver if I want to >> iterate? > > What do you mean by "iterate"? If you mean whether you can look up a >

Re: TLS communication director -> backend with X.509 cert checks?

Hi Timo, Heiko Schlittermann (Di 13 Okt 2015 22:33:23 CEST): > > Does the attached patch work? Compiles, but untested. > I'm about to test it. It seems to update the struct mail_host, but it looks as if the data in mail_host do not propagate down to login_proxy_new().

Re: iterate users with passwd-file passdb?

Eric Abrahamsen writes: Simply: Is it possible to iterate over users if I'm using the passwd-file passdb driver? Do I need a SQL-based driver if I want to iterate? What do you mean by "iterate"? If you mean whether you can look up a password entry in a multi-entry

Re: TLS communication director -> backend with X.509 cert checks?

On 14 Oct 2015, at 00:34, Heiko Schlittermann wrote: > > Hi Timo, > > Heiko Schlittermann (Di 13 Okt 2015 22:33:23 CEST): >>> Does the attached patch work? Compiles, but untested. >> I'm about to test it. > > It seems to update the struct

Re: iterate users with passwd-file passdb?

Timo Sirainen writes: > On 14 Oct 2015, at 00:01, Eric Abrahamsen wrote: >> >> Joseph Tam writes: >> >>> Eric Abrahamsen writes: >>> Simply: Is it possible to iterate over users if I'm using the passwd-file passdb driver?

Re: Thanks for Dovecot

On 10/13/2015 05:04 PM, Gedalya wrote: >> Thanks for making Dovecot. >> >> I just transitioned from Debian Wheezy to Void Linux. It was fairly >> easy to get Dovecot working on my Void box, and having Dovecot makes >> all of my email activities easier by doing one thing and doing it right. >> >>

Re: iterate users with passwd-file passdb?

On 14 Oct 2015, at 00:01, Eric Abrahamsen wrote: > > Joseph Tam writes: > >> Eric Abrahamsen writes: >> >>> Simply: Is it possible to iterate over users if I'm using the >>> passwd-file passdb driver? Do I need a SQL-based driver if I want to >>>

Re: Thanks for Dovecot

> Thanks for making Dovecot. > > I just transitioned from Debian Wheezy to Void Linux. It was fairly > easy to get Dovecot working on my Void box, and having Dovecot makes > all of my email activities easier by doing one thing and doing it right. > > Thank you for such great software. Same here.

Re: TLS communication director -> backend with X.509 cert checks?

Heiko Schlittermann (Mi 14 Okt 2015 00:10:50 CEST): > Timo Sirainen (Di 13 Okt 2015 23:49:20 CEST): > … > > > > Proxying in general does check that hostname matches the SSL certificate, > > because both the hostname and IP address are sent to login process.

Re: Indexing fails with .. FIELDS_INDEX_EXTENSION).c_str() )' failed

On Wed, 14 Oct 2015 07:28:42 +1100 Timo Sirainen wrote > Looks like a bug in clucene library. I don't know if there's anything that > can be done about it on Dovecot side. I recommend switching to fts-solr. Either that or fts-elasticsearch[1] Regards, Tim [1]

Re: TLS communication director -> backend with X.509 cert checks?

Heiko Schlittermann (Mi 14 Okt 2015 00:46:11 CEST): … > > And if I add -D to the director service, I can see "Debug: request > refreshed timeout to …", > but never I see "Debug: request added". And from what I > understand this would be the place where the mail_host