5.3.3 bounce: system not capable of selected features
5.3.3System not capable of selected featuresPermanent: retrying will not help
554 5.3.3 Remote server does not support SMTPUTF8
What it means
RFC 3463 defines X.3.3 as "System not capable of selected features". Your message asked for an SMTP extension or capability, and a server along the path does not have it. The message cannot be delivered without that feature, so it is refused.
Common modern triggers are internationalised email (SMTPUTF8, RFC 6531) sent to a server that only handles ASCII addresses, 8-bit content that cannot be downgraded, and delivery status requests a relay cannot honour. The example shows how a sending MTA typically words the SMTPUTF8 case when it generates the DSN itself. Compare 5.6.7, which is specific to non-ASCII addresses, and 5.5.1, which is a command the server does not recognise.
A 4.3.3 can show up when a feature is temporarily unavailable, for instance during an upgrade, but the permanent 5.3.3 is what you normally see, because capabilities rarely change mid-delivery.
Likely causes
- A sender or recipient address contains non-ASCII characters and a server in the path lacks SMTPUTF8.
- A message body uses 8-bit or binary MIME and the next hop does not advertise 8BITMIME or BINARYMIME, with no conversion possible.
- An application requests DSN or other extensions through a relay that strips or refuses them.
- An old mail gateway in front of a modern server advertises fewer features than the server behind it.
How to fix it
- Read the bounce for the feature it names, then compare it with the EHLO capabilities the recipient server advertises.
- For non-ASCII addresses, use an ASCII alias for the recipient or sender until both sides support SMTPUTF8.
- For 8-bit content, configure your sending software to encode bodies as quoted-printable or base64.
- If a gateway is the bottleneck, ask its admin to upgrade it or enable the missing extension.
Checks that apply
- SMTP Diagnostics Shows the EHLO extension list of the recipient server, so you can see whether SMTPUTF8, 8BITMIME, or DSN is offered.
- MX Lookup Lists every MX host so you can test each one, since backup MX hosts are often older and less capable.
FAQ
- How do I know which feature was missing?
- The text after the code usually names it. If not, test the recipient MX and compare its EHLO list with what your message needed.
- Will a retry help?
- Not unless the receiving side upgrades. Change the message or address so it no longer needs the missing feature.