Hi!  I'm investigating adding support for the SMTP ATRN command to the
Java Apache Mail Enterprise Server (Apache JAMES), which uses JavaMail
for transport.

Unfortunately, ATRN presents a challenge not anticipated by the JavaMail
API.  ATRN reverses the roles of client and server on an established TCP
connection, allowing a client with a dynamic IP address to trigger
delivery of queued mail.  The specification for ATRN is defined by
rfc2645, On-Demand Mail Relay.
http://www.cis.ohio-state.edu/cgi-bin/rfc/rfc2645.html

In order for a mail server to use JavaMail to deliver SMTP mail on a
"turned" connection, JavaMail must somehow be handed an already-existing
connection.  At the moment, the javax.mail.Service interface only offers
connect() methods that take a hostname and a port.  It would greatly
facilitate the implementation of ATRN in Java mail servers if there was
a version of connect() on Service that worked like this:

public void connect(java.net.Socket s) throws MessagingException;

This would make it easy for Java servers to deliver mail on TCP
connections established by clients, as required by rfc2645.

Thank you for considering this enhancement to the JavaMail
specification.

Jeff Schnitzer
[EMAIL PROTECTED]

--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to