Posted by adshill on February 25, 2009 at 12:51am
| Project: | HTML Mail |
| Version: | 6.x-1.x-dev |
| Component: | Code |
| Category: | support request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed (fixed) |
Issue Summary
Hi there. Great module and very useful for items sent from Rules that otherwise appear in a mess. However, the module is making the "From" address of the contact form come up as my server address instead of the user sending the mail thus making it impossible to reply to mails from the core contact module.
I disabled the module and all works as usual so it is definately the HTML mail module creating this.
Thanks.
Comments
#1
Can anyone help with this? :( All my e-mails are coming from:
annalin@serv01.mxxx.sgded.com
instead of the site e-mail or e-mail of the contact form. At the moment I am having to check in the logs for each e-mail address which is very very long process for a busy site! I really need this great module to display my nodes in e-mail, but this is making it almost unusable.
Any ideas? Thanks so much,
Adam
#2
It looks like the module overrides the pre-existing header content. In the htmlmail.module file at line 20, change this:
$message['headers'] = array('Content-Type' => 'text/html; charset=UTF-8;',
);
To this:
$message['headers']['Content-Type'] = 'text/html; charset=UTF-8;';#3
Works like a dream coyotegrey, Thanks a Lot!! :)
#4
See #338763: Headers being replaced (can't define From:)
#5
Hi,
this is working partly.
The sender is ok, how ever the text is now put in an un named attachment.
This is strange.
Can you help pls
#6
The fix was overwritten by a different release, so this problem is recurring, not a duplicate. However, it isn't critical, so I changed it to normal.
#7
Add me to this. Does not happen on ALL servers, but it does happen on the one I care about...
Good news is, the fix does the trick.
Now, can someone roll that into the next code rev?
#8
Coyote this fixed my issue thanks!!
#9
Fix works. Can it please be rolled into dev or official? Thanks!
#10
Here is a patch made from the current dev that incorporates the changes listed above that fixed it for me
#11
subscribe
#12
The patch from comment #10 worked for me. Thanks mariagwyn!
#13
#14
Automatically closed -- issue fixed for 2 weeks with no activity.