LDAP with additional alias file

[JacksonYuuki]

Hi!
I spent a few hours searching for an answer to this, but couldn't find one...
I connected my dms to openldap and created some users with an additional mailAlias, which seems to have deactivated my postfix_virtual.cf file.
The setup alias list shows every alias in the file, but when I send an email to one of the aliases, I receive a bounce message saying that the user doesn't exist.

Is it possible to use both LDAP mailAlias and the addresses I defined in the file?
I want to create email distribution lists for my organisation that include some external email addresses so I can't add them to ldap.

Maybe someone here can help me or can suggest another way how I can make this work.

[polarathene]

I connected my dms to openldap and created some users with an additional mailAlias, which seems to have deactivated my postfix_virtual.cf file.
The setup alias list shows every alias in the file, but when I send an email to one of the aliases, I receive a bounce message saying that the user doesn't exist.

Presently DMS disables overrides the file based aliases when LDAP config for aliases is detected:

docker-mailserver/target/scripts/startup/setup.d/ldap.sh

Lines 71 to 75 in cb76075

	if [[ -f /etc/postfix/ldap-aliases.cf ]] && [[ -f /etc/postfix/ldap-groups.cf ]]; then
	postconf 'virtual_alias_maps = ldap:/etc/postfix/ldap-aliases.cf, ldap:/etc/postfix/ldap-groups.cf'
	else
	_log 'warn' "'/etc/postfix/ldap-aliases.cf' and / or '/etc/postfix/ldap-groups.cf' not found"
	fi

docker-mailserver/target/scripts/startup/setup.d/ldap.sh

Lines 59 to 69 in cb76075

	if [[ -f /etc/postfix/ldap-users.cf ]]; then
	postconf 'virtual_mailbox_maps = ldap:/etc/postfix/ldap-users.cf'
	else
	_log 'warn' "'/etc/postfix/ldap-users.cf' not found"
	fi
	if [[ -f /etc/postfix/ldap-domains.cf ]]; then
	postconf 'virtual_mailbox_domains = /etc/postfix/vhost, ldap:/etc/postfix/ldap-domains.cf'
	else
	_log 'warn' "'/etc/postfix/ldap-domains.cf' not found"
	fi

The file based ones are originally configured here:

docker-mailserver/target/postfix/main.cf

Lines 103 to 107 in cb76075

	# Postfix lookup tables for verifying valid users and managed mail domains:
	# Populated during startup in: scripts/helpers/postfix.sh
	virtual_mailbox_domains = /etc/postfix/vhost
	# Populated during startup in: scripts/helpers/aliases.sh
	virtual_alias_maps = texthash:/etc/postfix/virtual

---

The setup ... related commands are not LDAP aware and just process our own config files in the DMS config volume AFAIK.

Is it possible to use both LDAP mailAlias and the addresses I defined in the file?

Yes I think it should be, it just might be a bit annoying to workaround until a PR is raised to resolve it better.

Postfix should accept multiple config files for the same setting (as shown in an above snippet for virtual_mailbox_domains that retained the vhost config file), and I think you should be able to adjust these settings as needed after DMS scripts have finished, by using our user-patches.sh support that runs at the end before starting services in the DMS container.

#!/bin/bash

# Resolve aliases first from `/etc/postfix/virtual` (derived from `postfix-virtual.cf` / `setup alias add ...`):
postconf 'virtual_alias_maps = /etc/postfix/virtual, ldap:/etc/postfix/ldap-aliases.cf, ldap:/etc/postfix/ldap-groups.cf'

If you want to give your LDAP information precedence, you could put /etc/postfix/virtual at the end of that list instead.

Just take those lines above for your user-patches.sh file and put it in the DMS config volume (/tmp/docker-mailserver), it should be run when you run a fresh DMS container (docker compose up --force-recreate). You can shell into the container and run the command postconf virtual_alias_maps and it should return the value set above if all is working correctly. I don't think anything in DMS reconfigures that setting after initial setup is done, so this solution should work for you.

[polarathene]

If the above does work for you and after some testing there are no issues with it, let me know (or raise a feature request). Nothing comes to mind why this shouldn't be the config used, but the LDAP support was contributed long ago without much context on such decisions 😓

[JacksonYuuki]

Hi and thank you!

I pasted the code in the user-patches.sh but it didn't work..but you wrote the solution to this a few lines above and I added texthash: to the script:

#!/bin/bash

# Resolve aliases first from `/etc/postfix/virtual` (derived from `postfix-virtual.cf` / `setup alias add ...`):
postconf 'virtual_alias_maps = texthash:/etc/postfix/virtual, ldap:/etc/postfix/ldap-aliases.cf, ldap:/etc/postfix/ldap-groups.cf'

I sent a testmail and it seems to work :D

Unfortunately, I don't have much time to test this any further right now.
In the meantime, I used a workaround involving LDAP accounts and Sieve filters, which I updated with scripts. I think I can now try my original plan again with the 'postfix-virtual' file and protected destinations for senders.

[polarathene]

Yeah that was a mistake by me, as you noticed texthash: should have been prepended to indicate the table type.

Unfortunately, I don't have much time to test this any further right now.

No worries 👍 I think it's a valid fix to address so I'll look into adding it into a future release of DMS. Thanks for bringing the bug to our attention :)