jumbokun

  • Apr 11, 2024
  • Joined Apr 5, 2024
  • 1 discussion
  • 3 posts
  • 0 best answers
  • Post posted... wait what?
  • In mailcowdockerized-unbound-mailcow-1 is unhealthy

    For anyone who might encounter the same issue here, I would suggest you directly ban healthy check of unbound in mailcow.conf, it works for me, because I know exactly what happend in my situation.

  • In mailcowdockerized-unbound-mailcow-1 is unhealthy

    Due to the server is in mainland China, I tested it in a hk server, all works (until send emails, cuz I need to apply for 25 port), so I think my dns settings regarding example.com should be correct.
    I also tried the methods regarding using external dns, I configure the both files with the dns server ip I found 127.0.0.1. It doesn’t work.
    For some particular reason I have to use the mainland server, so I wonder whether anyone encountered this situation before and how you solved it, thanks a lot.

    BTW, if I wanna use my email address like something@example.com, do I need to set MAILCOW_HOSTNAME to mail.example.com and then domain name example.com?.. Or the reverse way?.. Thanks a lot!

    So I knew that my unbound isn’t healthy because I can not ping 1.1.1.1 or 8.8.8.8 😀 its in mainland China.
    Anyway to disable this kind of check and let other parts do their job?

    So I knew that my unbound isn’t healthy because I can not ping 1.1.1.1 or 8.8.8.8 😀 its in mainland China.
    Anyway to disable this kind of check and let other parts do their job?

    [unknown]
    So I knew that my unbound isn’t healthy because I can not ping 1.1.1.1 or 8.8.8.8 😀 its in mainland China.
    Anyway to disable this kind of check and let other parts do their job?

    [unknown]
    So I knew that my unbound isn’t healthy because I can not ping 1.1.1.1 or 8.8.8.8 😀 The server is in mainland.
    Anyway to disable this kind of check and let other parts do their job?