docker-mailserver: Rspamd rejects `asciinema` e-mails

šŸ“ Preliminary Checks

  • I tried searching for an existing issue and followed the debugging docs advice, but still need assistance.

šŸ‘€ What Happened?

I wanted to log into asciinema but didn’t get the login email. When I used another one it worked fine.

When looking into logs I see that the message was outrights rejected instead of being moved to the spam folder:

Logs
May  7 23:04:43 mx postfix/smtpd[717267]: 0437429007C5: client=unknown[64.147.123.154]

May  7 23:04:43 mx postfix/cleanup[717285]: 0437429007C5: message-id=<>

May  7 23:04:43 mx postfix/cleanup[717285]: 0437429007C5: milter-reject: END-OF-MESSAGE from unknown[64.147.123.154]: 5.7.1 Spam message rejected; from=<hello@hello.asciinema.org> to=<my@email> proto=ESMTP helo=<wfhigh3-smtp.messagingengine.com>

May  7 23:04:43 mx postfix/smtpd[717267]: disconnect from unknown[64.147.123.154] ehlo=2 starttls=1 mail=1 rcpt=1 data=0/1 quit=1 commands=6/7

šŸ‘Ÿ Reproduction Steps

  1. Use rspamd
  2. Try to log into asciinema
  3. See no email in inbox or junk
  4. See that the server rejected it outright in the logs

šŸ‹ DMS Version

v13.3.1

šŸ’» Operating System and Architecture

Debian GNU/Linux 11 (bullseye) aarch64

āš™ļø Container configuration files

services:
  mailserver:
    image: ghcr.io/docker-mailserver/docker-mailserver:latest
    container_name: mailserver
    hostname: mx.example.com
    env_file: stack.env
    environment:
      SSL_TYPE: letsencrypt
      SSL_DOMAIN: mx.example.com
    ports:
      - "25:25"     # SMTP  (explicit TLS => STARTTLS, Authentication is DISABLED => use port 465/587 instead)
      - "143:143"   # IMAP4 (explicit TLS => STARTTLS)
      - "465:465"   # ESMTP (implicit TLS)
      - "587:587"   # ESMTP (explicit TLS => STARTTLS)
      - "993:993"   # IMAP4 (implicit TLS)
      - "4190:4190" # SIEVE
    volumes:
      - ./docker-data/dms/mail-data/:/var/mail/
      - ./docker-data/dms/mail-state/:/var/mail-state/
      - ./docker-data/dms/mail-logs/:/var/log/mail/
      - ./docker-data/dms/config/:/tmp/docker-mailserver/
      - /etc/localtime:/etc/localtime:ro
      - ../traefik/config/acme.json:/etc/letsencrypt/acme.json:ro
    restart: always
    stop_grace_period: 1m
    cap_add:
      - NET_ADMIN
    healthcheck:
      test: "ss --listening --tcp | grep -P 'LISTEN.+:smtp' || exit 1"
      timeout: 3s
      retries: 0

  whoami:
    image: docker.io/traefik/whoami:latest
    labels:
      - "traefik.http.routers.whoami.rule=Host(`mx.example.com`)"
      - "traefik.http.routers.whoami.tls.certresolver=lets-encrypt"
    restart: unless-stopped

šŸ“œ Relevant log output

May  7 23:37:09 mx postfix/postscreen[722801]: CONNECT from [64.147.123.154]:50973 to [172.20.0.3]:25

May  7 23:37:09 mx postfix/postscreen[722801]: PASS OLD [64.147.123.154]:50973

May  7 23:37:09 mx postfix/smtpd[722802]: warning: hostname wfhigh3-smtp.messagingengine.com does not resolve to address 64.147.123.154

May  7 23:37:09 mx postfix/smtpd[722802]: connect from unknown[64.147.123.154]

May  7 23:37:10 mx postfix/smtpd[722802]: Anonymous TLS connection established from unknown[64.147.123.154]: TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits)

May  7 23:37:10 mx postfix/smtpd[722802]: A64AD29008B0: client=unknown[64.147.123.154]

May  7 23:37:10 mx postfix/cleanup[722808]: A64AD29008B0: message-id=<>

