A few weeks ago, we moved ChoralNet to a new server. While the web site and most of the services we provide moved over fine and are providing you with faster, smoother access to ChoralNet, mail has been a case of technical Whack-a-Mole…whenever we fixed one problem, another problem would pop up somewhere else. Now that everything’s working the way it should be, there are a few things you need to know:
If you’re a new ChoralNet user and have been waiting for a password assignment email that’s never come, go to My ChoralNet and click Forgot my Password. Enter the email address you registered. You’ll receive a new password–and then you’ll be good to go. Welcome to ChoralNet–we’re looking forward to your participation!
If you aren’t getting ChoralNet mail, but you used to, log into ChoralNet and see if there’s a note under the ChoralNet menu bar warning you that your mail is bouncing. If you see this, check to make sure that you haven’t marked your ChoralNet mail as spam, then click the message to restart your mail. Otherwise, go to My ChoralNet, choose Subscription E-mail Options, and check to make sure you have the subscriptions you should have. If this looks right, and you still aren’t receiving email, check with your system administrator. Mail from ChoralNet will be sent from , but our IP has changed, so it’s possible that your ChoralNet mail is being blocked as a result or marked as spam.
If you sent mail via Contact Us/Contact User in the last couple of weeks, it might or might not have gone through. If you sent something important, it’s probably a good idea to follow up and make sure everything worked.
If you subscribe to ChoralNet via RSS, e.g. via Bloglines or Google Reader, you need to update your ChoralNet RSS URLs. You can find the new URL by going to My ChoralNet, then Read my subscriptions, and click on the RSS button in your browser address bar (or click the RSS logo next to My subscriptions when the page appears).
We’re sorry for the inconvenience–and thanks to all of you who reported issues and put up with missing/long/broken emails in the processes.
David Topping says