We are creating an emergency handbook if we would have a critical
Is there someone who can suggest a company which can help to find how
the guys hacked the infrastructure and how to fix it?
I hope we never have to use it, but be prepared is better
I wonder if someone could point me in a correct direction for debugging mails between Proton and Outlook landing in spam... What happens is
* my domain XXX plugged to mail.protonmail.ch.
* my 2nd domain YYY plugged to mail.protection.outlook.com.
* every mail sent from Proton to Outlook lands in spam
* headers as seen by Outlook indicate SCL score 5
The content I use for the test is not anything synthetic but a real message. In the headers I can also see that the "basic configuration" is correct, i.e.
* SPF passed
* DKIM passed
* DMARC passed
so this gives no useful information sadly. Maybe someone here has experience with debugging Microsoft? The issue is that this makes my private mailbox unusable as whoever out there uses Outlook as their mail service is not getting my emails. Quite sick...
Thanks a lot for any help,
One of our customers includes the SPF-Policy of ip-plus.net in his
domain. Through this (and our monitoring of it), we noticed a problem
that popped up this morning. If someone at ip-plus.net / Swisscom could
have a look into it, that would be great.
➜ ~ dig +short TXT ip-plus.net | grep spf
"v=spf1 ip4:22.214.171.124 ip4:126.96.36.199/29 ip4:188.8.131.52/29
ip4:184.108.40.206/29 ip4:220.127.116.11/24 ip4:18.104.22.168
ip4:22.214.171.124/24 ip4:126.96.36.199/24 ip4:188.8.131.52/29 "
"a:mailout.ip-plus.net ip4:184.108.40.206/16 ip4:220.127.116.11/27
ip4:18.104.22.168/29 ip4:22.214.171.124/24 ip4:126.96.36.199/24
ip4:188.8.131.52" "ip4:184.108.40.206 ip4:220.127.116.11 mx -all"
The problematic part is the missing space before the second-last "ip4:"
block (after 18.104.22.168).
Error message the SPF validator throws is: SPF Permanent Error: Invalid
IP4 address: ip4:22.214.171.124ip4:126.96.36.199