1

Topic: Iredapd wblist whitelist alias

==== REQUIRED BASIC INFO OF YOUR IREDMAIL SERVER ====
- iRedMail version (check /etc/iredmail-release): 1.6.7 MARIADB edition
- Deployed with iRedMail Easy or the downloadable installer? Downloadable
- Linux/BSD distribution name and version: Rocky Linux 9.2
- 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.
====
I was trying to Whitelist several e-mail address to an alias address on our iredmail server
Using
python3 /opt/iredapd/tools/wblist_admin.py --account myalias@mydomain.com --list --whitelist addr1 addr2 etc.
They do add to the tables in amavis  but it appears that the whitelist in amavis is trying against the expanded address's and is not whitelisting based on the original alias recipient.
Do alias addresses work in the white/black list or do I need to add the senders to the expanded mail users accounts whitelists individually?
I also notice in the logs that it appears to be looking up the srs rewritten address of the sender
could be the problem?
Thank you

----

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

2

Re: Iredapd wblist whitelist alias

- Amavisd gets the expanded final recipient addresses instead of alias address.
- You have to add white/black lists for final recipients.
- SRS rewritten address could be a problem.

3

Re: Iredapd wblist whitelist alias

ZhangHuangbin wrote:

- Amavisd gets the expanded final recipient addresses instead of alias address.
- You have to add white/black lists for final recipients.
- SRS rewritten address could be a problem.

Thank you , I will use the expanded address's and circumvent the problem

4

Re: Iredapd wblist whitelist alias

ZhangHuangbin wrote:

- Amavisd gets the expanded final recipient addresses instead of alias address.
- You have to add white/black lists for final recipients.
- SRS rewritten address could be a problem.

In order to get wblists to work I will disable srs on my server.
Is it enough to comment out the 4 following lines in main.cf?

#sender_canonical_maps = tcp:127.0.0.1:7778
#sender_canonical_classes = envelope_sender
#recipient_canonical_maps = tcp:127.0.0.1:7779
#recipient_canonical_classes= envelope_recipient,header_recipient

proxy_read_maps = $canonical_maps $lmtp_generic_maps $local_recipient_maps $mydestination $mynetworks $recipient_bcc_maps $recipient_canonical_maps $relay_domains $relay_recipient_maps $relocated_maps $sender_bcc_maps $sender_canonical_maps $smtp_generic_maps $smtpd_sender_login_maps $transport_maps $virtual_alias_domains $virtual_alias_maps $virtual_mailbox_domains $virtual_mailbox_maps $smtpd_sender_restrictions $sender_dependent_relayhost_maps

PS Looking forward to the release of the new golang milter program, will this be able to solve these issues?
Thanks

5

Re: Iredapd wblist whitelist alias

jwelstead wrote:

Is it enough to comment out the 4 following lines in main.cf?

Yes. But do not comment out "proxy_read_maps =" line.

jwelstead wrote:

Looking forward to the release of the new golang milter program, will this be able to solve these issues?

No.