welcome email being sent to the site name instead of client email
anarcat - September 7, 2009 - 13:38
| Project: | Provision |
| Version: | HEAD |
| Component: | Code |
| Category: | bug report |
| Priority: | critical |
| Assigned: | Unassigned |
| Status: | closed |
Jump to:
Description
Now this is a weird one. I just reproduced this on HEAD, maybe it also affects 0.3. My welcome email was sent to "testssl" (which got expanded to "testssl@anarcat.ath.cx" by postfix) instead of "anarcat@localhost". The task log does say the right email:
Sent welcome mail to anarcat@localhostBut my mail logs say otherwise:
Sep 7 14:51:49 mumia postfix/smtp[29728]: E34448F440: to=<testssl@anarcat.ath.cx>, orig_to=<testssl>, relay=209.44.112.66[209.44.112.66]:587, delay=1.9, delays=0.25/0.42/0.92/0.26, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as 4FDBB14B89)This is the relevant code in install_6.inc:
$mail_success = drupal_mail('install', 'welcome-admin', $client_email, user_preferred_language($account), $mail_params, $from, TRUE);
if ($mail_success) {
drush_log(t('Sent welcome mail to @client', array('@client' => $client_email)), 'message');
}Obviously, something is wrong with drupal_mail, probably the argument ordering or something...
#1
Hum. I have no idea how this happened in the first place, but I can't reproduce anymore... Postponing.
#2
mig5 says he had problems with $account->mail and used $client_email instead, which was committed to D6. i have backported to d5, maybe that's all we needed to fix this issue.
#3
Yeah my task logs had said they sent to my normal email address too but wasn't the case.
That's weird because this issue only started to occur when that other fix was backported from install_5.inc (the 'create admin account anyway' issue), so it's surprising something needed to be backported in the other direction! I guess more investigation is required on this one.
#4
So nobody can reproduce this anymore, my guess is that we fixed it. Otherwise, i'm sure we'll stumble upon this later in the release cycle.
#5
Automatically closed -- issue fixed for 2 weeks with no activity.