Re: [Mailman-Developers] [Mailman-Users] Mailman 3: Deployment without LMTP

[Redirecting to mailman-developers]
On Jul 25, 2015, at 01:34 PM, Michael Hierweck wrote:
It wouldn't be out of the question to do it this way, although you're right that you have to have some special handling for rejections. Technically speaking, Mailman would still support "bounces", which are messages created out of whole-cloth by Mailman sent to the original sender out of band to the LMTP conversation, encapsulating the original message. In fact, your dot-forward-to-LMTP bridge would probably have to capture the LMTP 4xx and 5xx rejection codes and craft a bounce, although it could potentially allow Mailman itself to deliver this.
Remember though that the LMTP runner isn't all *that* special, in that upon successful acceptance of the message, it will just drop it in the appropriate queue for further processing. It's certainly conceivable that one could implement a new type of runner that interfaced with dot-forward files in much the same way that MM2 did, but with logic a bit more compatible with MM3's queue structure and database.
The trickiest part of all this is handling the security implications of using a dot-forward program. The core only supports LMTP delivery by default in MM3 so we get to ignore all the C wrappers and gid-mismatch fun of MM2.
FWIW, this could all be built as a separate plugin for the core.
Cheers, -Barry
participants (1)
-
Barry Warsaw