May  7 23:37:11 mx postfix/cleanup[722808]: A64AD29008B0: milter-reject: END-OF-MESSAGE from unknown[64.147.123.154]: 5.7.1 Spam message rejected; from=<hello@hello.asciinema.org> to=<my-email@example.com> proto=ESMTP helo=<wfhigh3-smtp.messagingengine.com>

May  7 23:37:11 mx postfix/smtpd[722802]: disconnect from unknown[64.147.123.154] ehlo=2 starttls=1 mail=1 rcpt=1 data=0/1 quit=1 commands=6/7

Improvements to this form?

No response

About this issue

  • Original URL
  • State: closed
  • Created 3 years ago
  • Comments: 45 (44 by maintainers)

Most upvoted comments

I’d just like to thank you all. Thanks to your help the asciinema.org emails are now -2.18 in SPAM score.

Also I think that the underlying issue (DNS being messed up when using hostname) option in Docker compose should be investigated. I might make a PR for docs so that the possibility of this issue is mentioned somewhere. I’ll try to gather some info on why this could happen but I cannot promise anything.

Again, thanks for your help, you’re awesome.

@georglauterbach

can you post an anonymized version of such an e-mail here? I’d be curious to see one.

Of course. It’s a simple email with a login link. You can also easily get one yourself by logging in/registering here: https://asciinema.org/login/new. There’s no password or anything so it’s not that annoying to make an account and test this out yourself.


The email (without the login token):

Welcome back!

Click the following link to log in to your asciinema.org account:

https://asciinema.org/session/new?t=<login-token-here>


If you did not initiate this request, just ignore this email. The request will expire shortly.
Source

Hopefully I didn’t leave anything sensitive in.

Return-Path: <hello@hello.asciinema.org>
Delivered-To: me@my.domain
Received: from mx.my.domain
	by mx.my.domain with LMTP
	id BriBOpdXS2YCegAAMGYE4w
	(envelope-from <hello@hello.asciinema.org>)
	for <me@my.domain>; Mon, 20 May 2024 16:00:55 +0200
Received: from fout3-smtp.messagingengine.com (fout3-smtp.messagingengine.com [103.168.172.146])
	by mx.my.domain (Postfix) with ESMTPS id 3C1FD2901CD5
	for <me@my.domain>; Mon, 20 May 2024 16:00:55 +0200 (CEST)
Received: from compute5.internal (compute5.nyi.internal [10.202.2.45])
	by mailfout.nyi.internal (Postfix) with ESMTP id E4C501381556
	for <me@my.domain>; Mon, 20 May 2024 10:00:47 -0400 (EDT)
Received: from mailfrontend1 ([10.202.2.162])
  by compute5.internal (MEProxy); Mon, 20 May 2024 10:00:47 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=
	hello.asciinema.org; h=cc:content-type:content-type:date:date
	:from:from:in-reply-to:mime-version:reply-to:reply-to:subject
	:subject:to:to; s=fm1; t=1716213647; x=1716300047; bh=Knun7XFdxq
	llWxxzAsFueCYLjNFjRM7+Vw2RB9DdGPs=; b=jwgYlURUOlU/n1ppl45sRHSUWb
	SOHKT8O78qcwGxQjp8hpToLA58U+QwDdG3oVDEF+SEO4di9wzBswlekcGEtLPu6F
	9BKrmiqo5HhR6F9jLH/V3M+CTCmgOZ0Q6mh1ec0Bl2JXCOm0nNCHcXxjE7Ieslo6
	QbDVZRkVfS5sT2BzUinJz/O6grk4baqYGkT2Z1zt+NFJMow05Zdq9h4oS2yvnb5I
	wxeTsT4USPYm1BC6MN0zI9UqCvjMw3fclT2HfQwWgEChGm3VYfNT63PVeDBa10od
	C1+dKc5U7Lm/Plt1XzPfKulTMngRmc8YrfQ/IHmAV3zJjsqiSMBNSU4U7pDQ==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=
	messagingengine.com; h=cc:content-type:content-type:date:date
	:feedback-id:feedback-id:from:from:in-reply-to:mime-version
	:reply-to:reply-to:subject:subject:to:to:x-me-proxy:x-me-proxy
	:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; t=1716213647; x=
	1716300047; bh=Knun7XFdxqllWxxzAsFueCYLjNFjRM7+Vw2RB9DdGPs=; b=T
	8RrVARKFp0WKiAvwuPCc7GFYjZCHLCgiU/9AC5+4msfZuWR6W22yHzcYYFCEN2oJ
	pcU02lGGBSikwrLrLwzLOeowfe4V2BphZKzFbWoDTzAUwxHtOHMkuGfBDaj6U3Ms
	N9ciVnVVidUqnGKwPLRw5us7Halsc+H+cXu9eQlT3rIsDIEW/Nc8oNT2Jwj3WPai
	9KYZzZNS50VVT+v4kil+KfOaN6jSrKI2BgImt2i99qAZCNCAAJf5EUOSbGrWyXzZ
	BicOgu7lQbBxshgryAso41tjFNykoHTB8PrXDN8zCVhPENdb+45zcNDtKDTMcoFQ
	BcRFOrvpXs0FNeC6U5PWA==
