I uncovered all of these searching for /my/ in the templates, there could be others.
I’ve modified the templates in question on our installation to have /community/my/... as I didn’t want to assume the %{base_url} variable would be available. Which gets our community around it for now.
Sadly, that is outside of what I have access to. I only run the Discourse instance and by run, I mean purely from the Discourse Software. I do not have access to the infrastructure or our proxy setups.
Even if you could do it that way, I wasn’t suggesting that you change your functional work-around to a different one! I just added it in case it’d work for someone else.
Sounds like it’ll be fixed before a whole lot longer anyway.
POP3 authentication failed. Please verify your pop3 credentials.
Email polling has generated 162 errors in the past 24 hours. Look at the logs for more details.
Connection to the POP3 server is failing with an authentication error. Please check your POP3 settings.
(Corrected) POP3 error aside, there are two links in the message, one to “the logs”, one to “POP3 settings”, both of which omit the subfolder.
Most of the relative links reported in this topic where already fixed in September. Today, I fixed the rest of them and added specs to prevent us from adding broken links in the future.
And, because I really like our translators, I made sure that the new interpolation keys were added to all existing translations – even on Transifex.