<div dir="ltr">Thanks everyone for the answers ! <div><br></div><div>I will scan the login entries in the syslog and use them. I thought about redirecting all the users logins entries to a specific file and then develop a script to delete mailboxes that have not been accessed in the last 90 days.</div>
<div><br></div><div><div><div><br></div>-- <br><pre><font face="'courier new', monospace">My best regards,
Fabio Soares Schmidt
Linux Professional Institute - LPIC-3
Microsoft Certified Technology Specialist: Active Directory</font></pre><div><br></div><div class="gmail_extra"><br><br><div class="gmail_quote">On 8 July 2014 01:21, Bron Gondwana <span dir="ltr"><<a href="mailto:brong@fastmail.fm" target="_blank">brong@fastmail.fm</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div class="">On Tue, Jul 8, 2014, at 06:51 AM, Nic Bernstein wrote:<br>
> On 07/07/2014 03:12 PM, Joseph Brennan wrote:<br>
> > "Fabio S. Schmidt" <<a href="mailto:fabio@improve.inf.br">fabio@improve.inf.br</a>> wrote:<br>
> ><br>
> >> I actually need to consider only the last access via IMAP or POP<br>
> > protocols.<br>
> ><br>
> > That can be very misleading, because a device may keep checking for new<br>
> > mail for a very long time after the user abandons the account.<br>
> ><br>
> > A recent timestamp on the user.seen file should be good, but that seems to<br>
> > update mysteriously sometimes.<br>
><br>
> The "lastupdated:" field of cyradm's "info mailbox" command will show<br>
> the last time the mailbox was updated in any way, so that includes<br>
> deliveries. The timestamp of the user.seen file will only reflect the<br>
> last time that the seen state of anything in the mailbox changed, but<br>
> does not tell you when the mailbox was last accessed.<br>
><br>
> I think you'd need to derive this information some other way, such as<br>
> from authentication logs. Of course the reliability and accessibility<br>
> of that will depend on your authentication mechanisms.<br>
<br>
</div>I would go by entries in the syslog. We run a custom saslauthd, which does<br>
logging, so we get it from there - but this is what shows up in syslog:<br>
<br>
imap[20174]: login: HOST [IP] user@domain plaintext User logged in<br>
<br>
You can scan those and use them.<br>
<span class=""><font color="#888888">--<br>
Bron Gondwana<br>
<a href="mailto:brong@fastmail.fm">brong@fastmail.fm</a><br>
</font></span><div class=""><div class="h5">----<br>
Cyrus Home Page: <a href="http://www.cyrusimap.org/" target="_blank">http://www.cyrusimap.org/</a><br>
List Archives/Info: <a href="http://lists.andrew.cmu.edu/pipermail/info-cyrus/" target="_blank">http://lists.andrew.cmu.edu/pipermail/info-cyrus/</a><br>
To Unsubscribe:<br>
<a href="https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus" target="_blank">https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus</a><br>
</div></div></blockquote></div><pre></pre>
</div></div></div></div>