[drupal-devel] [bug] Fix error reporting for failed mails to users

nedjo drupal-devel at drupal.org
Sat Apr 9 14:36:39 UTC 2005

Issue status update for http://drupal.org/node/20139

 Project:      Drupal
 Version:      cvs
 Component:    user.module
 Category:     bug reports
 Priority:     normal
 Assigned to:  Anonymous
 Reported by:  nedjo
 Updated by:   nedjo
 Status:       patch

There are (at least) four types of actions we sometimes want on mail
attempts: logging (both success and failure) and a user response
message (again, both success and failure).  So, even if user_mail()
handled logging (e.g., through two additional optional arguments passed
in, success and failure messages), we would still have to test for
success or failure of the call to know what message to return to the
Or else pass in four arguments, with the user message (success or
failure) returned.  But that seems awkward at best, and also defeats
the desirable practice of returning false on failure.
Anyone see an elegant way to handle this programatically?  If not,
handling each call separately as I've done is probably the way to go.


Previous comments:

April 7, 2005 - 14:12 : nedjo

Attachment: http://drupal.org/files/issues/user-mail-error-messages.patch (7.2 KB)

The user module has error handling for failed emails sent on password
changing, but not yet in other cases, so that users may register and
get a message that email has been sent when in fact it has not, an
issue reported, e.g., here [1].  This patch adds tests for mails sent
on  user registration, generating appropriate user feedback (e.g., 
"Unable to send mail", etc.) and logs errors to the watchdog.
[1] http://drupal.org/node/20026


April 7, 2005 - 14:16 : killes at www.drop.org

Looks goog, +1. I also consider the lack of tests a bug.


April 7, 2005 - 15:49 : Dries

Maybe we can extend user_mail() to log failed mail() attempts?  Like
that, all such instances would automatically get logged.


April 7, 2005 - 16:35 : killes at www.drop.org

user_mail() has no idea of the context in which it is called. So error
messages would be vague at best. I think the patch should go in as it

More information about the drupal-devel mailing list