Re: LMTP Client Capability?

Benoit TELLIER <[email protected]> Wed, 21 May 2025 12:26:29 +0000
Newsgroups gmane.comp.jakarta.james.user
Message-ID <[email protected]>
---=Part.75.348201004246a88a.196f2cf3a09.a135c9eb373fa1d9=-
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Accept-Language: fr-FR, en-US, vi-VN, ru-RU, ar-TN, it-IT, de-DE
Content-Language: en-US

Hello Malcom=2E

James supports natively LMTP for incoming traffic=2E

For =
outgoing traffic I think nothing exist yet=2E Failure you observed are thus=
 normal=2E

Confirming with ChatGPT jakarta=2Email do not have native suppo=
rt for LMTP so bending RemoteDelivery into it will be hasardous=2E

The doc=
umentation referenced is more for mstp or smtps support upon relaying throu=
gh a SMTP gateway=2E

I personnally think the best way around is to impleme=
nt a LMTPDelivery mailet, which can be way simpler than remoteDelivery as i=
t would not need a queue=2E

(btw interesting topic that was outside of my =
radar!)

--=C2=A0

Best regards,

Benoit TELLIER

General manager of Linago=
ra VIETNAM=2E
Product owner for Team-Mail product=2E
Chairman of the Apache=
 James project=2E

Mail: btellier@linagora=2Ecom
Tel: (0033) 6 77 26 04 58 =
(WhatsApp, Signal)


On May 20, 2025 9:18 PM, from Malcolm S <malcolm=2Esch=
ongalla@gmail=2Ecom>Hello,

I am hoping to confirm whether or not James has=
 built-in LMTP client
capability?  For instance: is it possible, without cu=
stom 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 ef=
forts can only
get James to EHLO to dovecot, which of course fails=2E  I ha=
ve an otherwise
robust configuration for local delivery and further SMTP ro=
uting=2E

At
james=2Eapache=2Eorg/server/3/apidocs/org/apache/james/transpo=
rt/mailets/RemoteDelivery=2Ehtml
,
Under the gateway:port sub-bullet, the d=
ocumentation references the
"default port for the specified connection type=
=2E" i=2Ee=2E, implying you can
specify multiple connection types=2E  Can a=
n LMTP connection be specified?
adding an "lmtp:///" prefix (or variations =
thereof) to my <gateway> URL
fails=2E

On the other hand, mailing list arch=
ives from 2013, 2010, and 2006
reference a lack of a built-in method=2E

If=
 the answer is yes it can be done (i=2Ee=2E, without deploying a custom
sub=
class of RemoteDelivery), how do I configure my processor in
mailetcontaine=
r=2Exml to specify outgoing LMTP transport?  If the answer is
no, could som=
eone perhaps clarify the "default port for the specified
connection" langua=
ge in the above-referenced documentation webpage?

Thank you very much in a=
dvance!

---=Part.75.348201004246a88a.196f2cf3a09.a135c9eb373fa1d9=---