Re: [mailop] getting unblocked at outlook?

Fri, 12 Jul 2024 08:26:33 -0700 

Dear List,
I have the same problem (reaching @outlook.com and @hotmail.com) for a mail-service handcrafted for sending side govermental "German Environment Agency's Single-Use Plastics Fund platform" see https://www.einwegkunststofffonds.de/en 


It's built in an azure tenant of german government running on Microsofts 
own netrange !



My last two mails included the "please escalate this to someone who can 
help me." and:



regarding "missing" standards: The Mail-Service at 51.116.98.43 for 
domain "einwegkunststofffonds.de" is built along the highest standards 
of German "Federal Office for Information Security".



BSI TR-03108 "Secure Email Transport" 
https://www.bsi.bund.de/EN/Themen/Unternehmen-und-Organisationen/Standards-und-Zertifizierung/Technische-Richtlinien/TR-nach-Thema-sortiert/tr03108/tr03108_node.html



According to public available "assessment" at i.e. 
https://internet.nl/mail/einwegkunststofffonds.de/1184937/#
100% of a very profound scan can be reached and beats qualification of 
Mail-Domain @outlook.com by far. (87%: 
https://internet.nl/mail/outlook.com/1291051/)



This domain and mailservices provides all current standards in 
Mail-Security and even modern standards like DANE TLS using DNSSEC 
based DNS Services that your services "@outlook.com" and 
"@hotmail.com" cannot provide. We offer DMARC and TLS-Reportng etc. etc.



Looking forward to get this IP of your own network range used in Azure 
Location FFM unblocked fast.


inetnum:        51.116.0.0 - 51.116.255.255
org:            ORG-MA42-RIPE
netname:        MICROSOFT
descr:          Microsoft Limited UK
country:        GB
admin-c:        DH5439-RIPE
tech-c:         MRPA3-RIPE
status:         LEGACY
mnt-by:         RIPE-NCC-LEGACY-MNT
mnt-by:         MICROSOFT-MAINT
created:        2015-05-21T16:59:44Z
last-modified:  2016-07-25T09:38:58Z
source:         RIPE


Bye

Am 12.07.2024 um 05:48 schrieb Michael Rathbun via mailop:

On Thu, 11 Jul 2024 16:42:55 -0400, Bill Cole via mailop<mailop@mailop.org>
wrote:


As far as I've ever been able to tell, S3150 means "Our Pseudo-AI thinks
you stink!" and the way out is to find the link on that page for senders
with  problems, jump through the hoops, respond to any requests for
info, and eventually get a reply from "Hotmail Sender Support" using the
magic phrase "not eligible for mitigation."  This incantation does not
mean what it seems. It is actually a signal that you have reached the
point where you can get a solution (usually?) by replying with the magic
phrase "PLEASE ESCALATE THIS TO SOMEONE WHO CAN ACTUALLY ASSIST ME"
which may or may not need to be in all caps.

This essentially represents my understanding of the net effect of the systems
being build when I worked there.


This may sound like I'm joking, but I am not.

This is sound reverse-engineering.


                                               No one has ever claimed
to have an explanation for why a S3150 blockage happens or what exactly
the 'mitigation' consists of.

Not that I have seen.  You might need a GUTS clearance to find out.

mdr

--
Databay AG Logo

*Ralf Schenk
*
fon:    +49 2405 40837-0
mail:   r...@databay.de
web:    www.databay.de <https://www.databay.de>

        Databay AG
Jens-Otto-Krag-Str. 11
52146 Würselen



Sitz/Amtsgericht Aachen • HRB: 8437 • USt-IdNr.: DE 210844202

Vorstand: Ralf Schenk, Dipl.-Ing. Jens Conze, Aresch Yavari, Dipl.-Kfm. 
Philipp Hermanns

Aufsichtsratsvorsitzender: Dr. Jan Scholzen


Datenschutzhinweise für Kunden: Hier nachlesen 
<https://www.databay.de/datenschutzhinweise-fuer-kunden>

_______________________________________________
mailop mailing list
mailop@mailop.org
https://list.mailop.org/listinfo/mailop






















					Reply via email to