<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"></head><body dir="auto">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.<div dir="auto"><br></div><div dir="auto">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 tells client username/password is wrong if IP is unauth..</div><div><br></div><div align="left" dir="auto" style="font-size:100%;color:#000000"><div>-------- Originalmeddelande --------</div><div>Från: Lefteris Tsintjelis <lefty@spes.gr> </div><div>Datum: 2021-11-12 18:48 (GMT+01:00) </div><div>Till: dovecot@dovecot.org </div><div>Ämne: IPv4/v6 based access checking and logging </div><div><br></div></div>Hi,<br><br>I am currently using postfix/dovecot with postfix admin and I track the <br>last login date already by using this:<br><br>https://doc.dovecot.org/configuration_manual/lastlogin_plugin/<br><br>Besides last login date, I would like to also implement IPv4 and IPv6 <br>last login tracking also and if possible, IP based login checking. Is <br>post-login scripting the best most efficient way to go?<br><br>Regards,<br><br>Lefteris<br></body></html>