[SOLVED] junk mail cleanup

[mmorse]

Re-reading that I realize you may be asking if it records the exact mail removed - never checked - but you can enable some more logging (see this post) and find out.

[mmorse]

Mmm
I don't really understand I think

I've setup the following:
'Spam message lifetime: 1day'

And this is the output on the console:

[zimbra@eigenwijze-1 ~]$ zmprov gs eigenwijze-1.linux.iu.nl | grep zimbraMailPurgeSleepInterval
zimbraMailPurgeSleepInterval: 0

How can I change it to the right ?

Mail over the 'lifetime' will be removed when the purge thread hits it - the user inherits the COS value unless you set it explicitly on the user's account:

COS Level-
Check by:
zmprov gc COSName | grep Lifetime
Set by:
zmprov mc COSName zimbraMailTrashLifetime 30d
zmprov mc COSName zimbraMailSpamLifetime 30d

OR User Level-
Check by:
zmprov ga user@domain.com | grep Lifetime
Set by:
zmprov ma user@domain.com zimbraMailTrashLifetime 30d
zmprov ma user@domain.com zimbraMailSpamLifetime 30d

The purge thread itself:
Check by:
zmprov gs server.domain.com | grep zimbraMailPurgeSleepInterval
Set by:
zmprov ms server.domain.com zimbraMailPurgeSleepInterval 1m

0 on any of those disables automatic purging for that machine/account

So really it's a but of math logic -say you have:
-6 users
-zimbraMailTrashLifetime 30d
-zimbraMailPurgeSleepInterval 1d
-A message in the trash of account 5 that's 31 days old - this mail is now 'capable of being removed' as it's over the zimbraMailTrashLifetime.

Day 32: Mailboxes 1/2 are purged
Day 33: Mailboxes 2/3/4 (I'm not gonna nail down this timing right now - 3 gets purged for sure)
Day 34: Mailboxes 4/5/6 are purged

So really that message in account 5's trash technically stayed around till day 34.

This allows for better scaling rather than just everyone in one big cron job putting load on the server - for instance you could decide to purge 1400 accounts per day.

[Cheakamus]

Your info was exactly what I wanted to know. Thanks. For the record:

zimbra@tantalus:~$ grep Purge log/mailbox.log | grep "jay@thinktek.ca" | tail -3
2008-04-13 10:42:46,191 INFO [MailboxPurge] [name=jay@thinktek.ca;mid=5;] mailbox - Purging messages.
2008-04-13 10:57:46,989 INFO [MailboxPurge] [name=jay@thinktek.ca;mid=5;] mailbox - Purging messages.
2008-04-13 11:12:47,638 INFO [MailboxPurge] [name=jay@thinktek.ca;mid=5;] mailbox - Purging messages.
zimbra@tantalus:~$

So it's getting to mine every 15 minutes or so, which IMHO is a bit too frequent (zimbraMailPurgeSleepInterval = 1m) so I have set it to 1h and will re look at it.

Thanks again!

Jay

[Priyantha Bleeker]

Mail over the 'lifetime' will be removed when the purge thread hits it - the user inherits the COS value unless you set it explicitly on the user's account:

COS Level-
Check by:
zmprov gc COSName | grep Lifetime
Set by:
zmprov mc COSName zimbraMailTrashLifetime 30d
zmprov mc COSName zimbraMailSpamLifetime 30d

OR User Level-
Check by:
zmprov ga user@domain.com | grep Lifetime
Set by:
zmprov ma user@domain.com zimbraMailTrashLifetime 30d
zmprov ma user@domain.com zimbraMailSpamLifetime 30d

The purge thread itself:
Check by:
zmprov gs server.domain.com | zimbraMailPurgeSleepInterval
Set by:
zmprov ms server.domain.com zimbraMailPurgeSleepInterval 1m

0 on any of those disables automatic purging for that machine/account

So really it's a but of math logic -say you have:
-6 users
-zimbraMailTrashLifetime 30d
-zimbraMailPurgeSleepInterval 1d
-A message in the trash of account 5 that's 31 days old - this mail is now 'capable of being removed' as it's over the zimbraMailTrashLifetime.

Day 32: Mailboxes 1/2 are purged
Day 33: Mailboxes 2/3/4 (I'm not gonna nail down this timing right now - 3 gets purged for sure)
Day 34: Mailboxes 4/5/6 are purged

So really that message in account 5's trash technically stayed around till day 34.

This allows for better scaling rather than just everyone in one big cron job putting load on the server - for instance you could decide to purge 1400 accounts per day.

Well when I try to do what you said.
I get the following;
[zimbra@$$$$ ~]$ zmprov gc COSName | grep Lifetime
ERROR: account.NO_SUCH_COS (no such cos: COSName)

[phoenix]

Well when I try to do what you said.
I get the following;
[zimbra@eigenwijze-1 ~]$ zmprov gc COSName | grep Lifetime
ERROR: account.NO_SUCH_COS (no such cos: COSName)

I assume you did put your Class of Service name in there instead of "COSName"?

[Priyantha Bleeker]

I assume you did put your Class of Service name in there instead of "COSName"?

Ah hahaha
No I didn't
But what do I have to put there instead of "COSName" ?

[phoenix]

Ah hahaha
No I didn't
But what do I have to put there instead of "COSName" ?

Well, the default COS is called "default" and if there are any other COS that you've created then you'll have the names. Have a look in the Admin UI under the Class of Service entry and you'll see which COS are defined.

[Priyantha Bleeker]

Ah thanks
This is the output:

[zimbra@$$$ ~]$ zmprov gc default | grep Lifetime
zimbraAdminAuthTokenLifetime: 12h
zimbraAuthTokenLifetime: 2d
zimbraMailMessageLifetime: 0
zimbraMailSpamLifetime: 1d
zimbraMailTrashLifetime: 1d
zimbraPasswordLockoutFailureLifetime: 1h
zimbraPrefInboxReadLifetime: 0
zimbraPrefInboxUnreadLifetime: 0
zimbraPrefJunkLifetime: 0
zimbraPrefSentLifetime: 0
zimbraPrefTrashLifetime: 0
[zimbra@eigenwijze-1 ~]$

[mmorse]

Ok, so with those values unless you've set it at the individual level at somepoint as well, your trash & spam are 'capable of being deleted' after one day.
Defaults for zimbraMailTrash/SpamLifetime are 30d
Default for zimbraMailPurgeSleepInterval is 1m (you might still need to set this)
See my prior post again for how to change those values

[Priyantha Bleeker]

Ok, so with those values unless you've set it at the individual level at somepoint as well, your trash & spam are 'capable of being deleted' after one day.
Defaults for zimbraMailTrash/SpamLifetime are 30d
Default for zimbraMailPurgeSleepInterval is 1m (you might still need to set this)
See my prior post again for how to change those values

Mmm okay.
But 'capable of being deleted' is not the same as 'will be deleted' after one day isn't it ? Because that is what I want