Benoit, Thank you for this reply, it answered my question very well. It is understandable that outgoing LMTP is not implemented, as it seems demand for such a feature is very low or nonexistent in the James user community. It may not be worth developing or maintaining.
Since my purposes are purely security research, I do not personally need outgoing LMTP, for now. But if someone has a future need, I could perhaps contribute a mailet once my current project is completed. Future archive readers are welcome to reach out. Sincerely, Malcolm On Wed, May 21, 2025 at 8:27 AM Benoit TELLIER <btell...@linagora.com> wrote: > Hello Malcom. > > James supports natively LMTP for incoming traffic. > > For outgoing traffic I think nothing exist yet. Failure you observed are > thus normal. > > Confirming with ChatGPT jakarta.mail do not have native support for LMTP > so bending RemoteDelivery into it will be hasardous. > > The documentation referenced is more for mstp or smtps support upon > relaying through a SMTP gateway. > > I personnally think the best way around is to implement a LMTPDelivery > mailet, which can be way simpler than remoteDelivery as it would not need a > queue. > > (btw interesting topic that was outside of my radar!) > > -- > > Best regards, > > Benoit TELLIER > > General manager of Linagora VIETNAM. > Product owner for Team-Mail product. > Chairman of the Apache James project. > > Mail: btell...@linagora.com > Tel: (0033) 6 77 26 04 58 (WhatsApp, Signal) > > > On May 20, 2025 9:18 PM, from Malcolm S <malcolm.schonga...@gmail.com > >Hello, > > I am hoping to confirm whether or not James has built-in LMTP client > capability? For instance: is it possible, without custom classes, for > James to relay a message received by its SMTP server, to a Dovecot server > over port 24 according to RFC 2033? Currently, my best efforts can only > get James to EHLO to dovecot, which of course fails. I have an otherwise > robust configuration for local delivery and further SMTP routing. > > At > > james.apache.org/server/3/apidocs/org/apache/james/transport/mailets/RemoteDelivery.html > , > Under the gateway:port sub-bullet, the documentation references the > "default port for the specified connection type." i.e., implying you can > specify multiple connection types. Can an LMTP connection be specified? > adding an "lmtp:///" prefix (or variations thereof) to my <gateway> URL > fails. > > On the other hand, mailing list archives from 2013, 2010, and 2006 > reference a lack of a built-in method. > > If the answer is yes it can be done (i.e., without deploying a custom > subclass of RemoteDelivery), how do I configure my processor in > mailetcontainer.xml to specify outgoing LMTP transport? If the answer is > no, could someone perhaps clarify the "default port for the specified > connection" language in the above-referenced documentation webpage? > > Thank you very much in advance! >