X-ME-Sender: <xms:jldLZp6nkhxVsF8B19i4WQYqc-xD1RTVEt1i9lNnZr4Dz8Lso8CcdQ>
    <xme:jldLZm5up75w36ltx-5Jc25rHd6NgXhSVmycNZq1Lb-kOdZR35WK9gk71gomV7Wqh
    LNMUTY8p3kGerbbf5g>
X-ME-Received: <xmr:jldLZgcxScMTilypDGWgYQsyxoarTJSmZMNxMdJSAnYD8MnRfnkwaRVrX47I0I7zPTenBdCvM-GZtQDK2S-310hLpbKeyemgYvit>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvledrvdeitddggeeiucetufdoteggodetrfdotf
    fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen
    uceurghilhhouhhtmecufedttdenucenucfjughrpefuhffvffhrgggtsehmtddtredttd
    ejnecuhfhrohhmpegrshgtihhinhgvmhgruceohhgvlhhloheshhgvlhhlohdrrghstghi
    ihhnvghmrgdrohhrgheqnecuggftrfgrthhtvghrnhepveffjeetuefgleeuieevveetve
    ehleeuvdfgtdevtefftdekueevgfejkeevhfdvnecuffhomhgrihhnpegrshgtihhinhgv
    mhgrrdhorhhgnecuvehluhhsthgvrhfuihiivgepudenucfrrghrrghmpehmrghilhhfrh
    homhephhgvlhhloheshhgvlhhlohdrrghstghiihhnvghmrgdrohhrgh
X-ME-Proxy: <xmx:jldLZiKWjXEa_asRyBU5LGcY0n9DNvdCUzuNk1umGJuVS7-aw9yE5w>
    <xmx:jldLZtI8x63nIx5Z72ZgLdQ4XULamv3ZkFlFQcbfT9kEWKFWwVPqyw>
    <xmx:jldLZrwt-Kyl3JgQLhlJrmkkS2sQMx2LoNkQAnSYTeTIwyqNxYHw7A>
    <xmx:jldLZpLyr0JBguevSDg53b_X5IutnGEbfGc6TGfVsY2D_iMGukAt6g>
    <xmx:j1dLZriDwH_sYVk0jY214mqsQynY3xsji5fD1zXw3qhpWwm-kE5mDTYd>
Feedback-ID: i39a149d2:Fastmail
Received: by mail.messagingengine.com (Postfix) with ESMTPA for <me@my.domain>;
 Mon, 20 May 2024 10:00:46 -0400 (EDT)
