jiocloud-devops team mailing list archive

[Mayank Kapoor <mayankkapoormail@xxxxxxxxx>]

We've found that the issue is between the CRM/ESB -> Gateway -> Google
Server to send email. Probably related to the Internet Access being
removed for a particular gateway node. Probably related to the internet
connectivity being removed from a server, which was flagged as malicious
by security team. Waiting for Abhishek to send Private IP of the gateway
server to check if that was the server for which Network DevOps removed
connectivity.

** Changed in: jio
       Status: New => Confirmed

** Changed in: jio
     Assignee: Reliance Jio DevOps (jiocloud-devops) => Mayank Kapoor (mayankkapoor)

-- 
You received this bug notification because you are a member of Reliance
Jio DevOps, which is a bug assignee.
https://bugs.launchpad.net/bugs/1459932

Title:
  Current Email functionality in the Public Cloud isn't working

Status in Jio:
  Confirmed

Bug description:
  We're using ESB to send emails to users for public cloud. Currently we use a google account to send these emails. On the production environment, we have the ESB notification server at https://49.49.4.176/il/notificationapi. Current flow:
  1. Users go to the "early access" PHP webpage.
  2. User signs up on that page with 5 info: Name, Organization, Email address, phone number and a captcha. Clicks on Submit.
  3. This person is registered as a "lead" in SugarCRM.
  4. The CRM support agent/user will convert this "lead" to a "contact" to confirm this is a valid user.
  5. This triggers an email to the registered email address.
  The issue is that the email is not going out to the user's registered email address.

To manage notifications about this bug go to:
https://bugs.launchpad.net/jio/+bug/1459932/+subscriptions