Add link of tutorial: Track user last login time.

This commit is contained in:
Zhang Huangbin 2020-04-18 12:42:39 +08:00
parent 193e815e3b
commit 1263a82ad0
6 changed files with 46 additions and 10 deletions

View File

@ -8,7 +8,8 @@
not yet support updating existing SQL record on conflict primary key.
References: [1](https://marc.info/?t=155411531600001&r=1&w=2), [2](https://marc.info/?t=155826327900001&r=1&w=2)
* This tutorial has been updated to support tracking last login time of
both IMAP and POP3, which is implemented in iRedMail-1.2.
both IMAP and POP3, which is implemented in iRedMail-1.2, you can find
the difference in upgrade tutorial for iRedMail-1.2 here: [For LDAP backend](./upgrade.iredmail.1.1-1.2.html#improved-last-login-track), [For SQL backends](./upgrade.iredmail.1.1-1.2.html#improved-last-login-track_1).
Dovecot ships a `last_login` plugin since Dovecot-2.2.14, it can be used to
easily save and update user's last-login timestamp in SQL database.

View File

@ -10,6 +10,7 @@
## ChangeLog
* Apr 18, 2020, mention how to configure Dovecot to track user last login time.
* Dec 11 2019, mention not to enable quota-status service in Dovecot-2.1.x.
* Dec 9, 2019, initial release.
@ -263,6 +264,10 @@ smtpd_recipient_restrictions =
Restarting Postfix service is required.
### [OPTIONAL] Track the time of user last login via IMAP/POP3
* [Track user last login time](./track.user.last.login.html)
## For MySQL/MariaDB backends
### [OPTIONAL] Enable mailbox quota status check in Dovecot and Postfix.
@ -350,6 +355,10 @@ smtpd_recipient_restrictions =
Restarting Postfix service is required.
### [OPTIONAL] Track the time of user last login via IMAP/POP3
* [Track user last login time](./track.user.last.login.html)
## For PostgreSQL backend
### [OPTIONAL] Enable mailbox quota status check in Dovecot and Postfix.

View File

@ -10,6 +10,7 @@
## ChangeLog
* Apr 18, 2020: Add link of tutorial: [Track user last login time](./track.user.last.login.html).
* Apr 17, 2020: initial release.
## General (All backends should apply these changes)
@ -74,10 +75,16 @@ chmod 0550 mlmmj-amime-receive
### Improved last login track
In iRedMail-1.0, Dovecot is configured to store user last login time in SQL
database `iredadmin`, but it only tracks either POP3 or IMAP login. In
iRedMail-1.2, it tracks both. Please follow steps below to implement this
improvement.
!!! attention
User last login track is optional if you didn't implement it while
upgrading iRedMail to 1.0. Here's the full tutorial to implement last login
track: [Track user last login time](./track.user.last.login.html).
In iRedMail-1.0, Dovecot is configured to store the time of user last login via
IMAP/POP3 in SQL database `iredadmin`, but it only tracks either POP3 or IMAP
login. In iRedMail-1.2, it tracks both. Please follow steps below to implement
this improvement.
* Open file `/etc/dovecot/dovecot.conf` (Linux/OpenBSD) or
`/usr/local/etc/dovecot/dovecot.conf` (FreeBSD), find the `last_login_key`

View File

@ -34,7 +34,8 @@
not yet support updating existing SQL record on conflict primary key.
References: <a href="https://marc.info/?t=155411531600001&amp;r=1&amp;w=2">1</a>, <a href="https://marc.info/?t=155826327900001&amp;r=1&amp;w=2">2</a></li>
<li>This tutorial has been updated to support tracking last login time of
both IMAP and POP3, which is implemented in iRedMail-1.2.</li>
both IMAP and POP3, which is implemented in iRedMail-1.2, you can find
the difference in upgrade tutorial for iRedMail-1.2 here: <a href="./upgrade.iredmail.1.1-1.2.html#improved-last-login-track">For LDAP backend</a>, <a href="./upgrade.iredmail.1.1-1.2.html#improved-last-login-track_1">For SQL backends</a>.</li>
</ul>
</div>
<p>Dovecot ships a <code>last_login</code> plugin since Dovecot-2.2.14, it can be used to

View File

@ -40,6 +40,7 @@
<li><a href="#enable-quota-status-check-in-postfix">Enable quota status check in Postfix</a></li>
</ul>
</li>
<li><a href="#optional-track-the-time-of-user-last-login-via-imappop3">[OPTIONAL] Track the time of user last login via IMAP/POP3</a></li>
</ul>
</li>
<li><a href="#for-mysqlmariadb-backends">For MySQL/MariaDB backends</a><ul>
@ -49,6 +50,7 @@
<li><a href="#enable-quota-status-check-in-postfix_1">Enable quota status check in Postfix</a></li>
</ul>
</li>
<li><a href="#optional-track-the-time-of-user-last-login-via-imappop3_1">[OPTIONAL] Track the time of user last login via IMAP/POP3</a></li>
</ul>
</li>
<li><a href="#for-postgresql-backend">For PostgreSQL backend</a><ul>
@ -72,6 +74,7 @@ check <a href="https://www.iredmail.org/support.html">the details</a> and
</div>
<h2 id="changelog">ChangeLog</h2>
<ul>
<li>Apr 18, 2020, mention how to configure Dovecot to track user last login time.</li>
<li>Dec 11 2019, mention not to enable quota-status service in Dovecot-2.1.x.</li>
<li>Dec 9, 2019, initial release.</li>
</ul>
@ -285,6 +288,10 @@ Dovecot-2.1.x or earlier versions.</p>
</code></pre>
<p>Restarting Postfix service is required.</p>
<h3 id="optional-track-the-time-of-user-last-login-via-imappop3">[OPTIONAL] Track the time of user last login via IMAP/POP3</h3>
<ul>
<li><a href="./track.user.last.login.html">Track user last login time</a></li>
</ul>
<h2 id="for-mysqlmariadb-backends">For MySQL/MariaDB backends</h2>
<h3 id="optional-enable-mailbox-quota-status-check-in-dovecot-and-postfix_1">[OPTIONAL] Enable mailbox quota status check in Dovecot and Postfix.</h3>
<p>With default iRedMail settings, Postfix accepts email without checking whether
@ -355,6 +362,10 @@ Dovecot-2.1.x or earlier versions.</p>
</code></pre>
<p>Restarting Postfix service is required.</p>
<h3 id="optional-track-the-time-of-user-last-login-via-imappop3_1">[OPTIONAL] Track the time of user last login via IMAP/POP3</h3>
<ul>
<li><a href="./track.user.last.login.html">Track user last login time</a></li>
</ul>
<h2 id="for-postgresql-backend">For PostgreSQL backend</h2>
<h3 id="optional-enable-mailbox-quota-status-check-in-dovecot-and-postfix_2">[OPTIONAL] Enable mailbox quota status check in Dovecot and Postfix.</h3>
<p>With default iRedMail settings, Postfix accepts email without checking whether

View File

@ -56,6 +56,7 @@ check <a href="https://www.iredmail.org/support.html">the details</a> and
</div>
<h2 id="changelog">ChangeLog</h2>
<ul>
<li>Apr 18, 2020: Add link of tutorial: <a href="./track.user.last.login.html">Track user last login time</a>.</li>
<li>Apr 17, 2020: initial release.</li>
</ul>
<h2 id="general-all-backends-should-apply-these-changes">General (All backends should apply these changes)</h2>
@ -103,10 +104,16 @@ chmod 0550 mlmmj-amime-receive
<h2 id="for-openldap-backend">For OpenLDAP backend</h2>
<h3 id="improved-last-login-track">Improved last login track</h3>
<p>In iRedMail-1.0, Dovecot is configured to store user last login time in SQL
database <code>iredadmin</code>, but it only tracks either POP3 or IMAP login. In
iRedMail-1.2, it tracks both. Please follow steps below to implement this
improvement.</p>
<div class="admonition attention">
<p class="admonition-title">Attention</p>
<p>User last login track is optional if you didn't implement it while
upgrading iRedMail to 1.0. Here's the full tutorial to implement last login
track: <a href="./track.user.last.login.html">Track user last login time</a>.</p>
</div>
<p>In iRedMail-1.0, Dovecot is configured to store the time of user last login via
IMAP/POP3 in SQL database <code>iredadmin</code>, but it only tracks either POP3 or IMAP
login. In iRedMail-1.2, it tracks both. Please follow steps below to implement
this improvement.</p>
<ul>
<li>Open file <code>/etc/dovecot/dovecot.conf</code> (Linux/OpenBSD) or
<code>/usr/local/etc/dovecot/dovecot.conf</code> (FreeBSD), find the <code>last_login_key</code>