Subject: =?UTF-8?B?TG9naW4gdG8gYXNjaWluZW1hLm9yZw==?=
From: =?UTF-8?B?YXNjaWluZW1h?= <hello@hello.asciinema.org>
To: me@my.domain
Date: Mon, 20 May 2024 14:00:45 +0000
Reply-To: admin@asciinema.org
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="----=_Part_3837186536_2557352301.3238294641"
X-Rspamd-Queue-Id: 3C1FD2901CD5
X-Rspamd-Server: edb8408fe457
X-Spamd-Result: default: False [6.89 / 11.00];
	MISSING_MID(2.50)[];
	SUBJ_EXCESS_BASE64(1.50)[];
	FROM_EXCESS_BASE64(1.50)[];
	DMARC_NA(1.00)[asciinema.org];
	MIME_BASE64_TEXT_BOGUS(1.00)[];
	R_SPF_ALLOW(-1.00)[+ip4:103.168.172.128/27];
	CTYPE_MIXED_BOGUS(1.00)[];
	R_DKIM_ALLOW(-1.00)[hello.asciinema.org:s=fm1,messagingengine.com:s=fm1];
	HFILTER_URL_ONLY(0.39)[0.17763157894737];
	MIME_GOOD(-0.10)[multipart/mixed,multipart/alternative,text/plain];
	MIME_BASE64_TEXT(0.10)[];
	RCVD_COUNT_THREE(0.00)[3];
	GREYLIST(0.00)[pass,meta];
	ARC_NA(0.00)[];
	RCPT_COUNT_ONE(0.00)[1];
	MIME_TRACE(0.00)[0:+,1:+,2:+,3:~];
	RCVD_TLS_LAST(0.00)[];
	FROM_HAS_DN(0.00)[];
	REPLYTO_DOM_NEQ_FROM_DOM(0.00)[];
	PREVIOUSLY_DELIVERED(0.00)[me@my.domain];
	TO_DN_NONE(0.00)[];
	FROM_EQ_ENVFROM(0.00)[];
	TO_MATCH_ENVRCPT_ALL(0.00)[];
	RCVD_VIA_SMTP_AUTH(0.00)[];
	MISSING_XM_UA(0.00)[];
	ASN(0.00)[asn:209242, ipnet:103.168.172.0/24, country:US];
	DKIM_TRACE(0.00)[hello.asciinema.org:+,messagingengine.com:+];
	HAS_REPLYTO(0.00)[admin@asciinema.org]
X-Rspamd-Action: add header
X-Spam: Yes

------=_Part_3837186536_2557352301.3238294641
Content-Type: multipart/alternative; boundary="----=_Part_2649317485_3238082434.1923471972"

------=_Part_2649317485_3238082434.1923471972
Content-Type: text/plain;charset=UTF-8

Welcome back!

Click the following link to log in to your asciinema.org account:

https://asciinema.org/session/new?t=<login-token-here>


If you did not initiate this request, just ignore this email. The request will expire shortly.

------=_Part_2649317485_3238082434.1923471972
Content-Type: text/html;charset=UTF-8
Content-Transfer-Encoding: base64

PCFET0NUWVBFIGh0bWw+CjxodG1sPgogIDxoZWFkPgogICAgPG1ldGEgY2hhcnNldD0idXRmLTgi
PgogIDwvaGVhZD4KICA8Ym9keT4KPHA+V2VsY29tZSBiYWNrITwvcD4KCjxwPkNsaWNrIHRoZSBm
b2xsb3dpbmcgbGluayB0byBsb2cgaW4gdG8geW91ciBhc2NpaW5lbWEub3JnIGFjY291bnQ6PC9w
PgoKPHA+PGEgaHJlZj0iaHR0cHM6Ly9hc2NpaW5lbWEub3JnL3Nlc3Npb24vbmV3P3Q9U0ZNeU5U
WS5nMmdEYUFKaUFBTnNRbUptU25iNGJnWUFQXzlObG84QllnQUJVWUEuSnAxUVdRS1RSUm5ELXNS
dXJWcllLWFpRdzN1Smg3RzhTNG9RT2tMb3pKZyI+aHR0cHM6Ly9hc2NpaW5lbWEub3JnL3Nlc3Np
b24vbmV3P3Q9U0ZNeU5UWS5nMmdEYUFKaUFBTnNRbUptU25iNGJnWUFQXzlObG84QllnQUJVWUEu
SnAxUVdRS1RSUm5ELXNSdXJWcllLWFpRdzN1Smg3RzhTNG9RT2tMb3pKZzwvYT48L3A+Cgo8cD4K
ICA8YnI+CiAgSWYgeW91IGRpZCBub3QgaW5pdGlhdGUgdGhpcyByZXF1ZXN0LCBqdXN0IGlnbm9y
ZSB0aGlzIGVtYWlsLiBUaGUgcmVxdWVzdCB3aWxsIGV4cGlyZSBzaG9ydGx5Lgo8L3A+CgogIDwv
Ym9keT4KPC9odG1sPg==
------=_Part_2649317485_3238082434.1923471972--
------=_Part_3837186536_2557352301.3238294641--

