If i understand the documentation correctly it's possible

https://docs.iredmail.org/manage.iredapd.html

You can test by yourself until the master of the forum gives you a definitive answer

Looking at the docs: https://docs.iredmail.org/manage.iredap … acklisting

"For per-user or per-domain whitelists and blacklists, please use option --account. for example:"

it looks as if I can whitelist like this:

# python wblist_admin.py --account andrew@mydomain.com --add --whitelist joe@newgmail.com fred@newyahoo.com

at the bottom of the page it mentions running a cron job to update the whitelist

"fetch all mail domains stored in sql table greylisting_whitelist_domains instead of fetching from command line arguments."

So am I correct in thinking that the whitelist is stored in the sql dbase, so when you run the python command it updates the sql table?

And just to confirm: the presence of a whitelist will only allow those in the whitelist to send to --account andrew@mydomain.com, any others will bounce back.

Sorry for all the questions! Please let me know if my assumptions are all wrong (or right) !

To clarify:

@Neutro's replies are correct (Thank you, @Neutro ). You can use iRedAPD for global, per-domain and per-user white/blacklists. All details mentioned here: https://docs.iredmail.org/manage.iredapd.html

Note: To block all except whitelisted ones, you need to blacklist "@." (without quotes), it's a catch-all match which means "all people".

This is correct.

iRedMail has white/blacklists in few places, for example, Postfix, iRedAPD, Amavisd, etc. Storing white/blacklists in Amavisd SQL database will make the data available to both iRedAPD (white/blacklisting during smtp session) and Amavisd (after-queue content based spam/virus scanning).