We have a problem with all emails sent via our Gmail API App.
All of them deliver with a warning about the safety of the email
This message seems dangerous. Many people marked similar messages as phishing scams, so this might contain unsafe content. Avoid clicking links, downloading attachments, or replying with personal information.
This happens only when sending an email through our Gmail API but when sent via SMTP will deliver the message without any warning.
This warning message appears on all emails sent via our Gmail API Application, no matter if the sender is a Google workspace user or a free Gmail user.
Can anyone help on this?
Related
Messages sent through the Gmail API to a Gmail address are getting tagged in Gmail with
Be careful with this message. It contains content that's typically used to steal personal information.
The message basically just says test. And the identical content message sent through Gmail SMTP doesn't get tagged with that warning.
It seems really strange that Gmail would mark messages that are coming through a Gmail owned API as suspicious but when they come through SMTP it does not warn about it.
I was getting this as well. Simply removing the 'from' portion of the email solved it for me. If you are authenticated gmail figures that stuff out on its own.
I have a problem sending mail with JavaMail Service in GAE.
I did all the code in the documentation, i debug it online and it work fine, and it count the mail sended in the quota section the problem is, i didn't receive anything, and also checked with the account sender and it's the same there isn't any trace of mail sended. I tried this for some mails address and it's not working too.
Anyone had this problem yet? A solution to this?
The problem is that the mail sended as SPAM on gmail account.
Read doc: https://cloud.google.com/appengine/docs/java/mail/#Java_Authenticating_mail_DKIM
The email used to send the mails must be a member of the application. It can be the problem... It was with me.
https://cloud.google.com/appengine/docs/python/mail/
The link is about python but for sure that the same email rules apply to Java.
For security purposes, the sender address of a message must be one of the >following:
The Gmail or Google Apps Account of the user who is currently signed in
Any email address of the form anything#appname.appspotmail.com or >anything#appalias.appspotmail.com
Any email address listed in Email API Authorized Senders found in the App >Engine Settings page of the Developers Console
Although this Google document describes a simple way for a GAE app to send a message to a Talk/Chat user, apparently this feature has been discontinued. Is there another method for a GAE app to send a message to a Talk/Chat user?
As an aside: for SMS'es from real phones sent to my Google Voice number, each SMS received is also received as an email in my Gmail account. And the sender of the email is 18888888888.19999999999.somegibberishchars-#txt.voice.gmail.com, where 1888... is my GV number and 1999... is the sender of the SMS. I can reply an SMS to the sender by simply sending mail to this email address. This email address does not expire, ie I can still send SMS'es using this months later.
Is there a similar way to deliver messages to Talk/Chat by sending to a specially formatted email address?
I was trying to send emails to my client from my application after few sent mails all mails bounces back with a message saying "You have reached a limit for sending mail. Your message was not sent." And one more thing when i see my developer console gmail api it still showing 0% usage.what is this issue? is this a bug or something else?
There's an extra limit on sending because it's a vector for abuse--it doesn't show up in the developers console but it's the same as sending via SMTP or the web interface.
This seems to have a good overview:
http://www.labnol.org/internet/email/gmail-daily-limit-sending-bulk-email/2191/
I am using the XMPPservice's sendMessage method
to send a message to google mail but the message
can not be sent without any error log.
Thank
A common error source is that the receiver first has to accept an invite from the sender. Only then messages will be relayed to the receiver. Have you sent an invite and was it accepted?
If the Gmail recipient is using Google Apps (e.g. Google Apps for Business), the recipient domain must publish SRV records in their DNS to allow routing of the XMPP packets to the Gmail Chat backend. The vast majority of Google Apps domains will not likely have SRV records configured.
If the recipient is a #gmail.com / #googlemail.com account, then (as #schuppe suggest) the most likely cause of this issue is due to the fact that the recipient did not accept the invite from the sender.