Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Discussion regarding the deployment of reply-by-email to comment #2781

Closed
namangupta01 opened this issue Jun 7, 2018 · 12 comments · Fixed by #2823
Closed

Discussion regarding the deployment of reply-by-email to comment #2781

namangupta01 opened this issue Jun 7, 2018 · 12 comments · Fixed by #2823

Comments

@namangupta01
Copy link
Member

As discussed with @jywarren on gitter, opening this issue to discuss the things to be done regarding to start our new reply-by-email feature.

@jywarren
Copy link
Member

jywarren commented Jun 7, 2018

Great! Can you link back to the conversation PR and copy in some of the notes from there?

@namangupta01
Copy link
Member Author

sure.

@namangupta01
Copy link
Member Author

Previous discussion regarding this is in #2669.
In the discussion, @icarito gave information about the service being used by stable, unstable.

What mailman server do you mean? We do not offer our own SMTP service but use an external service (GMail). Currently localhost SMTP is redirected to this GMail account and in the case of unstable and stable SMTP mail goes all to "[email protected]" mailbox inside the staging server. The server is not setup to collect mail or accept mail from other servers.

See #2669 for detail discussion.

@namangupta01
Copy link
Member Author

As in stable and unstable all the mail goes to mailbox inside the staging server we can setup pop3 protocol to receive mail from [email protected].
And in case of localhost SMTP is redirected to any gmail account we can use the configuration of that gmail account.

@jywarren jywarren added this to the Email notifications overhaul milestone Jun 11, 2018
@jywarren
Copy link
Member

OK -- we'll wait for @icarito to chime in on the next step, but if you want to organize a checklist here that'd be helpful too!

@jywarren
Copy link
Member

So i think we're wanting to make a mailbox for this, using Google Apps? I can do that and send info to @icarito

@jywarren
Copy link
Member

What should its address be? [email protected]? Something friendlier? [email protected]?

@namangupta01
Copy link
Member Author

[email protected] looks awesome.

@icarito
Copy link
Member

icarito commented Jun 12, 2018

Hi,
Jeff gave me information on one mailbox.
notifications@ is for production.
Could we make one mailbox for staging and we can point stable and unstable to pick up fro there? maybe [email protected] ?
Then, we need to add email variables to environment at staging. @jywarren this is done in Jenkins configuration at the web interface, for each task configuration. For the case of production we have an environment.sh file which is not git-tracked.

@jywarren
Copy link
Member

Also linking to #2823

@jywarren
Copy link
Member

OK, created notifications-staging@ and notifications-unstable@

@jywarren
Copy link
Member

OK, confirmed emails are being received in notifications-staging@ and notifications@. I did not set up the unstable branch one but could in the future if we want. Also noting Naman has opened #2823 for the docker-compose part -- great!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants