Skip to content

Guide · Send-only SMTP

VPS send email: a send-only setup for apps, websites and alerts on a USDT-paid server

Your application, your WordPress site and your server's alerts need to send mail from a VPS you pay for in USDT or another coin, since crypto is the only way to pay, and nothing on that VPS needs to receive mail. Here are the three routes, a Postfix that never listens on the internet, msmtp for scripts, the DNS records, and what the logs say when a message does not arrive.

Updated By Nymhost LLC17 min read

Sending from a VPS, in short

To send email from a VPS without running a full mail server, pick one of three routes. Direct delivery: a send-only Postfix that listens on 127.0.0.1 only and delivers on port 25, which is open on every Nymhost VPS. A relay (smarthost): Postfix or msmtp logs in to a mail service on port 587 or 465, and that service delivers. An HTTP API: your application posts each message to a provider over HTTPS. Whatever the route, publish SPF, sign with DKIM and ask support about reverse DNS. Mail your application sends one message at a time is fine; bulk email is forbidden.

VPS send email: three routes and when to pick each

A VPS sends email in one of three ways. They differ in who hands the message to the recipient's server, whose IP address receivers judge, and what happens when delivery fails. On many clouds only the last two work because outbound port 25 is blocked (the 12-host comparison on the port 25 page shows where). On a Nymhost VPS, outbound port 25 is open in all 9 cities, so direct delivery is on the table too.

Three ways to send email from a VPS, from the Postfix and msmtp documentation, read 18 November 2026
RouteLeaves the VPS onWho delivers to the recipientWhose IP reputation countsIf delivery failsSoftware on the VPS
Direct deliveryPort 25, to each recipient's MX hostYour PostfixYour VPS IPv4 addressAfter a temporary error, Postfix keeps the message and retries, for up to 5 days by default (maximal_queue_lifetime)Postfix, send-only
Relay (smarthost)Port 587 (STARTTLS) or 465 (TLS from the first byte), with a loginThe relay serviceThe relay'sThrough Postfix: queued and retried. Through msmtp: the command fails with an error code and the caller must retryPostfix or msmtp
HTTP APIPort 443 (HTTPS), with an API keyThe providerThe provider'sThe API answers with an error; your code must retryNone: a library in your application

With a relay or an API, a third party handles every message you send, under its own rules and rate limits.

Which route fits which sender

  • Direct delivery when the mail goes to you or to people who expect it, at low volume, and you would rather no third party handled it: server alerts, a contact form that writes to your inbox, password resets for a small application. It needs a clean IP address and reverse DNS.
  • A relay when messages must reach large mailbox providers and your VPS address has no sending history yet. Its reputation carries the mail; in exchange it applies its own rules and limits, and every message passes through it.
  • An HTTP API when your application already makes HTTPS calls and you want no mail software on the server. Failures come back to your code, which must log or retry them.

You can also mix the first two: deliver directly and relay only the domains that are hard to reach, as in the hybrid setup below.

Postfix send only: a server that never listens on the internet

Postfix's documentation calls the closest setup a null client: a machine that can only send mail, receives none from the network and delivers nothing locally. Its example hands everything to a central mail hub; the version here delivers directly instead. Four settings:

  • inet_interfaces = loopback-only: Postfix accepts mail from the VPS itself only. Nothing listens on your public address, so there is no firewall port to open and nothing for strangers to relay through. The manual says to stop and start Postfix after this change; a reload is not enough.
  • mydestination =, empty: no local delivery, so every message leaves the server.
  • myorigin = $mydomain: mail goes out as [email protected], not [email protected].
  • relayhost =, empty: direct delivery. Postfix looks up each recipient's MX record and connects on port 25.

Set myhostname to a name that resolves to your VPS, such as vps.example.com: Postfix sends it in its HELO greeting, and it is the name to ask for in reverse DNS. inet_protocols = ipv4 keeps delivery on the address your SPF record and PTR cover; the IPv6 note on the port 25 page explains why. smtp_tls_security_level = may encrypts whenever the receiving server offers STARTTLS; Postfix's TLS guide advises against mandatory TLS for delivery to the internet.

When the Debian or Ubuntu installer asks for the type of mail configuration, pick Internet Site, then run the commands below. Programs on the VPS can then call sendmail or connect to 127.0.0.1 port 25 without a password, because Postfix trusts only the local machine by default (mynetworks_style = host since Postfix 3.0).

Send-only Postfix with direct delivery on port 25 (Debian, Ubuntu)
apt install -y postfix
postconf -e "myhostname = vps.example.com"
postconf -e 'myorigin = $mydomain'
postconf -e "mydestination ="
postconf -e "relayhost ="
postconf -e "inet_interfaces = loopback-only"
postconf -e "inet_protocols = ipv4"
postconf -e "smtp_tls_security_level = may"
# inet_interfaces and inet_protocols need a full stop and start
systemctl stop postfix
systemctl start postfix
postconf -n
ss -ltnp | grep ':25 '

SMTP relay (smarthost) on port 587 or 465 with SASL

A relay, or smarthost, accepts your messages after a login and delivers them for you. Postfix logs in through the Cyrus SASL library, and Debian 13's Postfix package only suggests libsasl2-modules, which provides the PLAIN and LOGIN mechanisms: install it. From Postfix's SASL and TLS guides:

  • relayhost = [smtp.relay.example]:587 sends all mail to the relay; the brackets stop MX lookups for that name.
  • smtp_sasl_password_maps names a file with one username:password per relay, keyed exactly as relayhost is written, brackets and port included.
  • smtp_sasl_tls_security_options = noanonymous allows a plaintext login once the session is encrypted. Without it Postfix refuses plaintext mechanisms, and if the relay offers nothing else it logs No worthy mechs found.
  • smtp_tls_security_level = secure requires TLS and checks the relay's certificate. The TLS guide says this level suits a client that sends all its mail to one mail hub; encrypt encrypts without checking.

postmap copies the password file's group and other permissions to the table it builds, so make the file readable by root only first. $default_database_type, written the way Postfix's manual writes it, picks hash or lmdb for your build.

For port 465, use relayhost = [smtp.relay.example]:465 with smtp_tls_wrappermode = yes, and :465 in sasl_passwd; the manual says wrapper mode needs the encrypt level or stronger.

Relay all mail through a smarthost on port 587
apt install -y libsasl2-modules
postconf -e "relayhost = [smtp.relay.example]:587"
postconf -e "smtp_sasl_auth_enable = yes"
postconf -e 'smtp_sasl_password_maps = $default_database_type:/etc/postfix/sasl_passwd'
postconf -e "smtp_sasl_tls_security_options = noanonymous"
postconf -e "smtp_tls_security_level = secure"
postconf -e "smtp_tls_CAfile = /etc/ssl/certs/ca-certificates.crt"
/etc/postfix/sasl_passwd (one line per relay), then build the table
[smtp.relay.example]:587    USERNAME:PASSWORD

# then, as root:
chmod 600 /etc/postfix/sasl_passwd
postmap /etc/postfix/sasl_passwd
postfix reload

Hybrid: deliver directly, relay only some domains

With outbound port 25 open, you can relay only the domains that need it. Keep the send-only setup (relayhost empty, smtp_tls_security_level = may) and add three tables. Postfix logs in only where sasl_passwd has an entry for the next hop, so direct deliveries never send the password. Write that next hop the same way in every table, as the TLS guide asks.

Relay only mail for gmail.com, deliver everything else directly
postconf -e 'transport_maps = $default_database_type:/etc/postfix/transport'
postconf -e 'smtp_tls_policy_maps = $default_database_type:/etc/postfix/tls_policy'
postconf -e "smtp_tls_CAfile = /etc/ssl/certs/ca-certificates.crt"
postconf -e "smtp_sasl_auth_enable = yes"
postconf -e 'smtp_sasl_password_maps = $default_database_type:/etc/postfix/sasl_passwd'
postconf -e "smtp_sasl_tls_security_options = noanonymous"

# /etc/postfix/transport
gmail.com                   smtp:[smtp.relay.example]:587

# /etc/postfix/tls_policy
[smtp.relay.example]:587    secure

# /etc/postfix/sasl_passwd (chmod 600 before postmap)
[smtp.relay.example]:587    USERNAME:PASSWORD

postmap /etc/postfix/transport
postmap /etc/postfix/tls_policy
postmap /etc/postfix/sasl_passwd
postfix reload

msmtp: a lighter way to send from scripts and cron

msmtp is an SMTP client, not a mail server: it reads one message, hands it to the server named in its configuration and exits, with no daemon and no listening port. Debian's msmtp-mta package adds /usr/sbin/sendmail, so cron and PHP use msmtp unchanged. Install msmtp-mta or Postfix, not both: each provides that command.

The trade-off is the queue. If the relay cannot be reached, msmtp exits with an error code and the message is lost unless the caller retries; Postfix would keep it. For alerts that is often acceptable, and Debian's msmtp package includes optional queue scripts (msmtpq).

Two Debian details. /etc/msmtprc holds the password, so Debian's README for msmtp suggests mode 0640 and group msmtp: the setgid msmtp binary can read it, other users cannot. And msmtp's AppArmor profile limits passwordeval to helpers such as gpg, secret-tool and pass. For a relay on port 465, set port 465 and tls_starttls off.

/etc/msmtprc for a relay on port 587
defaults
auth on
tls on
syslog LOG_MAIL

account relay
host smtp.relay.example
port 587
from [email protected]
user USERNAME
password PASSWORD

account default : relay
Install, protect the file, test
apt install -y msmtp msmtp-mta
# write /etc/msmtprc as above, then:
chmod 0640 /etc/msmtprc
chgrp msmtp /etc/msmtprc
msmtp --pretend
msmtp --serverinfo
printf 'From: [email protected]\nSubject: msmtp test\n\nSent from my VPS.\n' | msmtp [email protected]

Send from PHP, WordPress, cron and system alerts

Most software on a Linux server sends mail by calling /usr/sbin/sendmail, which Postfix and msmtp-mta both provide. Once one of them works:

  • PHP. mail() runs the program in sendmail_path, by default /usr/sbin/sendmail -t -i. Nothing to change in php.ini.
  • WordPress. wp_mail() builds the message with PHPMailer and hands it to PHP's mail(). Without a From header it uses wordpress@ plus your site's domain (minus any www), so that domain needs the SPF and DKIM records below; the wp_mail_from filter or an SMTP plugin changes it. WordPress's reference warns that a true return value does not mean the message arrived: read the mail log.
  • Applications with SMTP settings. Point them at 127.0.0.1, port 25, no login, to use the local Postfix, or straight at the relay on port 587 with its credentials.
  • cron. A job's output is mailed to the crontab owner, or to the address in MAILTO; MAILTO="" turns it off.
  • Security updates. unattended-upgrades mails its report to the address in Unattended-Upgrade::Mail. The Debian wiki notes that this may need a local mail transport, which you now have.
Send cron output and update reports to a full address
# crontab -e
[email protected]
0 4 * * * /usr/local/bin/backup.sh

# /etc/apt/apt.conf.d/52unattended-upgrades-local
Unattended-Upgrade::Mail "[email protected]";

SPF, DKIM and DMARC for a sending domain

Receivers check that the domain in your From address allows the server that sent the message. Google asks every sender to Gmail for SPF or DKIM, valid forward and reverse DNS and TLS, and adds DMARC above 5,000 messages a day. Set up all three anyway.

  • SPF lists who may send for the domain. Publish only one SPF record: under RFC 7208, two produce a permanent error. If a hosted mailbox already sends for the domain, add the VPS to that record. Terms such as include: and a each cost a DNS lookup, with a limit of 10.
  • DKIM signs each message. A relay or API provider tells you which records to publish. For direct delivery, sign with OpenDKIM as in step 6 of the mail server tutorial. Mail from PHP, cron and other sendmail callers reaches Postfix outside SMTP, and Postfix's Milter guide filters it through non_smtpd_milters only: set it as well as smtpd_milters, or that mail leaves unsigned.
  • DMARC says what receivers should do when the checks fail and where to report. Start with p=none (no preference, in the words of RFC 9989) and an rua address you read.

Google also asks for one From address per category of message; a subdomain such as alerts.example.com keeps server mail apart from personal mail.

SPF record per route for example.com, with the documentation address 203.0.113.10; syntax from RFC 7208 (April 2014), read 18 November 2026
How the domain sendsSPF record (one TXT record on example.com)Notes
Direct from the VPSv=spf1 ip4:203.0.113.10 -allAdd ip6: only if you deliver over IPv6 with its own PTR
Through a relay or an APIv=spf1 include:spf.relay.example -allThe provider's documentation gives the exact include:
A hosted mailbox and the VPSv=spf1 include:spf.mailhost.example ip4:203.0.113.10 -allOne record that lists both senders

-all makes every other sender a fail. Check the result in the Authentication-Results header of a test message, as the next section shows.

Test sending and read the logs

Send one message to an address you control at a large mailbox provider, then follow it in the log. Postfix writes one line per delivery attempt, with the recipient, the server it connected to (relay=), a status code (dsn=) and a status such as sent. The text in brackets is the receiving server's own answer, the fastest clue when something goes wrong. After a temporary error the message waits in the deferred queue and Postfix tries again later: postqueue -p lists what is waiting, postqueue -f retries now.

When the message arrives, open its full headers and find Authentication-Results, the header defined in RFC 8601. You want spf=pass and dkim=pass, plus dmarc=pass once DMARC is published. msmtp also logs one line per attempt: smtpstatus= and smtpmsg= carry the server's answer on failure, and exitcode=EX_OK means success.

Send a test message and follow it (Postfix)
printf 'From: [email protected]\nSubject: Test from my VPS\n\nIf you read this, sending works.\n' | sendmail -f [email protected] [email protected]
journalctl -u 'postfix*' --since '10 minutes ago'
postqueue -p
postqueue -f

# with msmtp and syslog LOG_MAIL instead:
journalctl --since '10 minutes ago' | grep msmtp
A successful delivery line, as printed in Postfix's documentation (shortened)
postfix/smtp[30840]: 19B6B2900FE: to=<[email protected]>, relay=mail.example.com[1.2.3.4], delay=0.22, delays=0.04/0.01/0.05/0.1, dsn=2.0.0, status=sent (250 2.0.0 Ok)

Why a VPS cannot send email: common failures

Start from what the log or the bounce says, fix one thing, and send another test.

Common send-only failures, with Gmail codes from Google's SMTP error reference and settings from the Postfix manuals, read 18 November 2026
SymptomLikely causeFix
Messages stay deferred and the reason says the connection timed outPort 25 filtered by an output rule in your own firewall, or by a provider that blocks itRun the port 25 test; check nft list ruleset or ufw status verbose
Mail to your own domain never reaches your mailboxThe domain is in mydestination, so Postfix delivers it locallypostconf -e "mydestination =", then postfix reload
Gmail answers 550 5.7.25The sending IP has no PTR record, or its forward DNS does not matchAsk support about reverse DNS, or relay mail for that domain
Gmail answers 550 5.7.26 or 550 5.7.27The message is unauthenticated, or SPF failedOne SPF record that lists the real sender; add DKIM
Gmail answers 550 5.7.1 about IPv6 sending guidelinesPostfix delivered over IPv6 from an address without a PTRinet_protocols = ipv4, then stop and start Postfix
SASL authentication failure: No worthy mechs foundPlaintext login refused by the default policy, or the SASL modules are missingsmtp_sasl_tls_security_options = noanonymous; install libsasl2-modules
The relay refuses with a 5xx answer naming the senderThat From address is not allowed on your relay accountSend from an address your relay account accepts; in msmtp, set from
PHP or cron mail leaves without a DKIM signatureThe DKIM milter is in smtpd_milters onlypostconf -e 'non_smtpd_milters = $smtpd_milters', then postfix reload
Gmail answers 421 4.7.28, or rate-limits you with 421 4.7.0An unusual rate of mail from your IP, or a low reputationFind what is sending (postqueue -p, the log); an abused form or plugin is a common source

What a Nymhost VPS may send

Outbound port 25 is open on every plan for your own mail. The rule is about what you send.

Forbidden, VPS suspended

  • Newsletters and marketing mail to lists
  • Cold outreach, or mail to bought or scraped addresses
  • An open relay that forwards mail for anyone
  • Phishing, or mail that impersonates someone

Fine

  • Password resets, receipts and notices your application sends its users
  • Contact form messages delivered to your own inbox
  • Server alerts, cron output and update reports
  • Mail you write yourself, one message at a time

Spam and bulk email are forbidden from any server or address, as the usage rules say. A form or plugin abused to send spam still makes your VPS the sender: keep it updated.

Pay for a send-only VPS in USDT

