Re: sieve filter bevor.spam, arnt take effect

On Mon, 12 Apr 2021, mau...@gmx.ch wrote: Hi again, Your dovecot.conf neither contains the sieve settings nor includes the conf.d/90-sieve.conf file, which means that you only get whatever default config dovecot includes. Good luck.. Now i put everyting that I "need" for forward spam to fold

Re: error 42 ssl certificate expired

gmail (Di 13 Apr 2021 06:16:38 CEST): > Hi, > > I got news: dovecot is the one that is broken, i got setup all other stuff > updated to latest BUT not dovecot, and i got working system. Are you referring to the original topic of this thread? Or is this a new issue? I'm asking, because your addr

Re: error 42 ssl certificate expired

To me it seems you are serving a valid cert, i checked with openssl s_client -connect host:443 -servername domain Not sure why you have all those local_name blocks there when the cert you are offering covers all your names already. Aki > On 13/04/2021 07:59 gmail wrote: > > > I got forcibl

Re: error 42 ssl certificate expired

I got forcibly renewed my certs. dovecot -nP: # 2.3.7.2 (3c910f64b): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.7.2 () # OS: Linux 5.9.0-rc5-lja-tv+ x86_64 Ubuntu 20.04.2 LTS # Hostname: superman.sillywalk.org auth_debug = yes auth_debug_passwords = yes auth_mechanisms = plain login auth

Re: error 42 ssl certificate expired

Uh. You are practically proposing that all versions after 2.3.7.2 would be serving expired SSL certs, due to some bug? It that was the case, then I would believe we would've been inundated with bug reports for the past year or so. Installation probably breaks because you are using expired cert,

Re: error 42 ssl certificate expired

Hi, I got news: dovecot is the one that is broken, i got setup all other stuff updated to latest BUT not dovecot, and i got working system. if I upgrade dovecot, the installation breaks. I'm using letencrypt's certs. The version that is good is 2.3.7.2 (3c910f64b) Heiko Schlittermann kirj

Re: error 42 ssl certificate expired

Hi, > In our case this is an internally used Dovecot Mail server that's used for … > certificates worth the expense? Just curious on what everyone's opinion is > of Digital Certs signed by certificate authorities that are only used inside > the LAN. Thoughts? Aki is right. On the long run it's ea

AW: AW: sieve filter bevor.spam, arnt take effect

>Hi again, >Your dovecot.conf neither contains the sieve settings nor includes the conf.d/90-sieve.conf file, which means that you only get whatever >default config dovecot includes. >Good luck.. Now i put everyting that I "need" for forward spam to folder Junk-E-Mail.tje the goal are that the

Re: Only INBOX is searched when using gmail with dovecot FTS and solr

Any ideas on this? I am sure that I can't be the only one having issues with the search function while using Gmail. Hi, I am using https://github.com/docker-mailserver/docker-mailserver to setup my mailserver and added solr for full-text search. Nearly everything is working as expected. But

Re: error 42 ssl certificate expired

I confirm that the solution in Thunderbird, was they had to click on the account's inbox, then click get messages, then click the confirm security exception button on the server identity pop-up, and that fixes the issue.  I could see that under Tools > Options > Certificates for the server sect

AW: sieve filter bevor.spam, arnt take effect

Thanks for your answer after remark this line restart the service and nothing changed... oot@nmail:/etc/dovecot# cat dovecot.conf # 2.2.27 (c0f36b0): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.16 (fed8554) # OS: Linux 4.9.0-12-amd64 x86_64 Debian 9.12 # Enable installed protocols !inc

Re: Letsencrypt/OpenSSL test - Verify return code: 21

On 2021-04-10 12:09 p.m., Brady Shea wrote: I finally 'fixed' it myself by using the LE 'fullchain.pem' certificate as the location for the 'ssl_cert' entry (and chain.pem for the ca entry). Previously, it was using the normal cert.pem file location. This is still the way it's setup on the

Re: AW: sieve filter bevor.spam, arnt take effect

