-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Comments
Great! Can you link back to the conversation PR and copy in some of the notes from there? |
sure. |
Previous discussion regarding this is in #2669.
See #2669 for detail discussion. |
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]. |
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! |
So i think we're wanting to make a mailbox for this, using Google Apps? I can do that and send info to @icarito |
What should its address be? |
|
Hi, |
Also linking to #2823 |
OK, created |
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! |
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.The text was updated successfully, but these errors were encountered: