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.
| Comment | File | Size | Author |
|---|---|---|---|
| #10 | htmlmail-382950.patch | 739 bytes | jrglasgow |
Comments
Comment #1
adshill commentedCan 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
Comment #2
coyotegrey commentedIt looks like the module overrides the pre-existing header content. In the htmlmail.module file at line 20, change this:
To this:
$message['headers']['Content-Type'] = 'text/html; charset=UTF-8;';Comment #3
adshill commentedWorks like a dream coyotegrey, Thanks a Lot!! :)
Comment #4
timtrinidad commentedSee #338763: Headers being replaced (can't define From:)
Comment #5
zwirbel commentedHi,
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
Comment #6
Setzler commentedThe 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.
Comment #7
cayenne commentedAdd 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?
Comment #8
djinn23 commentedCoyote this fixed my issue thanks!!
Comment #9
mariagwyn commentedFix works. Can it please be rolled into dev or official? Thanks!
Comment #10
jrglasgow commentedHere is a patch made from the current dev that incorporates the changes listed above that fixed it for me
Comment #11
davea commentedsubscribe
Comment #12
matt v. commentedThe patch from comment #10 worked for me. Thanks mariagwyn!
Comment #13
Christopher Herberte commented