LMTP Client Capability?

Malcolm S <[email protected]> Tue, 20 May 2025 15:16:59 -0400
Newsgroups gmane.comp.jakarta.james.user
Message-ID <CAB_XT3HiTAOpgQKQPhyr4L2LBszCY_0dxWLCNOnCaLxszH_YPg@mail.gmail.com>
--000000000000ae76550635961844
Content-Type: text/plain; charset="UTF-8"

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
https://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!

--000000000000ae76550635961844--