Can you try without Portainer? I don’t know if that influences the behaviour?

It shouldn’t at all. It’s just a nicer way to use docker-compose as you have everything in an UI. I’ll try to look into it by copying the compose file and starting it outside of Portainer.

I don’t know how we could troubleshoot it further with you unless you can identify something we can actually act on?

I’ll try to spin up a new container. I’ll make a backup and try whether something in the volumes is messing this up by running it with the devault mailserver.env and then with mine.

Ok I thought that I’d give the mailserver.env file a quick test by passing it to the test container: docker run --rm -it --platform linux/arm64 --env-file mailserver.env mailserver/docker-mailserver apt update

But everything works as expected so that’s not the issue.

Thanks for all your suggestions, help and explanations.


Honestly I didn’t realize this was still open.

Sounds cool for testing but that would not solve that my public domain has a rDNS something like ip-10-222-16-4.myisp.com instead of my domain.

Depending on who you ask, this is either not serious at all, or a deal-breaker. If you ask me, I think it’s awful, and there is likely noting you can do when relying on an ISP. The ISP will not set a proper rDNS for you (kind of understandable).

I want to give a brief explanation of my point of view. In my main.cf, I have

smtpd_sender_restrictions_default =
    permit_mynetworks
    permit_sasl_authenticated
    reject_unknown_reverse_client_hostname
    reject_unknown_sender_domain
    permit

Either you are in mynetworks or authenticated; otherwise you are checked. The first check, reject_unknown_reverse_client_hostname will reject the request ā€œwhen the client IP address has no address -> name mappingā€. If you do not have a PTR entry, you are rejected; you’d not be rejected here.

Others may use reject_unknown_client_hostname, though. This is way stricter. According to the Postfix docs, this check rejects requests if

  1. the client IP address->name mapping fails, or
  2. the name->address mapping fails, or
  3. the name->address mapping does not match the client IP address.

ā€œThis is a stronger restriction than the reject_unknown_reverse_client_hostname feature, which triggers only under condition 1) above.ā€ At this point, you’re done, and your mail would be rejected.

Now, reject_unknown_client_hostname is tricky. You are very strict, but you risk loosing legitimate e-mails. Hence, most people use reject_unknown_reverse_client_hostname and let anti-spam measures evaluate the fact that your rDNS may not exist (very bad), or that your rDNS may not match (bad). This increases your score, and hence the likelyhood of being greylisted, marked as spam, etc. - you name it.

That being said, there is more to it. For example, whether the assumption that illegitimate e-mails have not PTR record still holds up in 2024. Depending on the link you click on, you get different answers.


Because https://github.com/asciinema/asciinema-server/issues/445 is resolved upstream, I will also close this issue. If you’d like to go on with the discussion, feel free to use our discussions 😃

Indeed, this is because my.domain has not DNS<->rDNS match 😃

So it is local only? Now that I think of it though my DNS is one domain (the intended one) and the rDNS is a subdomain of my isp with the internal ip in it. How can I check whether that issue exists outside local emails?

That’s a formidable idea! If you can, also mention the missing Message-ID header and the weird Base64 stuff. You can link to this issue and possibly to comments as well.

I already prepared the issue and I linked to your comment where you explained the issues which I think you did pretty well. The issue is on my laptop though so I’ll post it later (on my phone RN).

Hi, I got into the WebUI of rspamd and I got some reasons for why was asciinema greylisted.

Here’s the report:

