Miscellaneous first checks
Affected Component(s)
rspamd will not easily learn to recognize spam
What happened and when does this occur?
I have trained rspamd with two email-folders containing spam or ham like so
First get stats on learned spam
`docker exec -it mailserver sh
rspamc stat
Statfile: BAYES_SPAM type: redis; length: 0; free blocks: 0; total blocks: 0; free: 0.00%; learned: 1; users: 1; languages: 0
Statfile: BAYES_HAM type: redis; length: 0; free blocks: 0; total blocks: 0; free: 0.00%; learned: 6; users: 1; languages: 0
Total learns: 7
`
Then I train rspamd with a folder full of spam, and a folder full of spam
rspamc learn_spam /var/mail/fanscees.com/hanscees/.spam/cur rspamc stat Statfile: BAYES_SPAM type: redis; length: 0; free blocks: 0; total blocks: 0; free: 0.00%; learned: 413; users: 1; languages: 0 Statfile: BAYES_HAM type: redis; length: 0; free blocks: 0; total blocks: 0; free: 0.00%; learned: 6; users: 1; languages: 0 Total learns: 419
Same with ham training
rspamc learn_ham /var/mail/hanscees.com/hanscees/.Ham/cur rspamc stat Statfile: BAYES_SPAM type: redis; length: 0; free blocks: 0; total blocks: 0; free: 0.00%; learned: 413; users: 1; languages: 0 Statfile: BAYES_HAM type: redis; length: 0; free blocks: 0; total blocks: 0; free: 0.00%; learned: 354; users: 1; languages: 0 Total learns: 767
I also have enabled that rspamd learns from users when they move email in and out the inbox.junk folder: see attached txt script
rspamd-patches.txt
Problem is now, after doing a docker-compose down, all learned material seems gone.
docker-compose down docker-compose up -d Statfile: BAYES_SPAM type: redis; length: 0; free blocks: 0; total blocks: 0; free: 0.00%; learned: 0; users: 0; languages: 0 Statfile: BAYES_HAM type: redis; length: 0; free blocks: 0; total blocks: 0; free: 0.00%; learned: 0; users: 0; languages: 0 Total learns: 0
I think something should be added to the mailstate that is preserved, but no idea what.
What did you expect to happen?
I expect learned spam to persist over a reset of the docker image
How do we replicate the issue?
do what I did above
DMS version
1301
What operating system is DMS running on?
Linux
Which operating system version?
photon 4
What instruction set architecture is DMS running on?
AMD64 / x86_64
What container orchestration tool are you using?
Docker
docker-compose.yml
services:
mailserver:
image: docker.io/mailserver/docker-mailserver:edge
#image: docker.io/mailserver/docker-mailserver:latest
container_name: mailserver
# If the FQDN for your mail-server is only two labels (eg: example.com),
# you can assign this entirely to `hostname` and remove `domainname`.
hostname: mail
domainname: fanscees.net
env_file: mailserver.env
# More information about the mail-server ports:
# https://docker-mailserver.github.io/docker-mailserver/edge/config/security/understanding-the-ports/
# To avoid conflicts with yaml base-60 float, DO NOT remove the quotation marks.
ports:
- "25:25" # SMTP (explicit TLS => STARTTLS)
- "143:143" # IMAP4 (explicit TLS => STARTTLS)
- "465:465" # ESMTP (implicit TLS)
- "587:587" # ESMTP (explicit TLS => STARTTLS)
- "993:993" # IMAP4 (implicit TLS)
- "995:995" # pop3 (implicit TLS)
- "110:110" # pop3 (implicit TLS)
volumes:
#- etc:/etc
- maildata:/var/mail/
- mailstate:/var/mail-state/
- log:/var/log/
- Tconfig:/tmp/docker-mailserver/
- /etc/localtime:/etc/localtime:ro
- ssl:/tmp/ssl
restart: always
stop_grace_period: 1m
environment:
# If you need SSL connection, you can provide your own certificates
- SSL_TYPE=manual
- SSL_CERT_PATH=/tmp/ssl/fullchain.pem
- SSL_KEY_PATH=/tmp/ssl/privkey.pem
cap_add:
- NET_ADMIN
healthcheck:
test: "ss --listening --tcp | grep -P 'LISTEN.+:smtp' || exit 1"
timeout: 3s
retries: 0
volumes:
maildata:
mailstate:
Tconfig:
log:
ssl:
Relevant log output
No response
Other relevant information
I have also enabled the auto-learn rule on spam form your documentation
What level of experience do you have with Docker and mail servers?
Code of conduct
Improvements to this form?
No response
Miscellaneous first checks
Affected Component(s)
rspamd will not easily learn to recognize spam
What happened and when does this occur?
I have trained rspamd with two email-folders containing spam or ham like so
First get stats on learned spam
`docker exec -it mailserver sh
rspamc stat
Statfile: BAYES_SPAM type: redis; length: 0; free blocks: 0; total blocks: 0; free: 0.00%; learned: 1; users: 1; languages: 0
Statfile: BAYES_HAM type: redis; length: 0; free blocks: 0; total blocks: 0; free: 0.00%; learned: 6; users: 1; languages: 0
Total learns: 7
`
Then I train rspamd with a folder full of spam, and a folder full of spam
rspamc learn_spam /var/mail/fanscees.com/hanscees/.spam/cur rspamc stat Statfile: BAYES_SPAM type: redis; length: 0; free blocks: 0; total blocks: 0; free: 0.00%; learned: 413; users: 1; languages: 0 Statfile: BAYES_HAM type: redis; length: 0; free blocks: 0; total blocks: 0; free: 0.00%; learned: 6; users: 1; languages: 0 Total learns: 419Same with ham training
rspamc learn_ham /var/mail/hanscees.com/hanscees/.Ham/cur rspamc stat Statfile: BAYES_SPAM type: redis; length: 0; free blocks: 0; total blocks: 0; free: 0.00%; learned: 413; users: 1; languages: 0 Statfile: BAYES_HAM type: redis; length: 0; free blocks: 0; total blocks: 0; free: 0.00%; learned: 354; users: 1; languages: 0 Total learns: 767I also have enabled that rspamd learns from users when they move email in and out the inbox.junk folder: see attached txt script
rspamd-patches.txt
Problem is now, after doing a docker-compose down, all learned material seems gone.
docker-compose down docker-compose up -d Statfile: BAYES_SPAM type: redis; length: 0; free blocks: 0; total blocks: 0; free: 0.00%; learned: 0; users: 0; languages: 0 Statfile: BAYES_HAM type: redis; length: 0; free blocks: 0; total blocks: 0; free: 0.00%; learned: 0; users: 0; languages: 0 Total learns: 0I think something should be added to the mailstate that is preserved, but no idea what.
What did you expect to happen?
I expect learned spam to persist over a reset of the docker image
How do we replicate the issue?
do what I did above
DMS version
1301
What operating system is DMS running on?
Linux
Which operating system version?
photon 4
What instruction set architecture is DMS running on?
AMD64 / x86_64
What container orchestration tool are you using?
Docker
docker-compose.yml
Relevant log output
No response
Other relevant information
I have also enabled the auto-learn rule on spam form your documentation
What level of experience do you have with Docker and mail servers?
Code of conduct
Improvements to this form?
No response