[SOLVED] junk mail cleanup

[jonix]

Totally new to zimbra and impressed !
2 questions:
- how to cleanup the junkmail folders periodically ? Can an expire date be set ?
- Is there an option where I can give an administrator email who must be notified when the queue increases exponentiallly ...

Looking forward for more zimlets :-)

Regards,


Johan (Belgium)

[mmorse]

Welcome to the forums,

Totally new to zimbra and impressed !

With the thread logo I gather you meant 'it wins hands down' or did you mean that a thumbs up? -lol

- how to cleanup the junkmail folders periodically ? Can an expire date be set ?

In the admin console gui > individual user (or COS) > advanced tab > scroll to the bottom > and you can set:
Spam message lifetime -Number of days a message can remain in the Junk folder before it is automatically purged. The default is 30 days.
Trashed message lifetime - Number of days a message remains in the Trash folder before it is automatically purged. The default is 30 days.

There's also this but I doubt you're looking to set it, do be careful or you'll wipe everyone's email by setting it to 1 day etc:
Email message lifetime - Number of days a message can remain in any folder before it is automatically purged. The default is 0; email messages are not deleted.

(All of these can also be set via CLI.)

If you checkout v5 in the hosted demo or install your own RC1 (though I wouldn't use any IMAP with RC1 as there's currently a tiny bug in the betas) an end-user can go to preferences and set their own lifetimes (based on admin minimum allowances of course)

- Is there an option where I can give an administrator email who must be notified when the queue increases exponentiallly ...

In case stuff is starting to get stuck there an RFE for: Bug 11092 - queue alert
(That's for a pop in the admin-console; didn't want to add another email to the mix, though you could certainly note that an admin email woudl be acceptable too.)

But you can also file an new RFE in bugzilla for 'heavy use threshold warnings' (both of queue and all message traffic) if you'd like.
However do realize that you can use SNMP to monitor a few things. And there's even an HypericHQ plugin. (could rattle off company names all day)

Looking forward for more zimlets :-)

Start developing or tell us what you'd like to see!

[jonix]

we have several zimbra's running now:-)

[Cheakamus]

In the admin console gui > individual user (or COS) > advanced tab > scroll to the bottom > and you can set:
Spam message lifetime -Number of days a message can remain in the Junk folder before it is automatically purged. The default is 30 days.
Trashed message lifetime - Number of days a message remains in the Trash folder before it is automatically purged. The default is 30 days.

I have those set yet there's still messages in my Trash folder dating back to January. Is there a separate cron job that needs to be run or something? When and how does that value get checked to do a purge?

Jay

[mmorse]

What's your ZCS version? http://www.zimbra.com/forums/announc...html#post62754

If it's 5.0.x:
zmprov gs server.domain.com | grep zimbraMailPurgeSleepInterval

[Cheakamus]

Release 5.0.2_GA_1975.DEBIAN4.0 DEBIAN4.0 FOSS edition

> zmprov gs tantalus.thinktek.ca | grep zimbraMailPurgeSleepInterval
zimbraMailPurgeSleepInterval: 0
>

Your post set me on the trail to this command:

> zmprov ModifyServer tantalus.thinktek.ca zimbraMailPurgeSleepInterval 1h
> zmprov gs tantalus.thinktek.ca | grep zimbraMailPurgeSleepInterval
zimbraMailPurgeSleepInterval: 1h

so I suspect things are much better now. I'll find out soon then set it to 1d once I'm confident it's working.

Thanks!

[mmorse]

Actually unless you're the only account, I would set it to something lower like 1m (or stick with 1h) - if you set it to 1d then it'd only purge 2 or so accounts per day.

To explain it better:
There really is no concept of a "purge interval". The purge thread is constantly running, purging mailboxes in memory, one at a time. Between every one-two mailboxes it sleeps for the interval specified by zimbraMailPurgeSleepInterval. I have much fewer mailboxes on my server so 1d is fine for me - set accordingly after you work out the math. This is way more robust than the old method & allows for spreading the load out overtime, which is especially nice for larger setups.

Work on this was done via Bug 13435 - User-definable expiration policy for systems folders where PurgeThread was implemented, which iterates all the mailboxes on the server and purges them one at a time. Mailboxes are only purged if they're loaded into the server cache & the thread sleeps between subsequent purges.
In short, the current mailbox purge algorithm only affects mailboxes that are in memory - as the theory is that if a mailbox is not in memory, it's not being accessed, not receiving mail, and therefore has less of a need to be purged.
Bug 20720 - Guarantee that mailboxes will be purged was filed for the issue of wanting a double check - possibly by making use of a zimbraMailLastPurgedTimestamp.

And yes zmpurgemessages, which used to produce some heavier load, was removed from cron/libexec in Bug 20705 - Remove zmpurgemessages

Of course it's all dependent on the zimbraMailSpamLifetime/zimbraMailTrashLifetime (default 30d) for what mail is removed.

[Priyantha Bleeker]

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@$$$$ ~]$ zmprov gs eigenwijze-1.linux.iu.nl | grep zimbraMailPurgeSleepInterval
zimbraMailPurgeSleepInterval: 0

How can I change it to the right ?

[Cheakamus]

Do the purges get audited in the logs anywhere?

[mmorse]

Do the purges get audited in the logs anywhere?

Yes, /opt/zimbra/log/mailbox.log:
2008-04-11 12:01:51,252 INFO [MailboxPurge] [name=name@domain;mid=#;] mailbox - Purging messages.

To find out who last got cleaned up simply run:
zmprov gs server.domain.com | grep zimbraMailLastPurgedMailboxId