Mailcow-dockerized: I can send emails but can't receive any.

Created on 27 Aug 2019  路  26Comments  路  Source: mailcow/mailcow-dockerized

Hi
I have installed mailcow on Centos 7.6. Installation worked smoothly. But only problem is I can't receive any email from any host including own host. In Sogo I can see my all sent mails in sent tab but inbox is empty.

Rspamd scans all incoming and outgoing emails but incoming emails are shows Unknown on Authenticated user in history tab.

I found some errors on Dovecot log.

  • 27/08/2019, 19:32:25 err indexer-worker([email protected])<6591>: Error: Mailbox Sent: Status lookup failed: Internal error occurred. Refer to server log for more information. [2019-08-27 18:32:25]
  • 27/08/2019, 00:52:49 err indexer-worker([email protected])<18185>: Error: Mailbox Sent: Status lookup failed: Internal error occurred. Refer to server log for more information. [2019-08-26 23:52:49]
  • 27/08/2019, 00:37:57 err indexer-worker([email protected])<18185>: Error: Mailbox Sent: Status lookup failed: Internal error occurred. Refer to server log for more information. [2019-08-26 23:37:57]
  • 26/08/2019, 23:09:33 err indexer-worker([email protected])<16366>: Error: Mailbox Sent: Status lookup failed: Internal error occurred. Refer to server log for more information. [2019-08-26 22:09:33]
  • 26/08/2019, 23:01:35 err indexer-worker([email protected])<16366>: Error: Mailbox Sent: Status lookup failed: Internal error occurred. Refer to server log for more information. [2019-08-26 22:01:35]

my DNS setup is

**;; A Records
mail.somedomain.com IN A 11.222.33.444

;; AAAA Records
mail.somedomain.com IN AAAA 2001:db8:85a3:8d3:1319:8a2e:370:7348

;; CNAME Records
autoconfig.somedomain.com IN CNAME mail.somedomain.com.
autodiscover.somedomain.com IN CNAME mail.somedomain.com.

;; MX Records
somedomain.com IN MX 10 mail.somedomain.com

;; TXT Records
dkim._domainkey.somedomain.com IN TXT "v=DKIM1;k=rsa;t=s;s=email;p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDGMjj8MVaESl30KSPYdLaEreSYzvOVh15u9YKAmTLgk1ecr4BCRq3Vkg3Xa2QrEQWbIvQj9FNqBYOr3XIczzU8gkK5Kh42P4C3DgNiBvlNNk2BlA5ITN/EvVAn/ImjoGq5IrcO+hAj2iSAozYTEpJAKe0NTrj49CIkj5JI6ibyJwIDAQAB"
_dmarc.somedomain.com IN TXT "v=DMARC1; p=reject; rua=mailto:[email protected]"
somedomain.com IN TXT google-site-verification=-dhsoFQadgDKJR7BsB6bc1j5yfqjUpg_b-1pFjr7o3x
somedomain.com IN TXT "v=spf1 mx ~all"**

In system & container tab Solr stats is Solr is starting, disabled or died. But It's actually running in a container. I restarted too. But status is same.

my mailcow is running in mai.somedomain host. Actually I need to send and receive emails from [email protected] not [email protected]

Please help me to sort this out. Last two days I have been struggling to sort this out. But no luck.

Thank you very much.

Most helpful comment

Make sure to have the following DNS records:

;; A Records
mail.somedomain.com.    1   IN  A   x.x.x.x

;; CNAME Records
autoconfig.somedomain.com.  1   IN  CNAME   mail.somedomain.com.
autodiscover.somedomain.com.    1   IN  CNAME   mail.somedomain.com.

;; MX Records
somedomain.com. 1   IN  MX  10 mail.somedomain.com.

