Joris Le Blansch

Are you talking about sync jobs inside mailcow GUI or are you talking about the imapsync command line tool?

OK sounded as you were using the CLI tool from your initial report. That works fine and is what I usually use. But the `bad option timeout1` seems to indicate...

That's just the current status bar (AFAIK showing up to the last 40 minutes). You can see much more detail drilling down in your monitor and selecting a time span...

Ah, I see what you mean. I'm usually only looking at backend. For the status pages, there is a discussion around this topic here #637 . So you can contribute...

This works for me testing with your steps just now:  But I have the server TZ same as client TZ that's probably where the difference comes...

(...)_Just fixing the bug will change the state_(...) is addressed to who? The idea is to collaborate and not just * wait* for someone to pickup on an issue that...

Thanks for your reply. If that was already in 1.7 I should also have it in my fork of `main` (correct?) but my result shows wrongly as > 10 DNS...

Thanks for the detailed explanation! Indeed I counted 6 "manually" but didn't look at the MX records which explains the 12 and hence the > 10 warning/error. So that means,...

Indeed that would be great, otherwise we would get returns like "but it works on MXToolbox" or whatever other "trusted" tool and a table showing the lookups actually counted will...

For the expiration date to appear on the status page, you need to switch "Show Certificate Expiry" to on on the bottom left when editing the status page. ![Screenshot from...