Email status red even when valid

[nebulon]

@d19dotca this indeed required a rate-limit fix and was deployed.

[d19dotca]

@nebulon Thanks! Question... how does the service it's hitting which you needed to raise the rate limit actually work in this situation? I ask because I'd have assumed the red dot only shows up if there's something in the Status tab that's wrong, so seeing those all be green yet the main dot on Mail page be red was alarming/concerning. I assume there should maybe be another fix to ensure those are consistently displayed? Or to allow for a sort of graphical pop-over if it's due to rate limiting in the future?

[d19dotca]

It seems this issue is back for me today with red dots even though the status details show it as all valid (no DNS issues, no blacklists, etc).

Oct 03 22:39:28 box:sysinfo/generic getServerIPv4: getting server IP
Oct 03 22:39:28 box:sysinfo/generic getServerIPv4: getting server IP
Oct 03 22:39:28 box:sysinfo/generic getServerIPv4: getting server IP
Oct 03 22:39:28 box:sysinfo/generic getServerIPv4: getting server IP
Oct 03 22:39:28 box:sysinfo/generic getServerIPv4: getting server IP
Oct 03 22:39:28 box:sysinfo/generic getServerIPv4: getting server IP
Oct 03 22:39:28 box:sysinfo/generic getServerIPv4: getting server IP
Oct 03 22:39:28 box:sysinfo/generic getServerIPv4: getting server IP
Oct 03 22:39:28 box:sysinfo/generic getServerIPv4: getting server IP
Oct 03 22:39:28 box:sysinfo/generic getServerIPv4: getting server IP
Oct 03 22:39:28 box:sysinfo/generic getServerIPv4: getting server IP
Oct 03 22:39:28 box:sysinfo/generic getServerIPv4: getting server IP
Oct 03 22:39:28 box:sysinfo/generic getServerIPv4: Error getting IP null
Oct 03 22:39:28 box:sysinfo/generic getServerIPv4: Error getting IP null
Oct 03 22:39:28 box:sysinfo/generic getServerIPv4: Error getting IP null
Oct 03 22:39:28 box:sysinfo/generic getServerIPv4: Error getting IP null
Oct 03 22:39:28 box:sysinfo/generic getServerIPv4: Error getting IP null
Oct 03 22:39:28 box:mail Ignored error - dns.ptr : Unable to detect IPv4. API server (ipv4.api.cloudron.io) unreachable
Oct 03 22:39:28 box:mail check rbl was rejected. This is not expected
Oct 03 22:39:28 box:sysinfo/generic getServerIPv4: Error getting IP null
Oct 03 22:39:28 box:sysinfo/generic getServerIPv4: Error getting IP null
Oct 03 22:39:28 box:sysinfo/generic getServerIPv4: Error getting IP null
Oct 03 22:39:28 box:sysinfo/generic getServerIPv4: Error getting IP null
Oct 03 22:39:28 box:sysinfo/generic getServerIPv4: Error getting IP null
Oct 03 22:39:28 box:mail Ignored error - dns.ptr : Unable to detect IPv4. API server (ipv4.api.cloudron.io) unreachable
Oct 03 22:39:28 box:mail check rbl was rejected. This is not expected
Oct 03 22:39:28 box:sysinfo/generic getServerIPv4: Error getting IP null
Oct 03 22:39:28 box:sysinfo/generic getServerIPv4: Error getting IP null
Oct 03 22:39:28 box:mail Ignored error - dns.ptr : Unable to detect IPv4. API server (ipv4.api.cloudron.io) unreachable
Oct 03 22:39:28 box:mail check rbl was rejected. This is not expected
Oct 03 22:39:28 box:sysinfo/generic getServerIPv4: Error getting IP null
Oct 03 22:39:28 box:mail Ignored error - dns.ptr : Unable to detect IPv4. API server (ipv4.api.cloudron.io) unreachable
Oct 03 22:39:28 box:mail check rbl was rejected. This is not expected
Oct 03 22:39:28 box:sysinfo/generic getServerIPv4: Error getting IP null
Oct 03 22:39:28 box:mail Ignored error - dns.ptr : Unable to detect IPv4. API server (ipv4.api.cloudron.io) unreachable
Oct 03 22:39:28 box:mail check rbl was rejected. This is not expected
Oct 03 22:39:28 box:sysinfo/generic getServerIPv4: Error getting IP null
Oct 03 22:39:28 box:sysinfo/generic getServerIPv4: Error getting IP null
Oct 03 22:39:28 box:sysinfo/generic getServerIPv4: Error getting IP null
Oct 03 22:39:28 box:sysinfo/generic getServerIPv4: Error getting IP null
Oct 03 22:39:28 box:mail Ignored error - dns.ptr : Unable to detect IPv4. API server (ipv4.api.cloudron.io) unreachable
Oct 03 22:39:28 box:mail check rbl was rejected. This is not expected
Oct 03 22:39:28 box:sysinfo/generic getServerIPv4: Error getting IP null
Oct 03 22:39:28 box:mail Ignored error - dns.ptr : Unable to detect IPv4. API server (ipv4.api.cloudron.io) unreachable
Oct 03 22:39:28 box:mail check rbl was rejected. This is not expected
Oct 03 22:39:28 box:sysinfo/generic getServerIPv4: Error getting IP null
Oct 03 22:39:28 box:mail Ignored error - dns.ptr : Unable to detect IPv4. API server (ipv4.api.cloudron.io) unreachable
Oct 03 22:39:28 box:mail check rbl was rejected. This is not expected
Oct 03 22:39:28 box:sysinfo/generic getServerIPv4: Error getting IP null
Oct 03 22:39:28 box:sysinfo/generic getServerIPv4: Error getting IP null
Oct 03 22:39:28 box:mail Ignored error - dns.ptr : Unable to detect IPv4. API server (ipv4.api.cloudron.io) unreachable
Oct 03 22:39:28 box:mail check rbl was rejected. This is not expected
Oct 03 22:39:28 box:sysinfo/generic getServerIPv4: Error getting IP null
Oct 03 22:39:28 box:sysinfo/generic getServerIPv4: Error getting IP null
Oct 03 22:39:28 box:sysinfo/generic getServerIPv4: Error getting IP null
Oct 03 22:39:28 box:mail Ignored error - dns.ptr : Unable to detect IPv4. API server (ipv4.api.cloudron.io) unreachable
Oct 03 22:39:28 box:mail check rbl was rejected. This is not expected
Oct 03 22:39:28 box:sysinfo/generic getServerIPv4: Error getting IP null
Oct 03 22:39:28 box:mail Ignored error - dns.ptr : Unable to detect IPv4. API server (ipv4.api.cloudron.io) unreachable
Oct 03 22:39:28 box:mail check rbl was rejected. This is not expected

