By cayenne on

I've upgraded a nicely-working D5 site to D6.11. Pretty much everything seems good, except that mail, which used to come from "website@example.com" now comes from "apache@webhost.com"

Obviously, that's not the desired result. I have carefully checked the site information page, and the desired mail (hosted on gmail) is there.

This is a D6 installation on Redhat, with PHP 5.1.6.

I'm confident that there's a simple fix, but my search of the web has not found it....

⋅ Categories: Drupal 6.x

Comments

cog.rusty’s picture

cog.rusty commented

Strange. Why would Drupal edit an email address?

Are those emails coming from Drupal, or are they cron notifications or anything similar?

Besides the site information page, do you have any email-related module with it own settings? Try a search for that string in your whole drupal database with phpmyadmin.

cayenne’s picture

cayenne commented

I did the search, and no dice. I'm not surprised, because the email is the host's default sending address. It feels like Drupal is not using the sending address I specified.

I had tried the SMTP mail module, but it just gave me the White Screen of Death.

I have now tested the Contact form, and it sends from Apache@(webhost).com, too!

:)

cayenne’s picture

cayenne commented

Well, it's in the config somewhere. I used the exact same code with a new database and the problem is gone. I have to use the existing database, but this narrows it down a bit.

:)

cog.rusty’s picture

cog.rusty commented

From what I understand from http://api.drupal.org/api/function/drupal_mail/6 if a 'site_mail' variable has not been set then PHP's 'sendmail_from' is used.

$default_from = variable_get('site_mail', ini_get('sendmail_from'));

Take a look in the variables table in the two databases at the 'site_mail' variable.

cayenne’s picture

cayenne commented

Darn. When I disabled that module, the problem went away.
I hope I can work around that, because I really like the HTML mail module.

M

:)

cog.rusty’s picture

cog.rusty commented

That seems to be a known issue, fixed and broken again. See:

http://drupal.org/node/382950
http://drupal.org/node/338763