So sites, when provisioned, are sending an e-mail, where for a while they were not, or were sending an e-mail to www.example.com@aegir.yourdomain.com (i.e using the site url as part of the email address). I fixed that in #570600: welcome email being sent to the site name instead of client email

However now the e-mails that are sent, are completely blank. I think a couple of people reproduced this but it got lost in the cracks somewhere. It's just been brought to my attention again and I realise this is consistently reproducible in HEAD and presumably the 0.4 alpha release.

Acbot says this started occuring around the 8th September for him.

This is possibly part of #486934: broken IPC communication on Drupal 6 (AKA "welcome email not being sent"), anarcat reports the same issue in comment #23

CommentFileSizeAuthor
#2 580264_blank_mail.patch1.78 KBmig5

Comments

anarcat’s picture

anarcat commented
Version: » 6.x-0.4-alpha1

I confirm this issue.

Anonymous’s picture

Anonymous (not verified) commented
Status: Active » Fixed
StatusFileSize
new 580264_blank_mail.patch1.78 KB

So this turned out to be because we lost the entire install_mail() function which drupal_mail() depends on in install_send_welcome_email(), in drupal 6.

I think we lost this in an earlier fix where we backported something from drupal5? You can see the function is removed entirely in this diff between 1.15 and 1.14.

I've put it back in and committed to HEAD. I also confirmed that Drupal 5 doesn't need it, drupal_mail() was different back then.

Since (in my opinion) this is a fairly nasty bug that got into the 0.4 alpha, attached is a patch as well for those who don't want to work off HEAD.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

lloydpearsoniv’s picture

lloydpearsoniv commented
Status: Closed (fixed) » Active

how do you run the the patch or use head???

Anonymous’s picture

Anonymous (not verified) commented
Status: Active » Closed (fixed)

To apply the patch, make sure you have the 'patch' program installed on your server. On Debian/Ubuntu, apt-get install patch

download this patch to your server

In this particular case, I submitted a non-clean patch accidentally, but you can still apply it

1) backup /var/aegir/.drush/provision to somewhere else for safety
2) edit your aegir user's crontab and comment out the dispatch entry (unless you know you'll be very quick at applying the patch before the queue tries to run again and in case it breaks your Provision :) )
3) cd /var/aegir/.drush/provision/platform/drupal
4) patch -p0 < /path/to/the/patch/file

If it reports any failures or conflicts, you'll want to remove it all and restore the provision module from your backup.

Read the Drupal documentation if you're not sure.

lloydpearsoniv’s picture

lloydpearsoniv commented

is there a way i can get it to resend the welcome email so that i can login to the site that was created?

Anonymous’s picture

Anonymous (not verified) commented

You could go to the site and click 'I've forgotten my password' and have a onetime login link e-mailed to you? I don't think we do anything to prevent a normal Drupal action like that.

Otherwise you might be interested in my 'Login Reset' drush command I wrote:

#567094: Password reset link

You can git clone my repo, drop the 'login_reset' folder into /var/aegir/.drush and then run /var/aegir/drush/drush.php --root=/var/aegir/drupal-6.14 --uri=http://example.com login_reset where that root is the relevant platform that your site's installed inside. and obviously substitute the --uri

Anonymous’s picture

Anonymous (not verified) commented
Issue tags: +aegir-0.3-hotfix