service/email.md

@@ -845,10 +845,14 @@ We currently manage Mailman through the `profile::mailman` Puppet
 class, as the [forge modules](https://forge.puppet.com/modules?q=mailman) ([thias/mailman](https://forge.puppet.com/modules/thias/mailman/readme) and
 [nwaller/mailman](https://forge.puppet.com/modules/nwaller/mailman/readme)) are both only for Mailman 2.
 
-Note that the profile currently sets up Mailman with a SQLite
-database, even though it *does* install PostgreSQL and a matching
-user. The configuration of that database user needs to be redone by
-hand after Puppet runs:
+At first we were relying purely on the Debian package to setup
+databases, but this kind of broke apart. The profile originally setup
+the server with a SQLite database, but now it installs
+PostgreSQL and a matching user. It also configures the Mailman server to
+use those, which breaks the Puppet run.
+
+To workaround that, the configuration of that database user needs to
+be redone by hand after Puppet runs:
 
     apt purge mailman3 mailman3-web
     rm -rf /var/spool/postfix/mailman3/data /var/lib/mailman3/web/mailman3web.db