;; SRV Records
_autodiscover._tcp.somedomain.com.  1   IN  SRV 0 1 443 mail.somedomain.com.
_caldavs._tcp.somedomain.com.   1   IN  SRV 0 1 443 somedomain.com.
_carddavs._tcp.somedomain.com.  1   IN  SRV 0 1 443 somedomain.com.
_imaps._tcp.somedomain.com. 1   IN  SRV 0 1 993     somedomain.com.
_imap._tcp.somedomain.com.  1   IN  SRV 0 1 143     somedomain.com.
_pop3s._tcp.somedomain.com. 1   IN  SRV 0 1 995     somedomain.com.
_pop3._tcp.somedomain.com.  1   IN  SRV 0 1 110     somedomain.com.
_sieve._tcp.somedomain.com. 1   IN  SRV 0 1 4190    somedomain.com.
_smtps._tcp.somedomain.com. 1   IN  SRV 0 1 465     somedomain.com.
_submission._tcp.somedomain.com.    1   IN  SRV 0 1 587 somedomain.com.

;; TLSA Records
_110._tcp.mail.somedomain.com.  1   IN  TLSA    3 1 1 xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
_143._tcp.mail.somedomain.com.  1   IN  TLSA    3 1 1 xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
_25._tcp.mail.somedomain.com.   1   IN  TLSA    3 1 1 xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
_4190._tcp.mail.somedomain.com. 1   IN  TLSA    3 1 1 xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
_443._tcp.mail.somedomain.com.  1   IN  TLSA    3 1 1 xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
_465._tcp.mail.somedomain.com.  1   IN  TLSA    3 1 1 xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
_587._tcp.mail.somedomain.com.  1   IN  TLSA    3 1 1 xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
_993._tcp.mail.somedomain.com.  1   IN  TLSA    3 1 1 xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
_995._tcp.mail.somedomain.com.  1   IN  TLSA    3 1 1 xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

;; TXT Records
_caldavs._tcp.somedomain.com.   1   IN  TXT "path=/SOGo/dav/"
_carddavs._tcp.somedomain.com.  1   IN  TXT "path=/SOGo/dav/"
dkim._domainkey.somedomain.com. 1   IN  TXT "v=DKIM1;k=rsa;t=s;s=email;p=xxxxxxxxxxxxxxxxxx"
somedomain.com. 1   IN  TXT "v=spf1 mx ~all"

the xxxxxxxxxxxxxx values are obtainable from:

  • Configurations menu > Configuration & Details > Configuration > ARC/DKIM keys
  • Mail Setup menu > Domains > Action - DNS

Goodluck

All 26 comments

;; MX Records
somedomain.com IN MX 10 mail.somedomain.com

The dot is missing at the end, paths are relative, not absolute! This means that it is pointing to mail.somedomain.com.somedomain.com instead of mail.somedomain.com

It should be somedomain.com IN MX 10 mail.somedomain.com.
or you can also instead write: somedomain.com IN MX 10 mail since it's relative

_Note that if you change DNS records it takes up to 24h for changes to take effect._

Thank you very much for the reply. I'm using Cloudflare DNS. I believe cloudflare is updating dns instantly. I import the DNS from cloudflare and check the MX settings. mail.somedomain.com. is there. It's a typo.

I just change somedomain.com IN MX 10 mail. But now incoming mails going nowhere. Its not showing in Rspamd history.
Please hep me.

**Hi can anybody please help me to sort this out.

thank you.**

Hi can anybody please look into my problem. Still it isn't sorted. Please help me.

thank you guys.

Make sure to have the following DNS records:

;; A Records
mail.somedomain.com.    1   IN  A   x.x.x.x

;; CNAME Records
autoconfig.somedomain.com.  1   IN  CNAME   mail.somedomain.com.
autodiscover.somedomain.com.    1   IN  CNAME   mail.somedomain.com.

;; MX Records
somedomain.com. 1   IN  MX  10 mail.somedomain.com.

