Duplicate plugins - FTS Xapian
Hi There seems to be 2 plugins doing the same thins - https://github.com/slusarz/dovecot-fts-flatcurve/ - https://github.com/grosjo/fts-xapian/ (mine) Both are in the doc of dovecot https://doc.dovecot.org/configuration_manual/fts/ I am currently working hard to push it to RPM package, and plugin is already approved by ArchLinux and Debian Isn't there double work here ? Thanks JM
Re: lmtp panic with 2.3.16 (runnung ubuntu) and larger mails
Hi, i managed to "resolv" the Issue. i removed the sieve script - after that the issue was gone. Afterwards i replaced it with a new file with the same (!!) content (of course i had a backup on client-side) and it still worked. I created the new file same way as i did with the old (buggy) file - with the sieve-manager-plugin in thunderbird. I have no clue whats going on. regards, Friedhelm Am 30.08.2021 um 07:40 schrieb Aki Tuomi: On 29/08/2021 18:27 Friedhelm Buescher wrote: Hi, when sending larger Mails (> 1MB, for example a jpg attachment), the lmtp crashes: Could you please send gdb bt full? Obtain core, see https://www.dovecot.org/bugreport-mail for information on how you might get that. Then do `gdb /usr/lib/dovecot/lmtp /path/to/core` and issue `bt full`, and send that. Thanks! Aki
Re: Dovecot Director: Preferred backend server
HAProxy is fundamentally different as it operates on connections only, which is not what you usually want on IMAP Servers. Instead you want to route all connections from the same USER to the same server and for this you must have a layer-7 proxy like dovecot director. The implication with something like HAProxy would be that a user may has severall connections from different devices (Desktop mailclinet, Smartphone, Tablet, etc.) and if these (indpendent) connections go to seperate backend servers, it will cause issues. -- https://steven.varco.ch/ > Am 30.08.2021 um 18:56 schrieb dove...@ptld.com: > >> I have a dovecot cluster with directror and two IMAP Servers behind. >> Since they are in geographical different locations I would like to >> have users to go to a specific IMAP backend server (if both are up) >> and only switch to the other if one goes down (failover). >> As to my current knowledge the PassDB extra field „host=„ is not >> suitable in this case as it would never route the client to a >> different backend, even if the „user specific backend“ would be down. >> Is their a way in dovecot to achive this? As far as I searched the >> documentation I could not find any information on this so far. >> If not, it may also help if I could get certain users to „initially" >> go to a specific backend (since director usually routes a client/user >> to the same backend server it initially connects) and therefore it >> would be interesting to know how dovecot director chooses wether a >> user goes to server1 or server2? >> And if a client already gets to server2, how to bring it „back“ to server1? > > > Have you looked into HAProxy? Don't know if it the answer you seek but it > allows for sticky connections and does keep alive checking to stop routing to > a non-responsive server. > https://www.haproxy.org/
Re: Dovecot Director: Preferred backend server
> On 30/08/2021 19:09 Steven Varco wrote: > > > Hi All > > I have a dovecot cluster with directror and two IMAP Servers behind. > > Since they are in geographical different locations I would like to have users > to go to a specific IMAP backend server (if both are up) and only switch to > the other if one goes down (failover). > > As to my current knowledge the PassDB extra field „host=„ is not suitable in > this case as it would never route the client to a different backend, even if > the „user specific backend“ would be down. > > Is their a way in dovecot to achive this? As far as I searched the > documentation I could not find any information on this so far. > > If not, it may also help if I could get certain users to „initially" go to a > specific backend (since director usually routes a client/user to the same > backend server it initially connects) and therefore it would be interesting > to know how dovecot director chooses wether a user goes to server1 or server2? > And if a client already gets to server2, how to bring it „back“ to server1? > > thanks in advance, > Steven > > -- > https://steven.varco.ch/ > https://www.tech-island.com/ Hi! Use dovecot director tag feature. You can match users with tag= to a specific backend@tag. Aki
Re: Dovecot Director: Preferred backend server
> Op 30 aug. 2021 om 18:11 heeft Steven Varco het > volgende geschreven: > > Hi All > > I have a dovecot cluster with directror and two IMAP Servers behind. > > Since they are in geographical different locations I would like to have users > to go to a specific IMAP backend server (if both are up) and only switch to > the other if one goes down (failover). > > As to my current knowledge the PassDB extra field „host=„ is not suitable in > this case as it would never route the client to a different backend, even if > the „user specific backend“ would be down. > > Is their a way in dovecot to achive this? As far as I searched the > documentation I could not find any information on this so far. > > If not, it may also help if I could get certain users to „initially" go to a > specific backend (since director usually routes a client/user to the same > backend server it initially connects) and therefore it would be interesting > to know how dovecot director chooses wether a user goes to server1 or server2? > And if a client already gets to server2, how to bring it „back“ to server1? This is documented. > > thanks in advance, > Steven > > -- > https://steven.varco.ch/ > https://www.tech-island.com/ > >
Re: Dovecot Director: Preferred backend server
Haven’t looked at this use case, so I’m unsure if there’s existing functionality to achieve this. If not: you could set the default vhost count of the failover server to 0, and up it once some health check sets the primary server to down. Sent from mobile > Op 30 aug. 2021 om 18:11 heeft Steven Varco het > volgende geschreven: > > Hi All > > I have a dovecot cluster with directror and two IMAP Servers behind. > > Since they are in geographical different locations I would like to have users > to go to a specific IMAP backend server (if both are up) and only switch to > the other if one goes down (failover). > > As to my current knowledge the PassDB extra field „host=„ is not suitable in > this case as it would never route the client to a different backend, even if > the „user specific backend“ would be down. > > Is their a way in dovecot to achive this? As far as I searched the > documentation I could not find any information on this so far. > > If not, it may also help if I could get certain users to „initially" go to a > specific backend (since director usually routes a client/user to the same > backend server it initially connects) and therefore it would be interesting > to know how dovecot director chooses wether a user goes to server1 or server2? > And if a client already gets to server2, how to bring it „back“ to server1? > > thanks in advance, > Steven > > -- > https://steven.varco.ch/ > https://www.tech-island.com/ > >
Re: Dovecot Director: Preferred backend server
I have a dovecot cluster with directror and two IMAP Servers behind. Since they are in geographical different locations I would like to have users to go to a specific IMAP backend server (if both are up) and only switch to the other if one goes down (failover). As to my current knowledge the PassDB extra field „host=„ is not suitable in this case as it would never route the client to a different backend, even if the „user specific backend“ would be down. Is their a way in dovecot to achive this? As far as I searched the documentation I could not find any information on this so far. If not, it may also help if I could get certain users to „initially" go to a specific backend (since director usually routes a client/user to the same backend server it initially connects) and therefore it would be interesting to know how dovecot director chooses wether a user goes to server1 or server2? And if a client already gets to server2, how to bring it „back“ to server1? Have you looked into HAProxy? Don't know if it the answer you seek but it allows for sticky connections and does keep alive checking to stop routing to a non-responsive server. https://www.haproxy.org/
Dovecot Director: Preferred backend server
Hi All I have a dovecot cluster with directror and two IMAP Servers behind. Since they are in geographical different locations I would like to have users to go to a specific IMAP backend server (if both are up) and only switch to the other if one goes down (failover). As to my current knowledge the PassDB extra field „host=„ is not suitable in this case as it would never route the client to a different backend, even if the „user specific backend“ would be down. Is their a way in dovecot to achive this? As far as I searched the documentation I could not find any information on this so far. If not, it may also help if I could get certain users to „initially" go to a specific backend (since director usually routes a client/user to the same backend server it initially connects) and therefore it would be interesting to know how dovecot director chooses wether a user goes to server1 or server2? And if a client already gets to server2, how to bring it „back“ to server1? thanks in advance, Steven -- https://steven.varco.ch/ https://www.tech-island.com/
Re: Local auth works with dovecot-proxy, remote does not
I think I have found the issue: I'm missing the auth_proxy_self setting: https://doc.dovecot.org/configuration_manual/authentication/proxies/ When I set this to the IP of the server, it seems to perform the authentication without issues for webmail as external clients such as Thunderbird. Greetings, Camilo Sperberg On Tue, Aug 24, 2021 at 2:37 PM Camilo Sperberg wrote: > Hi list! > > I've configured dovecot-proxy to redirect users to another server if their > data is indeed on that other server. > > Webmail (which runs on the same machine) works perfectly fine, but clients > such as Thunderbird and Outlook do not work as intended, I suspect it to be > a problem with the IP that dovecot-proxy sees, but I can't figure out what > is wrong: I've already done a lot of Googling and also tried to change the > login_trusted_networks value, but to no avail. > > I've enabled debug log and here is the relevant part of a call that fails > and another one that succeeds (FYI 10.164.0.3 is the machine that is doing > the proxying and where webmail is located, 10.164.0.20 is the 'node', these > logs come from that node, doveconf -n is also provided in the gist): > https://gist.github.com/unreal4u/64de0f05b6e3b98034cdb0ae52ce1196 > > So as far as I can interpret the logs, in the failure case it is basically > saying it should go to the node, despite it already being on that node: > Aug 24 11:29:07 mail-node-2 dovecot: auth: Debug: client passdb out: > OK#0112#011user=m...@xx.xx > #011host=10.164.0.20#011port=143#011proxy#011pass= > > In the success case, I don't see any mention of a proxy: > Aug 24 11:35:21 mail-node-2 dovecot: auth: Debug: client passdb out: > OK#0116#011user=m...@x.xx > > > What am I missing here? Has this something to do with > authentication-allow-nets or authentication-allow-real-nets ? If so: where > to define it? Is there something else I'm missing? > > Thanks in advance for your help, > Camilo Sperberg >
