We are currently investigating issues some players are having on the megaservers. We will update as new information becomes available.
We are currently investigating issues some players are having with the ESO Store and Account System. We will update as new information becomes available.
In response to the ongoing issue, the North American and European megaservers are currently unavailable while we perform maintenance.
https://forums.elderscrollsonline.com/en/discussion/comment/8235739/
https://forums.elderscrollsonline.com/en/discussion/comment/8235739/
In response to the ongoing issue, the ESO Store and Account System have been taken offline for maintenance.
No Verification Email Sent SOLVED - FIX
Rivell
Soul Shriven
Long story short I placed a support ticket a month ago stating I could not log into my account (But I could log into the game and forms). Thought this would be a simple fix, but no one replied to my ticket. Broke down and started to contacted Devs, the ESO Facebook even resorted to trying to use my old laptop I started playing the game with. I was about to quit and never play another ZOS game ever again. I read the following post and it had me thinking:
Outlook No Verification Email Sent
1. Go to Outlook.com and create a new email account. Your going to use this account for your ESO account only.
2. After creating your Outlook Email address, login to your account on www.theelderscrollsonline.com and change the email address associated with your account to the outlook.com account you created.
After doing this, you won't have any more problems with verification codes.
Why this happens - in lamends terms
The reason this happens is because the email service ZOS uses to forward these emails(a 3rd party most likely) has ended up on a DNSBL or an RBL and the email server your using simply refuses to accept the messages. Each ISP or mail provider makes their own decisions on this, all the DNSBL such as Spamhaus or Sorbis do is a query is made, if it returns true(meaning the senders IP is in the database because its a spam sender) then the provider makes the decision to accept these message or to reject them. When rejected they are pretty much silent to the user, as the server just refuses to accept the message if its set up that way, and thats that.
You end up on a DNSBL by either being infected with a bot that sends spam mail, or the IP in question was spamming in the past and never contacted the DNSBL to tell them they cleaned up their systems and should be removed.
If i was maintaining the servers used to send those codes, i'd use this site below to query the IP addresses of the servers they use to send verification codes, and if they are on any of those lists, i would contact that list and get themselves removed from the RBL or DNSBL
My Solution Did Not Involve Outlook, But Similar Solution With My Work Emial
My emails were being block from my work email at Ideas and Pixels within their IMAP spam folder. I went and logged into the UControls and there it was. This happened because ESO uses a third party email system (Probably to save money) and it was flagged as spam that my auto email system picked up. Sadly I really wish someone would have contacted me regarding this issue a month ago with my original support ticket!
I hope this helps some other people with this issue and this is why I started a new thread, because I see it everywhere on the forum.
Edited by ZOS_Icy on August 10, 2024 10:31AM Outlook No Verification Email Sent
1. Go to Outlook.com and create a new email account. Your going to use this account for your ESO account only.
2. After creating your Outlook Email address, login to your account on www.theelderscrollsonline.com and change the email address associated with your account to the outlook.com account you created.
After doing this, you won't have any more problems with verification codes.
Why this happens - in lamends terms
The reason this happens is because the email service ZOS uses to forward these emails(a 3rd party most likely) has ended up on a DNSBL or an RBL and the email server your using simply refuses to accept the messages. Each ISP or mail provider makes their own decisions on this, all the DNSBL such as Spamhaus or Sorbis do is a query is made, if it returns true(meaning the senders IP is in the database because its a spam sender) then the provider makes the decision to accept these message or to reject them. When rejected they are pretty much silent to the user, as the server just refuses to accept the message if its set up that way, and thats that.
You end up on a DNSBL by either being infected with a bot that sends spam mail, or the IP in question was spamming in the past and never contacted the DNSBL to tell them they cleaned up their systems and should be removed.
If i was maintaining the servers used to send those codes, i'd use this site below to query the IP addresses of the servers they use to send verification codes, and if they are on any of those lists, i would contact that list and get themselves removed from the RBL or DNSBL
My Solution Did Not Involve Outlook, But Similar Solution With My Work Emial
My emails were being block from my work email at Ideas and Pixels within their IMAP spam folder. I went and logged into the UControls and there it was. This happened because ESO uses a third party email system (Probably to save money) and it was flagged as spam that my auto email system picked up. Sadly I really wish someone would have contacted me regarding this issue a month ago with my original support ticket!
I hope this helps some other people with this issue and this is why I started a new thread, because I see it everywhere on the forum.
0
-
snips86x✭This has been the bain of our life, trying to login when the game requires additional authentication. We've also attempted to recover an old account and run into the same issue.
This is such a terrible system.
ZOS, when are you going to take advantage of app based 2FA?!?! It would solve this issue and stop us metephorically pulling our hair out and wanting to cancel our subs!0 -
ZOS_IcymodGreetings,
We have closed this topic as it was originally created in February 2016. In many cases, it's better to create a new thread on a topic that you want to discuss as opposed to bumping one that is rather old.
Thank you for your understanding.0
This discussion has been closed.