Automate Gmail replies with canned response and Filters

I am trying to use Canned Responses within the Google Filters. Most times it works and sends a response to the sender. But I discovered that certain inbound emails it sends it to a different address and not the specified FROM address. We get emails from a WebForm service using a form on our website, that once submitted is sent to our support email account. The inbound email has the basic information entered by the customer. The service generates an email with all the info customer entered, and sends it to us with the FROM address being the user's email address he was required to enter in the "email" field. If you MANUALLY reply back to the Webform email it goes to the proper email address, the customer's email address that they filled in the form. If I use the Canned Responses in a Google filter to send a "confirmation email" to this very same email it fails to go to the customer's specified email address in the FROM field. Instead it goes to the RETURN-PATH header field from the email sender (ie "no-r...@[login to view URL]") After experimenting with this I determined that a Canned Response in any Filter created would only go to the RETURN-PATH. It ignores the FROM header field AND the REPLY-TO header field (if it exists) within the inbound emails. It doesn't appear this action follows the RFC # 822 recommendation in section 4.4.x for automatic replies. (Note that the RFC spec says "recommendation" and not "required") Hence this feature will not work for any email sent by someone other than what is specified as the REPLY-TO address. From the spec it implies that the RETURN-PATH should only be used for mail delivery error messages back to the actual originator of the message. That any other replies to delivered messages should go to REPLY-TO or FROM, in that order of priority. So anyone experience this issue? I can't really tell if this is a problem with the add-on lab OR if it a problem with how Google allows it to be integrated into the filters option. I have no idea how to contact the developer of this app to see if what I found is true and if there is a fix for it. Calling Google Support didn't help as they consider this a problem with the add-on. Not sure what to do about this. Anyone got some insight?