Hi everyone, I have been using mailcow selfhosted for about 3 years. So far everything has worked without problems, only after the last update on July 13th. I get "no mailbox selected" when I log into SOGo. Before that, the last time was on July 6th. `update.sh` executed. [Unfortunately, other discussions didn't work for me.](https://community.mailcow.email/d/23-mailcow-on-aws-no-mailbox-selected) I hope you can help me here. If someone needs further information / logs, please let me know. Christian dovecot log: ``` dovecot-mailcow_1 | Jul 14 23:20:01 mail CRON[1179]: pam_unix(cron:session): session opened for user vmail by (uid=0) dovecot-mailcow_1 | Jul 14 23:20:02 mail CRON[1182]: (vmail) CMD (/usr/local/bin/repl_health.sh >> /dev/console 2>&1) dovecot-mailcow_1 | Jul 14 23:20:02 mail CRON[1181]: pam_unix(cron:session): session opened for user vmail by (uid=0) dovecot-mailcow_1 | Jul 14 23:20:02 mail CRON[1180]: pam_unix(cron:session): session opened for user vmail by (uid=0) dovecot-mailcow_1 | Jul 14 23:20:02 mail CRON[1185]: (vmail) CMD (/usr/local/bin/quarantine_notify.py >> /dev/console 2>&1) dovecot-mailcow_1 | Jul 14 23:20:02 mail CRON[1187]: (vmail) CMD (/usr/local/bin/trim_logs.sh >> /dev/console 2>&1) dovecot-mailcow_1 | Jul 14 23:20:02 mail CRON[1178]: pam_unix(cron:session): session opened for user root by (uid=0) dovecot-mailcow_1 | Jul 14 23:20:02 mail CRON[1190]: (root) CMD ( /usr/local/bin/imapsync_cron.pl 2>&1 | /usr/bin/logger) dovecot-mailcow_1 | Jul 14 23:20:02 mail dovecot: imap-login: Disconnected (auth failed, 1 attempts in 0 secs): user=, rip=172.22.1.1, lip=172.22.1.250 dovecot-mailcow_1 | Jul 14 23:20:02 mail dovecot: imap-login: Disconnected (auth failed, 1 attempts in 0 secs): user=, rip=172.22.1.1, lip=172.22.1.250 dovecot-mailcow_1 | Jul 14 23:20:02 mail CRON[1179]: pam_unix(cron:session): session closed for user vmail dovecot-mailcow_1 | Jul 14 23:20:04 mail dovecot: imap-login: Disconnected (auth failed, 1 attempts in 0 secs): user=, rip=172.22.1.1, lip=172.22.1.250 dovecot-mailcow_1 | Jul 14 23:20:04 mail dovecot: imap-login: Disconnected (auth failed, 1 attempts in 0 secs): user=, rip=172.22.1.1, lip=172.22.1.250 ``` SOGo log: ``` sogo-mailcow_1 | Jul 14 23:19:59 012ee9bf8e5f sogod [63]: SOGoRootPage successful login from '217.253.81.128' for user 'hausbau@familie-hesseling.de' - expire = -1 grace = -1 sogo-mailcow_1 | Jul 14 23:19:59 012ee9bf8e5f sogod [63]: [ERROR] current source cannot synchronize defaults sogo-mailcow_1 | Jul 14 23:19:59 012ee9bf8e5f sogod [63]: 217.253.81.128 "POST /SOGo/connect HTTP/1.0" 200 64/98 0.013 - - 0 - 14 sogo-mailcow_1 | Jul 14 23:20:00 012ee9bf8e5f sogod [63]: [ERROR] current source cannot synchronize defaults sogo-mailcow_1 | Jul 14 23:20:00 012ee9bf8e5f sogod [63]: 217.253.81.128 "GET /SOGo/hausbau%40familie-hesseling.de HTTP/1.0" 302 0/0 0.003 - - 0 - 14 sogo-mailcow_1 | Jul 14 23:20:00 012ee9bf8e5f sogod [63]: [ERROR] current source cannot synchronize defaults sogo-mailcow_1 | Jul 14 23:20:00 012ee9bf8e5f sogod [63]: [ERROR] current source cannot synchronize defaults sogo-mailcow_1 | Jul 14 23:20:00 012ee9bf8e5f sogod [63]: 217.253.81.128 "GET /SOGo/hausbau%40familie-hesseling.de/view HTTP/1.0" 302 0/0 0.007 - - 0 - 14 sogo-mailcow_1 | Jul 14 23:20:00 012ee9bf8e5f sogod [63]: [ERROR] current source cannot synchronize defaults sogo-mailcow_1 | Jul 14 23:20:00 012ee9bf8e5f sogod [63]: 217.253.81.128 "GET /SOGo/so/hausbau@familie-hesseling.de/Mail HTTP/1.0" 302 0/0 0.005 - - 0 - 14 sogo-mailcow_1 | Jul 14 23:20:00 012ee9bf8e5f sogod [63]: [ERROR] current source cannot synchronize defaults sogo-mailcow_1 | Jul 14 23:20:00 012ee9bf8e5f sogod [63]: [ERROR] current source cannot synchronize defaults sogo-mailcow_1 | Jul 14 23:20:00 012ee9bf8e5f sogod [63]: [ERROR] current source cannot synchronize defaults sogo-mailcow_1 | Jul 14 23:20:01 012ee9bf8e5f sogod [63]: 217.253.81.128 "GET /SOGo/so/hausbau@familie-hesseling.de/Mail/view HTTP/1.0" 200 22128/0 0.163 85925 74% 2M - 14 sogo-mailcow_1 | Jul 14 23:20:01 012ee9bf8e5f CRON[293]: pam_unix(cron:session): session opened for user sogo by (uid=0) sogo-mailcow_1 | Jul 14 23:20:01 012ee9bf8e5f CRON[294]: (sogo) CMD ( /usr/sbin/sogo-ealarms-notify -p /etc/sogo/sieve.creds 2>/dev/null) sogo-mailcow_1 | Jul 14 23:20:01 012ee9bf8e5f CRON[292]: pam_unix(cron:session): session opened for user sogo by (uid=0) sogo-mailcow_1 | Jul 14 23:20:01 012ee9bf8e5f CRON[295]: (sogo) CMD ( /usr/sbin/sogo-tool expire-sessions 480) sogo-mailcow_1 | Jul 14 23:20:01 012ee9bf8e5f sogod [63]: [ERROR] current source cannot synchronize defaults sogo-mailcow_1 | Jul 14 23:20:01 012ee9bf8e5f sogod [63]: [ERROR] current source cannot synchronize defaults sogo-mailcow_1 | Jul 14 23:20:01 012ee9bf8e5f sogod [63]: 217.253.81.128 "GET /SOGo/so/hausbau@familie-hesseling.de/Calendar/alarmslist?browserTime=1594761595 HTTP/1.0" 200 63/0 0.184 - - 0 - 14 sogo-mailcow_1 | Jul 14 23:20:01 012ee9bf8e5f sogod [74]: [ERROR] current source cannot synchronize defaults sogo-mailcow_1 | Jul 14 23:20:01 012ee9bf8e5f sogod [74]: [ERROR] current source cannot synchronize defaults sogo-mailcow_1 | Jul 14 23:20:01 012ee9bf8e5f sogod [74]: [ERROR] current source cannot synchronize defaults sogo-mailcow_1 | Jul 14 23:20:02 012ee9bf8e5f sogod [74]: [ERROR] IMAP4 login failed: ```

Oh, yes, I forget the `source mailcow.conf` part in front of the command, sorry. Try to login as mailbox user and reset the EAS cache.

Hi, Please try this (run from within the mailcow folder): ``` source mailcow.conf MAILCOW_BRIDGE=$(docker-compose config | grep -i com.docker.network.bridge.name | cut -d':' -f2) while read NAT_ID; do iptables -t nat -D POSTROUTING $NAT_ID done <

The output of `ip6tables -L -vn -t nat` would be great, too. :)

Hi diekuh! Thank you for the fast answer. ip6tables is attached: [upl-file uuid=f384f5f8-d558-44d8-bd98-19d4227d795d size=6kB]ip6tables.txt[/upl-file] When I execute your commands the following error message appears: `Usage: grep [OPTION]... PATTERN [FILE]... `. The variable `$IPV4_NETWORK` was empty, according to mailcow.conf it is `172.22.1`. So I executed the commands one after the other and lo and behold: it works, SOGo finds the mailboxes again! Only the synchronization with the active sync devices like smartphone does not work yet, do you have an idea or tip here? In the log I find nothing noticeable, except for the errors with current source cannot synchronize defaults: ``` sogo-mailcow_1 | Jul 15 18:47:59 46169aa8b950 sogod [70]: [ERROR] current source cannot synchronize defaults sogo-mailcow_1 | Jul 15 18:47:59 46169aa8b950 sogod [70]: [ERROR] current source cannot synchronize defaults sogo-mailcow_1 | Jul 15 18:47:59 46169aa8b950 sogod [70]: SOGoUserHomePage user 'christian@allround-sounds.de' logged off sogo-mailcow_1 | Jul 15 18:47:59 46169aa8b950 sogod [70]: 217.253.81.128 "GET /SOGo/so/christian@allround-sounds.de/logoff HTTP/1.0" 302 0/0 0.091 - - 0 - 12 sogo-mailcow_1 | Jul 15 18:47:59 46169aa8b950 sogod [70]: 217.253.81.128 "GET /SOGo/so/ HTTP/1.0" 200 9252/0 0.032 30518 69% 0 - 12 sogo-mailcow_1 | Jul 15 18:48:01 46169aa8b950 cron[10]: (*system*sogo) RELOAD (/etc/cron.d/sogo) sogo-mailcow_1 | Jul 15 18:48:02 46169aa8b950 CRON[79]: pam_unix(cron:session): session opened for user sogo by (uid=0) sogo-mailcow_1 | Jul 15 18:48:02 46169aa8b950 CRON[78]: pam_unix(cron:session): session opened for user sogo by (uid=0) sogo-mailcow_1 | Jul 15 18:48:02 46169aa8b950 CRON[80]: (sogo) CMD ( /usr/sbin/sogo-tool expire-sessions 480) sogo-mailcow_1 | Jul 15 18:48:02 46169aa8b950 CRON[81]: (sogo) CMD ( /usr/sbin/sogo-ealarms-notify -p /etc/sogo/sieve.creds 2>/dev/null) sogo-mailcow_1 | Jul 15 18:48:03 46169aa8b950 CRON[78]: pam_unix(cron:session): session closed for user sogo sogo-mailcow_1 | Jul 15 18:48:03 46169aa8b950 CRON[79]: pam_unix(cron:session): session closed for user sogo sogo-mailcow_1 | Jul 15 18:48:27 46169aa8b950 sogod [74]: Sleeping 45 seconds while detecting changes for user christian@familie-hesseling.de in Ping... sogo-mailcow_1 | Jul 15 18:48:42 46169aa8b950 sogod [11]: [WARN] pid 74 has been hanging in the same request for 1 minutes sogo-mailcow_1 | Jul 15 18:49:01 46169aa8b950 CRON[87]: pam_unix(cron:session): session opened for user sogo by (uid=0) sogo-mailcow_1 | Jul 15 18:49:01 46169aa8b950 CRON[88]: (sogo) CMD ( /usr/sbin/sogo-tool expire-sessions 480) sogo-mailcow_1 | Jul 15 18:49:02 46169aa8b950 CRON[91]: pam_unix(cron:session): session opened for user sogo by (uid=0) sogo-mailcow_1 | Jul 15 18:49:02 46169aa8b950 CRON[92]: (sogo) CMD ( /usr/sbin/sogo-ealarms-notify -p /etc/sogo/sieve.creds 2>/dev/null) sogo-mailcow_1 | Jul 15 18:49:02 46169aa8b950 CRON[91]: pam_unix(cron:session): session closed for user sogo sogo-mailcow_1 | Jul 15 18:49:02 46169aa8b950 CRON[87]: pam_unix(cron:session): session closed for user sogo sogo-mailcow_1 | Jul 15 18:49:13 46169aa8b950 sogod [74]: Sleeping 45 seconds while detecting changes for user christian@familie-hesseling.de in Ping... ```

I deleted the EAS cache, and after 1-2 hours the smartphones started to synchronize the emails. Thank you so much! @"diekuh"#p1045

SOGo "no mailbox selected"

diekuh

Great to hear that! 🙂

chesseling

Hi @diekuh, I hope you can help me with another problem related to this.
After I have executed your commands (I have to execute them every time the server is restarted), other docker containers from other networks (like 172.19.x.y) on the same host cannot send emails to the email server. $HOSTNAME is used as smtp host.

SMTP Error: Could not connect to SMTP host.
It looks like after your commands above, no connection can be made from other docker networks.

chesseling

Alright, now everything works!

certdumper did not work propertly, so no certificates were copied from traefik and the certificate had expired a few days ago.

jtdoank

chesseling
can you help inform me how to delete EAS cache,

i just restore from mailcow backup to other server and now i am facing no mailbox selected 😓

thanks

chesseling

jtdoank Log in at Mailcow as an mailbox user (not at SOGo), under Mailbox -> Settings click on Reset Active Sync Device Cache -> Reset Now.

But that doesn’t sound like the problem that the EAS cache could solve. Are the accounts with the mailboxes still in Mailcow? You only see the error in SOGo?

jtdoank

chesseling

Hi so sorry late reply,
already reset but still no result

Yes, the account still on the mailcow and even the message also still count as it is
also
Yes the error is only on SOGo

but its seems the dovecot problem
did anyone ever facing this problem?

jtdoank

anyone?

saranya-sreedharan

jtdoank

Hi I am facing that issue. How you resolved that? Kindly help me with this

jtdoank

update

this morning, Indonesian time
suddenly the sogo it works

even i didn’t do anything

jtdoank

just now i tried update the mailcow
and
sadly it happen again

no mailbox selected on sogo

jtdoank

just check and as I expected,
the mailbox is works

hehehe

nothing to do from last check

jtdoank

saranya-sreedharan as i inform, nothing to do just tried update and recheck in view days

saranya-sreedharan

jtdoank

Ok.
actually I am getting like this “504 gateway time-out” while checking the DNS of the domain, Did you got like this?Then “NO MAILBOX SELECTED” in sogo .

jtdoank

I dont have like yours
At that time all is working perfectly but sogo no mailbox selected

saranya-sreedharan

jtdoank

Ok thank you.

jtdoank

saranya-sreedharan no worries…help each other Eventhough i dont have any solution to your problem at this moment

ashcoft

i just update the mailcow-dockerize and voila, the mailbox is available