Closed goose-ws closed 2 years ago
Same for me, unfortunately.
@stefangweichinger @goose-ws Just to rule out the obvious (which is still an issue of the viewer I think): Do you have any single DMARC report in the database already or not? The viewer only works correctly AFAIR after the first report has been received and parsed into the database by the cronjob, which runs every 15 min. DMARC reports are async and triggered by the involved MX'es only after you have send some mails (can be daily or weekly, depending on the policies and how the MX respects those options).
mysql> select count(*) from dmarc_report.report;
+----------+
| count(*) |
+----------+
| 1690 |
+----------+
1 row in set (0.00 sec)
@gutmensch thanks for that feedback. I forwarded one mail to that new imap mailbox, but it seems my docker container has issues connecting via IMAP (using TLS, yes). Might be some docker or network issue here, I have to check that. (the container runs on the mailserver, and connects to IMAPs via a DNS record pointing to a WAN IP which is port-forwarded ... could be a problem).
@gutmensch solved here. Switched to using SSL, now the IMAP connection works, the first report was read and is displayed in the WebGUI of your application. Great, thanks!
@stefangweichinger @goose-ws Just to rule out the obvious (which is still an issue of the viewer I think): Do you have any single DMARC report in the database already or not? The viewer only works correctly AFAIR after the first report has been received and parsed into the database by the cronjob, which runs every 15 min. DMARC reports are async and triggered by the involved MX'es only after you have send some mails (can be daily or weekly, depending on the policies and how the MX respects those options).
mysql> select count(*) from dmarc_report.report; +----------+ | count(*) | +----------+ | 1690 | +----------+ 1 row in set (0.00 sec)
I had a single one, at the time I posted this issue. I've received a few more, while waiting for replies, and it appears to be working as expected now. Not sure if it was that, or something else. But I'll take it. Thanks.
I checked out previous issues #9 and #15 as well as pull request #12 -- however, I'm not able to get around this error.
Here's my compose file:
The port is commented out as I'm reverse proxying to the container, rather than accessing the container on its own.
When I pull up the web interface, I get:
The nginx logs from the container itself confirm this:
The mailbox itself seems to be in fine working order:
I've tried all the fixes from the previous issues/pull request, to no avail. Does anyone see where I'm going wrong?