Message aging policy
Dear folks,
I need to create message aging policy (based on the age of the message) and mbox aging policy( if there is no login /incoming message in n number of days).
The users that are affected by these policies will be based on an private LDAP attribute. Is there a way that I can incoopperate this LDAP attribute value to setup the aging policy filter?
Thanks,
T Dang
[403 byte] By [
tindang] at [2007-11-26 10:49:28]

# 1
As far as I know, there is no way that the aging system can know how long it's been since a user has logged into his mailbox.As far as I know, there is also no way to connect an LDAP attribute to expiration.
# 2
Thanks for the information, Jay.T Dang
# 3
Dear Jay,The command: mboxutil -o [-t number of days without activities)\] ==> list of orphan mbox ..what are orphan mboxes?thanks
# 4
Traditionally, "orphan mailboxes" were defined as, "mailboxes that have no ldap entry".
I don't believe that the -t will help you, here.
In any case, output from mboxutil or options for mboxutil aren't going to help you with automatic message expiration.
Perhaps if you put your requirements in a more detailed way, I could make better suggestions.
# 5
Dear Jay,
The requirements include:
Delete selected mailbox which is ZERO in size or no activity (no message deposited or login) in X number days
The other requirement which requires the remove of message or delete of mailbox are based on a value of LDAP attribute associated with the subscriber.
Thanks
# 6
Ok.
>Delete selected mailbox which is ZERO in size or no activity (no message deposited or login) in X number days
mboxutil is your friend, here. I suggest writing something that calls mboxutil, and parses the output. These are not orphaned, unless they've been deprovisioned in ldap, not something you mentin.
>The other requirement which requires the remove of message or delete of mailbox are based on a value of LDAP attribute associated with the subscriber.
Hm. You're pretty much on your own for this one. Unless the "vcalue of LDAP attreibute" is, "DELETED" in "UserStatus".
# 7
Dear Jay,
>mboxutil is your friend, here. I suggest writing something that calls mboxutil, and parses the output. These are not orphaned, unless they've been deprovisioned in ldap, not something you mentin.
I can use "mboxutil -l" for the ZERO size case.
But for the inactivity case, the comand "mboxutil -l" ==> list of mbox which include the time of last msg. For mail box without message, no date returned ... I guess that since your earlier post, you have indicated that there is no way to determine the time of the last login (activity)
mbox -o -t n ==> I guess I won't be able to use this option, since this will output only orphan mail boxes.
Thanks,
T Dang
Message was edited by:
tindang
# 8
For access times, you can useimsconnutil http://docs.sun.com/app/docs/doc/819-2651/6n4u5ce7b?a=view#acmcp
# 10
Dear Jay,The other requirement about message aging ... that is to delete amy message which is older than X days for each mbox based on an selected LDAP attribute.Any suggestion?ThanksT DangMessage was edited by: tindang
# 11
I know of no way to achieve what you are asking for.
You can create aging rules by user, if you want, but that's not by ldap query.
In a large deployment, having tools like "imexpire" do ldap lookups is very likely to cause serious performance issues.
you care certainly welcome to open a support case, and create an "RFE" (Request For Enhancement". Such get rather low priority, unless they're very popular. Yours is the first such request I"ve heard.
# 12
Dear Jay,My understand is that there is no limit on the number of rule , so I can create as many rule :such as: store.expirerule.*.* as I want.Is that correct ?ThanksT Dang
# 13
I can't say how many have been tested, but theoretically, there isn't a limit. I suspect that thousands could impact preformance, though.
You can create expiration rule files in the user's directory tree, though. Those should get evaluated when imexpire is run. That may be a better way to go for many, many rules.
# 14
Thanks Jay,T DangMessage was edited by: tindang
# 15
Dear Jay,
If the number of mailboxes is as much as multiple millions, do you have any performance information on how long it would take to do the followings:
* expiration rule to delete expired message
* mboxutil -l (list all message)
* imsconnutil (list the last access time of each mbox)
Thanks,
T Dang
# 16
> Dear Jay,
>
> If the number of mailboxes is as much as multiple
> millions, do you have any performance information on
> how long it would take to do the followings:
>
> * expiration rule to delete expired message
Depends on many things I can't know. Try it, and see.
> * mboxutil -l (list all message)
Depends on many things. I would not run this every few minutes, as it will cause excessive disk access.
> * imsconnutil (list the last access time of each
> mbox)
Should not take long, accesses in-memory data.
>
> Thanks,
>
> T Dang
# 17
Dear Jay,
Thanks for the imformation ...
I tried to use: imsconnutil
imsconnutil -c -s imap
==> Feature is not enbled for imap
Can you let me know that feature is not enabled for imap ?
The imsconnutil is not enabled for imap ? what do I need to do so I can get only imap last access time ?
If I run
imsconnutil -l
==> it gives all mailbox numbers with IMAP, HTTP, POP last acess with values of " NOT-RECORDED"
Am I missing something ?
Thanks
T Dang