iafrica.com email servers, SPF and DMARC

iafrica.com publishes a single MX host, nav-gateway.mweb.co.za. With no backup host, a sender that can't reach it queues the message and retries until the server answers or the queue gives up.

The record on 5 November 2026 was v=spf1 include:_spf-mweb.synaq.com include:spf1.mweb.co.za ~all.

In plain terms, it delegates to _spf-mweb.synaq.com and spf1.mweb.co.za. The top level uses 2 DNS-querying terms; SPF allows 10 in total including nested includes (RFC 7208 §4.6.4).

It ends in a soft fail (~all): mail from unlisted servers should be accepted but treated as suspicious.

The record is v=DMARC1; p=quarantine; sp=none; rua=mailto:[email protected].

p=quarantine asks receivers to send failing mail to spam. Subdomains get sp=none.

Aggregate reports go to mweb.co.za, so the domain's owner sees who sends mail as @iafrica.com.

What that means for you: if a contact gives an @iafrica.com address and you send to them, nothing changes. But never put an @iafrica.com address in the From line of mail sent through your own tool or ESP. It can't pass DMARC for iafrica.com, and this policy tells receivers to junk it.

Our checker treats @iafrica.com like any domain: syntax, MX, disposable and role checks first, then a made-up address to rule out a catch-all, then your address at RCPT TO, disconnecting without sending. We have not published a test of how nav-gateway.mweb.co.za answers for @iafrica.com, so we make no claim here about whether single mailboxes can be confirmed; each result carries its own reason.

DNS tells you where mail goes, not whether one person's mailbox still exists. For a list, run the whole file through a verifier before you send: invalid rows come out, risky rows (catch-all, unknown, refused) go in their own segment, and valid rows are safe to mail.