;; SRV Records
_autodiscover._tcp.somedomain.com.  1   IN  SRV 0 1 443 mail.somedomain.com.
_caldavs._tcp.somedomain.com.   1   IN  SRV 0 1 443 somedomain.com.
_carddavs._tcp.somedomain.com.  1   IN  SRV 0 1 443 somedomain.com.
_imaps._tcp.somedomain.com. 1   IN  SRV 0 1 993     somedomain.com.
_imap._tcp.somedomain.com.  1   IN  SRV 0 1 143     somedomain.com.
_pop3s._tcp.somedomain.com. 1   IN  SRV 0 1 995     somedomain.com.
_pop3._tcp.somedomain.com.  1   IN  SRV 0 1 110     somedomain.com.
_sieve._tcp.somedomain.com. 1   IN  SRV 0 1 4190    somedomain.com.
_smtps._tcp.somedomain.com. 1   IN  SRV 0 1 465     somedomain.com.
_submission._tcp.somedomain.com.    1   IN  SRV 0 1 587 somedomain.com.

;; TLSA Records
_110._tcp.mail.somedomain.com.  1   IN  TLSA    3 1 1 xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
_143._tcp.mail.somedomain.com.  1   IN  TLSA    3 1 1 xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
_25._tcp.mail.somedomain.com.   1   IN  TLSA    3 1 1 xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
_4190._tcp.mail.somedomain.com. 1   IN  TLSA    3 1 1 xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
_443._tcp.mail.somedomain.com.  1   IN  TLSA    3 1 1 xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
_465._tcp.mail.somedomain.com.  1   IN  TLSA    3 1 1 xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
_587._tcp.mail.somedomain.com.  1   IN  TLSA    3 1 1 xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
_993._tcp.mail.somedomain.com.  1   IN  TLSA    3 1 1 xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
_995._tcp.mail.somedomain.com.  1   IN  TLSA    3 1 1 xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

;; TXT Records
_caldavs._tcp.somedomain.com.   1   IN  TXT "path=/SOGo/dav/"
_carddavs._tcp.somedomain.com.  1   IN  TXT "path=/SOGo/dav/"
dkim._domainkey.somedomain.com. 1   IN  TXT "v=DKIM1;k=rsa;t=s;s=email;p=xxxxxxxxxxxxxxxxxx"
somedomain.com. 1   IN  TXT "v=spf1 mx ~all"

the xxxxxxxxxxxxxx values are obtainable from:

  • Configurations menu > Configuration & Details > Configuration > ARC/DKIM keys
  • Mail Setup menu > Domains > Action - DNS

Goodluck

Make sure to have the following DNS records:

;; A Records
mail.somedomain.com.  1   IN  A   x.x.x.x

;; CNAME Records
autoconfig.somedomain.com.    1   IN  CNAME   mail.somedomain.com.
autodiscover.somedomain.com.  1   IN  CNAME   mail.somedomain.com.

;; MX Records
somedomain.com.   1   IN  MX  10 mail.somedomain.com.

;; SRV Records
_autodiscover._tcp.somedomain.com.    1   IN  SRV 0 1 443 mail.somedomain.com.
_caldavs._tcp.somedomain.com. 1   IN  SRV 0 1 443 somedomain.com.
_carddavs._tcp.somedomain.com.    1   IN  SRV 0 1 443 somedomain.com.
_imaps._tcp.somedomain.com.   1   IN  SRV 0 1 993     somedomain.com.
_imap._tcp.somedomain.com.    1   IN  SRV 0 1 143     somedomain.com.
_pop3s._tcp.somedomain.com.   1   IN  SRV 0 1 995     somedomain.com.
_pop3._tcp.somedomain.com.    1   IN  SRV 0 1 110     somedomain.com.
_sieve._tcp.somedomain.com.   1   IN  SRV 0 1 4190    somedomain.com.
_smtps._tcp.somedomain.com.   1   IN  SRV 0 1 465     somedomain.com.
_submission._tcp.somedomain.com.  1   IN  SRV 0 1 587 somedomain.com.

