--- title: "How To Add mtasv.net To Your SPF Record | AutoSPF" description: "Learn how to add mtasv.net to your SPF record correctly to authorize email sending, prevent SPF errors, and improve email deliverability." image: "https://autospf.com/og/blog/how-to-add-mtasv-net-to-your-spf-record.png" canonical: "https://autospf.com/blog/how-to-add-mtasv-net-to-your-spf-record/" --- Quick Answer To add mtasv.net to your SPF record, include the required SPF mechanism provided by your email service, such as include:mtasv.net if instructed. Then publish the updated SPF TXT record in your domain's DNS and verify it to ensure proper email authentication. Share [ ](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fautospf.com%2Fblog%2Fhow-to-add-mtasv-net-to-your-spf-record%2F "Share on LinkedIn") [ ](https://twitter.com/intent/tweet?text=How%20To%20Add%20mtasv.net%20To%20Your%20SPF%20Record&url=https%3A%2F%2Fautospf.com%2Fblog%2Fhow-to-add-mtasv-net-to-your-spf-record%2F "Share on X/Twitter") [ ](https://www.facebook.com/sharer/sharer.php?u=https%3A%2F%2Fautospf.com%2Fblog%2Fhow-to-add-mtasv-net-to-your-spf-record%2F "Share on Facebook") [ ](https://reddit.com/submit?url=https%3A%2F%2Fautospf.com%2Fblog%2Fhow-to-add-mtasv-net-to-your-spf-record%2F&title=How%20To%20Add%20mtasv.net%20To%20Your%20SPF%20Record "Share on Reddit") [ ](mailto:?subject=How%20To%20Add%20mtasv.net%20To%20Your%20SPF%20Record&body=Check out this article: https%3A%2F%2Fautospf.com%2Fblog%2Fhow-to-add-mtasv-net-to-your-spf-record%2F "Share via Email") ![Add mtasv.net](https://media.mailhop.org/autospf/spf-security-4964-1783417838291.jpg) mtasv.net is associated with Postmark, the [transactional email](https://www.scaleway.com/en/blog/what-is-a-transactional-email/?%5F%5Fcf%5Fchl%5Ff%5Ftk=gbqsXMIQHup4Agto2bESiJKHnT5f6ZA8rjBu4qP0CD0-1783408157-1.0.1.1-8mQPrwAxjByTX2L.ICO%5FB6hHIY0Z6v9CVod3z16rmj4) service operated under Postmarkapp. When your application sends mail through Postmark mail servers, receiving systems such as Google, Gmail, Microsoft, Outlook, Fastmail, and G Suite need a way to confirm that Postmark is authorized to send on behalf of your domain. That is where an SPF record comes in. An SPF record is a type of [DNS record](https://contabo.com/blog/wiki/dns-records/) published in your domain’s DNS settings. It lists the services, mail servers, and **authorized IP addresses** allowed to send mail for your domain. Adding `include:mtasv.net` tells inbox providers that Postmark’s infrastructure is part of your approved email authentication setup. You may also see pm.mtasv.net in Postmark configurations, especially around [Return-Path](https://www.sequenzy.com/glossary/return-path), bounce address handling, and bounce processing. In many Postmark setups, the Return-Path is used to route failed delivery notices, bounces, and error report data back to Postmark for bounce tracking and email delivery reports. _A custom Return-Path may use a CNAME such as a subdomain pointing to pm.mtasv.net, while the SPF record authorizes Postmark for sending_. In short: - mtasv.net is used in SPF authorization for Postmark sending. - pm.mtasv.net is commonly associated with **Postmark Return-Path** and bounce processing. - The SPF record helps receiving email server systems validate the email sender. - The DNS record supports email authentication, anti-spoofing, deliverability, and [domain reputation](https://prospeo.io/s/what-is-domain-reputation). SPF works alongside other email security mechanisms, including DKIM, a DKIM signature, and sometimes legacy checks such as SenderID. While SPF validates the sending source, DKIM validates that the message content and selected email headers were not altered. Together, they form a stronger authentication workflow for recipients and inbox providers. ## When You Need to Include mtasv.net for Email Authentication You need to include **mtasv.net in your SPF record** when your domain sends email through Postmark, and you want that email to pass SPF checks. This is especially important for transactional messages such as password resets, receipts, notifications, alerts, and user account confirmations. _If Postmark is sending mail using your domain in the From address, your SPF record should authorize Postmark mail servers_. Without this authorization, receiving systems may treat the message as suspicious, route it to spam, or reject it, depending on the recipient provider’s acceptance practices and acceptance criteria. ![Correct vs Incorrect SPF Setup](https://media.mailhop.org/autospf/dns-lookup-error-3585-1783418212891.jpg) You should consider adding `include:mtasv.net` when: - Your application sends **transactional email through Postmark**. - Your DNS settings do not already authorize Postmark. - Postmark’s domain verification screen asks you to update your SPF record. - You use a custom Return-Path for better domain alignment. - You want consistent email delivery across Gmail, Outlook, Microsoft, [Google Workspace](https://nethunt.com/blog/what-is-google-workspace/), Fastmail, and other inbox providers. - You rely on Postmark bounce processing, bounce tracking, and email delivery reports. The Return-Path is particularly important. The visible From address is what users usually see in their email client, but the Return-Path is used behind the scenes for handling bounces. When Postmark manages the Return-Path through pm.mtasv.net, it can process failed deliveries, classify bounces, and provide cleaner deliverability data in tools such as Postmark’s Activity view or Log Explorer. However, SPF alone is not the entire email authentication picture. For stronger email security, configure SPF, DKIM, and **Return-Path alignment** where possible. This reduces [anti-spoofing](https://www.geoweeknews.com/articles/trimble-announces-gps-and-beidou-anti-spoofing-solution/) risks, protects your domain reputation, and helps prevent unauthorized services from impersonating your domain. Also, ensure your sending practices align with Postmark’s Terms of Service, acceptable use policy, and no-spam policy. Postmark is designed for permission-based transactional messaging, not purchased addresses, a third-party list, or bulk promotional spam. If you need help with abuse-related issues, Postmark references contacts such as [abuse@postmarkapp.com](mailto:abuse@postmarkapp.com), while account or setup questions are typically directed to [support@postmarkapp.com](mailto:support@postmarkapp.com). ## How to Check Your Current SPF Record Before Making Changes Before adding mtasv.net, check your existing SPF record. A domain should usually have only one SPF TXT record. **Multiple SPF records** can cause SPF validation failures even if each DNS record looks correct. ![SPF Lookup Limit Gauge](https://media.mailhop.org/autospf/spf-record-limit-5349-1783418286020.jpg) You can inspect your current SPF record using command-line tools or online [SPF lookup](https://autospf.com/blog/what-is-an-spf-lookup-and-why-it-matters/) services such as SPF-Record.com, SPF-Record.de, emailsherpa.net, emailsherpa, or other DNS diagnostic platforms. Some administrators also use Cloudflare DNS tools, the Cloudflare Community, Google Admin Toolbox, DNSBL Check utilities, or mail testing platforms to review SPF, MX, CNAME, and email authentication status. A **typical SPF lookup** checks for [TXT records](https://www.digicert.com/faq/dns/what-is-a-txt-record) at your root domain, for example: ``` example.com TXT "v=spf1 include:mtasv.net include:_spf.google.com ~all" ``` _If you use Google Workspace or G Suite, you may already have Google’s SPF include_. If you send through Microsoft 365, you may have Microsoft’s SPF include. Your goal is to merge Postmark into the existing SPF record—not create a separate one. For example, do this: ``` v=spf1 include:mtasv.net include:_spf.google.com include:spf.protection.outlook.com ~all ``` Do not do this: ``` v=spf1 include:mtasv.net ~all v=spf1 include:_spf.google.com ~all ``` The second example creates duplicate [SPF records](https://autospf.com/blog/what-spf-records-are-and-how-they-protect-email-domains/) and can break email authentication. When **reviewing your DNS record**, also check related [DNS settings](https://www.ntchosting.com/encyclopedia/dns/settings/): - [MX records](https://www.cloudns.net/wiki/article/12/) for inbound mail routing. - CNAME records for custom Return-Path or tracking domains. - DKIM records provided by Postmark. - Any legacy SenderID references. - Whether pm.mtasv.net appears in your Return-Path configuration. - Whether your current SPF record exceeds the SPF lookup limit. The SPF standard allows a maximum of 10 [DNS lookups](https://threat.media/definition/what-is-a-dns-lookup/) during evaluation. Each include, a, mx, redirect, or similar mechanism that may trigger an SPF lookup. If your SPF record includes too many **third-party services**, the SPF check may fail with a “permerror.” This is a common issue in domain management, especially for organizations using many SaaS email platforms. ![Bounce Processing Flowchart](https://media.mailhop.org/autospf/spf-record-4585-1783418344376.jpg) ## Step-by-Step Guide to Adding include:mtasv.net to Your DNS SPF Record Follow these steps to add Postmark authorization safely. - **Log in to your DNS provider**Open your DNS hosting provider, such as Cloudflare, your registrar, or your domain management platform. **Locate the DNS settings** for the domain used in your Postmark sending configuration. - **Find the existing SPF TXT record**Look for a TXT record that starts with: ``` v=spf1 ``` This is your current SPF record. It may already include Google, Microsoft, Fastmail, or another email delivery provider. - **Edit the existing SPF record**Add `include:mtasv.net` before the final mechanism, such as `~all`, `-all`, or `?all`.**Example before**: ``` v=spf1 include:_spf.google.com ~all ``` **Example after**: ``` v=spf1 include:_spf.google.com include:mtasv.net ~all ``` - **Do not create a second SPF record**SPF requires one consolidated DNS record. If you create another TXT record for Postmark, email authentication can fail. - **Check your Return-Path configuration**If Postmark asks you to configure a custom Return-Path, you may need a [CNAME record](https://www.cloudflare.com/learning/dns/dns-records/dns-cname-record/) pointing a subdomain such as pm.example.com to pm.mtasv.net. This helps Postmark **handle bounce processing**, bounces, and the bounce address while improving domain alignment. - **Save the DNS record** [DNS propagation](https://www.ibm.com/think/topics/dns-propagation) can take minutes or hours depending on TTL and provider behavior. Cloudflare updates are often fast, but some registrars take longer. - **Review Postmark verification**In Postmarkapp, recheck the sender signature or the domain authentication screen. Postmark should detect the SPF record, Return-Path, DKIM signature, and related DNS record changes once propagation completes. ### How to Verify the Update and Avoid Common SPF Configuration Mistakes After saving your DNS record, run another SPF lookup. Confirm that `include:mtasv.net` appears in the active SPF record and that the **result passes a syntax check**. You can use SPF-Record.com, SPF-Record.de, emailsherpa.net, DNSBL Check tools, or your DNS provider’s built-in lookup. _You can also send a test message to Gmail or Outlook and inspect the email headers to confirm SPF, DKIM, and Return-Path results_. Look for authentication results similar to: ``` spf=pass dkim=pass ``` You may also see the Return-Path referencing a **Postmark-managed domain** or a custom Return-Path that ultimately routes through pm.mtasv.net. ![Postmark SPF and Return-Path Configuration Guide](https://media.mailhop.org/autospf/spf-records-in-dns-4729-1783418397625.jpg) #### Avoid duplicate SPF records and excessive SPF lookups The most common mistake is publishing more than one SPF record. Another common problem is exceeding the 10-query SPF lookup limit. If your SPF record includes Postmark, Google, Microsoft, and several marketing or support systems, verify the full lookup chain. A clean SPF record supports reliable email delivery, but an overloaded record can create security risks and deliverability failures. If needed, remove obsolete services, especially old email server entries or vendors no longer used by your organization. #### Confirm Return-Path, bounce processing, and policy alignment SPF validates the **sending infrastructure**, but the Return-Path supports bounce processing. If your Postmark setup uses pm.mtasv.net, make sure the CNAME is correct and that the bounce address is functioning. Good bounce handling protects domain reputation by suppressing invalid recipients and reducing repeated failed delivery attempts. _Also, confirm that your messages comply with Postmark’s no-spam policy, acceptable use policy, and Terms of Service_. Include unsubscribe handling where appropriate, avoid purchased third-party list imports, and maintain clear permission records. These practices align with IT baseline protection guidance from organizations such as BSI and reduce long-term [email security](https://autospf.com/) risk. If verification still fails, review Postmark’s documentation, **check DNS propagation**, inspect the Log Explorer, and compare your setup against guidance from experts such as Chris Nagele and the broader Postmarkapp community. For persistent problems, contact [support@postmarkapp.com](mailto:support@postmarkapp.com) with your domain, current SPF record, SPF check results, and any error report details. ![Brad Slavin](https://media.mailhop.org/autospf/images/authors/brad-slavin.jpg) [ Brad Slavin ](/authors/brad-slavin/) General Manager Founder and General Manager of DuoCircle. Product strategy and commercial lead for AutoSPF's 2,000+ customer base. [LinkedIn Profile →](https://www.linkedin.com/in/bradslavin) ## Ready to get started? Try AutoSPF free — no credit card required. [ Book a Demo ](/book-a-demo/) ## Related Articles [ Intermediate 6m 10 Reasons Why DIY-ing SPF isn’t a Good Choice for Companies Apr 4, 2024 ](/blog/10-reasons-diy-ing-spf-isnt-good-choice-for-companies/)[ Intermediate 5m The 12.4 billion shield for your email communications: Why DMARC software is the unsung hero in the war against phishing actors! Nov 19, 2025 ](/blog/12-4-billion-dmarc-software-shield-protecting-email-from-phishing-actors/)[ Intermediate 3m 3 points to consider before setting your SPF record to -all (HardFail) May 22, 2025 ](/blog/3-points-to-consider-before-setting-your-spf-record-hardfail/)[ Intermediate 3m 5 key contributors to the development of the Sender Policy Framework Nov 12, 2024 ](/blog/5-key-contributors-to-sender-policy-framework-development/) ```json {"@context":"https://schema.org","@type":"Organization","@id":"https://www.wikidata.org/wiki/Q138897474","name":"AutoSPF","url":"https://autospf.com","logo":{"@type":"ImageObject","url":"https://autospf.com/images/autospf-logo.png"},"description":"Automatic SPF flattening and email authentication management. Resolve SPF lookup limits, flatten SPF records, and maintain email deliverability across all your domains.","parentOrganization":{"@type":"Organization","@id":"https://www.wikidata.org/wiki/Q138883901","name":"DuoCircle LLC","url":"https://www.duocircle.com","sameAs":["https://www.wikidata.org/wiki/Q138883901","https://www.crunchbase.com/organization/duocircle-llc","https://www.linkedin.com/company/duocircle","https://github.com/duocircle"],"subOrganization":[{"@type":"Organization","@id":"https://www.wikidata.org/wiki/Q138898167","name":"DMARC Report","url":"https://dmarcreport.com"},{"@type":"Organization","@id":"https://www.wikidata.org/wiki/Q138897474","name":"AutoSPF","url":"https://autospf.com"},{"@type":"Organization","@id":"https://www.wikidata.org/wiki/Q138897912","name":"Phish Protection","url":"https://www.phishprotection.com"}]},"sameAs":["https://www.wikidata.org/wiki/Q138897474","https://www.linkedin.com/company/autospf","https://x.com/autospf01","https://www.g2.com/products/autospf/reviews"],"contactPoint":{"@type":"ContactPoint","contactType":"customer support","url":"https://autospf.com/contact-us/"},"knowsAbout":["SPF Record Flattening","Sender Policy Framework","Email Authentication","DNS Management","DMARC","DKIM"]} ``` ```json {"@context":"https://schema.org","@type":"WebSite","name":"AutoSPF","url":"https://autospf.com","description":"Automatic SPF flattening and email authentication management. Resolve SPF lookup limits, flatten SPF records, and maintain email deliverability across all your domains.","publisher":{"@type":"Organization","name":"AutoSPF","url":"https://autospf.com","logo":{"@type":"ImageObject","url":"https://autospf.com/images/autospf-logo.png"},"description":"Automatic SPF flattening and email authentication management. Resolve SPF lookup limits, flatten SPF records, and maintain email deliverability across all your domains.","parentOrganization":{"@type":"Organization","@id":"https://www.wikidata.org/wiki/Q138883901","name":"DuoCircle LLC","url":"https://www.duocircle.com","sameAs":["https://www.wikidata.org/wiki/Q138883901","https://www.crunchbase.com/organization/duocircle-llc","https://www.linkedin.com/company/duocircle","https://github.com/duocircle"],"subOrganization":[{"@type":"Organization","@id":"https://www.wikidata.org/wiki/Q138898167","name":"DMARC Report","url":"https://dmarcreport.com"},{"@type":"Organization","@id":"https://www.wikidata.org/wiki/Q138897474","name":"AutoSPF","url":"https://autospf.com"},{"@type":"Organization","@id":"https://www.wikidata.org/wiki/Q138897912","name":"Phish Protection","url":"https://www.phishprotection.com"}]}}} ``` ```json {"@context":"https://schema.org","@type":"BlogPosting","headline":"How To Add mtasv.net To Your SPF Record","description":"Learn how to add mtasv.net to your SPF record correctly to authorize email sending, prevent SPF errors, and improve email deliverability.","url":"https://autospf.com/blog/how-to-add-mtasv-net-to-your-spf-record/","datePublished":"2026-07-07T00:00:00.000Z","dateModified":"2026-07-07T00:00:00.000Z","dateCreated":"2026-07-07T00:00:00.000Z","author":{"@type":"Person","@id":"https://autospf.com/authors/brad-slavin/#person","name":"Brad Slavin","url":"https://autospf.com/authors/brad-slavin/","jobTitle":"General Manager","description":"Brad Slavin is the founder and General Manager of DuoCircle, the company behind AutoSPF, DMARC Report, Phish Protection, and Mailhop. He founded DuoCircle in 2014 to solve the SPF 10-DNS-lookup problem at scale and has led the company's growth to 2,000+ customers. Brad's focus is product strategy, customer relationships, and the commercial and compliance side of email authentication (DPAs, SLAs, enterprise procurement) rather than hands-on DNS engineering.","image":"https://media.mailhop.org/autospf/images/authors/brad-slavin.jpg","knowsAbout":["Email Security Strategy","SaaS Product Management","Enterprise Compliance","Customer Success","Email Deliverability Business"],"worksFor":{"@type":"Organization","name":"AutoSPF","url":"https://autospf.com"},"sameAs":["https://www.linkedin.com/in/bradslavin"]},"publisher":{"@type":"Organization","@id":"https://www.wikidata.org/wiki/Q138897474","name":"AutoSPF","url":"https://autospf.com","logo":{"@type":"ImageObject","url":"https://autospf.com/images/autospf-logo.png"},"description":"Automatic SPF flattening and email authentication management. Resolve SPF lookup limits, flatten SPF records, and maintain email deliverability across all your domains.","parentOrganization":{"@type":"Organization","@id":"https://www.wikidata.org/wiki/Q138883901","name":"DuoCircle LLC","url":"https://www.duocircle.com","sameAs":["https://www.wikidata.org/wiki/Q138883901","https://www.crunchbase.com/organization/duocircle-llc","https://www.linkedin.com/company/duocircle","https://github.com/duocircle"],"subOrganization":[{"@type":"Organization","@id":"https://www.wikidata.org/wiki/Q138898167","name":"DMARC Report","url":"https://dmarcreport.com"},{"@type":"Organization","@id":"https://www.wikidata.org/wiki/Q138897474","name":"AutoSPF","url":"https://autospf.com"},{"@type":"Organization","@id":"https://www.wikidata.org/wiki/Q138897912","name":"Phish Protection","url":"https://www.phishprotection.com"}]},"sameAs":["https://www.wikidata.org/wiki/Q138897474","https://www.linkedin.com/company/autospf","https://x.com/autospf01","https://www.g2.com/products/autospf/reviews"],"contactPoint":{"@type":"ContactPoint","contactType":"customer support","url":"https://autospf.com/contact-us/"},"knowsAbout":["SPF Record Flattening","Sender Policy Framework","Email Authentication","DNS Management","DMARC","DKIM"]},"mainEntityOfPage":{"@type":"WebPage","@id":"https://autospf.com/blog/how-to-add-mtasv-net-to-your-spf-record/"},"articleSection":"intermediate","keywords":"","image":{"@type":"ImageObject","url":"https://media.mailhop.org/autospf/spf-security-4964-1783417838291.jpg","caption":"Add mtasv.net"},"speakable":{"@type":"SpeakableSpecification","cssSelector":[".answer-block","h1"]}} ``` ```json {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://autospf.com/"},{"@type":"ListItem","position":2,"name":"Blog","item":"https://autospf.com/blog/"},{"@type":"ListItem","position":3,"name":"Intermediate","item":"https://autospf.com/intermediate/"},{"@type":"ListItem","position":4,"name":"How To Add mtasv.net To Your SPF Record","item":"https://autospf.com/blog/how-to-add-mtasv-net-to-your-spf-record/"}]} ```