🇸🇰Slovakia @matus grinvalsky

Thank you! Now it make sense to me...

I am happy to test 4.x once stable release is available.

Matus

Matus Grinvalsky → created an issue.

Matus Grinvalsky → created an issue.

Matus Grinvalsky → created an issue.

Thanks! Works for me as well.

Actually, this behavior was introduced in version 3.9 and it is because of following chunk of code. Despite the name, the $admin_email holds the list of emails notification should be sent to, not admin email

The list if addresses for notification is populated to bcc and dummy address is used in to fields

      // Set a dummy no reply email if email list is not empty.
      $to = empty($admin_email) ? \Drupal::config('system.site')->get('mail') : 'noreply@noreply.com';
      $params = [
        'body' => $body,
        'subject' => $subject,
        'nid' => $node->id(),
      ];

      // Allow to alter $admin_email
      // by using hook_admin_content_notification_recipients_alter().
      // @see admin_content_notification.api.php
      \Drupal::moduleHandler()
        ->alter('admin_content_notification_recipients', $admin_email, $node);

      if (!empty($admin_email)) {
        $params['bcc'] = $admin_email;
      }

I assume that reason for this change is preventing full list of recipients to be disclosed to everyone on a list. In my opinion, it would be better to make the "to" address configurable instead hardcoding it to dummy address.

Sending/receiving bouncing emails is annoying and can potentially trigger some spam rules.

Matus Grinvalsky → created an issue.