In reply to @neo:shdw.fr
They are not. Microsoft usually pits me into spam folders. When I talk to the techs, they say it is a personal somain so cannot be trusted

In reply to @nextgens:matrix.org
Then you can try to set sign_networks with an override... Mailu will use the first domains' keys for both DKIM and ARC IIRC

i have this (trying to set use_vault = false because mailu admin won't return a reply for a domain that's not added). /dkim/... exists, and the mail is coming from a network listed in /overrides/dkim_ip.map. any ideas why it still might not be signing, anything else that needs to be done?

2341edaa290e:/app# cat /overrides/dkim_signing.conf 
sign_networks = "/overrides/dkim_ip.map";
path = "/dkim/$domain.$selector.key";
use_vault = false;

In reply to @nextgens:matrix.org
Then you can try to set sign_networks with an override... Mailu will use the first domains' keys for both DKIM and ARC IIRC

i have this (trying to set use_vault = false because mailu admin won't return a reply for a domain that's not in "Domains"). /dkim/... exists, and the mail is coming from a network listed in /overrides/dkim_ip.map. any ideas why it still might not be signing, anything else that needs to be done?

2341edaa290e:/app# cat /overrides/dkim_signing.conf 
sign_networks = "/overrides/dkim_ip.map";
path = "/dkim/$domain.$selector.key";
use_vault = false;

3wc ~ they/them superfly
I think I've found a solution to make mailman DKIM signing work with mailu (make sure to set DMARC mitigation to replace from or envelop and do that conditionless, not sure how the default for new lists can be changed so it doesn't need to be set everytime).

Based on the great blog post you mentioned (which seems to be the single complete resource regarding mailu+mailman), the documentation from docker mailman and looking at the mailu source I've used the following for /container-data/mailu/overrides/postfix/postfix.cf:

# Support the default VERP delimiter.
recipient_delimiter = +
unknown_local_recipient_reject_code = 550
owner_request_special = no

virtual_mailbox_maps = regexp:/opt/mailman-core-data/postfix_lmtp, \${podop}mailbox
virtual_mailbox_domains = \${podop}domain
transport_maps = regexp:/opt/mailman-core-data/postfix_lmtp, lmdb:/etc/postfix/transport.map, \${podop}transport
local_recipient_maps = regexp:/opt/mailman-core-data/postfix_lmtp
#relay_domains = regexp:/opt/mailman-core-data/postfix_domains, \${podop}transport

Then add domains in mailman as usual and also add it to the mailu mail domains (not the relay domains). Then generate dkim stuff in mailu and add it to the DNS like usual. Also make sure the domain has no wildcard receive (e.g. %@example.org) set, but apart from that, mailing lists and "normal" inboxes or aliases can even be intermingled for the same domain (but I prefer to have an extra lists.example.org so it's clearly separated).

In reply to @qg:supercable.onl

3wc ~ they/them superfly
I think I've found a solution to make mailman DKIM signing work with mailu (make sure to set DMARC mitigation to replace from or envelop and do that conditionless, not sure how the default for new lists can be changed so it doesn't need to be set everytime).

Based on the great blog post you mentioned (which seems to be the single complete resource regarding mailu+mailman), the documentation from docker mailman and looking at the mailu source I've used the following for /container-data/mailu/overrides/postfix/postfix.cf:

# Support the default VERP delimiter.
recipient_delimiter = +
unknown_local_recipient_reject_code = 550
owner_request_special = no

virtual_mailbox_maps = regexp:/opt/mailman-core-data/postfix_lmtp, \${podop}mailbox
virtual_mailbox_domains = \${podop}domain
transport_maps = regexp:/opt/mailman-core-data/postfix_lmtp, lmdb:/etc/postfix/transport.map, \${podop}transport
local_recipient_maps = regexp:/opt/mailman-core-data/postfix_lmtp
#relay_domains = regexp:/opt/mailman-core-data/postfix_domains, \${podop}transport

Then add domains in mailman as usual and also add it to the mailu mail domains (not the relay domains). Then generate dkim stuff in mailu and add it to the DNS like usual. Also make sure the domain has no wildcard receive (e.g. %@example.org) set, but apart from that, mailing lists and "normal" inboxes or aliases can even be intermingled for the same domain (but I prefer to have an extra lists.example.org so it's clearly separated).

In reply to @nextgens:matrix.org
You need it to operate a mailing list; without you can't "impersonate" another domain if it is DMARC protected

In reply to @nextgens:matrix.org
It's also useful when you forward emails and why Mailu signs everything with it