-
Notifications
You must be signed in to change notification settings - Fork 2
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
Set up mail for training.openedx.org #762
Comments
This can be updated via the eduNext control center. I've shared the link with you in a different channel. |
@feanil I can't change this setting. Do I need to contact support? |
Yea, we'll need new DNS records on our side for that setting. So if you contact support, they should be able to provide you the info we need to add. We can use this ticket to track those changes. Also, I have a suggestion, should we be using the |
@feanil OK, could you explain the steps to move to openedx.org? Or - since you have access to the edunext control center - would it make more sense for you to do this rather than me be a go-between? |
Depends on urgency, I can take a look at this late next week if it is not urgent. The steps for moving would be the same as the steps for moving to the axim.org domain. Just update any from email addersses to use the |
Things are working right now (emails are not caught by spam), and we're announcing the course on Tuesday, so I'd like to be in the middle of doing a change right now since I don't fully understand the host user stuff and not sure I can do it without your help. If you could get to it in the next few weeks I think that would be best. |
Ok, I'll put it on my todo list and try to get it going next week. |
I've updated the e-mails to end with |
@sarina this should be all set now. The e-mail will all come from the |
thanks!! |
See #666 - need to set this up for axim.org
@feanil we're planning to announce the training course next Tuesday. Do you think you can get on this ASAP, so that I can get eduNEXT to configure things properly?
The text was updated successfully, but these errors were encountered: