I think that ordinary customers of mxroute.com -- probably the great majority -- signed up because they want reliable mail delivery and reception, and they're not especially interested in how this is

No, it's not. I included in every single signup email since the beginning of the service what to use as the SPF record. If someone went rogue, that has nothing to do with me or MXroute. That has to do

Also I remember one of mxroute's advertised features (I never used it myself) was that users could log into mailchannels for some purposes (tickets?). Whatever that was, if they used it, it was part

customers know it's there: https://headwayapp.co/mxroute-changelog

Most Improved: Mxroute

MXRoute - BlackFriday - 60GB disk - 15 usd year / 1.25 usd Month

(Quote)

OK, so follow up question, since it would appear that internal MXroute -> MXroute email would count toward my hourly quota.

improved provider : mxroute.com

(Quote)

(Quote)

Btw if anyone likes stats, this is first iteration of public monitoring on our in-house MC replacement: http://stats.mxroute.com/d/QvKnwwKik/mxroute-outbound?refresh=10s&orgId=1

So we're looking at first iteration of this logic so one thing I should stress is that it's existence and method are both subject to change. Right now this is meant to be the guard rail on the edge of

Saw you mention this in the other MXroute thread and I've been thinking about it ever since. Figured this would be a good time to ask some questions.

Mxroute.com

* MXroute.com

I see now that you just changed the record at mxroute.com ... not the SPF records customers were recommended to publish. This is fine, thanks for clarifying.

The name server at ghost.mxroute.com is still returning

The SPF record you need to configure has always been "v=spf1 include:mxroute.com -all". We changed the record on mxroute.com. So you never need to change anything.

The name server at ghost.mxroute.com is still returning the old record