mailcow-dockerized
mailcow-dockerized copied to clipboard
Domain-wide disclaimer.
How difficult would it be to implement domain-wide disclaimers (signatures)?
What would be the right way to do it?
I suppose we need a "disclaimer" field per domain in the mysql database and then auto-generate config file for some additional milter (altermime?)
Hi, Rspamd will provide this feature probably in the near future. At least we can add/modify mime content. Altermime is not a milter and will break DKIM by changing the content after signing. We could also write our own milter for that. Besides that we COULD implement a second pre-smtpd with Altermime. But I donโt like that idea. It would require multiple changes like another Rspamd listener for just rate limits and stuff like that.
@andryyy Thanks for the feedback. I am not intimately familiar with the milters, but I suppose its not a rocket science, so if you give me a pointer in the right direction I would be happy to code it in python.
So I just write a python milter, that would connect to the mailcow mysql database, look up the domain and the address (I guess we would need a flag to either add disclaimer to all the addresses or only those with a tick) and then add that disclaimer to the message.
Where in the pipeline should we call that milter? Is that smtpd content-milter?
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
I have a requirement to be able to do this as well. Any ideas if or when it would be possible?
@patschi I'd be interested in putting in for the future. Being able to add signatures on a per domain, or even per email address basis to ensure correct/uniform signatures would be great!
Hey together,
I've seen that rspamd has already implemented a function to do this way back in 2019 with version 1.9 of rspamd: https://rspamd.com/announce/2019/03/12/rspamd-1.9.0.html
Mailcow actually ships with version 2.5 of rspamd so this tool is widely available. You can check this using the following command:
docker-compose exec rspamd-mailcow rspamadm mime modify -h
Since I don't know my way around well enough in hacking the config of rspamd or other mailcow components maybe someone of you does?
How can I process my outgoing mails as files to this rspamadm tool to get several disclaimers applied depending on their source domain?
Regards Christian
I think there is no way to do it via API.
Hello,
Iam also interested to use a domain wide disclaimer as signature. Any new informations/tutorials etc. here? ;)
Regards Schmandre
I am also interested, is this generally planned
It would be very interesting for our implementation as well.
I also think it would be great. Regards, Piotr
Super. Zieht ihr die denn dann bzw. rechnet den Aufwand gegen die ab oder wie lรคuft das?
If I understand You correctly this could be implemented in few ways.
Ie. We can add separate option for domain manager so he can add unified signature for all emails in specific domain.
Haha, sorry, I responded to the wrong mail... :) Ignore it, please. I deleted it.
Interested in this as well. We need it in order to comply to GDPR
For GDPR? Why?
Some countries require a legal imprint on all comms, including who controlling members of staff are.
It is not that you cannot add a signature as of today. :) You just cannot do it in bulk.
but i think that's the main show-stopper to use mailcow-dockerized in corporate environments
I doubt that. We use it in many corporate environments without that feature.
larger companies (banks, law firms, airlines to name a few) have a policy of adding mandatory disclaimer added to all outgoing post
when i say corporate, i mean corporate, not just business
We do actually have law firms and banks as customers. :)
If anybody is willing to pay for the development or create a PR, I welcome the change.
well of course we all speak from own experience and it may be different from country to country and company to company, but for a fact i know of certain corporate policies which require the IT department to ensure/enforce mandatory company-wide disclaimers to avoid employees mistakes or some errors / omissions in setting own signatures, especially when such disclaimers are legally required by country law
@andryyy What is the correct way to add a signature/disclaimer right now? I mean, not via sogo, but a signature applied by system even if i use an email client. Is there a way even not bulk?
In the past you added every feature that I have requested, so i think it will not be a problem to pay and support this "corporate" feature just to thank you for the great work you are doing :)
well of course we all speak from own experience and it may be different from country to country and company to company, but for a fact i know of certain corporate policies which require the IT department to ensure/enforce mandatory company-wide disclaimers to avoid employees mistakes or some errors / omissions in setting own signatures, especially when such disclaimers are legally required by country law
I'm in this kind of situation. And the only solution would be to migrate to office 365, which is not an option . mailcow works great with large amounts of email and storage space, it's open and people and community behind it's awesome.
I've also had a request from a client for something like this. In this case, a Christmas message.
Has anybody figure out how to do this themselves?
Hi together,
we also need a solution that allows us to attach one signature per domain. I have also seen that variables are being worked on in the signatures.
Under "What's next" it says "Disclaimers/signatures with variables to use in a pre-defined template per domain and mailbox. ๐"
Can you give an update on this?
Best regards, Oliver
Hello, it will be great to have this option too. Thank you
This feature would be very interesting for us. What is the current state of this?
I am working and actually almost finished with a pre processor, that will remove Ads and Trackers as well as suspicious CSS and images. Adblocking will be provided by BraveBlock using Adblock lists.
When this part is done, it will be very easy to use it the other way round for changing mail content by part and adding a disclaimer via Jinja template.
It is a pita to walk the parts and modify them. MIME is really a bit...difficult. ;)
Hello Any update on that subject? Best regards