I am now back to my original issue that I have to restore from backup. Adding the dqs key makes it so all passwords are no good anymore. The admin password is back to the default one. Making it as I just installed mailcow. I opened a new post so I can troubleshoot this issue separately. Thanks

@"pkernstock"#p31004 [code] docker-compose down -v docker-compose up -d [/code]

@"pkernstock"#p31008 So which of these should I use to restore: [code] [ 0 ] - all [ 1 ] - Redis DB [ 2 ] - Rspamd data [ 3 ] - SQL DB [ 4 ] - Postfix data [ 5 ] - Mail directory (/var/vmail) [ 6 ] - Crypt data [/code]

Adding DQS key messes up all my mailcow passwords

pkernstock

I’d expect you doing some steps wrong honestly.
What commands are you exactly using to start and stop the docker stack?
Copy them exactly from your output history please.

maybl8

pkernstock

docker-compose down -v 
docker-compose up -d

pkernstock

maybl8 docker-compose down -v

From the Docker Compose docs:

Remove named volumes declared in the “volumes” section of the Compose file and anonymous volumes attached to containers

Source: https://docs.docker.com/reference/cli/docker/compose/down#:~:text=Remove%20named%20volumes%20declared%20in%20the%20%22volumes%22%20section%20of%20the%20Compose%20file%20and%20anonymous%20volumes%20attached%20to%20containers

So effectively -v does remove all your mailcow data. That is what the parameter does.

Also, docker-compose is deprecated for a long time. Don’t use it. Use docker compose plugin as outlined in the mailcow docs.

DocFraggle

maybl8 docker-compose down -v
docker-compose up -d

You got it the wiring was, that’s all…

docker compose down
docker compose up -d

maybl8

pkernstock
I knew that about the docker-compose but didn’t notice I had that in there.
So is there a way to get the passwords working again without doing a restore?
And why is when add the DQS key this problem happens?
I have done the restart before and didn’t have issues.

pkernstock

maybl8 So is there a way to get the passwords working again without doing a restore?

Just don’t use -v where you tell docker to remove your data as per above docker documentation. If you use -v, it is expected.

maybl8 And why is when add the DQS key this problem happens?

Because you seem to accidentally use the parameter after configuring DQS key.

maybl8

pkernstock
So which of these should I use to restore:

[ 0 ] - all
[ 1 ] - Redis DB
[ 2 ] - Rspamd data
[ 3 ] - SQL DB
[ 4 ] - Postfix data
[ 5 ] - Mail directory (/var/vmail)
[ 6 ] - Crypt data

DocFraggle

DocFraggle You got it the wiring was

Wanted to write “You got it the wrong way around”

pkernstock

maybl8 So which of these should I use to restore:

I don’t know, sorry. Never used this script. I rely on and use snapshots on the virtual machine running my mailcow instance.

DocFraggle

maybl8 all!

maybl8

DocFraggle
Ok system is back and letting me login again.
Can I have the steps for doing this DQS key?
I don’t want to kill my system again.
Please and thanks for your patience.

DocFraggle

maybl8 Add it as before in mailcow.conf and DON’T USE the -y switch for docker compose down! That’s all

docker compose down
docker compose up -d

maybl8

DocFraggle
Got it working.
Thanks for all the help.
I am going to go read some docs.
I am going to get a backup system setup for doing backups properly.
Hope I don’t screw up my system anymore.

maybl8

maybl8
I ran the BLT DQS content test and it sent an email that it said should be blocked.
It was suppose to look in the body of the email for a domain that should have been flagged as spam.
Are there other settings in rspamd I need to set?

DocFraggle

maybl8 One of the 11 mails got through? Or how many?

maybl8

DocFraggle
Nine and 1 got through. lol
Ok see your point

DocFraggle

Check the results, you can see the mail protocol in detail if you click on it

maybl8

DocFraggle
This is a log from postfix showing DQS is working:

postfix-mailcow-1  | Feb 27 10:32:03 4bc642328ab9 postfix/postscreen[5658]: CONNECT from [89.44.209.15]:48362 to [172.22.1.253]:25
postfix-mailcow-1  | Feb 27 10:32:03 4bc642328ab9 whitelist_forwardinghosts: Look up 89.44.209.15 on whitelist, result 200 DUNNO
postfix-mailcow-1  | Feb 27 10:32:03 4bc642328ab9 postfix/dnsblog[5675]: addr 89.44.209.15 listed by domain b4nf4wop2vfuv3iqynh3yc5wxe.zen.dq.spamhaus.net as 127.0.0.3
postfix-mailcow-1  | Feb 27 10:32:03 4bc642328ab9 postfix/dnsblog[5674]: addr 89.44.209.15 listed by domain bl.mailspike.net as 127.0.0.10
postfix-mailcow-1  | Feb 27 10:32:04 4bc642328ab9 postfix/dnsblog[5673]: addr 89.44.209.15 listed by domain hostkarma.junkemailfilter.com as 127.0.0.2
postfix-mailcow-1  | Feb 27 10:32:04 4bc642328ab9 postfix/dnsblog[5673]: addr 89.44.209.15 listed by domain hostkarma.junkemailfilter.com as 127.0.1.1
postfix-mailcow-1  | Feb 27 10:32:06 4bc642328ab9 postfix/postscreen[5658]: DNSBL rank 11 for [89.44.209.15]:48362
postfix-mailcow-1  | Feb 27 10:32:07 4bc642328ab9 postfix/tlsproxy[5679]: CONNECT from [89.44.209.15]:48362
postfix-mailcow-1  | Feb 27 10:32:13 4bc642328ab9 postfix/tlsproxy[5679]: warning: TLS library problem: error:0A000102:SSL routines::unsupported protocol:../ssl/statem/statem_srvr.c:1657:
postfix-mailcow-1  | Feb 27 10:32:13 4bc642328ab9 postfix/tlsproxy[5679]: TLS handshake failed for service=smtpd peer=[89.44.209.15]:48362
postfix-mailcow-1  | Feb 27 10:32:13 4bc642328ab9 postfix/postscreen[5658]: HANGUP after 6.3 from [89.44.209.15]:48362 in tests after SMTP handshake
postfix-mailcow-1  | Feb 27 10:32:13 4bc642328ab9 postfix/postscreen[5658]: DISCONNECT [89.44.209.15]:48362
postfix-mailcow-1  | Feb 27 10:32:13 4bc642328ab9 postfix/tlsproxy[5679]: DISCONNECT [89.44.209.15]:48362

DocFraggle

👍