Simon

Hi Chris,

When you edit a backup schedule, you can configure how many backups will be stored on the server (will keep the n newest ones per schedule).

I personally keep 14 daily database backups and 4 weekly complete backups on the server (and have a daily cronjob on another server that downloads the Zip files).

I’m currently playing around with the new RegEx functionality that was added in 2.5.2 (adding stuff to the _is_regexp_spam function in antispam-bee/antispam_bee.php).

Maybe I’ll be able to at least cage the spammers that are hammering my blog from changing IPs (but mostly CN).

If you enable the ‘Delete comments by spam reasons’ option, you can select which reasons will get the spam comment immediately deleted.

Each one of those will then increase the ‘Blocked’ counter.

I think this is basically what you want.

The reason to keep marked spam is to have Antispam Bee double check the “poster’s” IP if ‘Look in the local spam database’ is enabled.
If the IP of your spam comments are all different, it cannot catch them.

I don’t think it does any text analysis as for example advanced mail spam plugins do.

Most of my spam comments get trapped in the CSS Hack, if you are not subject to the EU laws, you might also want to enable the Tornevall public antispam database.

First, thank you very much for the plugin. My previous solution stopped working and I needed to find a replacement and BackupWordpress works great!

Since this thread already touches that topic, I’m not going to create a new one for it.

I’d love to have an option to get the notification (so I know that the backup is running fine), but never with an attachment.

I have a remote computer that daily mirrors the backup directory, so I don’t need it in my inbox too.

Currently, I’m commenting out the whole block with

if ( filesize( $file ) < 1000 * 1000 * 10 ) {
[..]
}

in backupwordpress/classes/email.php, but I have to remember to do this after every update.

An option ‘[ ] Attach backup to notification’ would be very nice.

Thank you. Yes the development version works fine again.
I only had to upload the new qtranslate.php file.