I tried to reach someone at LogMeIn, but have given up...maybe someone here has the ability to let their IT team know their SPF setup is not correct. Not only is the SPF record incorrect, the person setting up the SPF record has used the "-all" syntax that tells the world that LogMeIn is REALLY SURE it is right. So these are "hard" fails...the worst to have. The IP address of one of their servers is missing from SPF...this needs to be fixed if they want emails to be delivered to those of us who take security seriously...
Server Missing from SPF:
Received: from o27.logmeininc.com (o27.logmeininc.com [168.245.49.54])
SPF Record as of 4/20/2020 at 10AM
v=spf1 mx:3amlabs.com ip4:69.25.20.1 ip4:74.201.74.1 ip4:64.74.18.1 ip4:64.94.46.1 ip4:63.251.47.1 ip4:111.221.57.0/24 ip4:64.95.128.1 ip4:63.254.155.123 ip4:74.112.65.204 ip4:74.112.65.210 ip4:167.89.58.109 ip4:173.199.30.10 ip4:91.82.95.146 ip4:207.106.191.64/26 ip4:216.219.114.10 ip4:168.245.77.74 ip4:167.89.58.180 include:_spf.salesforce.com include:spf-001a0901.pphosted.com include:spf.protection.outlook.com include:stspg-customer.com include:mailsenders.netsuite.com -all
