Recent changes to feature-requests

Offer more logging strategies

DavidM — Fri, 20 Mar 2026 12:36:16 -0000

I think it would be useful to offer more levels of logging. The current default & verbose work well but are quite 'chatty' and thus one can overlook issues.

I would like options to show just:

1) good connections with traffic sucsessfully sent.
2) failed authentication sessions
3) good authentication sessions

or similar.

Example:
emailrelay: 20260320.110200.177: info: 91.92.243.228;62359: smtp connection from 91.92.243.228:62359
emailrelay: 20260320.110200.197: info: dnsbl: address [91.92.243.228] allowed by [spam.dnsbl.example.com]
emailrelay: 20260320.110200.197: info: dnsbl: address [91.92.243.228] allowed by [block.dnsbl.example.com]
emailrelay: 20260320.110200.197: info: tx>>: "220 smtp2.xxxx.net -- E-MailRelay V2.6.1 -- Service ready"
emailrelay: 20260320.110200.269: info: 91.92.243.228;62359: rx<<: "EHLO User"
emailrelay: 20260320.110200.269: info: 91.92.243.228;62359: tx>>: "250-smtp2.xxxx.net says hello"
emailrelay: 20260320.110200.269: info: 91.92.243.228;62359: tx>>: "250-AUTH CRAM-SHA512 CRAM-SHA256 CRAM-SHA1 CRAM-MD5 PLAIN LOGIN"
emailrelay: 20260320.110200.269: info: 91.92.243.228;62359: tx>>: "250-VRFY"
emailrelay: 20260320.110200.269: info: 91.92.243.228;62359: tx>>: "250-PIPELINING"
emailrelay: 20260320.110200.269: info: 91.92.243.228;62359: tx>>: "250 8BITMIME"
emailrelay: 20260320.110200.330: info: 91.92.243.228;62359: rx<<: "AUTH LOGIN"
emailrelay: 20260320.110200.330: info: 91.92.243.228;62359: tx>>: "334 VXNlcm5hbWU6"
emailrelay: 20260320.110200.391: info: 91.92.243.228;62359: rx<<: [authentication response not logged]
emailrelay: 20260320.110200.391: info: 91.92.243.228;62359: tx>>: "334 UGFzc3dvcmQ6"
emailrelay: 20260320.110200.454: info: 91.92.243.228;62359: rx<<: [authentication response not logged]
emailrelay: 20260320.110200.454: warning: 91.92.243.228;62359: failed authentication of remote client using mechanism [login] and missing secret for [scan]
emailrelay: 20260320.110200.454: info: 91.92.243.228;62359: tx>>: "535 authentication failed"
emailrelay: 20260320.110200.529: info: 91.92.243.228;62359: rx<<: "QUIT"
emailrelay: 20260320.110200.529: info: 91.92.243.228;62359: tx>>: "221 OK"
emailrelay: 20260320.110200.529: info: 91.92.243.228;62359: smtp connection closed: smtp protocol done: 91.92.243.228:62359
emailrelay: 20260320.110200.529: info: forwarding: [client disconnect]
emailrelay: 20260320.110200.530: info: forwarding: no messages to send

So that sessions attempted to authenticate but failed and no traffic was sent.

emailrelay: 20260320.001021.623: info: 144.202.39.78;33798: smtp connection from 144.202.39.78:33798
emailrelay: 20260320.001021.640: info: dnsbl: address [144.202.39.78] allowed by [spam.dnsbl.example.com]
emailrelay: 20260320.001021.640: info: dnsbl: address [144.202.39.78] allowed by [block.dnsbl.example.com]
emailrelay: 20260320.001021.640: info: tx>>: "220 smtp2.xxxxx.net -- E-MailRelay V2.6.1 -- Service ready"
emailrelay: 20260320.001021.764: info: 144.202.39.78;33798: smtp connection closed: peer shutdown: 144.202.39.78:33798
emailrelay: 20260320.001021.765: info: forwarding: [client disconnect]
emailrelay: 20260320.001021.765: info: forwarding: no messages to send

This one (presumably) did not attempt to authenticate and failed with no traffic being sent.

#44 Docker file?

Graeme Walker — Tue, 03 Feb 2026 20:24:27 -0000

status: open --> closed

#43 Create arm emailrelay_x.x_arm64-deb12.deb

Graeme Walker — Tue, 03 Feb 2026 20:23:43 -0000

status: open --> closed

#42 verifying sender domains

Graeme Walker — Tue, 03 Feb 2026 20:22:34 -0000

status: open --> closed

#40 Network filter abandon result

Graeme Walker — Tue, 03 Feb 2026 20:17:33 -0000

status: open --> closed

#44 Docker file?

hijmen — Sat, 10 Jan 2026 14:50:21 -0000

Thank you for the reply. Yes, that was the one I found to be most downloaded on docker hub.
I installed it and it is working fine. I used the config and secrets file from my vm installation, changed the dns entry in my router and had it up and running in a few minutes.

#44 Docker file?

Graeme Walker — Fri, 09 Jan 2026 16:07:12 -0000

I don't think I could add much value by publishing a docker image myself since I don't use docker at all. Dogukan Cagatay's contribution in DockerHub looks very good though. Can you use that?

Docker file?

hijmen — Thu, 08 Jan 2026 21:59:07 -0000

HI Graeme,

I enjoy using e-mailrelay in my personal environment, especially for older gear and application that do not support modern authentication for their email warnings and messages (mostly for monitoring purposes).

I am in the process of moving from dedicated VMs for my applications to a Docker based approach.

Is there a possibility you will publish a docker image for emailrelay to the docker repository in the near feature?
(I believe I have found one, but do not know if you are the publisher or a third party just created the image)

Regards
Hijmen

Docker file?

hijmen — Thu, 08 Jan 2026 21:59:07 -0000

Ticket 44 has been modified: Docker file?
Edited By: Graeme Walker (graeme_walker)
Status updated: 'open' => 'closed'

#40 Network filter abandon result

Yunus YILDIRIM — Mon, 10 Nov 2025 07:17:05 -0000

Patch it and test it.
It seems fine and works as expected when respond "100" over network filter