BuddyPress.org

I’ve mentioned this quite a few times on this support forum, if you want to get emails through to the more annoying of the email services out there you must ensure you have a RDNS entry PTA record and also an SPF entry for you domain hotmail is failing to be able to check these two records and thus considering mail from your server to be spam.

One thing this isn’t is a problem with BP or WP it’s about server and domain configuration.

@rossagrant

Here’s quite a comprehensive list of links to help you troubleshoot:
http://answers.google.com/answers/threadview?id=606426

EDIT: that’s actually a rather old thread. This is probably better: http://mail.live.com/mail/troubleshooting.aspx

I dig some digging into this problem since I was having it as well. The user’s account is activated successfully when they click the email. The problem occurs when you login from the activation successful page (activate.php). If the user opens another browser and goes to the site homepage to login, there will be no problem. For me, this was happening because the plugin that I was using to handle logins was including a hidden redirect to the source page in the form. So after the user logged in, it was redirecting to activate.php which by default asks you to activate, even if you are logged in.

So check the html for the form that you use to login and make sure there is no redirect to the source page.

Here’s how to get around activation. I was having the same problem on my test server, since it couldn’t send out activation emails. If you need activation emails enabled, then this workaround will not work for you.

For users that have already been created and cannot login, you can go into the wp_users table in the database and change their ‘user_status’ from ‘2’ to ‘0’ (if you have database access). ‘user_status’ is not used in WordPress — it’s a dead field — but Buddypress uses it to redirect to the homepage if a user has not been activated (aka user_status=2).

To avoid the problem for future user registrations, you can change a file to avoid activation (if you have FTP access). In the buddypress plugin directory, find bp-core/bp-core-signup.php. Find the line that says:
`$wpdb->query( $wpdb->prepare( “UPDATE $wpdb->users SET user_status = 2 WHERE ID = %d”, $user_id ) );`
In my installation (1.2. it is on line 357. Change the 2 on that line to a 0. So it should look like this:
`$wpdb->query( $wpdb->prepare( “UPDATE $wpdb->users SET user_status = 0 WHERE ID = %d”, $user_id ) );`

Now when a new user is created, they will automatically be able to login without their email needing to be confirmed.

Have you checked whether your server can send emails? Have your users checked their spam boxes? They ought to be receiving an email with an activation link.

@v_andreev

Did you try closing the window or tab, and then simply clicking the email link again?

I am posting this here because it might solve part of the problem and it worked for me: I found this <a href "https://buddypress.org/community/groups/buddypress-pending-activations/&quot; While it does not solve the issue of members being able to approve themselves, it does allow the ability to resend an activation link (email) and to manually approve members in the Que. It works with WP 3.1.3 and BP 1.2.8. I hope this helps the scores of people desperately seeking admin approval of new user registrations.

I found this <a href "https://buddypress.org/community/groups/buddypress-pending-activations/&quot; While it does not solve the issue of members being able to approve themselves, it does allow the ability to resend an activation link (email) and to manually approve members in the Que. It works with WP 3.1.3 and BP 1.2.8. I hope this helps the scores of people desperately seeking admin approval of new user registrations.

`Warning: Cannot modify header information – headers already sent by (output started at /path/wordpress/wp-content/plugins/buddypress/bp-themes/bp-default/registration/activate.php:3) in /path/wordpress/wp-includes/pluggable.php on line 897`

As @r-a-y suggests, in my experience at least, that kind of error is almost always malformed PHP files — trailing spaces, unclosed brackets, stuff like that. If you’ve pasted functions into your functions.php or bp-custom.php, look there first, then any other template files you’ve edited.

Don’t use @r-a-y codes

@mikey3d – Is that a general recommendation?

I did say it was test code. Looks like you have whitespace issues in your /registration/activate.php. Delete any trailing whitespace from the beginning of that file.

eg.
`   -spaces – <?php` – Delete that trailing space!

Your htaccess rewrite rules look like it will interfere with querystring variables.
eg. example.com/my-page/?variable=my-test

The only way I was able to surmount the same issue (emails not being sent, i.e. new user notification, password reset emails) was to disable the following plugin:

“BP Disable Activation”
https://wordpress.org/extend/plugins/bp-disable-activation/

Once I disabled this plugin, the missing emails flowed again.

As such, I returned the site to its default state of requiring new users to confirm their accounts.

Yes it already exist: https://buddypress.org/community/groups/bp-disable-activation/

Oh ok ; yes I’m with you now, usually think of duplicate content from the perspective of www and non www it’s really googles issue though, the url refers to the same thing ultimately.

However google trawls links in a page and the links are trailing slashed, from the perspective of inbound links that might not have the trailing slash added it could be an issue I guess.

“and it does support sending email and has for a few new user registrations.”

So it has actually *sent* mail.

Edit:

Your server is not the problem. Not entirely anyway. I signed up to your site and got two emails – one with an activation link and one confirmation email. Exactly like I am supposed to.

So your problem is *not* the server is not sending email. The problem is some of the people signing up are not getting them. Which means it’s mostly on their end. You can do a reverse dns entry, like @hnla stated above, but really that’s all you can do for some places like Hotmail & Comcast.

Not sure why this is a problem? the trailing slash is in essence a nicety in that it means one is asking for a directory rather than a file and it helps the server otherwise the server first searches for a file named /foo before checking if /foo is actually a directory /foo/ but you’re right although all my test sites links terminate correctly / I can manually write the url without and it’s not added but it doesn’t cause any issues – however I may well be missing the point of what you are explaining