You’re right, it’s the new user notification plugin that I had forgotten about downloading.
It’s not the email to the new user that’s messed up, it’s the email to me telling me that a new user signed up.
By adding the period wouldn’t that only block stuff from @123.mail.ru, @whateverelse.mail.ru, etc. and not @mail.ru? It’s the @mail.ru that seems to be the problem and not subdomains of mail.ru.
Works great, although I added a couple of rewrite rules.
/forum/profile to /forum/profile.php and /forum/tags to /forum/tags.php
The profile and tags pages were still returning 404 headers.
Ok, that wasn’t the plugin I thought it was. That one worked pretty well, minus a couple of glitches. It was still sending a 404 header for profile and tags pages so I added /forum/profile and /forum/tags to the rewrite rules and now they all return 200 headers.
Perfect. Thank you.
Just to make sure I’ve got it setup right. I’ve checked the Enable checkbox on top and added *mail.ru in the blacklist box. Whitelist box is empty. Sound correct?
I looked at doing that, but won’t it cause any non-existing page to show a 200 header as well?
When I added the key to wp-config it wouldn’t let me login into the wp admin either. What I had done was put the define() line at the end thinking that would work. I moved it up under the other define() line instead of the very end and the permissions problem went away.
What I did was edit the header file to include the code to load the WordPress stuff and then just included the header file from the WordPress theme. Then edited the footer.php file to just include the footer from WordPress. I did go through and add a few conditionals to the header.php so that different stuff would be in the <head> section depending on whether I was in forum or out of forum.
