Re: Filtering at border routers: Is it possible?

2019-03-23 Thread RALPH HAUSER
STOP EMAILING ME! TAKE ME OFF OF THIS! > On Mar 22, 2019, at 10:04 PM, John Hardin wrote: > >> On Fri, 22 Mar 2019, Benny Pedersen wrote: >> >> John Hardin skrev den 2019-03-22 22:23: >> Instead of taking on the job of filtering email for all of your clients (this, to me, will open

Re: Filtering at border routers: Is it possible?

2019-03-23 Thread @lbutlr
On 23 Mar 2019, at 14:03, Rupert Gallagher wrote: > I disagree with Kevin on port 587, because it is vulnerable to mitm attacks. You're going too needy too back that up with actual facts. > I was royally pissed when they introduced port 587 and deprecated port 465. > Port 587 is an RFC

Re: Filtering at border routers: Is it possible?

2019-03-23 Thread Grant Taylor
On 3/23/19 2:03 PM, Rupert Gallagher wrote: I was royally pissed when they introduced port 587 and deprecated port 465. Port 587 is an RFC mandated security loophole. Port 465 is golden. TCP port 465 has retroactively been returned to official status. It has two uses, SMTPS, and something

RE: Filtering at border routers: Is it possible?

2019-03-23 Thread Giovanni Bechis
Il 23 marzo 2019 12:53:52 CET, Giovanni Bechis ha scritto: >Il 22 marzo 2019 21:31:40 CET, bruno.carva...@xervers.pt ha scritto: >>Thank you all for your suggestions. >>I will follow the path of using a whitelist and block everyone. >>I can track the IPs, but i taught i could put in place

Re: Filtering at border routers: Is it possible?

2019-03-23 Thread Rupert Gallagher
I reject tons of spam from OVH. So much that I am banning whole CIDRs. Whatever they do, it's not working. On Sat, Mar 23, 2019 at 12:53, Giovanni Bechis wrote > Hi, > this is what OVH does (article in french, sorry): >

Re: Filtering at border routers: Is it possible?

2019-03-23 Thread Rupert Gallagher
I agree with Benny on port 25. I disagree with Kevin on port 587, because it is vulnerable to mitm attacks. I was royally pissed when they introduced port 587 and deprecated port 465. Port 587 is an RFC mandated security loophole. Port 465 is golden. On Sat, Mar 23, 2019 at 03:01, Kevin A.

RE: Filtering at border routers: Is it possible?

2019-03-23 Thread Giovanni Bechis
Il 22 marzo 2019 21:31:40 CET, bruno.carva...@xervers.pt ha scritto: >Thank you all for your suggestions. >I will follow the path of using a whitelist and block everyone. >I can track the IPs, but i taught i could put in place something (like >OVH by example) do (If their system detects spam being

Re: Filtering at border routers: Is it possible?

2019-03-23 Thread Matus UHLAR - fantomas
On 3/22/19 7:01 PM, Dave Warren wrote: To me, the big one is this: It sets your users up for failure. If a user configures their client on a network that allows unrestricted port 25 access and later moves (temporarily or permanently) to a network that does restrict port 25, they'll get an

Re: Filtering at border routers: Is it possible?

2019-03-23 Thread @lbutlr
On 22 Mar 2019, at 13:00, Matt V wrote: > WHY⁉️ Don't do this, it is just hostile. -- The Force can have a strong influence on a weak mind.