Re: Dovecot Submission Proxy Auth

Hi, Just found out that Postfix does not implement/support the AUTH=sender parameter. So, back to Dovecot, can we use variables in the submission_relay_user = submission_relay_password = then Dovecot will forward the username and password information of the current user to the Postfix submi

RE: Enable compression only for namespace with mdbox storage

Like mentioned here https://www.dovecot.org/pipermail/dovecot/2013-March/089084.html I have a namespace with mbox and a namespace with mdbox mailboxes. How do I only enable the compression for the mdbox mailboxes?

Enable compression only for namespace with mdbox storage

I have a namespace with mbox and a namespace with mdbox mailboxes. How do I only enable the compression for the mdbox mailboxes?

Re: managesieve configuration

I've missed a part at the end: This leads me to my question: How do I force Dovecot to print at least a STARTTLS line after a client connects to port 4190? Looking ... at the default configuration files in /etc/dovecot/conf.d/ I don't see an obvious difference. --Dominik

managesieve configuration

Hello list, I'm trying to get pidgeonhole/managesieve running, and I'm stuck connecting clients to the server (Dovecot 2.2.33.2-1ubuntu4.1 on an Ubnutu 18.04 machine). So far, my config looks like this: protocols = imap lmtp sieve disable_plaintext_auth = yes auth_mechanisms = pl

auth core dump

Title: auth core dump Hello. After upgrade from FreeBSD 11 to FreeBSD 12 and Dovecot 2.2 to Dovecot 2.3 hanged auth when user connected to imap: Jan 10 15:53:46 master: Info: Dovecot v2.3.4 (0ecbaf23d) starting up for imap, pop3 Jan 10 15:54:09 auth-worker: Fatal: master: service(auth-worker):

Need help deduplicating messages fetched with getmail into dovecot mailbox

Hello everyone, I'm using getmail to fetch some external mails from POP3 into a dovecot mailbox (providing IMAP). Getmail seems to have some serious problems keeping track of mails already fetched. I have every Mail exactly twice in my Mailbox delivered by Dovecot. Of course they are not in the or

Re: repo.dovecot.org expired certificate

Hi Aki, it doesn't happen very often but the certificate renew can fail, so it's best to check daily. certbot will only try to renew those certificates that are about to expire in a few weeks. I'm using a little perl script via cron which may be more flexible: #!/usr/bin/perl my $reload_coun

Re: repo.dovecot.org expired certificate

Hello, in the ExecStart I use also "--agree-tos" Instead of --post-hook, maybe --deploy-hook it's better I usually put my scripts in the folder /etc/letsencrypt/renewal-hooks/deploy/ instead of use --deploy-hook Andrea Il 10/01/19 09:14, Aki Tuomi ha scritto: > > Would be better if it would h

Re: repo.dovecot.org expired certificate

Would be better if it would happen automatically though. Aki On 10.1.2019 10.04, Filipe Carvalho wrote: > > Yup, that did the trick. > > Thanks! > > Filipe > > > On 1/10/19 7:47 AM, Aki Tuomi wrote: >> >> >> On 10.1.2019 9.42, Filipe Carvalho wrote: >>> >>> Hello, >>> >>> Not sure if this is the

Re: repo.dovecot.org expired certificate

Yup, that did the trick. Thanks! Filipe On 1/10/19 7:47 AM, Aki Tuomi wrote: > > > On 10.1.2019 9.42, Filipe Carvalho wrote: >> >> Hello, >> >> Not sure if this is the right place to post this, but the ssl >> certificate of the repo.dovecot.org server expired on the 9th of January. >> >> It's g