At the time of writing the article (05.11.2022), the situation resolved itself, without any edits on our part.
Often the most effective action is inaction.
Senior of any programming language
After the 20th of October, many users working with Facebook through our service faced the problem of receiving emails. In most cases, the codes are not sent to our services. In this article we will talk about the possible causes of this situation (in my opinion) and about one of the resolving way.
The subject of emails and domains is quite extensive. There are many things to discuss. If you like articles in this format, let us know and we will continue writing.
I am not Facebook security department employee and my opinion about this situation may be wrong. But I know for sure (checked) that emails with the code are not sent to working domains, working emails.
Sections of the article:
It’s all your fault, and your tech. work
A regular Facebook user
We would really like all the problems to be caused by the technical work. After all, if the problems are because of us, then they can be identified and corrected, but unfortunately they are not.
Because of the technical work, you can only get the NO_ACTIVATION
error. It is connected with the fact that we lost data for 5 days of our work in April 2022. And now online we are changing the structure of our databases that can be the reason of such errors.
The problem with Facebook is in the not sending the letter with the code. Other emails (“Forgot password”, notifications about new friends or messages) — still come.
You can check the work status of mailboxes and domains by sending an email letter from your personal email and receiving it from our support.
In your opinion, if we can give you a letter sent from your mail, then why can’t we give you a letter from Facebook? Write to the chat, it’s interesting to read.
“In general, guys, I tried to link a new mail to gmail, the letter arrives immediately, I communicated in other chats, also passwords come to all domains”
All of the following conclusions are based only on the author’s personal point of view.
There is no guarantee that this is the way of working.
The way of using this information is up to you.
The service and the author are not responsible for your decisions.
The difference between them is really big, and it lies in the trust (trust of the site where you register using your mail).
Imagine you’re a Facebook security system and explore the process of verifying a registration request. We will explore the most difficult (and the most interesting) option, analyzing only the protection of the entered mail.
To make the article shorter – I simplify some technical things giving you only the basis. An experienced user will surely find nuances that he will want to discuss in our chat.
The site considers the domain trusted, because in order to get such a mailbox, the user will also have to register there, which cannot be said about custom domains on our own servers…
Checking them we can see something like this:
Checking your IP, the site that accepts registration can simply remember it.
After checking it on whitelists with trusted addresses and not finding them there, the site may think that it’s just some organization or a person who prefers to use his personal domain to work on the network.
But doing such conclusions just to do it is a waste of resources. Therefore, the site will definitely accrue “points” to same IP address and will add them every time it notices registrations from it.
For example, on average, organizations register accounts for 5-10 employees. But your domain breaks all records and makes out an entire village of 5,000 accounts for one domain! What will the site do? Right. Will block the domain. And what will you do? Right. Register a new domain linking it to the same IP (after all, you don’t want to deal with new servers), and continue again.
And now to the points I mentioned above. By banning 3 such domains, you will receive 3 penalty points. The site will consider your organization “suspicious” and will block the IP address of the server that is the recipient of your emails.
After blocking the domain by IP, the following may happen to you:
Private IP addresses for a domain have the same meaning as proxies for your accounts. Mostly they are taken for anonymity, to make impossible to track and block the entire chain of accounts.
Private IP addresses have several features by which they can also be tracked and blocked by hundreds (but at the moment I do not know of any such case):
The above information may seem complicated to someone or just there is no desire to deal with that technical things. In this case we can make everything “turnkey”.
Service | Price |
---|---|
Without choosing subnet, geo and provider | 1000rub first month, then 500rub / month |
With choosing subnet | 1500rub first month, then 500rub / month |
With choosing provider | 5000rub first month, then 1000rub / month |
Setting MX, A records by support agent – 100rub / domain
Unfortunately we cannot guarantee Facebook to live up all your expectations even after such manipulations (after all anonymity is a complex process). But we know for sure that:
Have more questions? Contact us on the site or in Telegram
Thank you for your time and using our services ❤️
Вы не решили ReCaptcha!
Успешно! Вы зарегистрированы, зайдите в почту и перейдите по ссылке в письме для подтверждения.
Вы не решили ReCaptcha!
Успешно! Вы зарегистрированы, зайдите в почту и перейдите по ссылке в письме для подтверждения.