On 12.02.25 01:25, Steven Varco via dovecot wrote:
So, after my mandatory rant :D, the DEFAULT setup of dovecot should actually be as simple as possible.
I fully second that. There is no need to discuss whether dovecots default password storage complies to GDPR or not. The administrator or the liable person of a company is responsible for taking care about it, just as Steven Varco mentioned, the same goes with web servers or any publicly available service. The important point is: you can configure dovecot complying to the GDPR. Because what's next - argue that a web framework is not GDPR compliant in its standard configuration because there is no cookie consent popup by default? This is ridiculous. Regards, Robert _______________________________________________ dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-le...@dovecot.org
