I have been battling a problem for a while with MYOB and their mystaffinfo.com website. This website is a portal for staff to view their leave/pay etc data published from a companies payroll program hosted onsite.
I have a client which stopped recieving mystaffinfo.com e-mails a while back and I have tracked it down I believe to mystaffinfo.com's SPF records being incorrect.
It appears that mystaffinfo.com used to send e-mail out via mail.myob.com and mail1.myob.com and listed these as the only e-mail servers which e-mails should be sent from mystaffinfo.com using SPF records.
At some time after that, MYOB started routing their mystaffinfo.com e-mail through messagelabs for outbound messages but didn't change their SPF Records which are listed as per below
v=spf1 mx a:mail.myob.com a:mail1.myob.com -all
So any spam filter will see the connection coming from messagelabs and drop the message as SPAM. I have been in contact with MYOB over the last few months to get this resolved, and finally found someone on the helpdesk which wanted to help and understood the problem but inferred that getting this changed internally would probably be close to impossible and if we could change our e-mail server that would be easier.
Message labs IP ranges as per this document span a large range and our spam provider isn't too happy to work around this basic misconfiguration of MYOB's SPF records
MessageLab's IP Ranges for this part of the world http://www.asupport.com/web4help/messagelabs_ip_range_for_emea.htm
Does anyone know anyone which works at MYOB and could get this to the right person inside of MYOB?
Our client looks like they are going to drop this product as this issue and others are driving them mad, and the helpdesk is useless - they argued with us for the first week that the website didn't even SEND e-mails until we provided them with message headers proving otherwise, which doesn't instill confidence when your helpdesk don't know your own products.