MrBrian

Sorry, it took someone to hound me via email to notice that the file wasn’t available anymore, as i haven’t been very active on the forums lately. I’ve re-uploaded it and it’s still working and latest version.

https://www.mediafire.com/?aatdu92d1ed81l9

In the bad-bahavior folder, locate banned.inc.php. In that file you can customize the antispam replace rather easily. I have to agree that the average person would not realize the correct email address, but the author should just implement a captcha for the blockpage or a contact form because legitimate users that see that page are very few and the ones that email are even fewer.

The configuration page has the count for ‘blocked’ requests while the count on the log page is for ‘all requests’ which include permitted ones, so its normal for the numbers to be different.

I must say spam has really gone down on my blog network… sure takes the load off of akismet for comment spam – blocked over 50,000 baddies in the past 7 days.

Oh I see what I did there.. still had the code for the old menus in there for non-siteadmins. Fixed in this version.

https://rapidshare.com/files/417767287/bad-behavior-wpmu.zip

@ovidiu: The only things I changed in it’s behavior was moving the menus to Site Admin (so they are only accessible by siteadmins) and changed the database table and plugin options to store site wide instead of per blog. I also had to move around some files and code so that it would work in the mu-plugins folder. In it’s current state, bad bahaviour isn’t feasible for multisite for all the reasons mentioned already, so hopefully the author will make the needed updates for it. Use my modified version for the time being unless you don’t mind your bloggers managing it’s options, not knowing sitewide stats, and not being able to use http:BL without adding the key to every blog in your network – oh and “bad bahaviour statistics in the blog footer” is enabled by default so it’s displayed in the footer of all the blogs in your multisite. The main reason I made the mod was because it creates a database table for every blog, and for a blog network like mine with more than 10,000 blogs.. that’s a lot of unneeded database tables.

You’ll know BB is active on all your blogs by looking at the BB logs, but as long as the menus are showing up under Site Admin you’ll know it’s working. Since it’s in the mu-plugins folder, there’s no need to “activate network wide” and it won’t show up in the plugins menu.

Maybe you just needed “RewriteEngine On” at the top – none of the rewrite rules would work without it.

You probably haven’t set it up correctly.
https://www.callum-macdonald.com/code/wp-mail-smtp/

Your host may also be blocking outbound connections to that port.

Also it’s not recommended to use gmail smtp if you are going to have many signups. Gmail restricts outgoing emails per day to something like 100.

You’ll need to describe the problem more than that. Why can’t you send email through gmail? Do they not deliver, is wordpress unable to send the emails, do you get any errors, etc.

The New Blog Defaults plugin will give you control over the from email and from name for your wordpress emails – otherwise they will look like they came from “WordPress” as you have just found out.

Well your .htaccess is correct. Lets see your wp-config.php perhaps?

Unfortunately, it has to go in the plugins folder and be activated network wide. It’s not really optimized for multiuser because it creates an SQL table for every blog and stores it’s options per blog – you would have go into each individual blog’s dashboard to see whats been blocked or change the options making it impossible to use the blacklist api feature.

That’s why I created a modified version for WPMU – it’s working great for my blog network. You can put this one in mu-plugins and manage options/logs network wide instead of per blog. Thought I might as well share it.
https://rapidshare.com/files/413778697/bad-behavior.zip

There is, but its not free:
https://premium.wpmudev.org/project/set-password-on-wordpress-mu-blog-creation

If you didn’t do much other than install wordpress and add a few blogs, I would say it’s a problem with your host configuration especially when it comes to internal server errors it’s usually htaccess rules.

Which plugin? If it’s one site that you want to disable a plugin on, you can just go to that blog’s admin backend, plugins menu, and disable it.