Mail Question

[Joshua Smith]

One of my testers sent me the attached capture of the welcome message my app sent them.

Their reaction was that the gobledegook after "via" made them think there was something fishy about this email, and it might not be safe to follow the link.

I don't blame them.

Is there a way to NOT have this junk show up and scare off my potential users?

-Joshua

[Christopher]

Where is the image attached? I cannot see where it would be here. You
might try uploading the image to an image hosting site and post the
URL here.

[Joshua Smith]

Hmmm.  I got the attachment.  I guess google groups are inconsistent.

It was a picture of a gmail inbox. It looks like this:

sup...@q----------e.com via m3kw2wvrgufz5godrsrytgd7.apphosting.bounces.google.com to me show details 4:05 PM (9 minutes ago)

(I've hidden the email domain with -- characters).

If I open the details, it shows:

mailed-by m3kw2wvrgufz5godrsrytgd7.apphosting.bounces.google.com

So apparently, google thinks its a good idea to name their outgoing mail servers like this, and they think its a good idea to show this garbage to their users.

I'm concerned that it is going to scare off users.

Any idea if amazon mail service looks any less scary?

-Joshua

-- 
You received this message because you are subscribed to the Google Groups "Google App Engine" group.
To post to this group, send email to google-a...@googlegroups.com.
To unsubscribe from this group, send email to google-appengi...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.

[Christopher]

We send a lot of emails and haven't had this issue. Can you give an
example of how you are using the API?

On Oct 14, 4:19 pm, Joshua Smith <JoshuaESm...@charter.net> wrote:
> Hmmm.  I got the attachment.  I guess google groups are inconsistent.
>
> It was a picture of a gmail inbox. It looks like this:
>

> supp...@q----------e.com via m3kw2wvrgufz5godrsrytgd7.apphosting.bounces.google.com to me show details 4:05 PM (9 minutes ago)

>
> (I've hidden the email domain with -- characters).
>
> If I open the details, it shows:
>

> mailed-by       m3kw2wvrgufz5godrsrytgd7.apphosting.bounces.google.com

[Joshua Smith]

Take a look at one of the emails you send to a gmail account (in the web browser gmail interface). I suspect you will see this junk. I never noticed this before because my mail program doesn't show this junk (although it is there in the message if I view raw headers).

My call is simple as can be:

mail.send_mail(sender=MAIL_SENDER,
to=user.email,
subject="Welcome to {redacted}",
body=plain,
html=rich
)

[Christopher]

I see the long garbage as the field in the Return-Path field of the
email, but I have to turn on "Show all headers" in order to see this.
We use the Java SDK but is pretty much the same. Maybe it has to do
with what the plain/rich strings look like. Is the rich field proper
html?

Message msg = new Message();
msg.setSubject(subject);
msg.setSender(sender);
if (recipients.size() == 1) {
msg.setTo(recipients);
} else {
msg.setBcc(recipients);
}
msg.setReplyTo(replyTo);
msg.setTextBody(textContent);
msg.setHtmlBody(htmlContent);
msg.setAttachments(attachments);
try {
MailServiceFactory.getMailService().send(msg);
} catch (IOException e) {
e.printStackTrace();

[Joshua Smith]

I'm guessing that you are not using the gmail web interface (since there is no "show all headers" button there).

Could you have a look at one of your emails in gmail, and confirm/deny that it is electing to expose this garbage to the user?

Interesting point about the HTML. My HTML does not include html and body elements, but it's otherwise proper (and quite simple).

[Christopher]

I see what you're saying. GMail displays the Return-Path info as part
of the message. I'm not sure if there is anything you could do about
that. If anything, you might have to specify a header field on the
email that would indicate not to display this info or something. You
could try setting the Return-Path header to null or empty string, but
my guess is that this would not be allowed. If you test this out could
you post your results? The mail api we use in java has a setHeader
method, and I would assume the python has an equivalent.

[Ernesto Oltra]

You could always use Amazon SES instead of Appengine mail.

If you don't feel like managing Amazon yourself, http://sendgrid.com/ (built in top of Amazon SES) has articles, and tutorials to configure your DKIM and all this things to avoid the "via ..." messages in gmail and the security alerts in hotmail. It is the option my client has configured right now.

[Joshua Smith]

Which level did they go for? We're not doing bulk mailing, so the Lite package looks nice. But would we regret not getting the "Advanced Deliverability Features"? $80/month is awfully steep for something I don't really understand whether I need!

On Oct 15, 2011, at 5:29 AM, Ernesto Oltra wrote:

You could always use Amazon SES instead of Appengine mail.

If you don't feel like managing Amazon yourself, http://sendgrid.com/ (built in top of Amazon SES) has articles, and tutorials to configure your DKIM and all this things to avoid the "via ..." messages in gmail and the security alerts in hotmail. It is the option my client has configured right now.

--
You received this message because you are subscribed to the Google Groups "Google App Engine" group.

To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/rpOfoPMbTrQJ.

[Ernesto Oltra]

For the "via ..." problem you need what they call "Whitelisting", so Silver package is the minimum. That said, we have the Bronze package. They sign all the emails you send, so in Gmail:

X...@XX.appspotmail.com via sendgrid.info

sent by     sendgrid.info

signed by  sendgrid.info

That was enough for my client, and deliverability was **great** even when we were in the Lite package.

I know he received two/three reports of people saying that they saw the "via ..", then they went to the website (it was not so scary as the 12355...bounce.appengine.. etc) and they saw clearly it was only a mail company, so they trusted the email.

2011/10/15 Joshua Smith <Joshua...@charter.net>

[Ernesto Oltra]

I forgot to mention they offer click tracking on the links of your email, view tracking (using beacons) and have better "email don't exist", bounce rates, etc; stats. Support is great too and when starting they have a free tier so you can test the service before using it

The API is as simple as a POST urlfetch to an URL using your secret key.

2011/10/15 Ernesto Oltra <ernest...@gmail.com>