Re: 2.3.17: Panic on LMTP deliveries

2021-11-12 Thread Stephan Bosch
On 11/11/2021 14:20, Michael Glaus wrote: Since the doevcot update to 2.3.17 i get a panic if a mail is delivered with lmtp. In the logs i get these messages: lmtp(r...@example.com)<21067>: Error: lmtp-server: conn 10.0.0.105:52981 [1]: rcpt r...@example.com: duplicate db: User r...@exampl

IPv4/v6 based access checking and logging

2021-11-12 Thread Lefteris Tsintjelis
Hi, I am currently using postfix/dovecot with postfix admin and I track the last login date already by using this: https://doc.dovecot.org/configuration_manual/lastlogin_plugin/ Besides last login date, I would like to also implement IPv4 and IPv6 last login tracking also and if possible, IP

RE: IPv4/v6 based access checking and logging

2021-11-12 Thread Sebastian Nielsen
If yore gonna check for IP, you should do it in pre-login so you can reject the username/password combo if the registred IP of account does not match.But guess its better to write a custom login handler for that, that also checks user's ip against database, in addition to username/password, and

Re: IPv4/v6 based access checking and logging

2021-11-12 Thread Lefteris Tsintjelis
I don't suppose there is a handler already for this one? Yes, that would have been the best to also add a warning system in case of unauthorized IP access. On 12/11/2021 20:00, Sebastian Nielsen wrote: If yore gonna check for IP, you should do it in pre-login so you can reject the username/pas

Re: IPv4/v6 based access checking and logging

2021-11-12 Thread julio covolato
Em 12/11/2021 14:47, Lefteris Tsintjelis escreveu: Hi, I am currently using postfix/dovecot with postfix admin and I track the last login date already by using this: https://doc.dovecot.org/configuration_manual/lastlogin_plugin/ Besides last login date, I would like to also implement IPv4

Re: IPv4/v6 based access checking and logging

2021-11-12 Thread julio covolato
And a litle shell script to query data from db: #!/bin/sh # # ex.: uso: dovecotLastLogin.sh -d 10 #   dovecotLastLogin.sh -u julio #

Re: after replication with compression quotas are wrong

2021-11-12 Thread Arnaud Abélard
On 10/11/2021 15:52, Arnaud Abélard wrote: I've just removed dummy-c-1's mailbox completely on the target server, removed the quota plugin, forced a sync for dummy-c-1 only and once it was done reactivated the quota plugins: double usage again. I also downgraded from dovecot 2.3.17 to 2.2.2

Re: [SOLVED] after replication with compression quotas are wrong

2021-11-12 Thread Arnaud Abélard
Ah! At last, after comparing all default values using doveconf I found the culprit: mailbox_list_index. Default is "no" on dovecot 2.2.7, but "yes" on dovecot 2.3.4 (on debian, at least). Switching mailbox_list_index to "no" fixes my quota miscalculation problem. Arnaud On 12/11/2021 20:09, A

2.3.17 update breaks dsync over tcps: Received invalid SSL certificate unable to get certificate CRL

2021-11-12 Thread Salatiel Filho
Hi, I have updated dovecot from 2.3.16 (working flawless ) to 2.3.17 ( both Centos8 - community repo ) . Now dsync does not work anymore, logs shows: dovecot[30398]: doveadm(vmail): Error: Disconnected from remote: Received invalid SSL certificate: unable to get certificate CRL: /CN=imap.signed.

Re: IPv4/v6 based access checking and logging

2021-11-12 Thread Lefteris Tsintjelis
Exactly what I was looking for and the script as well! Thank you very much Julio On 12/11/2021 20:33, julio covolato wrote: Em 12/11/2021 14:47, Lefteris Tsintjelis escreveu: Hi, I am currently using postfix/dovecot with postfix admin and I track the last login date already by using this:

Re: IPv4/v6 based access checking and logging

2021-11-12 Thread julio covolato
Hi Lefteris. Say thank you to Aki Tuomi, he was the one who taught me all this!! That's the spirit of opem sourse! -- _Engº Julio Cesar Covolato 0v0 /(_)\ F: 55-11-99175-9260 ^ ^ PSI INTERNET -- Em 12/11/2021