Shared or global rspamd whitelist

basicmonkey

Is there a way in the rspamd settings map of re-using a whitelist for another domain? At present, mailcow generates a whitelist for my SoGo contacts for the domain that has those contacts in. I would like to use this whitelist for other domains too, or make it so that any contact on any domain will whitelist to all/selected domains. Our server is only for our organisation and so any contact should be whitelisted.

I notice that each whitelist group has a recipient regex which could be changed to add the other domains, but where could I do this without affecting future updates?

Could I add another rspamd setting to re-use a whitelist dynamically from a domain? I’d like to avoid having to create a whitelist file which would need updating.

I’ve raised an issue on the repo: mailcow/mailcow-dockerized3549

Many thanks,

James

diekuh

Hi,

I have seen the “issue”. But you just deleted the whole template without reading it and posted an invalid bug report. 🙁 At least use the feature request template. 🙂

You need to edit settings.php. This is actually not much hassle. I will talk to Michael about his thoughts on this. Should be optional, though…

André

basicmonkey

Hi André,

Thanks for coming back. Apologies for clearing off the template. I thought that as long as the relevant information was in there that I didn’t need to leave the template structure in. Will do next time!

Definitely optional, everyone has different use requirements!

I’ll reply on the Git repo now.

Cheers,

James

diekuh

What is your opinion on the ACL stuff? I think that’s pretty clever.

basicmonkey

Using ACLs is a great idea. It works well for calendars.

Like with calendars where you can share only date/time, you’d need to be able to share only the whitelist to other users as your address book could contain personal items which you don’t want others to see, but still apply to their whitelists.

For now, I’ve copied the whitelist generated from my main user (with the populated AB) as a manual rule in rspamd settings map so the function is working but isn’t dynamically updated. For simplicity, could there be a way of aliasing an existing whitelist for a domain?

A rule that takes ‘whitelist_jamesblahblah’ which is applied to ‘james@blah.blah’ but then apply to ‘*@blah.blah’ much like the manual whitelist entries in the domain setup. To achieve what I’m after, this would need to be cross domain too.

Thanks, James.

diekuh

You can connect domains with SOGo (make them visible for each other) and then share address books.

I understand your point though. You don’t want to have it visible for others. We need to check that. Perhaps I will make it an option via vars.local.inc.php.

basicmonkey

Thanks André, I didn’t see about connecting domains, very interesting and would help. Where abouts are the docs for this?

Mailcow is by far the best mail/contacts/calendar platform I’ve found. We’ve been through a lot over the years. Very nice interface, great integration.

diekuh

\o/ Thank you VERY much. 🙂

Edit data/conf/sogo/sogo.conf and find:

// SOGoDomainsVisibility = (
//  (domain1.tld, domain5.tld),
//  (domain3.tld, domain2.tld)
// );

So…

SOGoDomainsVisibility = (
  (domain1.tld, domain5.tld)
);

…will do it. Run docker-compose restart sogo-mailcow afterwards. 🙂

diekuh

We should probably split SOGo into sub-sections… whatever, better than nothing for now:

https://mailcow.github.io/mailcow-dockerized-docs/u_e-sogo/

basicmonkey

That’s very useful thanks. Means I can segregate some calendars across different accounts but share them between domains.

I’m going to try this and share address books between my user on each domain which will hopefully share the whitelist too. The other users can wait! ;o)

diekuh

That’s not implemented yet. I don’t know if and when someone will work on it.