WordPress.org

Making WordPress.org

Opened 21 months ago

Last modified 2 months ago

#1979 new defect

Forum notification emails use "to" as "noreply@wordpress.org"

Reported by: sterndata Owned by:
Milestone: Priority: low
Component: Support Forums Keywords:
Cc:

Description

See https://wordpress.org/support/topic/bug-wrong-to-field-in-new-mails/ Email seems to be sent with the receiver BCC'd, while the TO is noreply@…. Expecting the TO address to be set to the email's receiver.

Change History (5)

#1 @Ipstenu
21 months ago

This may be a 'can't fix' as the old system was bbpress1 and this is WordPress so it uses the same email as everything else.

I know we're 'expecting' it to us, but it just means updating filters.

#2 @dd32
21 months ago

This was a change in bbPress2.6 whereby all subscribers to a thread are emailed with a singular email BCC'd, rather than the previous behaviour of individual emails for each subscriber (which didn't always scale).

We can switch this back to sending individual emails if preferred, question is do we really need to?
We may also need to do this to ensure that emails actually get sent though, as noted in the above change, some servers have limits to the number of BCC's allowed (I'm not sure what the w.org email servers limits are)

The code to filter it would be something hooked to wp_mail doing something like..

if ( $to == 'noreply@..' && !empty( bcc ) ) {
   foreach ( bcc ) {
      wp_mail( bcc, $other_args )
   }
  return false;
}

#3 @netweb
21 months ago

There were further filters added in bbPress:changeset:5409, and there is a proposal to use cron for emails in #bbPress2797

This ticket was mentioned in Slack in #forums by clorith. View the logs.


2 months ago

#5 @Clorith
2 months ago

  • Priority changed from normal to low

We should wait for bbPress to move over to using cron for email scheduling, as this can easily be many looped emails in some situations (as we'd not want to send to multiple recipients to avoid disclosing emails of those involved in a topic between the participants).

Note: See TracTickets for help on using tickets.