Not Allowed in State 1

alep11

Hello, I updated Mailcow few days ago and I just realized I am not able to send emails. I am getting “Not allowed in state 1”. Checking my firewall and I see several blocks attempts from mail server trying to ping 1.1.1.1 not sure this is related as I never paid attention to this.
I tried to restart the dockerized container and noticed the unbound service not starting - could this be a DNS issue?

I also tried allowing the ping requests to 1.1.1.1 that were initially blocked by the firewall and removed the subdomain from the hostname from mailcow_hostname=domain.com in mailcow.conf. Think I saw a post out there with this suggestion.
I also tried rolling the server back and restoring mailcow from backups to no avail.

Any help would be greatly appreciated.

alep11

I was able to get the mail flowing again internally by disabling the health check. I no longer see the not allowed message, but mail isn’t working externally, and the update feature isn’t working either.
I am able to ping 1.1.1.1, 8.8.8.8, and 9.9.9.9
I am all over the place here sorry :-(

DocFraggle

The FQDN verification checks for two dots in your FQDN, but you changed it to domain.com (only one dot here) as you wrote above, right? Did you try to change it back to the old value (i.e. mail.domain.com) after disabling the health check?

OK, it seems this was changed to check for at least one dot. I remember that it checked for two dots some time back

mailcow/mailcow-dockerized718dcb6

alep11

All good now. Thank you so much.