Hey /g/ents I'm fighting an ISP right now; with a residential

File: stock-photo-mature-businesswoman-s-screaming-in-cables-isolated-on-white-background-75454411.jpg (44KB, 450x320px) Image search: [Google]

44KB, 450x320px

Please /g/, you are one of many hopes but I am interested in your input.

>>62175491
You'll have to read their TOS and not just assume if you think its right or wrong

>>62175552
Is it ever against TOS to connect out to SMTP servers? I mean I'm sure it can be but is that usual for an ISP?

>>62175585
For my ISP, they are ok with it. I do not know about yours however.

Blocking outbound port 25 connections on residential connections is, unfortunately, fairly common as a spam prevention measure.

>Please help /g/.
How, exactly?

It prevents spam/malware from being sent out from you mr home connection. Running an outbound mail server when you don't have reverse DNS or probably even a static ip is dumb. Get a vps and set it up properly and use it as your relay.

>>62175645
I already have a vps for this project, as soon as I started having weirdshit issues I stuck my shit in the cloud and everything started working fine but then i was thinking how can they block 25 out but really now that I think about it... it makes more sense to block 25 out to prevent spam as... you even said.

god dammit

>>62175491
fuck you OP
ISP here

Most mail servers are insecure as fuck, yours too probably.
Once your server joins the botnet, the IP address or even the whole subnet enters every blocking list out there. Should your ISP decide to sell the subnet, the value of the addresses are greatly lowered and the buyer (AWS mostly these days) can sue for fraud.

You've got a residential account, you're only paying for internet access - request data from internet and get a response, not the other way around. If you want to run servers, get a business line. Customers running servers creates a lot of headaches (and expenses in work hours) for the ISP.

>I am trying to play innocent
Stop lying and simply talk to them. We're human. If you were just testing something like in
>I was only doing come basic testing
(though I don't really believe you, you sound like a child caught with the hand in the cookie jar) we might consider unblocking you.

Record the fight plox. I wanna see.

>only need port 80 for the internet
fucking fuck

>>62176776
Fuck you.

Moscow, Russia, had 3 different ISP, all allow listening on any of 65k ports without any issue, one of those three charges $2 per month for that.

Die in a fire. Cunt.

>>62176776
^This guy is right. You aren't buying the right to do whatever you want with the internet unless their ToS states as much (at which point, you usually pay a LOT More). Add this to the fact that the overwhelming majority of people who are dumb enough to run into this kind of trouble are also dumb enough to not know how to secure their server correctly, and it makes sense that they don't want you causing them trouble.

>>62176929
He's only right in saying they can do whatever the fuck they want because they have a monopoly.

He's not right about how ISP should limit their customers arbitrarily because they feel like it.

>>62176987
They don't have a monopoly. I live in a town of less than 8k in the midwest, and have 7 options. Literally every job I've interviewed for over the summer (hey, free vacation to Texas, Colorado, Florida, and Kentucky) has even more options.

File: 1476586209750 (4).jpg (32KB, 384x420px) Image search: [Google]

32KB, 384x420px

>>62175491
If you wanna test shit build your own home lab or VM swarm and test it there, don't give retarded Brazilians or Chinese an opportunity to faceroll their scripts and add your mail server to the botnet because of that one thing you forgot to take care of or another. I'd tell them you were practicing for a certification or testing an application you wrote (or whatever your basic testing is), and that you were just ignorant of the restriction. I'd ask them what network traffic they do restrict in addition to mail, not only for informational reasons but also as a sanity check just in case they do turn out to be shitters.

If you absolutely must run an email server and won't have your lust satisfied unless those packets traverse the internet, go buy a $5 vps and set it up there.

You're making a basic error here.

tcp/25 is for connections from one MTA (mail transport agent; i.e. SMTP server) to another.

MUAs (mail user agents; i.e. mail clients) are supposed to use tcp/587 (submission) to send your email to your MTA.

You're absolutely not supposed to, and very probably not allowed to in your ToC, allowed to run an SMTP server from a residential connection. There are whole blocklists to prevent this, because botnets and spammers (although this is now an obsolete method of spamming because basically everyone blocked the email and the port, there are still one or two fools out there like you).

Please for the love of god read up on configuration first, before you commit the cardinal sin and run an SMTP open relay and find yourself booted off the VPS you're with.

workarounds.org has for many years now hosted a nice guide on configuring a pleasant Postfix/Dovecot configuration in Debian (or Debian-like distros): https://workaround.org/ispmail