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

Account activation emails #15

Open
NecroBones opened this issue Feb 17, 2016 · 4 comments
Open

Account activation emails #15

NecroBones opened this issue Feb 17, 2016 · 4 comments

Comments

@NecroBones
Copy link

I'll just start a separate issue for this one. I see lots of people have signed up already. My activation email never arrived (and I checked my spam folders). I'm wondering if it's just me that's unlucky, or if this is happening to more people?

@NecroBones
Copy link
Author

Also, I tried emailing "[email protected]" as it asks you to do if having trouble, and the message bounced:

[email protected]: host s3n1.52k.de[5.9.16.54] said: 530 Relaying not
allowed (in reply to RCPT TO command)

@ghost
Copy link

ghost commented Feb 17, 2016

I don't know if darklight is still awake, but if you hop on our IRC
channel, he can manually activate your account.

On Tue, Feb 16, 2016, 9:01 PM NecroBones [email protected] wrote:

Also, I tried emailing "[email protected]" as it asks you to do if
having trouble, and the message bounced:

[email protected]: host s3n1.52k.de[5.9.16.54] said: 530 Relaying not
allowed (in reply to RCPT TO command)


Reply to this email directly or view it on GitHub
#15 (comment)
.

@StollD
Copy link
Member

StollD commented Feb 17, 2016

It is a known issue and we are working on resolving it. Your error message might be useful for VITAS to troubleshoot the problem. While this happens, darklight, me and I think some others too (dunno, was away while that happened) have Admin access to the site and can activate you manually.

@NecroBones
Copy link
Author

Darklight activated me, so we're all good. Let me know if I can help troubleshooting the mail routing. I run my own mail server at my end, and the logs don't show any delivery attempt that I can match to the expected activation email, so it either didn't send, or there's a relay involved that's not routing the mail properly. For the reverse direction, with the error above, you'll typically see that sort of message if the recipient server isn't properly configured to take delivery of the message, so it thinks it's being asked to relay the message out to the world. I've had that problem before. ;)

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

No branches or pull requests

2 participants