Could you please release a new full release? (the existing should not be recommended )
I nearly pulled all my hair out trying to figure out why my emails were screwed.

It would be nice for other folks to not have to go through that .. if you put out a new release (not a dev version) it will notify all people with this module installed and they can save themselves the stress of this elusive bug.

I had enabled your module long ago and not realized the error it created until much later ... I thought it was something wrong on my server so I spent a whole day digging through that only to realize it indeed had to be a module problem ... then I had to go down the list un-installing each module to find out which was causing the problem. It wasn't apparent that your module would screw & chew the headers so it took a while! lol

Thanks for fixin it though!!!
Cheers!
^_^

Comments

timtrinidad’s picture

timtrinidad commented

Ditto.

rstryker’s picture

rstryker commented

I just marched down this same path.

Macronomicus’s picture

Macronomicus commented

Oooh .. damn that sucks!

rstryker’s picture

rstryker commented

Yea. I was only baffled for about a week though. Sounds like you had a rougher time of it.

Macronomicus’s picture

Macronomicus commented

Naw .. I got it after a very long day cause my hosting provider assured me it was nothing to do with my server and that I should look at drupal modules to find the problem. Im sure I would have been feeling around in the dark a bit longer with out that tip off!

I can see there are about 300 or so folks using this module .. I wonder if they've noticed their root account is being put on display in such a way! Not good at all! lol IMO its critical to get this fix in the recommended release!

rstryker’s picture

rstryker commented

I went the support route with my hoster as well. I felt a little dunce-like after insisting that there was some PHP or mail server property that had been mucked with. :)

Setzler’s picture

Setzler commented
Category: task » bug

Please fix. Just commit that bug fix. Seriously, that's all you need to do.

Christopher Herberte’s picture

Christopher Herberte commented
Status: Active » Fixed

Fixed in 6.x-1.1

Status: Fixed » Closed (fixed)

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