Thanks for letting me know that error is on your server, as well. That was really helpful, as my ability to reproduce on my test servers was hit or miss.
I updated Nico’s ticket with my findings, but figured it would be prudent to do so, here, as well.
I’ve not had any other reports of this issue, but it seems to potentially be related to a few things:
- The server having been converted to Dovecot or the Dovecot MSA (vs being newly installed after those were standard)
- /service/smtp2 having been removed (vs that folder never being on the server to begin with, as would be the case with a new install).
- An issue in the past where Dovecot went down, and then would not restart because SMTP2 started itself and was holding the port (which is something permanently solved by removing that folder)
So InterWorx, for some reason, on some servers is looking for logging for SMTP2, and of course that does not exist for servers running the Dovecot MSA to handle 587.
Good news is that this error does not look to be related to any expected logging. Dovecot log, Send log, SMTP, Maillog, etc, all logging correctly and up to date.
I did find a cache file on Nico’s server:
I removed that file, and the error resolved itself on the system health page. I ran various crons that look for problem detecting and logging, and it did not come back, either.
That cache file can be safely removed. It will regenerate if anything attempts to check the cached value of the SMTP2 port, but the only thing I could think of that might do so, since that service no longer exists, is the various crons, so it seems a safe bet it will stay gone.
I’m submitting a bug report to make it so that the problem detector doesn’t look for SMTP2 logging on servers using the Dovecot MSA, and to maybe remove that cache file, as well, if the Dovecot MSA is enabled. I don’t have an ETA. However, the error does not seem to mean anything that is supposed to be working is broken, and it can be easily reset by removing the above cache file.