Lost message?

i’m using kumod 2025.05.06-b29689af on our infrastructure and have now a customer reporting for not receiving an email.

at june 12 2025 kumomta received a message and until todays restart there was no log about it meanwhile:

zstdgrep “xxx@qards.de” /var/log/kumomta/202506-* | grep -v ‘webhook.log_hook’
/var/log/kumomta/20250612-085646.862481895:{“type":“Reception”,“id”:“bc1584fc476b11f08e2ebc2411afc7a8”,“sender”:"baifh.fbc.befc=bounce@newsletter.qards.de,“recipient”:"xxx@qards.de",“queue”:"21968-623:default-tenant@qards.de",“site”:“”,“size”:92048,“response”:{“code”:250,“enhanced_code”:null,“content”:“”,“command”:null},“peer_address”:{“name”:“”,“addr”:“172.18.0.17”},“timestamp”:1749718849,“created”:1749718849,“num_attempts”:0,“bounce_classification”:“Uncategorized”,“egress_pool”:null,“egress_source”:null,“source_address”:null,“feedback_report”:null,“meta”:{},“headers”:{“X-Envid”:“21968-623-2563”,“Message-Id”:“gy8.hb.1z7@newsletter.qards.de”},“delivery_protocol”:null,“reception_protocol”:“ESMTP”,“nodeid”:“476588fd-acb2-436c-b60e-4c84e2172869”,“session_id”:“0e743061-d639-4508-a306-66073f1fcaef”}

on today’s restart i got the log:
/var/log/kumomta/20250711-103259.288973175:{“type":“Expiration”,“id”:“bc1584fc476b11f08e2ebc2411afc7a8”,“sender”:"baifh.fbc.befc=bounce@newsletter.qards.de,“recipient”:"xxx@qards.de",“queue”:"21968-623:default-tenant@qards.de",“site”:“”,“size”:92048,“response”:{“code”:551,“enhanced_code”:{“class”:5,“subject”:4,“detail”:7},“content”:“Next delivery time would be 29days 1h 32m 8s 382ms 774us 693ns after creation, which exceeds max_age=12h”,“command”:null},"…

do you have any clue on that one? i mean sure there can be a delay due heavy load, but not for 29 days :wink:

fyi: Go to https://cal.com/team/kumomta/paid-support-session to book your time.
does not exist anymore :slightly_smiling_face:

Can you paste your config here?

do you need something different than init.lua?
init.lua (9.07 KB)

queue.toml:

# Allow optional scheduled sends based on this header
# https://docs.kumomta.com/reference/message/import_scheduling_header
scheduling_header = "X-Schedule"

# Set the tenant from this header and delete the header for added security
tenant_header = "X-Tenant"
remove_tenant_header = false

# Set the campaign from this header and delete the header for added security
campaign_header = "X-Campaign"
remove_campaign_header = false

# The tenant to use if no tenant_header is present
default_tenant = "default-tenant"

[tenant.'default-tenant']
egress_pool = 'pool-1'

[tenant.'account-0']
egress_pool = 'pool-1'

# The default set of parameters
[queue.default]
max_age = '12 hours'
strategy = "SingletonTimerWheel"
retry_interval = '1 mins'

# Base settings for a given destination domain.
# These are overridden by more specific settings
# in a tenant or more specific queue
[queue.'gmail.com']
max_age = '12 hours'
retry_interval = '17 mins```

New link is https://cal.com/team/kumomta-support/paid-support-session

Thanks for the heads-up.

Will take a look in a second at this.