������
And in response to Jo Booth:

Certainly had at least one case recently with a customer who hosts with Mesh|net using SMTP via snap to an xtra address, that went via orcon and failed.��

They had the Snap MXs in SPF etc��(+include:snap.net.nz -all��)��but not orcon or xtra.�� It looked like Xtra was looking at the Orcon EHLO��and failing.

I'm lost on this one; the customer hosts with Mesh|net, sent email via snap's SMTP to an xtra address - why did Orcon get the email?�� Snap should've done an MX lookup and connected to Xtra, which Xtra would pass if Snap were declared in the SPF record for the envelope-sender domain.

Mark.

��