[imc67]

@d19dotca was it solved then? I've never seen a full list of green dots while it should be.

[girish]

@d19dotca said in Email status red even when valid:

Oct 03 22:39:28 box:mail check rbl was rejected. This is not expected

This seems to be the root cause. Maybe another one of the rbl servers is gone now, let me check.

[girish]

I suspect it's failing because the IP detection fails. I have put a log now to double check if that is the issue.

Also, the red dot does not affect the mail server functionality in any way. It's merely diagnostics.

[d19dotca]

@imc67 said in Email status red even when valid:

@d19dotca was it solved then? I've never seen a full list of green dots while it should be.

Yes, it was solved for a bit once Cloudron added in their own SMTP port checker endpoint, as before it was an issue from SMTP port being unreachable (but incorrectly, Cloudron was marking that because it couldn't connect to a particular SMTP server in its test suite but was an issue with Microsoft removing the server they were using previously).

Recently though I noticed it again, before 7.3 and no difference with 7.3 either.

--

@girish said in Email status red even when valid:

Also, the red dot does not affect the mail server functionality in any way. It's merely diagnostics.

Yes that's correct, it's thankfully not impacting mail delivery, however is very annoying as of course anytime I see alerts of any kind I have a mini anxiety attack thinking something critically important is broken. Seeing false-alarms is not a great UX. Hopefully will be fixed soon.

[d19dotca]

@girish said in Email status red even when valid:

I suspect it's failing because the IP detection fails.

Ahhh, good idea! I just remembered that a few weeks ago I had changed my IP in Cloudron from Static IP Address to Public IP just to keep things a bit more automated in the event of a disaster recovery situation where I have to change IPs quickly. Oddly I hadn't noticed this behaviour change though until the other week (I dismissed it at first thinking it was temporary, and knowing that 7.3 was right around the corner hoping that'd maybe fix it too).

While it auto-detected perfectly fine (the IP always showed up in the Network tab as correctly detected), it seems that glitches out the Email status page for some reason. I just switched it back to Static IP and bam, it started working as expected again.

Is this a defect perhaps in the IP detection? It seems to work okay though as it correctly identified the IP address, so perhaps something a bit different where it wasn't using that correctly for some domains in the status checks? But then again, wouldn't the DNS MX record then be a mismatch in the status report if that was true?

Anyways just wanted to report back, it seems it does have something to do for me with the automatic IP detection in Cloudron for Public IP, works fine if I switch it back to Static.

[girish]

@d19dotca ah good, atleast in the next release we will have to logs to assist realizing this quicker!

Edit: I misread your comment. Mm, not sure why it's not detecting the IP correctly. If you go to Network page , does it show "xx.yy (autodetected)" correctly consistently ? (I guess you can refresh the page some 5-6 times to see if it's failing).

[d19dotca]

@girish Yes it always showed it correctly as auto-detected. That's why I was surprised that was an issue at all. If it couldn't identify the IP, wouldn't the status for all the mail domains fail the health check too?

[girish]

@d19dotca said in Email status red even when valid:

wouldn't the status for all the mail domains fail the health check too?

Excellent point.. Is your Cloudron having this issue right now? If so, if you drop us an email on support, I can debug this further.

[d19dotca]

@girish it isn’t because I made it static, however I can still offer you access and enable it to be the auto-discovery instead.

[imc67]

@d19dotca @girish @nebulon after all the recent versions this is still not solved here

[girish]

@imc67 yes, this one is only fixed in 7.3.5 . Still waiting for the fix for the graphs and mailbox listing issue to get that out.