Not getting emails from Public Mobile due to misconfigured SPF record

[implode]

I had problems logging in so I tried the reset password option, but I never got any emails.  Eventually, I figured out why.  Public Mobile has defined SPF record, but the mail that it sends out from isn't from one of those defined origin.

i5:~> host -t txt publicmobile.ca                            [7:18pm/02-08-17]
publicmobile.ca descriptive text "v=spf1 ip4:208.74.204.0/22 ip4:46.19.168.0/23 include:mailSPF.smtp.com include:spf.mandrillapp.com -all"

Now the self serve Public Mobile site sent mails from what I believe 208.38.59.82 and 208.38.59.78 (possibly the /24)

2017-02-08 19:35:23 H=donder.nssi.telus.com [208.38.59.82] F=<public-mobile-notifications@publicmobile.ca> rejected RCPT <X>: SPF check failed.
2017-02-08 19:39:37 H=donder.nssi.telus.com [208.38.59.82] F=<public-mobile-notifications@publicmobile.ca> rejected RCPT <X>: SPF check failed.
2017-02-08 19:42:29 H=orkaan.nssi.telus.com [208.38.59.78] F=<public-mobile-notifications@publicmobile.ca> rejected RCPT <X>: SPF check failed.

Now the community site sent from a range which was defined in the SPF record.

2017-02-08 19:44:12 1cbfeV-00086a-55 <= community-notifications@publicmobile.ca H=smtp.lithium.com [208.74.204.5] P=esmtp S=3333 id=1956978540.13915.1486611848004.JavaMail.lithium@sjc1papp67.sj.lithium.com

Manually whitelisting the network 208.38.59.0/24 worked around the SPF that's Public Mobile has defined with a reject -all

Public Mobile I think would need to append this network 208.38.59.0/24 to their SPF definition or add specific IPs to their SPF.

[kav2001c]

Yeah I also had issues for years with emails but never an explanation why

[WearySky]

I wonder if this is why people are also reporting not getting emails back when they use the contact us form, even though emails have reportedly been sent by CSRs?

[implode]

The -all would be on purpose rejection, but Public Mobile is missing a network range of a set of Telus SMTP servers that they relay out through which when destination mail servers also utilize SPF verification, they will reject emails identified as being from publicmobile.ca as the source is not in the defined SPF record.

[MoreYummy]

They probably do it the way it is now on purpose.