Metcalf, Jeffrey M ha scritto:
Hi All,
I have a requirement to use James 2.2.0 since it is bundled with a vendor
application. My ISP blocks outgoing traffic on port 25 and requires me to use
an SMTP gateway on port 587 to send e-mail to the outside world. Unfortunately
they also require authentication and it does not seen that the standard James
2.2.0 org.apache.james.transport.mailets.RemoteDelivery mailet supports
providing a username and password to the gateway feature.
I browsed the source code and it looks like I can just augment the JavaMail
Session in the code with auth properties to accomplish this. I am an
experienced Java developer but only have limited JavaMail experience, and if
someone has already done this, it would same me time if I could be directed to
a patch. I'm sure my problem is quite common, so I am sure that there is no
shortage of patches out there. Again my only limitation is the patch would
have to be applied to a 2.2.0 codebase since I am constrained by the vendor
application.
Take a look to 2.3.1 RemoteDelivery:
http://svn.apache.org/repos/asf/james/server/tags/build_2_3_1/src/java/org/apache/james/transport/mailets/RemoteDelivery.java
That remote delivery supports both:
1) Specific parameters for gatewayusername/gatewayPassword
2) "Custom javamail parameters" in the form of
<mail.xxxxxxx.xxx>value</mail.xxxxxxx.xxx>
It should not be too hard to backport the changes to 2.2.0, but I really
suggest anyone to upgrade to 2.3.1 as soon as possible as we fixed
really many issues since 2.2.0.
Stefano
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
