Topic · Email Infrastructure
SMTP RCPT TO command
SMTP RCPT TO identifies an envelope recipient to whom an SMTP server is being asked to deliver a message.
How it works
A server can accept or reject recipients independently before the message body is transferred.
What can go wrong
Recipient-specific refusals are sometimes incorrectly attributed to domain-wide DNS or authentication failure.
What to check or do
Compare RCPT responses across affected and unaffected addresses before changing global mail policy.
How to investigate SMTP RCPT TO command
- Signal to investigate
- A relay reports 550 for RCPT TO although the sender was authenticated.
- Evidence to collect
- Inspect recipient address syntax, accepted domains, forwarding policy and the recipient-stage SMTP response.
- Common wrong conclusion
- Sender authentication success does not mean the relay accepts every destination.
How to interpret the evidence
RCPT TO identifies the envelope recipient. Servers may reject addresses before DATA due to unknown users, anti-relay policy or recipient restrictions.
What to change and how to verify it
Correct address and routing policy; trace the actual SMTP rejection stage rather than assuming a message-content filter.
Put this into practice
Run a focused check, then explore protection if your domain needs it.