MISSING_MID (2.5)
FROM_EXCESS_BASE64 (1.5)
SUBJ_EXCESS_BASE64 (1.5)
MIME_BASE64_TEXT_BOGUS (1)
DMARC_NA (1) [asciinema.org]
CTYPE_MIXED_BOGUS (1)
HFILTER_URL_ONLY (0.390789) [0.17763157894737]
MIME_BASE64_TEXT (0.1)
DKIM_TRACE (0) [hello.asciinema.org:+,messagingengine.com:+]
REPLYTO_DOM_NEQ_FROM_DOM (0)
ARC_NA (0)
MISSING_XM_UA (0)
MIME_TRACE (0) [0:+,1:+,2:+,3:~]
RCVD_COUNT_THREE (0) [3]
TO_MATCH_ENVRCPT_ALL (0)
GREYLIST (0) [greylisted,Sun, 19 May 2024 22:00:55 GMT,new record]
FROM_HAS_DN (0)
TO_DN_NONE (0)
ASN (0) [asn:209242, ipnet:103.168.172.0/24, country:US]
PREVIOUSLY_DELIVERED (0) [me@my.domain]
HAS_REPLYTO (0) [admin@asciinema.org]
FROM_EQ_ENVFROM (0)
RCVD_TLS_LAST (0)
RCPT_COUNT_ONE (0) [1]
RCVD_VIA_SMTP_AUTH (0)
MIME_GOOD (-0.1) [multipart/mixed,multipart/alternative,text/plain]
R_SPF_ALLOW (-1) [+ip4:103.168.172.128/27]
R_DKIM_ALLOW (-1) [hello.asciinema.org:s=fm1,messagingengine.com:s=fm1]

The email was resent and recieved in spam after the greylist expired.

That’s not the first message that belongs to this e-mail (denoted by the ā€œtoo earlyā€). Can you search for the first and show me?

The too early message was because I created a new login that sent a new email not because the mailserver resent it before the greylist period expired. The greylist since expired and I receive the emails now. It’s in spam with a score of 6.11 though. I’ll see why that is and whether there’s something to do about that. Maybe it’s just because there were so many of what is basically the same email.

What happens if you set both, hostname: and OVERRIDE_HOSTNAME? Technically, what you’re experiencing shouldn’t happen, als both options should be equivalent šŸ¤”

They are not equivalent since the docker option modifies the network/DNS server of the container while OVERRIDE_HOSTNAME is an option inside the container that does not modify the networking.

I can try it once I have some free time.

In your containers, can you please run

$ rspamadm configdump options | grep -A 10 -F 'dns {'

to verify which DNS servers Rspamd is using. I also need

$ cat /etc/apt/sources.list.d/rspamd.list

and the contents of what is in the signedby= section, probably /etc/apt/trusted.gpg.d/rspamd.gpg. I’d also like to know what /etc/resolv.conf contains as well, just to double-check.


I don’t think so because it’s fine until I run it in my production container.

TBH that would indicate network problems in your production container.

Using SA + OpenDKIM works now because SA is simply not performing the reverse-DNS-mismatch check this way (it does, but it does not add as much weight IIRC). Still, this is not necessarily a Rspamd problem.

Try recreating the container?

That was one of the first things I tried but I can try again. I tried to update the container (this recreates it in Portainer), then it was recreated when I switched to edge from latest.

when I used Docker in VMs that I suspended, the containers would lose network connectivity upon restoring the VM

This system does not suspend at all. It’s a Raspberry Pi working 24/7 (I did update and restart it during these issues just in case there was something with the system).

Ok, I managed to setup spamassassin and opendkim. Opendkim even has my old key now (luckily it’s not that hard to follow the files and the config) so I’m set up without any issues now.

I have both .env files so I can easily switch between them for testing. I’ll be running spamassassin now, switching to rspamd only for testing and once it’s fixed (I’d like to have the more lightweight thing).

apt update is needed before you can use apt install in the container.

I know but

root@mx:/# apt update
Err:1 http://rspamd.com/apt-stable bookworm InRelease
  409  Conflict [IP: 188.114.96.9 80]
Err:2 http://deb.debian.org/debian bookworm InRelease
  530   [IP: 188.114.96.9 80]
Err:3 http://deb.debian.org/debian bookworm-updates InRelease
  530   [IP: 188.114.96.9 80]
Err:4 http://deb.debian.org/debian-security bookworm-security InRelease
  530   [IP: 188.114.96.9 80]
