1 Topic by tomierna (edited by tomierna 2026-07-21 23:08:36)

  • tomierna
  • Member
  • Offline
  • Registered: 2018-02-18
  • Posts: 24

Topic: iRedMail EE - Alias Delivery Restrictions?

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

Newly created alias accounts show "Moderators" for "Mail Deliver Restriction", where old alias accounts show "Unrestricted".

I created a new alias today, first one in a long while. I don't want to create these throwaway aliases as mailing lists because they are effectively single-use. All of my previously created aliases show "Unrestricted" and the new one says "Moderators" under the column "Mail Deliver Restriction".

I tried sending an email to this alias from an external account, and it went through fine.

Is this just a cosmetic error?

Post's attachments

iRedmail Alias Issue.jpg 53.12 kb, file has never been downloaded. 

You don't have the permssions to download the attachments of this post.

----

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

2 Reply by tomierna

  • tomierna
  • Member
  • Offline
  • Registered: 2018-02-18
  • Posts: 24

Re: iRedMail EE - Alias Delivery Restrictions?

When setting up an alias in 1.7.4, I think there was a radio button choice for "Who can send email to this account" with "Moderators" checked by default. When I created the above alias, I chose "Unrestricted"

After creation, the list showed "Moderators", and clicking on it didn't have a place to choose a different restriction.

I've updated to 1.8.1, and now clicking on the alias shows the "Access Policy" section, and I was able to choose "Unrestricted" and it stuck.

Are aliases officially mailing lists under the covers now, regardless of if they are created with the Alias workflow?

3 Reply by ZhangHuangbin

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

Re: iRedMail EE - Alias Delivery Restrictions?

Hi,

- Functions of mail alias account in latest EE release (v1.8.1) is same as old EE release, just default access policy is switched from "Unrestricted" to "Moderators".
- You can set access policy while creating account, or after creation on account profile page.
- With access policy "Moderators", if sender is not a moderator of the mail alias account, the email should be rejected with error "Not authorized".
- You mentioned the email "went through fine", could you please login to EE as global admin, then check whether option "Access Control" is enabled (toggled on) on `Server Settings` -> `Milter` section? And what's the related log lines in `/var/log/milter/milter.log`?

4 Reply by tomierna

  • tomierna
  • Member
  • Offline
  • Registered: 2018-02-18
  • Posts: 24

Re: iRedMail EE - Alias Delivery Restrictions?

I verified that "Access Control" was enabled in the "Milter" section.

Now that the server is updated to 1.8.1, it seems like the restriction is respected. The test email that went through was on version 1.7.4, on which the edit screen of the alias did not have the access policy section. 1.8.1 does have the access policy section, so I am able to change aliases to unrestricted.

Here is the (anonymized) milter log line for the email that went through on v1.7.4:

2026-07-21 14:45:36 INFO [1.2.3.4] response=continue [received, mail_from=my@gmail.com, rcpt_to=thetestaddress@mydomain.com, header_from=my@gmail.com, header_to=thetestaddress@mydomain.com, subject="Test", message_id=<854E3324-FD07-4C09-B4C2-AA1255FCD6A7@gmail.com>, hostname=mail-yx1-f48.google.com, helo=mail-yx1-f48.google.com, queue_id=4h4Kth6CwFz7y5Rh, tls_version=TLSv1.3, cipher=TLS_AES_128_GCM_SHA256, size=3338 (3.3 KiB), applied_plugins=1, duration=3.597251459s]

Here is an (anonymized) milter log line for a test with a newly setup alias with Moderators Access Control on v1.8.1:

2026-07-22 13:45:00 INFO [1.2.3.4] response=reply_code action=reject code=550 reason="550 Not authorized" [received, mail_from=my@gmail.com, rcpt_to=miltertest@mydomain.com, hostname=mail-yx1-f53.google.com, helo=mail-yx1-f53.google.com, tls_version=TLSv1.3, cipher=TLS_AES_128_GCM_SHA256, size=0 (0 B), applied_plugins=1, duration=130.364136ms, state=RcptTo]

It's worth noting that when I created this new test alias, even though I selected "Unrestricted" in the creation page, the permission was "Moderators" in the list and on the edit page.

5 Reply by ZhangHuangbin

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

Re: iRedMail EE - Alias Delivery Restrictions?

tomierna wrote:

It's worth noting that when I created this new test alias, even though I selected "Unrestricted" in the creation page, the permission was "Moderators" in the list and on the edit page.

This issue has been fixed today while testing another feature (called wrong function), will be available in upcoming EE release soon. smile