Not necessary. Cluebringer was dropped long time ago.

We can define few new parameters for this purpose:

- One parameter (with True/False value) to indicate whether adds "postmaster@" automatically while creating new mail domain name.
- One parameter (with a list of usernames) to define the additional alias addresses assigned to postmaster@ users while creating new mail domain. This is used only when above parameter is set to True.

There is another, way better solution.

/*!40101 SET @OLD_CHARACTER_SET_CLIENT=@@CHARACTER_SET_CLIENT */;
/*!40101 SET NAMES utf8 */;
/*!50503 SET NAMES utf8mb4 */;
/*!40014 SET @OLD_FOREIGN_KEY_CHECKS=@@FOREIGN_KEY_CHECKS, FOREIGN_KEY_CHECKS=0 */;
/*!40101 SET @OLD_SQL_MODE=@@SQL_MODE, SQL_MODE='NO_AUTO_VALUE_ON_ZERO' */;

-- Exportiere Struktur von Tabelle vmail.common_alias
CREATE TABLE IF NOT EXISTS `common_alias` (
  `address` varchar(128) NOT NULL,
  `goto` varchar(128) NOT NULL,
  `created` datetime DEFAULT current_timestamp(),
  `modified` datetime DEFAULT NULL ON UPDATE current_timestamp(),
  `active` tinyint(1) NOT NULL DEFAULT 1,
  PRIMARY KEY (`address`),
  UNIQUE KEY `address` (`address`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8;

-- Exportiere Daten aus Tabelle vmail.common_alias: ~4 rows (ungefähr)
DELETE FROM `common_alias`;
/*!40000 ALTER TABLE `common_alias` DISABLE KEYS */;
INSERT INTO `common_alias` (`address`, `goto`, `created`, `modified`, `active`) VALUES
    ('abuse', 'goto@mail', '2019-06-24 03:35:46', '2019-06-24 03:36:33', 1),
    ('hostmaster', goto@mail', '2019-06-24 03:37:45', '2019-06-24 03:37:57', 1),
    ('no-reply', 'goto@mail', '2020-01-12 04:32:23', '2020-01-12 04:32:44', 1),
    ('webmaster', 'goto@mail', '2020-01-19 14:25:48', '2020-01-19 14:26:04', 1);
/*!40000 ALTER TABLE `common_alias` ENABLE KEYS */;

/*!40101 SET SQL_MODE=IFNULL(@OLD_SQL_MODE, '') */;
/*!40014 SET FOREIGN_KEY_CHECKS=IF(@OLD_FOREIGN_KEY_CHECKS IS NULL, 1, @OLD_FOREIGN_KEY_CHECKS) */;
/*!40101 SET CHARACTER_SET_CLIENT=@OLD_CHARACTER_SET_CLIENT */;

/etc/postfix/mysql/virtual_common_alias_maps.cf

hosts       = 127.0.0.1:3306
user        = vmail
password    = yourpassword
dbname      = vmail
query       = SELECT goto FROM common_alias WHERE address = '%u' AND active='1' AND '%d' IN (SELECT domain FROM domain WHERE domain='%d');

/etc/postfix/main.cf

virtual_alias_maps =
    proxy:mysql:/etc/postfix/mysql/virtual_alias_maps.cf
    proxy:mysql:/etc/postfix/mysql/virtual_common_alias_maps.cf
    proxy:mysql:/etc/postfix/mysql/domain_alias_maps.cf
    proxy:mysql:/etc/postfix/mysql/catchall_maps.cf
    proxy:mysql:/etc/postfix/mysql/domain_alias_catchall_maps.cf

this will do the following:

each mail sent at abuse@yourmail.tld (postmaster, hostmaster, no-reply) will be automatically forwarded to your desired forwarding address, as long as the yourmail.tld is an active and enabled mail domain.

you dont need to create ANY mail accounts, you need to block them which should be easyly doable by a simple regex:

function EMAILCheckReserved($name)
    {
    return !preg_match("!^(?i)(abuse|hostmaster|postmaster|no-reply)$!", $name);
    }

just deny any creation of the reserved mailboxes.

for the no reply one, it actually needs to be a real mailbox, with 0 quota, just make sure the transport is set to "discard"

you can aswell allow sender forgery in iredapd to allow forged senders with no-reply@, but this is another thing, there are tutorials for doing this.

Hope this works out for you!

@ZhangHuangbin

I suggest this solution as implemented by default, just with empty database, so ppl can just add those aliases if wanted, it has 0 influence if the tables are left empty.

the management of mailboxes can aswell get implemented into iredadmin itself, as global admin you can choose to create and manage those common aliases and aswell block the creation of mailboxes with reserved virtual names.

makeing iredmail RFC valid by default would be a nice thing, and the effort is not that much

This solution is making things complex, no interest. Sorry.

We already have SQL tables and Postfix sql queries to get aliases/forwardings, no need to introduce a new sql table and new postfix sql query at all. We just need to create required aliases/forwardings while creating new domain, then why make things complex?

My preferred solution stays the same, but slightly improved:
==============
We can introduce a global parameter (a list with Python dicts) in iRedAdmin-Pro config file to indicate whether adds "postmaster@" automatically while creating new mail domain name.  Optionally set a hard-coded password (if empty, generate a random one instead). It's also able to specified alias addresses like "abuse@" to this account.

Note: currently we should just implement auto-create user account first, but ideally with this setting, it's able to auto-create any account type (e.g. an "all@" mailing list, alias, etc) while creating new domain.
==============

The (DRAFT) setting should look like this:

NEW_DOMAIN_POST_HOOKS = [
    {"type": "user",            # required
     "username": "postmaster",          # required
     "aliases": ["abuse", "no-reply"],    # optional
     "password": "my-hard-coded-password"},    # optional
    {"type": "ml",             # "ml" is subscribable (mlmmj) mailing list
     "username": "all",
     "aliases": ["all-employees", "all-people"]},
]

Hello ZhangHuangbin,
can you please write what's the current state of this feature?

I need to create postmaster@ alias for all my existing domains and it's unclear to me the best way to do that.

Thanks