;; TLSA Records
_110._tcp.mail.somedomain.com.    1   IN  TLSA    3 1 1 xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
_143._tcp.mail.somedomain.com.    1   IN  TLSA    3 1 1 xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
_25._tcp.mail.somedomain.com. 1   IN  TLSA    3 1 1 xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
_4190._tcp.mail.somedomain.com.   1   IN  TLSA    3 1 1 xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
_443._tcp.mail.somedomain.com.    1   IN  TLSA    3 1 1 xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
_465._tcp.mail.somedomain.com.    1   IN  TLSA    3 1 1 xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
_587._tcp.mail.somedomain.com.    1   IN  TLSA    3 1 1 xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
_993._tcp.mail.somedomain.com.    1   IN  TLSA    3 1 1 xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
_995._tcp.mail.somedomain.com.    1   IN  TLSA    3 1 1 xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

;; TXT Records
_caldavs._tcp.somedomain.com. 1   IN  TXT "path=/SOGo/dav/"
_carddavs._tcp.somedomain.com.    1   IN  TXT "path=/SOGo/dav/"
dkim._domainkey.somedomain.com.   1   IN  TXT "v=DKIM1;k=rsa;t=s;s=email;p=xxxxxxxxxxxxxxxxxx"
somedomain.com.   1   IN  TXT "v=spf1 mx ~all"

the xxxxxxxxxxxxxx values are obtainable from:

  • Configurations menu > Configuration & Details > Configuration > ARC/DKIM keys
  • Mail Setup menu > Domains > Action - DNS

Goodluck

Thank you very much for your great support. I'm very sorry about my absence. I will try it and let you know.

Solr seems to have died, could be out-of-memory. You can disable it, if you don't really need it. Or upgrade RAM.

We would need to information from the issue template. Like your OS, firewall (firewalld, ufw?) and such.

It would really help to know your domain, to check your DNS.

Please run docker-compose logs --tail=200 -f postfix-mailcow dovecot-mailcow right before you send yourself a mail. Then stop the logs and post them. :)

Solr seems to have died, could be out-of-memory. You can disable it, if you don't really need it. Or upgrade RAM.

We would need to information from the issue template. Like your OS, firewall (firewalld, ufw?) and such.

It would really help to know your domain, to check your DNS.

Please run docker-compose logs --tail=200 -f postfix-mailcow dovecot-mailcow right before you send yourself a mail. Then stop the logs and post them. :)

Thank you very much for the fast reply. Solr status is Solr is starting, disabled or died.

I'm running this email server on digital ocean $5 droplet. My OS is Centos 7.6. My server details are 1 CPU, 1GB ram, 25GB disk space. I have allocated 7GB of swap.
I'm using firewalld but all necessary ports open.

