CiviCRM Community Forums (archive)

Posting this in case anyone else is trying to use gmail (in particular a google apps gmail account) for civimail.

I was able to get this to work, except for one problem.  When someone replys to a mailing it is properly processed AND I get it back in the correct mailbox as a reply, BUT when I try to reply back to them it doesn't address the mail to them.  Instead it addresses the mail to me (same mailbox), even though the reply-to mail header clearly says it should go back to them.

Anyway, banged my head against a wall for awhile thinking it was somehow a civimail problem before stumbling across this thread...

http://www.google.com/support/forum/p/gmail/thread?tid=4641785bf01dbd9a&hl=en

Hopefully when gmail fixes that bug it will go away.

In the meantime, I'm wondering if there is some workaround.  The bug is VERY particular.  It appears that gmail only disrespects the reply-to header when the From header is the same as the mailbox you are in.  So if I've configured my outgoing mail as follows

mail from civi from myoutgoing@mydomain.com
and the reply channel at myincoming@mydomain.com
when someone replies it goes to myincoming+etc...@mydomain.com
The processor processes it and forwards it on back to myoutgoing@mydomain.com with a FROM header of myoutgoing@mydomain.com and a reply-to header of the address of the person who replied.

SO, is there some code workaround where I can have the processor forward it back to my account with something OTHER than myoutgoing@mydomain.com as the FROM header?  Perhaps I can have it put myincoming@mydomain.com as the FROM header instead just for that particular case?  Might help me avoid this bug while google gets this bug fixed.

SO, is there some code workaround where I can have the processor forward it back to my account with something OTHER than myoutgoing@mydomain.com as the FROM header?  Perhaps I can have it put myincoming@mydomain.com as the FROM header instead just for that particular case?  Might help me avoid this bug while google gets this bug fixed.

You’d need to hack the reply-processing code. In general, we only know that emails with From set to myoutgoing@mydomain.com work; it’d open a new can of worms if CiviMail started forwarding replies with arbitrary Froms (e.g., it’d be hard to track why only replies are not working if the localhost server bounced everything except myoutgoing@mydomain.com – and maybe a couple of others, to make stuff more complicated).

To be a bit more constructive: you want to edit CRM/Mailing/Event/BAO/Reply.php, the send() function, and add an explicit From: header there.