2 days ago
I have been logging in with email for the past few months. After August 7th, it stopped and I cannot get code. I tried to access with Github, which works except my Github account is tied to a different email address so it created a second Railway account. I am fine changing the emails, but need to get my project transferred out of the workspace in the account that is locked up due to email. I have a Pro account, this is being posted from the Github Hobby account that I can actually access.
Error checks outcome below:
Login codes from noreply@trymagic.com delivered successfully until August 7, 2026, and no longer arrive. Message trace on our Microsoft 365 tenant shows no delivery attempts from that sender since then. Please ask Magic to check their suppression list for my address and remove it.
The address could be either tlbaugh@djcon.com or tbaugh@djcon.com.
5 Replies
2 days ago
Railway authenticates through external providers, and we cannot transfer projects between accounts, merge accounts, or change login identities. This is a security boundary that protects your account, not a policy limitation.
The email login codes are sent by Magic, a third-party authentication provider. We don't have access to Magic's suppression lists or delivery systems, so resolving the delivery issue is between your email provider (Microsoft 365) and Magic (noreply@trymagic.com). If your M365 tenant is blocking or filtering that sender, whitelisting it there is the path to restoring code delivery. Once the codes arrive again, you can sign into the original account normally and your projects will be there. If the original account also has GitHub linked as a sign-in method, signing in with GitHub using that linked identity would reach it directly.
Status changed to Awaiting User Response Railway • 2 days ago
Railway
Railway authenticates through external providers, and we cannot transfer projects between accounts, merge accounts, or change login identities. This is a security boundary that protects your account, not a policy limitation. The email login codes are sent by Magic, a third-party authentication provider. We don't have access to Magic's suppression lists or delivery systems, so resolving the delivery issue is between your email provider (Microsoft 365) and Magic (noreply@trymagic.com). If your M365 tenant is blocking or filtering that sender, whitelisting it there is the path to restoring code delivery. Once the codes arrive again, you can sign into the original account normally and your projects will be there. If the original account also has GitHub linked as a sign-in method, signing in with GitHub using that linked identity would reach it directly.
2 days ago
Thanks for the reply. Understood that Magic's email delivery is outside your control — so let me reframe what I'm asking for, because it doesn't require touching Magic at all.
I'm permanently locked out of my email-based account (login codes from noreply@trymagic.com stopped arriving after August 7, 2026 — our Microsoft 365 message trace shows no delivery attempts from that sender since, while your news.railway.app and notify.railway.app mail still delivers fine, which points to a suppression on Magic's provider's side).
What I'm requesting is within Railway's control: please transfer my project from the locked email account to my other Railway account (created via GitHub login), or otherwise add that account as an admin so I can transfer it myself.
To verify I own the locked account, I can provide:
- The account email address
- Monthly Stripe invoices / receipt numbers for the subscription billed to that account
- The project name and service details
- The August 7, 2026 login code email from noreply@trymagic.com addressed to me
- Any other verification you need
If a transfer isn't possible, please advise how I can cancel the subscription on the locked account, since I have no way to access billing settings.
I'd appreciate this being escalated if it's beyond first-line support — I'm a paying customer with a production service I currently cannot administer.
Status changed to Awaiting Railway Response Railway • 2 days ago
2 days ago
We understand the frustration, and we appreciate you laying out what you need clearly. To be direct about both asks:
Transferring a project between accounts, adding an admin to another account, or merging accounts is not something we can do regardless of verification provided. This is a security boundary that protects every account on the platform, not a policy we can escalate past. The only paths back into the email-based account are resolving the Magic code delivery on the email/provider side, or signing in with another method already linked to that account (if one exists).
For cancelling the subscription on the account you cannot access, we can help with that. To locate it we need a few details from your card or bank statement for the charges: the last 4 digits of the card being charged, the card's expiry month and year, the exact charge amount and date from a recent statement entry, and the card brand (Visa, Mastercard, etc.).
Status changed to Awaiting User Response Railway • 1 day ago
8 hours ago
Okay. Just so you guys know, while you say the bounce list is maintained by Magic - Magic says the bounce list is maintained on the provider's (your) side and that you could clear the problem with the email not being sent for confirmation. They say they cannot do that because they don't maintain the bounce list for their users.
Status changed to Awaiting Railway Response Railway • about 8 hours ago
5 hours ago
We appreciate you passing that along. We don't have visibility from support into the specifics of how Magic's suppression architecture works or who manages which list, so we can't confirm or act on that from here.
For the subscription cancellation on the locked account, we can move forward on that once we have the details from your card or bank statement for the charges: the last 4 digits of the card being charged, the card's expiry month and year, the exact charge amount and date from a recent statement entry, and the card brand (Visa, Mastercard, etc.).
Status changed to Awaiting User Response Railway • about 5 hours ago