Unable to deliver emails after upgrade to 1.5.0 (Same happens on 1.6.0)

[yurividal]

Support guidelines

• I've read the support guidelines

I've found a bug and checked that ...

• ... the documentation does not mention anything about my problem
• ... there are no open or closed issues that are related to my problem

Description

Ever since i updated to 1.5.0, i can no longer deliver emails.
All emails return to sender, with the following error:

I added BLOCKLIST_API_SECRET to my env, but that didn't do the trick.

Expected behaviour

the app should continue working as it did on 1.3.8

Actual behaviour

emails to catch-all are rejected

Steps to reproduce

Upgrade from 1.3.8 to 1.5.0 or 1.6.0
Send an email to a new alias
email gets rejected

Docker info

Client: Docker Engine - Community
 Version:    28.1.1
 Context:    default
 Debug Mode: false
 Plugins:
  buildx: Docker Buildx (Docker Inc.)
    Version:  v0.23.0
    Path:     /usr/libexec/docker/cli-plugins/docker-buildx
  compose: Docker Compose (Docker Inc.)
    Version:  v2.35.1
    Path:     /usr/libexec/docker/cli-plugins/docker-compose

Server:
 Containers: 9
  Running: 8
  Paused: 0
  Stopped: 1
 Images: 29
 Server Version: 28.1.1
 Storage Driver: overlay2
  Backing Filesystem: extfs
  Supports d_type: true
  Using metacopy: false
  Native Overlay Diff: true
  userxattr: false
 Logging Driver: json-file
 Cgroup Driver: systemd
 Cgroup Version: 2
 Plugins:
  Volume: local
  Network: bridge host ipvlan macvlan null overlay
  Log: awslogs fluentd gcplogs gelf journald json-file local splunk syslog
 Swarm: inactive
 Runtimes: io.containerd.runc.v2 runc
 Default Runtime: runc
 Init Binary: docker-init
 containerd version: 05044ec0a9a75232cad458027ca83437aae3f4da
 runc version: v1.2.5-0-g59923ef
 init version: de40ad0
 Security Options:
  apparmor
  seccomp
   Profile: builtin
  cgroupns
 Kernel Version: 5.15.0-161-generic
 Operating System: Ubuntu 22.04.5 LTS
 OSType: linux
 Architecture: x86_64
 CPUs: 4
 Total Memory: 3.82GiB
 Name: vps
 ID: 5a02e337-4199-401c-98e9-80882fd5914e
 Docker Root Dir: /var/lib/docker
 Debug Mode: false
 Experimental: false
 Insecure Registries:
  containers.sut.local
  ::1/128
  127.0.0.0/8
 Live Restore Enabled: false
 Default Address Pools:
   Base: 10.32.0.0/16, Size: 24

Docker Compose config

Logs

nothing relevant prints in the logs about this issue

Additional info

No response

[yurividal]

This only affects catch-all new aliases. For existing aliases it still works

[yurividal]

@crazy-max this has been fixed in 1.6.1

anonaddy/anonaddy#866 (comment)