Expand my Community achievements bar.

SOLVED

Gmail Email Service not working in Connected Asset (Remote DAM )

Avatar

Level 1

I have enabled 465 port through following documentations: https://experienceleague.adobe.com/docs/experience-manager-learn/cloud-service/networking/examples/e... and https://developer.adobe.com/experience-cloud/cloud-manager/reference/api/#operation/enableEnvironmen...

No we are using GMAIL as SMTP server for now.

Following are the configuration

I have followed to enable the advanced networking option.

Following are the networking configuration:

1) PUT request-->https://cloudmanager.adobe.io/api/program/29357/environment/92253/advancedNetworking Body: { "nonProxyHosts": [ "smtp.gmail.com" ], "portForwards": [ { "name": "smtp.gmail.com", "portDest": 465, "portOrig": 30002 } ]

2) After enabling the advanced Networking option ,the POST request is-> https://cloudmanager.adobe.io/api/program/29357/networkInfrastructures Body : { "kind": "flexiblePortEgress", "region": "wa1" }

After enable the advanced Networking , we are able to get the result as port is enabled: https://cloudmanager.adobe.io/api/program/29357/environment/92253/advancedNetworking

But the email is not getting triggered.

Anyone please help me on this.

Thanks in advance.

1 Accepted Solution

Avatar

Correct answer by
Level 7

Now, it seems to be an issue from gmail side. 

This typically is an indication that one of the following reasons listed below is affecting your inbox:

 

1) You have too many concurrent connections/services synched with this email address (Note: Every time you connect an inbox to a service, whether it be a mail client, an online tool, or logging into a webmail client, this counts as a connection. Under Google, the limit is 10 concurrent connections and some services can utilize multiple concurrent connections)

2) You/someone else has attempted too many logins using an incorrect password within a short period of time

3) You have reached an email sending limit under your inbox and are temporary locked out of making any new connection attempts to this inbox.

4) You do not have DKIM setup properly and Google is getting hung up authenticating your inbox.

 

Refer this for last one - 

https://confluence.atlassian.com/jirakb/too-many-login-attempts-error-using-google-smtp-with-jira-se... 

 

View solution in original post

3 Replies

Avatar

Level 7

Have you checked the logs? What error it is giving?

For any such issue it is important to find out the root cause and that you can only get it from the logs. So, carefully examine the logs if you don't find any meaning information then enable the debug log and see what error it is showing.

 

Avatar

Level 1

I am getting the below error in log:

Caused by: javax.mail.AuthenticationFailedException: 454 4.7.0 Too many login attempts, please try again later. t1-20020a628101000000b0050d47199857sm3007323pfd.73 - gsmtp

Avatar

Correct answer by
Level 7

Now, it seems to be an issue from gmail side. 

This typically is an indication that one of the following reasons listed below is affecting your inbox:

 

1) You have too many concurrent connections/services synched with this email address (Note: Every time you connect an inbox to a service, whether it be a mail client, an online tool, or logging into a webmail client, this counts as a connection. Under Google, the limit is 10 concurrent connections and some services can utilize multiple concurrent connections)

2) You/someone else has attempted too many logins using an incorrect password within a short period of time

3) You have reached an email sending limit under your inbox and are temporary locked out of making any new connection attempts to this inbox.

4) You do not have DKIM setup properly and Google is getting hung up authenticating your inbox.

 

Refer this for last one - 

https://confluence.atlassian.com/jirakb/too-many-login-attempts-error-using-google-smtp-with-jira-se...