Serendipity Forums

What's the difference between the headers in an email that works and the s9y email that doesn't? In particular, I notice that there are no colons ':' in the headers you quoted here.

Maybe it's got something to do with your spam settings. Try adding the reply-to address to your address book, if you're still interested in getting this to work in GMail.

I don't use GMail for Serendipity, so I can't answer this. I'm just bumping your entry so someone else might have a closer look.

Y'know, I have a GMail account, and a sandbox blog. I could try setting them up to work together.

I assume you just set the "Blog's E-Mail address" in Configuration?

I inserted my Gmail address in the blog configuration, then left a comment. The comment is ready to be moderated, but no email was sent to my Gmail account. Maybe I skipped a configuration step somewhere, like asking for notifications.

So I tried again with the Contact Form plugin. I configured it to send to my Gmail account. I filled the contact form with the name "Judebert" and a home email address. It took a while, but the email eventually got to Gmail. Gmail claimed it came from "me", but the "reply-to" header was my home address. Unfortunately, when I tried to reply, it tried to go to Gmail, instead of the "reply-to" address, just like yours.

So I changed the blog configuration's "from" email in configuration to an address local to the server. I left the Contact Form's configuration "to" address the Gmail address. When I filled out the contact form again, Gmail claimed it came from "Test2", and it tried to reply to my home address, as expected.

I thought perhaps this was an optimization, since mail between Gmail accounts could be handled more efficiently than mail that needed to be sent externally. So I tried another test: I changed the blog configuration email set to my wife's Gmail account. The reply was destined for my home address.

In short, it looks like Google messed up the Gmail replies. Anything "From:" the <i>current account's address</i> is sent to the current account; otherwise the "reply-to" field is honored as usual.

The workaround is to set the blog address to something *other* than your Gmail address. Anything should do. As long as Gmail doesn't think the email came from "me", it'll do what it's supposed to.