Reading package lists... Done
N: See apt-secure(8) manpage for repository creation and user configuration details.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
E: The repository 'http://rspamd.com/apt-stable bookworm InRelease' is not signed.
E: Failed to fetch http://rspamd.com/apt-stable/dists/bookworm/InRelease  409  Conflict [IP: 188.114.96.9 80]
N: See apt-secure(8) manpage for repository creation and user configuration details.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
E: The repository 'http://deb.debian.org/debian bookworm InRelease' is not signed.
E: Failed to fetch http://deb.debian.org/debian/dists/bookworm/InRelease  530   [IP: 188.114.96.9 80]
E: Failed to fetch http://deb.debian.org/debian/dists/bookworm-updates/InRelease  530   [IP: 188.114.96.9 80]
E: The repository 'http://deb.debian.org/debian bookworm-updates InRelease' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
E: Failed to fetch http://deb.debian.org/debian-security/dists/bookworm-security/InRelease  530   [IP: 188.114.96.9 80]
E: The repository 'http://deb.debian.org/debian-security bookworm-security InRelease' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.

Could you chime in with what version of Docker and Docker Compose you’re running?

I use the v2 plugin, not the old binary:

āÆ docker compose version
Docker Compose version v2.27.0

If you really want to push it along without tackling that yourself, it may help if you can reproduce it between two DMS container instances which allows for isolating into an offline environment fully under our control. I understand if that’s too much hassle, but I’m also a bit surprised no one else is reporting similar issues šŸ¤”

If you’d help me set up such environment I’ll gladly do so. I’m not that familiar with mailservers (that’s why I use DMS) but I’m happy to help.

I’m also a bit surprised no one else is reporting similar issues

AFAIK not that many people use asciinema. I reckon that a pretty small number of people that

  1. Use asciinema
  2. Use it with their own mail server
  3. Use DMS
  4. Use it with rspamd

One gotcha you can run into is the default DNS used fails (using q within a container):

The command you supplied doesn’t work as there’s no arm64 image. Also the repositoried in DMS image are broken so I cannot install q in the container.

While setting the container DNS to use cloudflare 1.1.1.1 works: $ docker run --rm -it --dns 1.1.1.1 ghcr.io/natesales/q -v -x 64.147.123.154

I"ve set the container to use Cloudflare:

    dns:
      - 1.1.1.1
      - 1.0.0.1

I also recall Docker in the past year had a bug with a release with DNS too. I don’t recall specifics, but it might help to ensure you’re using the latest Docker + Docker Compose if a DNS issue remains.

I think I encountered it, that’s why I have manually set 1.1.1.1 on some containers.

docker exec -it dms-container-name dig -x 64.147.123.154 should confirm it

root@mx:/# dig -x 64.147.123.154

; <<>> DiG 9.18.24-1-Debian <<>> -x 64.147.123.154
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 47792
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;154.123.147.64.in-addr.arpa.   IN      PTR

;; ANSWER SECTION:
154.123.147.64.in-addr.arpa. 3600 IN    PTR     wfhigh3-smtp.messagingengine.com.

;; Query time: 2787 msec
;; SERVER: 127.0.0.11#53(127.0.0.11) (UDP)
;; WHEN: Thu May 09 11:46:09 CEST 2024
;; MSG SIZE  rcvd: 102

You could try disabling the check temporarily via rspamd config perhaps?

I’d rather not. I don’t know hot that config works and I don’t like running ā€œspecializedā€ setups that I have to fix every major release.

Exactly what I predicted: HFILTER_HOSTNAME_UNKNOWN means DNS didn’t work at the time of filtering the message. That’s a common issue, but it means your setup is working fine per se. You probably need to double-check your DNS servers.

Please have a look at the Rspamd log (our Rspamd docs describe the location) and see how such a score came to be. Post the result here, please.


I suspect a (temporary) DNS issue. A hostname mismatch causes a +6 in the spam score.

Why? Because of

warning: hostname wfhigh3-smtp.messagingengine.com does not resolve to address 64.147.123.154

wfhigh3-smtp.messagingengine.com does resolve to 64.147.123.154. Reverse-DNS checks out, too.

DNS is, in my experience, the most frequent source of errors. We have a dedicated section in our docs on this issue as well (with a big warning and error admonitions).

Could you please try reproduce the failure with the :edge image? There was some rspamd fixes there that may have already addressed this.