A server that sends your application's mail is a running cost like any other, and crypto is the only way to pay for it. USDT suits that cost because it tracks the dollar, the currency of every price and of the $25 minimum top-up: send it on Tron (TRC-20), credited after 20 confirmations, about 2 minutes on the checkout, or on Ethereum (ERC-20), after 12, and send exactly the amount the checkout shows on the network you picked. $25 covers Offshore 1, enough for alerts and a small site, for 6 months ($14.83), and the $10.17 left stays on a balance that never expires; paying for a VPS with USDT on Tron or Ethereum goes through both networks.

Nymhost checkout preview: four rental lengths, Offshore plan cards and an order summary for Offshore 4 at $68.79 a year
The first step of the Nymhost checkout: the rental length (3, 6 and 12 months save 10%, 20% and 30%), the Offshore plans and the order summary, here Offshore 4 for 12 months at $68.79.

VPS plans for sending email

A send-only Postfix or msmtp is a small program next to your application, so choose the plan for the application. Offshore 1 ($3.09 a month, 1 GB of RAM) fits alerts and a small site; Global 2 ($3.19, 2 GB) or Offshore 2 ($4.89, 2 GB) leave room for WordPress. Outbound port 25 is open on all of them. To receive mail as well, see which VPS for a full mail server. Every plan and city is on the pricing page, and the anonymous VPS overview lists what Nymhost keeps about you.

Nymhost Offshore

Amsterdam · Reykjavik · Zurich · Bucharest

Offshore 1

$3.09/ month

3 mo $8.346 mo $14.8312 mo $25.95

  • 1 vCPU
  • 1 GB RAM
  • 20 GB NVMe
  • 2 TB traffic
Deploy Offshore 1

Offshore 2

$4.89/ month

3 mo $13.206 mo $23.4712 mo $41.07

  • 1 vCPU
  • 2 GB RAM
  • 40 GB NVMe
  • 4 TB traffic
Deploy Offshore 2

Offshore 4

Best balance

$8.19/ month

3 mo $22.116 mo $39.3112 mo $68.79

  • 2 vCPU
  • 4 GB RAM
  • 80 GB NVMe
  • 8 TB traffic
Deploy Offshore 4

Offshore 8

$13.49/ month

3 mo $36.426 mo $64.7512 mo $113.31

  • 4 vCPU
  • 8 GB RAM
  • 160 GB NVMe
  • 12 TB traffic
Deploy Offshore 8

Offshore 16

$20.49/ month

3 mo $55.326 mo $98.3512 mo $172.11

  • 8 vCPU
  • 16 GB RAM
  • 320 GB NVMe
  • 20 TB traffic
Deploy Offshore 16

Nymhost Global

New York · Dallas · Los Angeles · London · Amsterdam · Frankfurt

Global 2

$3.19/ month

3 mo $8.616 mo $15.3112 mo $26.79

  • 1 vCPU
  • 2 GB RAM
  • 40 GB NVMe
  • 2 TB traffic
Deploy Global 2

Global 4

$6.39/ month

3 mo $17.256 mo $30.6712 mo $53.67

  • 2 vCPU
  • 4 GB RAM
  • 65 GB NVMe
  • 2 TB traffic
Deploy Global 4

Global 6

$9.59/ month

3 mo $25.896 mo $46.0312 mo $80.55

  • 2 vCPU
  • 6 GB RAM
  • 120 GB NVMe
  • 6 TB traffic
Deploy Global 6

Global 8

$19.19/ month

3 mo $51.816 mo $92.1112 mo $161.19

  • 4 vCPU
  • 8 GB RAM
  • 160 GB NVMe
  • 12 TB traffic
Deploy Global 8

Global 24

$29.39/ month

3 mo $79.356 mo $141.0712 mo $246.87

  • 8 vCPU
  • 24 GB RAM
  • 400 GB NVMe
  • 12 TB traffic
Deploy Global 24

Prices in US dollars, checked on 18 November 2026. Paid from a crypto balance (minimum top-up $25); 3, 6 and 12 months save 10, 20 and 30%. Every plan: KVM, root over SSH, 1 dedicated IPv4 + /64 IPv6, shared 1 Gbit/s port.

Sending email from a VPS: questions

Can I send email from a VPS without a full mail server?

Yes. A send-only Postfix accepts mail from programs on the VPS only and delivers it: no mailboxes, no IMAP, no open port. msmtp is lighter still; it hands each message to a relay and exits. Or call a provider's HTTP API from your application. Receiving mail is a separate job, covered in the full mail server tutorial.

