Closed GoogleCodeExporter closed 9 years ago
Verified that mail from GmailApp shows up as from maestro. Posted to see if
anybody else has solved this problem:
http://www.google.com/support/forum/p/apps-script/thread?tid=4253e9bb7e978116&hl
=en
Original comment by blairk...@gmail.com
on 11 Oct 2011 at 4:58
Issue 23 has been merged into this issue.
Original comment by blairk...@gmail.com
on 3 Jan 2012 at 4:53
Sorry, I just noticed the merge notice.
Hi. The maestro reference appears in more than one place. Se below for a
sample from one email. I have replaced the long ID with "XXX". Note
especially the maestro line for Return-Path: which some mailers will try to use?
This is addition to the possible problem of some mailers filtering this as
spam. E.g., see:
https://groups.google.com/a/googleproductforums.com/forum/#!category-topic/apps-
script/services/tGxlioK1ejg
Thanks.
Lester
Return-Path: <XXX.dct@maestro.bounces.google.com>
Received-SPF: neutral (google.com: 131.215.239.119 is neither permitted nor
denied by domain of XXX.dct@maestro.bounces.google.com)
client-ip=131.215.239.119;
Authentication-Results: mx.google.com; spf=neutral (google.com: 131.215.239.119
is neither permitted nor denied by domain of
XXX.dct@maestro.bounces.google.com) smtp.mail=XXX.dct@maestro.bounces.google.com
Original comment by les...@ingber.com
on 23 Jan 2012 at 7:26
Hi,
I also have this problem.
is there a work around for this.
tnx
m
Original comment by michasea...@gmail.com
on 9 Sep 2012 at 8:14
Hi Michaseafood,
Although it's been debated if it matters at all, currently there is no way to
remove this from your sent messages. If you would like to 'star' the issue,
you'll receive updates automatically when the occur.
Thanks for checking out the script!
-Blair
Original comment by blairk...@gmail.com
on 10 Sep 2012 at 1:14
Because I can't really control the status of this bug (up to the Google Script
Apps team), going to close as 'WontFix'.
If in the future there is a way to send without this in the headers I'll
re-open the issue.
Original comment by blairk...@gmail.com
on 18 May 2013 at 8:24
Original issue reported on code.google.com by
blairk...@gmail.com
on 30 Sep 2011 at 10:33