The ejabberd script shipping with the Debian package (see here) explicitly sets the umask to 027 (see line 72 of that file). While this is a real security improvement (e.g. our databases are now no longer world-readable) this breaks mod_muc_log: the log-files created by it are owned by ejabberd:ejabberd, permissions rw-r-----. This of course makes the files unreadable by any webserver, e.g. Apache. I don't want to put Apache into the ejabberd-group either, because then it would b able to read ejabberds database files.
Would it be possible to add an "umask" option to mod_muc_log that configures what umask will be used for the logfiles?