fix: supervisor-app.conf - Correct the log location for postgrey

[polarathene]

Description

Looks like this should have been like every other service and reference a log file(s) based on program name in the supervisor log directory.

• The prior location /var/log/mail/mail.log has a symlink from /var/log/mail.log created in the Dockerfile.
• /var/log/mail/mail.log is created at container startup and tailed as part of the mailserver supervisord service.

---

This should fix a recently reported failure from running the new make run-local-instance dev command:

Error: The directory named as part of the path /var/log/mail/mail.log does not exist in section 'program:postgrey' (file: '/etc/supervisor/conf.d/supervisor-app.conf')
For help, use /usr/bin/supervisord -h
make: *** [Makefile:37: run-local-instance] Error 2

NOTE: I haven't verified this yet, just preparing the PR in anticipation that it addresses the issue.

Type of change

• Bug fix (non-breaking change which fixes an issue)

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• New and existing unit tests pass locally with my changes
• I have added information about changes made in this PR to CHANGELOG.md

[thechubbypanda]

Just testing this branch, getting the same error but with rspamd now:

Error: The directory named as part of the path /var/log/mail/rspamd.log does not exist in section 'program:rspamd' (file: '/etc/supervisor/conf.d/supervisor-app.conf')

Perhaps there's something else at play here?

[thechubbypanda]

Ok nevermind... It appears some remaining docker-data or something was messing things up. I cleaned the lot during some bisecting and now it appears to be working. I'm just so confused as to why it's now working as I even re-cloned the repo...

[polarathene]

Ok nevermind... It appears some remaining docker-data or something was messing things up.

That does seem odd, but glad it's not likely a bug in v13.1 😅

I guess we can merge this as an improvement still. Shall we delay it to v14 then @georglauterbach ? (otherwise feel free to merge)

---

If you'd like to share some information about your environment here, it might help troubleshoot if we get any similar reports.

I know I've recently had some issues with WSL2 with Docker (not possible to use host networking mode, at least not with binding ports within WSL distro, whilst bridge networks aren't accessible on the Windows host, only localhost via port publishing...which would require split DNS for my CoreDNS server to return 127.0.0.1 to windows and container IPs within containers).

[georglauterbach]

I think it's best to delay until v14.0.0.