1 Topic by svjoseph

  • svjoseph
  • svjoseph
  • Member
  • Offline
  • Registered: 2017-05-05
  • Posts: 28

Topic: System Whitelist

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

Question:  Is it possible to have a system whitelist that is impossible for customers to override with settings in iRedAdmin?

----

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

svjoseph's Website

2 Reply by ZhangHuangbin

  • ZhangHuangbin
  • ZhangHuangbin
  • iRedMail Developers
  • Offline
  • Registered: 2009-05-06
  • Posts: 31,094

Re: System Whitelist

Why don't allow customers to override the white/blacklists?

3 Reply by svjoseph

  • svjoseph
  • svjoseph
  • Member
  • Offline
  • Registered: 2017-05-05
  • Posts: 28

Re: System Whitelist

I want a small number of addresses that my customers can't block, such as my system notification addresses.

svjoseph's Website

4 Reply by ZhangHuangbin

  • ZhangHuangbin
  • ZhangHuangbin
  • iRedMail Developers
  • Offline
  • Registered: 2009-05-06
  • Posts: 31,094

Re: System Whitelist

In this case, it's better to do it with Postfix "check_sender_access".

5 Reply by svjoseph

  • svjoseph
  • svjoseph
  • Member
  • Offline
  • Registered: 2017-05-05
  • Posts: 28

Re: System Whitelist

https://lists.amavis.org/pipermail/amav … 05314.html

I used something like this .. seemed to work .. it's a hard whitelist.

$policy_bank{'WHITELIST'} = {
      whitelist_sender_maps => [ read_hash('/etc/amavis/whitelist') ],
};

644 root:amavis  /etc/amavis/whitelist

svjoseph's Website