Re: [mail-crypt-plugin] How to decrypt mailbox?

On 21.5.2019 8.03, emordin via dovecot wrote: > Hi, > > So I am able to encrypt email using the crypt plugin, but when I try > to access the email by logging in thru mutt or roundcube the email is > still encrypted. > Is the decryption process automatic or do I have to create a custom > program

Re: Dovecot with LDAP Proxy

On 20.5.2019 20.06, Federico Bartolucci via dovecot wrote: > Hello, > > configuring Dovecot with LDAP authentication, adding the parameter in > ther sql config file: > > pass_attrs = \ >     =proxy=y > > I see then backend connections always addressed to localhot port 143: > >

[mail-crypt-plugin] How to decrypt mailbox?

Hi, So I am able to encrypt email using the crypt plugin, but when I try to access the email by logging in thru mutt or roundcube the email is still encrypted. Is the decryption process automatic or do I have to create a custom program with the decrypt.rb code? Thanks. Sent with

Re: Further issues on FTS engine

On 20/05/2019 08:27, Joan Moreau via dovecot wrote: > > Hi, > > Additionally to the long list of problem on the FTS previously > discussed, here a new: > > > WHen I reset the indexes, the indexer-worker seems paralelleizing the > indexing (which is good), however, the number available in "ps aux |

enforcing multiple per-mailbox quotas for shared mailboxes

Hi! I'm trying to get quotas for shared mailboxes set up on my server. It's not working, and I fail to understand why. Documentation for setup of this complexity is rather scarce on the web, and the discussions I found either don't directly apply or terminate with "I got it working" but no

Re: Create a malicious directory

On 20 May 2019, at 06:50, Reto via dovecot wrote: > How is that dangerous? Exactly. -- At night when the bars close down Brandy walks through a silent town And loves a man who's not around

Re: Create a malicious directory

First, you might want to control access to who is allowed to use your server, your email and dovecot. If they are malicious, maybe you want to disallow their access. Second, you might want to make sure that dovecot and doveadm, do not have permissions to run programs outside of a few that are

Dovecot with LDAP Proxy

Hello, configuring Dovecot with LDAP authentication, adding the parameter in ther sql config file: pass_attrs = \     =proxy=y I see then backend connections always addressed to localhot port 143: /user=uten...@domanin.com proxy   lip=127.0.0.1   lport=143   / while I expect that

Re: Create a malicious directory

How is that dangerous? If you pipe output from a directory listing to *any* command you need to sanitize it. That's normal if you have data that can be created by a user. The issue is known since the very beginning of Linux

Re: Dict issue with PostgreSQL for last_login plugin (duplicate key)

‐‐‐ Original Message ‐‐‐ On Sunday, May 19, 2019 10:45 PM, John Fawcett via dovecot wrote: > so basically if this works just as well: > > INSERT INTO last_logins (last_login,username,domain) VALUES > (1558273000,'u...@domain.tld','domain.tld') ON CONFLICT DO UPDATE SET >

Further issues on FTS engine

Hi, Additionally to the long list of problem on the FTS previously discussed, here a new: WHen I reset the indexes, the indexer-worker seems paralelleizing the indexing (which is good), however, the number available in "ps aux | grep dove" shows that it does not move: dovecot 28549 0.0