Hi again, Your dovecot.conf neither contains the sieve settings nor includes the conf.d/90-sieve.conf file, which means that you only get whatever default config dovecot includes. Good luck.. On Mon, 12 Apr 2021, Maurizio Caloro wrote: Thanks for your answer after remark this line rest

Re: error 42 ssl certificate expired

> On 12/04/2021 17:13 Christopher Wensink > wrote: > > > Dovecot Team, > > I need a little help.  I came in this morning and it seems like the SSL > Certificates expired for dovecot (on an internal mail server) and nobody > can move email into  their folders on this server.  In Thunderbir

connection closed every ten minutes

Greetings, I use mutt on Ubuntu to access my IMAP mailboxes, on my Centos email server that runs dovecot. Everything has worked without problems for years. About one week ago, the connection between mutt and dovecot became unstable. Before, I could leave mutt connected for days in a row, no probl

Re: connection closes every 10 minutes

> On 12 Apr 2021, at 16:47, Marco Fioretti wrote: > > Apr 12 16:12:49 SERVERNAME dovecot: imap(ACCOUNTNAME): Logged out in=164 > out=757 This log line means that the connection with the server is terminated gracefully, with the client issuing a "LOGOUT" command. That makes me think the iss

connection closes every 10 minutes

Greetings, I use mutt on Ubuntu to access my IMAP mailboxes, on my Centos email server that runs dovecot. Everything has worked without problems for years. About one week ago, the connection between mutt and dovecot became unstable. Before, I could leave mutt connected for days in a row, no probl

error 42 ssl certificate expired

Dovecot Team, I need a little help.  I came in this morning and it seems like the SSL Certificates expired for dovecot (on an internal mail server) and nobody can move email into  their folders on this server.  In Thunderbird they just see in the status bar:  HISTORY: checking mail server capa

AW: sieve filter bevor.spam, arnt take effect

Thanks for your answer after remark this line restart the service and nothing changed... oot@nmail:/etc/dovecot# cat dovecot.conf # 2.2.27 (c0f36b0): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.16 (fed8554) # OS: Linux 4.9.0-12-amd64 x86_64 Debian 9.12 # Enable installed protocols !inc

Re: sieve filter bevor.spam, arnt take effect

Hello, (Excuse me for top-posting, but the message below is too messy) Your sieve config according to "dovecot -n" does not match what you have in 90-sieve.conf. Have you deleted the line "!include conf.d/*.conf" in doveconf.conf? Please double check that, as your config may not be what you'd

AW: sieve filter bevor.spam, arnt take effect

Please kindly want to ask for any possible update ? Von: mau...@gmx.ch Gesendet: Montag, 12. April 2021 10:44 An: 'dovecot@dovecot.org' Betreff: sieve filter bevor.spam, arnt take effect Hello Please willing to filter "bevor spam" mail... filtering arnt take effect .. please i dont see th

sieve filter bevor.spam, arnt take effect

Hello Please willing to filter "bevor spam" mail... filtering arnt take effect .. please i dont see the mistake. Thanks for any possible update. Debian buster -- root@nmail:/etc/dovecot# dpkg -l | grep dovecot dovecot-core1:2.3.4.1-5+deb10u6 dovecot-imapd

sieve filter bevor.spam, arnt take effect

Hello Please willing to filter "bevor spam" mail... filtering arnt take effect .. please i dont see the mistake. Thanks for any possible update. Debian buster -- root@nmail:/etc/dovecot# dpkg -l | grep dovecot dovecot-core1:2.3.4.1-5+deb10u6 dovecot-imapd

Re: Sieve doesn't work after LTMP Director implementation

> On 12/04/2021 10:28 Gonzalo Palacios Goicolea > wrote: > > > Hi All, > We're running dovecot director por proxying imap/pop queries to the backends. > Yesterday we add LMTP proxying and it works fine, but we have realized that > Sieve filters are no longer working after this change. Is it

Sieve doesn't work after LTMP Director implementation

Hi All, We're running dovecot director por proxying imap/pop queries to the backends. Yesterday we add LMTP proxying and it works fine, but we have realized that Sieve filters are no longer working after this change. Is it mandatory to add some config to the directors or backends after implem