mydomain is somedomain.com (doesn't have a website or webserver installed)
email server runs on mail.somedomain..com (where mailcow installed)

I will do exactly as you described and post the details here.
Thank you again for helping me.

Can you check SKIP_SOLR and SKIP_CLAMD are both "y" in mailcow.conf? 1 GB of RAM is not enough. :(

But that's probably not your problem, just saying. :)

Your MX looks valid, I can telnet it.

Can you check SKIP_SOLR and SKIP_CLAMD are both "y" in mailcow.conf? 1 GB of RAM is not enough. :(

But that's probably not your problem, just saying. :)

Your MX looks valid, I can telnet it.

Thank you very much. I will do as you explained and let you know the results.

Solr seems to have died, could be out-of-memory. You can disable it, if you don't really need it. Or upgrade RAM.
We would need to information from the issue template. Like your OS, firewall (firewalld, ufw?) and such.
It would really help to know your domain, to check your DNS.
Please run docker-compose logs --tail=200 -f postfix-mailcow dovecot-mailcow right before you send yourself a mail. Then stop the logs and post them. :)

Thank you very much for the fast reply. Solr status is Solr is starting, disabled or died.

I'm running this email server on digital ocean $5 droplet. My OS is Centos 7.6. My server details are 1 CPU, 1GB ram, 25GB disk space. I have allocated 7GB of swap. I'm using firewalld but all necessary ports open.

mydomain is emailbypost.com (doesn't have a website or webserver installed)
email server runs on mail.emailbypost.com (where mailcow installed)

I will do exactly as you described and post the details here.
Thank you again for helping me.

ah well that's the issue right there.

the minimum requirements for mail cow to work properly on digital ocean (with CLAMD disabled) is the 10$ plan and you might want to get the 20$ if you have more than 10 users.
I'm telling you this based on experience, we use DO as well

As @andryyy suggested, you prolly don't need Solr so make sure to disable it from the mailcow.conf file also for the 10$ plan you must disable CLAMD and i prefer disabling IPv6 as well.

Goodluck

Solr seems to have died, could be out-of-memory. You can disable it, if you don't really need it. Or upgrade RAM.
We would need to information from the issue template. Like your OS, firewall (firewalld, ufw?) and such.
It would really help to know your domain, to check your DNS.
Please run docker-compose logs --tail=200 -f postfix-mailcow dovecot-mailcow right before you send yourself a mail. Then stop the logs and post them. :)

Thank you very much for the fast reply. Solr status is Solr is starting, disabled or died.
I'm running this email server on digital ocean $5 droplet. My OS is Centos 7.6. My server details are 1 CPU, 1GB ram, 25GB disk space. I have allocated 7GB of swap. I'm using firewalld but all necessary ports open.
mydomain is emailbypost.com (doesn't have a website or webserver installed)
email server runs on mail.emailbypost.com (where mailcow installed)
I will do exactly as you described and post the details here.
Thank you again for helping me.

ah well that's the issue right there.

the minimum requirements for mail cow to work properly on digital ocean (with CLAMD disabled) is the 10$ plan and you might want to get the 20$ if you have more than 10 users.
I'm telling you this based on experience, we use DO as well

As @andryyy suggested, you prolly don't need Solr so make sure to disable it from the mailcow.conf file also for the 10$ plan you must disable CLAMD and i prefer disabling IPv6 as well.

Goodluck

Hi thank you very much for helping me. as @andryyy suggested I have tried to disable Solr in mailcow.conf file by setting SKIP_SOLR = y. then I used docker-compose up -d to rebuild the containers.
But still I can see Solr in mailcow logs page and Slor container has green colour with restart text. In the same page Solar status is Solr is starting, disabled or died.
I kinder confused. Is Solar disabled or running?
Anyway I can't receive any email yet. I will try to disable CLAMD too.

please help me

docker-compose up -d isn't sufficient man.

you need to do the following:

1- ssh into the server and cd into mailcow dir
2- docker-compose down --remove-orphans
3- docker system prune -a -f --volumes (please omit the word "--volumes" if you have data on mailcow, if this is a new setup then keep it)
4- ./update.sh

follow the onscreen prompts and the containers should be up after a while.
but first please double check that CLAMD and Solr are disabled

docker-compose up -d isn't sufficient man.

you need to do the following:

1- ssh into the server and cd into mailcow dir
2- docker-compose down --remove-orphans
3- docker system prune -a -f --volumes (please omit the word "--volumes" if you have data on mailcow, if this is a new setup then keep it)
4- ./update.sh

follow the onscreen prompts and the containers should be up after a while.
but first please double check that CLAMD and Solr are disabled

I will follow your steps. I'm new to Docker and this is my first Docker installation.
I will post the results. Your help is really helpful. Thank you again.

docker-compose up -d isn't sufficient man.

you need to do the following:

1- ssh into the server and cd into mailcow dir
2- docker-compose down --remove-orphans
3- docker system prune -a -f --volumes (please omit the word "--volumes" if you have data on mailcow, if this is a new setup then keep it)
4- ./update.sh

follow the onscreen prompts and the containers should be up after a while.
but first please double check that CLAMD and Solr are disabled

Hi I did all you steps but still I can see Solr and Clamd is green in mailcow system information. Still Solar status shows as Solr is starting, disabled or died.

In mailcow.conf that two options already disable. I ran your commands while Slor and Clamd disable.

SKIP_CLAMD=y
SKIP_SOLR=y

Please help me. It looks like update.sh doesn't care about config file at all I'm really confused here.
Anyway still I cant receive any emails including localhost.

Can you do docker-compose down --remove-orphans and then do docker ps -a?

what do you see

also please post the docker and docker-compose versions

docker-compose --version
docker --version

one last thing, there should be a file called .env inside the mailcow dir,
please make sure it exist and post its content.

Can you do docker-compose down --remove-orphans and then do docker ps -a?

what do you see

also please post the docker and docker-compose versions

docker-compose --version
docker --version

Hi thank you for the reply. I checked which containers are running by docker ps -a -f status=running command and it shows Solr and Clamd is up and running.

docker-compose version 1.24.1, build 4667896b
Docker version 19.03.1, build 74b1e89

I checked .env file and it exactly same as mailcow.config file. Inside .env file both SKIP_CLAMD=y and
SKIP_SOLR=y

Still I haven't done Can you do docker-compose down --remove-orphans and then do docker ps -a?

please help me.

it is okay, they are just in idle and spawn a bash with nothing else.

it is okay, they are just in idle and spawn a bash with nothing else.

Thank you very much for the help. What do you think?

just a random thought, if you can access the web UI then mailcow is running fine, and it might be a firewall issue.

have you setup any firewalls on DO? if so, make sure to have those ports configured and allowed:

https://github.com/mailcow/mailcow-dockerized/issues/2931#issuecomment-530857116

edit: the V6 ones aren't necessary
edit2: those are to be applied on DO's firewall and inside the droplet if you have ufw installed
edit3: you didn't show us the postfix logs

can you afford spawning an ubuntu droplet and do a quick test?
if you don't want to bother changing DNS records simply recreate the droplet from Ubuntu 18.04.3 x64bit image.

Have you setup your domain as a relay? make sure that option is disabled.

can you afford spawning an ubuntu droplet and do a quick test?
if you don't want to bother changing DNS records simply recreate the droplet from Ubuntu 18.04.3 x64bit image.

Have you setup your domain as a relay? make sure that option is disabled.

Thank you very much for the help.
No domain isn't setup as relay. I'm using cloudflare as my dns manager but website is paused in cloudflare.

Yes I can test it on ubuntu droplet. I prefer Centos because its stable and lite. I will let you know the results.

Do you think this issue cause by OS or firewall or Docker?
Why in RSpamd Authericate User shows as Unknown for all inbound mails except localhost alias?
Please help me

Dont forget to post the logs I asked for. :) While receiving a mail.

Dont forget to post the logs I asked for. :) While receiving a mail.

sure. thank you very much for helping me.

@M034B5 @andryyy
Thank you very much for the great support you guys have given me. I didn't understood correctly what @M034B5 told me about Relay domain. Actually It was in Domain configuration page - > Backup MX Options. I have deselected Relay Domain and Relay All Recipients option. That's it. It worked like a charm.

Again thank you very much for helping me.

@M034B5 @andryyy Thank you for the support again. I'm going to close this thread now.

Glad you got it fixed. :)

Was this page helpful?
0 / 5 - 0 ratings

Related issues

Adorfer picture Adorfer  路  3Comments

a3li picture a3li  路  3Comments

poldixd picture poldixd  路  3Comments

zkryakgul picture zkryakgul  路  3Comments

starcraft0429 picture starcraft0429  路  3Comments