Dev.to Security 🔐 Cybersecurity 👁 0 📖 1 min read

SMTP 451 4.7.1 greylisting: causes & fix

The receiver deliberately rejects the first delivery attempt from an unknown sender; a properly working mail server retries after a few minutes and gets through. Common causes First contact with a new sender

The receiver deliberately rejects the first delivery attempt from an unknown sender; a properly working mail server retries after a few minutes and gets through.

Common causes

  • First contact with a new sender: Postgrey or Rspamd greylisting works as designed.
  • Applications or devices (scanners, ticket systems) send directly without a queue and never retry.
  • Large senders use IP pools, so each retry comes from a different IP and counts as new again.
  • Other 4.7.1 policies, e.g. rate limits or temporary policy server errors.

How to check it

Find greylisting entries in the log

journalctl -u postfix --since today | grep -i greylist

Check whether greylisting is in the restrictions

postconf smtpd_recipient_restrictions

Check Postgrey status

systemctl status postgrey

What actually helps

  1. Wait: normally the message arrives after 5–15 minutes, no action needed.
  2. Whitelist important partners, for Postgrey in /etc/postgrey/whitelist_clients.local, then systemctl reload postgrey.
  3. Make applications send through a local MTA with a queue (Postfix as relay) instead of direct SMTP.

FAQ

Is 451 4.7.1 a problem on my side?

Usually not. Greylisting is the receiver's choice. It only becomes a problem if your system does not retry.

Does greylisting still make sense today?

It slows down simple spam bots but also delays legitimate mail like login codes. Many admins now use it only for mail with a medium spam score.

Full page with every command and the German/Italian version: daniele-michelin.com/en/errors/smtp-451-4-7-1-greylisting/

First published at daniele-michelin.com. The error lexicon covers HTTP, DNS, TLS, mail, database, PHP, nginx, systemd and Nextcloud, in German, English and Italian.

📰 Read the original article on Dev.to Security

Originally published by Dev.to Security. Aggregated on AIWithGhost for educational purposes — full credit and traffic to the original publisher.