1

Topic: Question regarding the nature of the whitelist

======== Required information ====
- iRedMail version: mail_version = 0.8.6
- Store mail accounts in which backend (LDAP/MySQL/PGSQL): MySQL
- Linux/BSD distribution name and version: CentOS 6.5
- Related log if you're reporting an issue: N/A
====

I was curious, if a domain is added to the whitelist does this mean that all mail from that domain is passed into the system no matter what?

Also does this whitelist/blacklist system support wildcards? For example would the following block all mail from any domain ending in .eu if entered into the blacklist section?

@*.eu

----

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

2

Re: Question regarding the nature of the whitelist

According to Cluebringer document, you can use '*' as a wildcard match, for example, 'hello.*.example.com'. But not sure '*.eu' is ok.
http://wiki.policyd.org/policies#specifications

3

Re: Question regarding the nature of the whitelist

ZhangHuangbin wrote:

According to Cluebringer document, you can use '*' as a wildcard match, for example, 'hello.*.example.com'. But not sure '*.eu' is ok.
http://wiki.policyd.org/policies#specifications

Thanks. I'll have to try it out to find out more.

But regarding the nature of the whitelist, anything that is on it is automatically passed into the system, correct?

4

Re: Question regarding the nature of the whitelist

HAL9000 wrote:

But regarding the nature of the whitelist, anything that is on it is automatically passed into the system, correct?

Yes. You can check records in SQL table "cluebringer.access_control", it uses 'OK' as smtp action.