After enabling and creating a new article, I ran the drush cron to send the notifications. I received these messages (edited for privacy):
in_array() expects parameter 2 to be array, null given notify.module:743 [warning]
exim: bad -f address "Your Sitename": missing or malformed local part (expected word or "<")
Error sending email (from webmaster@sitename.com to webmaster@sitename.com with reply-to not [error]
set).
in_array() expects parameter 2 to be array, null given notify.module:743 [warning]
exim: bad -f address "Your Sitename": missing or malformed local part (expected word or "<")
Error sending email (from webmaster@sitename.com to youruser@yourplace.com with reply-to not set). [error]
Cron run successful. [success]
Unable to send email. Contact the site administrator if the problem persists. [error]I got this error for each of my users. There may be two issues here or they may be part of the same thing. It seems that the reply-to address is either not set at all or is set to the Site Name with an expected email address after it in <>
For example:
Site Name <site_email@site.com>
Regardless, the notification did not reach my users, even though the logging message (in /admin/reports/dblog) did say it was successfully sent:
User Your User (youruser@yourplace.com) notified successfully.
The same errors that appeared above appear in logging as well, but the exim messages did not.
| Comment | File | Size | Author |
|---|---|---|---|
| #5 | reply_to_update-2952325-5.patch | 541 bytes | kferencz91 |
Comments
Comment #2
joverstreet001 commentedComment #3
joverstreet001 commentedComment #4
joverstreet001 commentedI updated to the latest version and the site name issue seems to be resolved, but the emails still aren't being sent. The only errors I'm getting are:
Unable to send email. Contact the site administrator if the problem persists....when I'm choosing 'Send batch now' and the log shows the same error as described above:
Error sending email (from webmaster@sitename.com to youruser@yourplace.com with reply-to not set).I've seen a couple of other modules with this error such as https://www.drupal.org/project/smtp/issues/2622678, where it may be that there's just an issue sending emails and this message is a side-effect.
Other things (like resetting passwords or activating a user) are sending emails without issue.
Any ideas on what's causing the reply-to not set issue?
Comment #5
kferencz91 commentedThe quotation marks around the $messagefrom variable in notify.module seemed to be the issue for me. Once I removed them, notifications were sent. Patch attached (first contrib patch, so sorry if the naming convention or anything is off! Please advise if it needs updated!)
Comment #6
kferencz91 commentedComment #7
joverstreet001 commentedThank you @kferencz91 for working on this! I got around this particular issue by loading the SMTP Authentication Support module (https://www.drupal.org/project/smtp), which allows me to explicitly define things like the From address.
I'll try to load up a test environment without it and test your patch when I have some extra time. This module seems like it would be in more demand, but it seems to need some developer attention.
Thanks again!
Comment #8
gisleUnfortunately, nobody has signed up for the vacant position as maintainer of the Drupal 8 version of Notify.
I actively maintain the Drupal 7 version (and I have clients that are paying me for doing it). As for the Drupal 8 version, I have no sponsorship.
However, I will commit Drupal 8 patches created by the community to the repo, but only after the community have tested them and declared them to be RTBC.
Comment #9
joverstreet001 commentedGisle,
I really appreciate all of the work you've done on this project. I wish I was more of a developer and that I could help out, but I'm more on the devops side and would probably break more things than I fixed. Let me know if there are things I could do to test or troubleshoot this module or help out in some other way.
Thanks again!
Comment #10
vuilComment #11
vuilComment #13
vuilThe patch has been committed! Thank you.