We are a group of researchers from Yale University building a tool to finding bugs in configurations files. To evaluate the effectiveness of our tool, we randomly selected 1000 open source configuration files to verify and are requesting feedback on our error report. Your file https://raw.githubusercontent.com/megumiteam/amimoto/b5ff72de9ac596b5666c85cc1502a60caac124e3/etc/my.cnf was among those files. When we ran our tool your file, it reported the following potential errors.

[INTEGER RELATION ERROR: Expected innodb-thread-concurrency[mysqld] <= innodb-log-file-size[mysqld]
Found values: ["innodb-thread-concurrency[mysqld]=16","innodb-log-file-size[mysqld]=16m"]
In the training set we saw: ">=" 0 times, "<=" 48 times, "==" 2 times

INTEGER RELATION ERROR: Expected query-cache-type[mysqld] <= max-allowed-packet[mysqld]
Found values: ["query-cache-type[mysqld]=1","max-allowed-packet[mysqld]=1m"]
In the training set we saw: ">=" 0 times, "<=" 55 times, "==" 1 times

FINE GRAINED ERROR: Expected innodb-flush-log-at-trx-commit[mysqld] * tmp-table-size[mysqld] <= innodb-buffer-pool-size[mysqld]
Found values: ["innodb-buffer-pool-size[mysqld]=64m","innodb-flush-log-at-trx-commit[mysqld]=2","tmp-table-size[mysqld]=64m"]
In the training set we saw: ">=" 3 times, "<=" 65 times, "==" 0 times
]

The training set referenced in the report is taken from the industrial configuration files at https://github.com/tianyin/configuration_datasets. Note that even if your system is currently working, these bug may manifest itself only under large traffic loads or different system environments.

If you feel the any of above errors may indeed cause problems either on your system, or a different system, please comment on this issue report in the space below. This will help use to improve our tool. If you do not believe this is a potential bug, please feel free to close this issue. If possible we would appreciate your feedback before July 27.

If you would like find out more about how we detected these bug, you can find the open source tool at https://github.com/santolucito/ConfigV. For a quick overview of this tool, you can watch this video at https://youtu.be/plliEh-5MpM. If you have further questions, or would like to get involved with this project, feel free to reach out over email at [email protected].

Thank you for your time!

一部コアの問題のような気もしますが、ここでも報告させて頂きます。

ユーザーをダッシュボードから新規追加

ユーザー名：test
メールアドレス：[email protected]

エラーメッセージ

Fatal error: Uncaught exception 'phpmailerException' with message 'Invalid address: wordpress@_' in /var/www/vhosts/i-XXXXXXXX/wp-includes/class-phpmailer.php:946
Stack trace:
#0 /var/www/vhosts/i-XXXXXXXX/wp-includes/pluggable.php(352): PHPMailer->setFrom('wordpress@_', 'WordPress')
#1 /var/www/vhosts/i-XXXXXXXX/wp-includes/pluggable.php(1726): wp_mail('hogehoge@...', '[SITE NAME]')
#2 /var/www/vhosts/i-XXXXXXXX/wp-includes/user.php(2350): wp_new_user_notification(35, NULL, 'both')
#3 [internal function]: wp_send_new_user_notifications(35, 'both')
#4 /var/www/vhosts/i-XXXXXXXX/wp-includes/plugin.php(524): call_user_func_array('wp_send_new_use...', Array)
#5 /var/www/vhosts/i-XXXXXXXX/wp-admin/includes/user.php(196): do_action('edit_user_creat...', 35, 'both')
#6 /var/www/vhosts/i-XXXXXXXX/wp-admin/user-new.php(116): edit_user()
#7 {main} thrown in /var/www/vhosts/i-XXXXXXXX/wp-includes/class-phpmailer.php on line 946

原因

WordPress4.6より、wp_mailメソッド内で、phpMailerのsetFromメソッドが使用されることになっている。
参考：https://core.trac.wordpress.org/changeset/38287

Nginx環境下だと、$_SERVER['SERVER_NAME']の値は_となっており、メールアドレスがwordpress@_となる。
以上により、phpMailerのsetFromメソッドが例外を発生させる。

ちなみに、$_SERVER['SERVER_NAME']の値を参照するかはコアのチケットでもやりとりされているがマイルストーンはついていない。
参考：https://core.trac.wordpress.org/ticket/25239

対策

wp_mailのfromメールアドレスはフィルターで書き換え可能なので、今のところ以下で回避しています。

function my_wp_mail_from( $original_email_address ) {
    return 'wordpress@' . parse_url( get_home_url( get_current_blog_id() ), PHP_URL_HOST );
}
add_filter( 'wp_mail_from', 'my_wp_mail_from' );