Do I need to ask Nymhost to open port 25 for sending?

No. Outbound port 25 is open on every Nymhost VPS, in all 9 cities, from the moment it is built, with no ticket and no review. Postfix can deliver straight to other mail servers. The one condition is the rule on content: spam and bulk email are forbidden, and a VPS used for either is suspended.

Should I use an SMTP relay or send directly from my VPS?

Send directly when the mail goes to you or to people who expect it, at low volume, and your IP has reverse DNS. Use a relay when messages must reach large mailbox providers from an address with no sending history, accepting that the relay handles every message. With port 25 open you can mix both: direct by default, relay for one domain.

Why do emails from my VPS go to spam?

Usually one of four things: no reverse DNS on the IP, SPF or DKIM failing for the From domain, an address with no history or a blocklist entry, or Postfix delivering over IPv6 without a PTR. The receiving server's answer in your mail log and the Authentication-Results header of a delivered message tell you which.

How do I make WordPress send email from my VPS?

Install a send-only Postfix or msmtp-mta. WordPress sends through PHP's mail(), which calls /usr/sbin/sendmail, so no plugin is required. Use a From address on your own domain (the default is wordpress@ plus the site's domain) and publish SPF and DKIM for that domain. An SMTP plugin pointed at a relay is the alternative.

Port 587 or 465 for an SMTP relay?

Both carry submission with a login. Port 587 starts in plain text and switches to TLS with STARTTLS; port 465 uses TLS from the first byte. Postfix needs smtp_tls_wrappermode = yes for 465, and msmtp needs tls_starttls off. Use the port your relay documents; the port comparison gives the RFC background.

How many emails can I send from a Nymhost VPS?

The rule is about what you send, not a number. Messages your application or server sends to people who expect them are fine; newsletters, marketing lists and cold outreach are bulk email and are forbidden. Receivers set their own limits: Google asks senders to keep their spam rate below 0.3% and rate-limits unusual volumes from one IP.

Sources

  1. Postfix Standard Configuration Examples: Postfix on a null client Postfix
  2. Postfix SASL Howto: SASL authentication in the Postfix SMTP client Postfix
  3. Postfix TLS Support (opportunistic, mandatory and secure levels, client-side submissions, TLS policy table) Postfix
  4. postconf(5): inet_interfaces, mydestination, relayhost, smtp_tls_wrappermode, mynetworks_style, maximal_queue_lifetime, default_database_type Postfix
  5. transport(5) Postfix
  6. Postfix before-queue Milter support (SMTP and non-SMTP filters) Postfix
  7. sendmail(1), the Postfix sendmail-compatible interface Postfix
  8. postmap(1) Postfix
  9. postqueue(1) Postfix
  10. Postfix Connection Cache (delivery log line example) Postfix
  11. Postfix Performance Tuning: deferred mail delivery attempts Postfix
  12. msmtp manual, version 1.8.34 msmtp
  13. msmtp README.Debian (AppArmor, /etc/msmtprc permissions, msmtp-mta) Debian
  14. Package msmtp-mta 1.8.28-3 in trixie: file list (/usr/sbin/sendmail) Debian
  15. Package msmtp in trixie: file list (msmtpq queue scripts) Debian
  16. Package postfix 3.10.13 in trixie (suggests libsasl2-modules) Debian
  17. Package libsasl2-modules in trixie (LOGIN and PLAIN mechanisms) Debian
  18. update-ca-certificates(8) (/etc/ssl/certs/ca-certificates.crt) Debian
  19. Mail runtime configuration (sendmail_path) PHP
  20. wp_mail() function reference WordPress
  21. crontab(5) on Debian 13 (MAILTO) Debian
  22. UnattendedUpgrades (Unattended-Upgrade::Mail) Debian Wiki
  23. ss(8) manual page man7.org (Linux man-pages)
  24. Email sender guidelines Google
  25. Gmail SMTP errors and codes Google
  26. RFC 7208: Sender Policy Framework (SPF), sections 3.2 and 4.6.4 IETF
  27. RFC 9989: Domain-Based Message Authentication, Reporting, and Conformance (DMARC) IETF
  28. RFC 8601: Message Header Field for Indicating Message Authentication Status IETF