Thanks Ikai, it's good to know that the issue will be considered.
On Mon, Apr 18, 2011 at 11:47 AM, Ikai Lan (Google) ika...@google.com wrote:
Points taken. I'll bring up the issue next chance I get.
I can't make any promises though, because some things that should be easy
are actually really
AWESOME!
This is my biggest issue at the moment - something like 25% of my
customers use Yahoo Mail, and don't receive emails they have
requested. DKIM will solve the problem, because I've got it working on
Google Apps for the same email addresses, and those messages get
through. I know this is
Points taken. I'll bring up the issue next chance I get.
I can't make any promises though, because some things that should be easy
are actually really difficult.
Ikai Lan
Developer Programs Engineer, Google App Engine
Blog: http://googleappengine.blogspot.com
Twitter:
Ikai,
I totally understand that you guys want to focus on the interesting parts of
the problem, but you could make one really simple change that would probably
*solve* the problem for most of your users: allow us to set the DKIM header
on outgoing mail. All it would require is allowing write
Ikai-- totally agree re:bulk email, but please please please add DKIM, which
(I'm told) is 90% of the solution for
enterprise/extranet apps that need to use email for workflow. The Big
Reason I chose AppEngine was to get
an integrated solution from one vendor: forcing me to use multiple vendors
+1
On Apr 16, 9:02 pm, n8gray n8g...@gmail.com wrote:
Ikai,
I totally understand that you guys want to focus on the interesting parts of
the problem, but you could make one really simple change that would probably
*solve* the problem for most of your users: allow us to set the DKIM header
+1
On Apr 16, 10:06 pm, Adam Sah adam@gmail.com wrote:
Ikai-- totally agree re:bulk email, but please please please add DKIM, which
(I'm told) is 90% of the solution for
enterprise/extranet apps that need to use email for workflow. The Big
Reason I chose AppEngine was to get
an
It's not an ideal situation, I agree. However - we're just not at capacity
to deal with negotiating with email providers, policing policy violations,
and so forth. Providing an email service isn't anywhere near as trivial as
people think. We don't want App Engine to become a mass emailing service
@Icai
I agree on most of what you write above, and I understand that you
prefer to focus on more important things, also having run Email
services for enterprises in the past I do know it is not trivial.
But
still I believe Email service is a major asset for GAE and dropping
it (or anything
That sounds like a good idea. There's a good chance we'll change the quotas
for email sometime in the near future. When we do that it would make sense
for us to document that we do not suggest App Engine as a service for
sending large amounts of email, and for reliable email delivery, to look at
IMHO it is not a good policy for GAE to abandon(?) services middle way
instead of improving - enhancing those. ;-(
Regards
Nick
On Mar 23, 7:31 pm, Ikai Lan (Google) ika...@google.com wrote:
That sounds like a good idea. There's a good chance we'll change the quotas
for email sometime in the
me 2. Have integrated the SES service within our GAE apps. work good and
solved our problems
sure it would be more nice if GAE can provide email service at the quality
level similar to the Amazon SES one (at least would not be classified as
SPAM), so we dont need to manage both . could we make
I actually think we are moving away from this direction. For customers
sending large volumes of email or who require delivery guarantees, we'll be
encouraging the use of services that are specifically designed for this
functionality.
Ikai Lan
Developer Programs Engineer, Google App Engine
Blog:
Ikai,
On that note, do you have any services besides SES that you
recommend? SES works well with GAE however you must slowly up your
quotas, forcing you to send some mail via SES and some through GAE
until your quotas are adjusted high enough...
On Mar 22, 4:29 pm, Ikai Lan (Google)
SendLabs is another option:
http://dyn.com/enterprise-email/sendlabs-solutions
On 23 March 2011 09:57, Jamie H ja...@mhztech.com wrote:
Ikai,
On that note, do you have any services besides SES that you
recommend? SES works well with GAE however you must slowly up your
quotas, forcing you
Hi Ikai,
thx for your note. with this, we could better decide on which cases we would
like to send emails through GAE and which we would like to use other
external services.
and would it be more formally stated in any documents, or any guideline for
these considerations be documented? if i'm a
I use too random directions for each user.This means, I take its
user.user_id(), build sha1, and send e-mail to each user from
directions like that:
alert-[user]@[app].appspotmail.com
I think you have to enable inbound email for this to work, but i'm not
sure. This is the method I have seen in
Wow, great idea! I have been having some delivery issues lately with
GAE and looking for an alternative.
I just downloaded a pythong Amazon SES library, signed up for SES, and
put it all together and it works like a charm with GAE!
On Mar 20, 10:31 pm, Nickolas Daskalou n...@daskalou.com wrote:
Hi Ernesto,
thx for your suggestion! yes, i think it shall work.
but in general if we can't ask all our users to add our email to their
contact list (or they are not willing to do so), how can emails sent by us
prevent to be regarded as spam? all our subject, body etc. are nothing
spam-liked,
Hi Eric,
Have you looked at Amazon's Simple Email Service (SES)?
http://aws.amazon.com/ses/
Pretty much the same cost as sending email using GAE, except with SES you
only get 2,000 free emails if you're sending email from an EC2 instance.
I haven't used it myself but apparently they scan
Ask the user to add the e-mail from address of your e-mails to their
contacts list, so your e-mails would never been sent to spam again
(for that users, at least).
It's a bit hacky, but can do a great work meanwhile you find another
solution.
On 18 mar, 07:52, Eric Ka Ka Ng ngk...@gmail.com
21 matches
Mail list logo
