Just because that big cloud providers are ignoring best practices,
doesn't stop them from being best practices.
This is really a topic for MAAWG to address and have a conversation
about. However, this trend towards allowing anonymized services and
internet space is NOT good for the future of the internet, and/or security.
And there does seem to be an actual intentional strategic business
decision amongst the large cloud providers to simply ignore best
practices and interoperability agreements, whether it be RFC's, ARIN
guidelines, or simply quiet business practice changes.
I have help talks with many in the industry over the last few months,
and one quote stands out.. "We are not competing against each other, we
are competing against the big cloud providers".
At a certain size, the 'too big to block'(TBTB), it seems that
accountability goes out the window.
The path we are on, it isn't inconceivable that TBTB simply decides not
to allow others to even communicate. The internet was founded on
transparency, responsibility, and co-operation, but this appears to be
changing, and we do have to step up and have a voice.
Using 'Data Privacy' as an excuse for anonymity which helps their
business practices make more money, or an avoidance of responsibility is
a threat to all users of the internet.
Tin foil hat wearing people may even suggest that they don't mind
threats emerging from their networks, as long as it doesn't affect their
customers, and is a tool to bring more business.
Imagine the day where you can't use email unless you use Gmail or o356.
Yes, we have to disagree on this point.. the move to the cloud does NOT
mean that it absolves company(s) of transparency, responsibility, or
interoperability.
The thousands of cloud IP(s) seen every day involved in hacking attempts
from the TBTB companies hurt real human beings, and we should get back
to the principles that at at the root of the concepts of a World Wide Web.
On 2022-03-28 20:49, Graeme Slogrove via mailop wrote:
SWIP
-> Neither Microsoft nor Amazon do SWIP. And they never will. I've escalated to
their product managers and it's not happening. BYOIP is coming for Azure which we
will likely pursue.
-> We've run the same service in EU and AU for 2+ years. Never had a problem
nor needed SWIP.
-> As to the approach of operators that choose to block entries with no SWIP,
the world is moving to cloud. It may not be the best overall strategy going
forward to block spam. Maybe it blocks some spam, but likely interferes with other
large corporates in cloud from communicating with a higher than acceptable false
positive rate
"Website"
Easy to provide plenty of large players that don't have websites (or broken
ones) for the domain they use in the mail server FQDN. Either way, if you
believe it makes a huge difference, it's an easy task. rsapps.net, anyone?
I think we may have to agree to disagree on the requirements to run/operate a
mail server. YMMV.
-----Original Message-----
From: mailop <[email protected]> On Behalf Of Michael Peddemors via
mailop
Sent: Tuesday, 29 March 2022 12:00 PM
To: [email protected]
Subject: Re: [mailop] AT&T blocking IP addresses
-----------------------------------------------------------------------------------------------------------------------------------------
CAUTION: This email originated from outside of the organization. Do not click
links or open attachments unless you recognize the sender and know the content
is safe.
-----------------------------------------------------------------------------------------------------------------------------------------
And once again..
NetRange: 52.145.0.0 - 52.191.255.255
CIDR: 52.152.0.0/13, 52.146.0.0/15, 52.145.0.0/16,
52.148.0.0/14, 52.160.0.0/11
NetName: MSFT
NetHandle: NET-52-145-0-0-1
Parent: NET52 (NET-52-0-0-0-0)
NetType: Direct Allocation
OriginAS:
Organization: Microsoft Corporation (MSFT)
RegDate: 2015-11-24
Updated: 2021-12-14
Ref: https://rdap.arin.net/registry/ip/52.145.0.0
OrgName: Microsoft Corporation
Every organization choosing to use this IP space SHOULD insist that MS give
them SWIP or 'rwhois'.
Otherwise you may look like the many spammers using their IP Space.
As well.. *sigh* (Time to put that 'Operating an Email Server 101'
course back on line)
http://twsegcloud.com/
If you saw connections from an IP with no SWIP and no website, would YOU allow
traffic from it?
On 2022-03-28 15:30, Graeme Slogrove via mailop wrote:
We are actively using the new IP ranges as published a few weeks ago,
everything seemed fine until this morning
Server refused mail at MAIL FROM - 553 5.3.0 flpd577 DNSBL:RBL 521<
52.165.84.32 >_is_blocked.For assistance forward this error to
[email protected] <mailto:[email protected]>
The ranges again are
52.165.84.32/28
52.165.84.16/28
20.81.235.112/28
20.81.235.96/28
Anyone from AT&T that I can contact to escalate this block, as it’s
affecting customers.
Regards,
*Graeme Slogrove ***
Sr. Director, Product Engineering
--
"Catch the Magic of Linux..."
------------------------------------------------------------------------
Michael Peddemors, President/CEO LinuxMagic Inc.
Visit us at http://www.linuxmagic.com @linuxmagic
A Wizard IT Company - For More Info http://www.wizard.ca
"LinuxMagic" a Registered TradeMark of Wizard Tower TechnoServices Ltd.
------------------------------------------------------------------------
604-682-0300 Beautiful British Columbia, Canada
This email and any electronic data contained are confidential and intended
solely for the use of the individual or entity to which they are addressed.
Please note that any views or opinions presented in this email are solely
those of the author and are not intended to represent those of the company.
_______________________________________________
mailop mailing list
[email protected]
https://list.mailop.org/listinfo/mailop
