Date: Wed, 21 Jan 2026 20:34:14 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 274988] add cron.d/dma to periodically flush the queue Message-ID: <bug-274988-227-4HZJQ9C9PT@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-274988-227@https.bugs.freebsd.org/bugzilla/>
index | next in thread | previous in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274988 Xin LI <delphij@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|bugs@FreeBSD.org |ronald@FreeBSD.org CC| |delphij@FreeBSD.org --- Comment #2 from Xin LI <delphij@FreeBSD.org> --- I think dma(8) is not really equipped to function as a complete MTA, and 30 minutes is likely too long given how common greylisting is, even though RFC 5321 Section 4.5.4.1 recommends an interval of 30 minutes or more. That said, while I agree that a cron.d entry is a reasonable workaround, I think if stuck mail is a concern, the real problem is that dma(8) should NOT be used in this scenario. In all my setups, for example, the sole purpose of dma(8) is to send email to my mail hub (which runs Postfix), and some of them do not use dma(8) at all and run full Postfix. In order to really fix this, dma(8) would need a mechanism to perform this operation by itself, but that probably contradicts its design goals. -- You are receiving this mail because: You are the assignee for the bug.home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-274988-227-4HZJQ9C9PT>