1

Topic: Intentional Policy Rejection. Why?

==== REQUIRED BASIC INFO OF YOUR IREDMAIL SERVER ====
- iRedMail version (check /etc/iredmail-release): 0.9.9
- Deployed with iRedMail Easy or the downloadable installer? DL
- Linux/BSD distribution name and version: Debian 9
- Store mail accounts in which backend (LDAP/MySQL/PGSQL): MySQL
- Web server (Apache or Nginx): Nginx
- Manage mail accounts with iRedAdmin-Pro? No
- [IMPORTANT] Related original log or error message is required if you're experiencing an issue.
====

Why does the server bounce a message to try again? I keep having this happen, and mostly for time sensitive emails. Mind you I have a 2GB RAM server and I am the only one using email on it, so it should not be due to resources.

Can you explain why this happens so I can better understand it?

----

Spider Email Archiver: On-Premises, lightweight email archiving software developed by iRedMail team. Supports Amazon S3 compatible storage and custom branding.

2

Re: Intentional Policy Rejection. Why?

This is caused by greylisting service running on iRedMail server, it works as designed.
Visit http://greylisting.org for technical details about greylisting.

Also, FYI:

- https://docs.iredmail.org/manage.iredapd.html
- You can upgrade to iRedAPD-2.8, it improves greylisting plugin, if sender IP is listed in SPF DNS record of sender domain, no greylisting applied. https://docs.iredmail.org/upgrade.iredapd.html

3

Re: Intentional Policy Rejection. Why?

That makes perfect sense, and is actually kindof neat. Thank you for explaining.

Also, yes, I upgraded last night to iRedAPD-2.8 and noticed a nice change in the greylisting service not bouncing everything. Very nice addition. Thank you so much.