On Thu, 2021-03-04 at 10:54 +0100, Yassine Chaouche wrote:
> This is pretty wild. Is that perl sorcery ?
Used to be but as I migrated to a new server I thought I would use
python this time around.
--
Greg
signature.asc
Description: This is a digitally signed message part
Sorry, the output didn't format properly. The takeaway fields are as follows:
Last Modified : 2020-08-18 19:46:12
Last IMAP : 2021-03-04 10:52:03
Last POP3 : None
Last Delivery : 2021-03-04 10:26:49
--
Greg
signature.asc
Description: This is a digitally signed messa
On Wed, 2021-03-03 at 04:57 -0700, @lbutlr wrote:
> I've noticed several threads over the last year or so about last-
> login, and I was curious WHY people care about tracking this in the
> database. I can see wanting to know if a user has logged in recently,
> but this seems quite easy to tell by
On Tue, 2019-09-10 at 08:41 +0200, Maciej Milaszewski IQ PL via dovecot
wrote:
> Hi
> This is for all dovecot version ?
Not sure. Any version of dovecot that builds it's config from the
conf.d folder will work. Not sure on the specific SSL certificate
syntax but I have been using the aformentioned
On Fri, 2019-09-06 at 17:25 -0700, remo--- via dovecot wrote:
> What is the best way to adopt multiple certs?
I have a setup that creates letsencrypt certs for each customer domain.
To automate this I have the following at the end of conf.d/10-ssl.conf
!include ssl.d/*.conf
This includes any
What problem are you seeing? It uses the correct SSL certs when I
connect.
prompt> gnutls-cli --port 993 mail.nimmini.de
Processed 149 CA certificate(s).
Resolving 'mail.nimmini.de:993'...
Connecting to '46.38.231.143:993'...
- Certificate type: X.509
- Got a certificate list of 2 certificates.
-
On Sat, 2018-12-08 at 11:03 +0100, Marco Fioretti wrote:
> Greetings,
> I have had to reinstall my email server on another Linux (centos 7.6)
> VPS, with a newer version of dovecot, other software and a brand new
> letsencrypt certificate just for email withpostfix and dovecot (that
> certificate w
Hello,
I am trying out 2.2.19.rc1 on a lightly loaded server with no problems
so far. The reason I wanted to try 2.2.19.rc1 was to get access to the
%{listener} variable in the auth phase so I can modify the SQL
password_query according to which unix_listener is being queried.
According to the do
