181–190 of 322 posts
Telekom is a bunch of strange folks. I lately was not able to send mails, from my private mail servrr to my fathers telekom mail. After investigation I found out my server got blocked. After a decade of working. I mailed them, and they told me to register my mailserver with them. I shall tell them what mails I will send from there and about what content. I couldn’t believe my eyes. Sure, thats how mail was supposed t…
Small tangent, but I feel like it is a good time to drop the term "net neutrality", which covers way too much ground. In the past in political discussions, the term "violation of net neutrality" was used to protest multiple different issues: * Traffic shaping (e.g. slowing down Bittorrent traffic) * Traffic fast lanes (pay for priority access to some content providers) * Selective zero-rating (exclude some providers…
Telekom is a bunch of strange folks. I lately was not able to send mails, from my private mail servrr to my fathers telekom mail. After investigation I found out my server got blocked. After a decade of working. I mailed them, and they told me to register my mailserver with them. I shall tell them what mails I will send from there and about what content. I couldn’t believe my eyes. Sure, thats how mail was supposed t…
Earlier quoted context omitted.
Blocking port 25 is perfectly reasonable. There are no sane and legitimate reasons for running an SMTP server on a residential connection. Even most server providers will block it unless you give them some very good reasons. Blocking 53 is just weird though.
I'm not sure you read the OP's comment in full. They are talking about inbound traffic from the Internet. It's certainly a lot more common a case to self-host an MX than running an open DNS resolver or authorative name server.
Although the GP wrote "53/tcp" that is a weird situation, because most (not all) DNS is over UDP.
One day I suddenly found my DNS resolver logs were very active with veritable gibberish. And it seems that my router had been pwned and joined some sort of nefarious botnet.
I only found this out because I was using NextDNS at the time, and my router's own resolver was pointed there, and NextDNS was keeping meticulous, detailed logs of every query.
So I nipped it in the bud, by determining which device it was, by ruling out other devices, and by replacing the infected demon router with a safe one.
But yeah, if your 53/udp or 25/tcp is open, you can pretty much expect to join a botnet of the DNS or SMTP-spam varieties.
They were the only provider that hijacked DNS lookup failures to redirect to their own page.
They're gone out of this market now, fortunately.
ISPs are the worst. Currently I use Telekom's 5G for my home internet connection in Hungary as Telekom is the only company who has a cable in my street, but they refused to sell me wired internet due to the hole they use to take their underground cable up to the houses being already over capacity (it turns out this "hole" serves like the entire street with cables being run across everyone's attic...). I previously us…
ISPs are the worst. Currently I use Telekom's 5G for my home internet connection in Hungary as Telekom is the only company who has a cable in my street, but they refused to sell me wired internet due to the hole they use to take their underground cable up to the houses being already over capacity (it turns out this "hole" serves like the entire street with cables being run across everyone's attic...). I previously us…
Earlier quoted context omitted.
Been there, done that. After a bit of back and forth, Telekom basically recommended that I go and use one of the big SMTP servers and stop bothering them. While I hated myself for doing it, I eventually switched to Gmail for peace of mind.
This is one of the reasons why I'm not planning to host my own e-mail server. It's not that I can't do it, but I don't want to sink time into investigating and working around/solving things like that.
Telekom is a bunch of strange folks. I lately was not able to send mails, from my private mail servrr to my fathers telekom mail. After investigation I found out my server got blocked. After a decade of working. I mailed them, and they told me to register my mailserver with them. I shall tell them what mails I will send from there and about what content. I couldn’t believe my eyes. Sure, thats how mail was supposed t…
I think this is standard. It applies to domains as well. I experienced government services blocks as well -- they send me an email, yet block my reply. I complain every time and rarely does anyone care, the support person does not escalate, so my email remains blocked, sometimes I'm told system is working as configured, completely ignoring that I am a real person and system is hostile towards me. It's just general fr…
Earlier quoted context omitted.
I don't know if it's the case in Germany, but here in France consumer FTTH networks are of the GPON persuasion. These need to handle encryption and be able to properly register on the tree, so I'm not completely shocked they require some form of ISP-provided device to terminate the fiber connection. There's also a EU law which says that users should be able to bring their own modems / routers, so AFAIK providers say…
The 8311 discord is a great source of technical info and help on using your own PON equipment of various sorts with providers
In the case where the terminating equipment is a small box that exposes ethernet, with no routing or otherwise interfering the function of my own router, I think it's good enough. An argument could be made for the all-in-one devices, like saving some power.
I get the geek factor, and it's one of the reasons why I run my own router, but for this specific bit, which needs to be fairly well integrated with the ISP's network, combined with their usual abysmal support, I think it's a better bet to just leave it alone.