You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-dev@james.apache.org by "Metcalf, Jeffrey M" <Je...@pfizer.com> on 2007/04/26 03:55:52 UTC
Gateway SMTP server authentication patch for James 2.2.0
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.
Best regards,
Jeffrey M. Metcalf
Senior Advisor
Technology Engineering
Worldwide Technology and Business Innovation
Pfizer Inc
E-Mail: Jeffrey.M.Metcalf@pfizer.com
Office: (860) 686-1796
----------------------------------------------------------------------
LEGAL NOTICE
Unless expressly stated otherwise, this message is confidential and may be privileged. It is intended for the addressee(s) only. Access to this E-mail by anyone else is unauthorized. If you are not an addressee, any disclosure or copying of the contents of this E-mail or any action taken (or not taken) in reliance on it is unauthorized and may be unlawful. If you are not an addressee, please inform the sender immediately.
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
Re: Gateway SMTP server authentication patch for James 2.2.0
Posted by Norman Maurer <no...@apache.org>.
Hi Jeffrey,
isn't it just possible to replace it with james 2.3.1 ? The release
canidat is allready released and the final version will come soon ( VOTE
is running).
We fixed many bugs since 2.2.0. So i whould try to upgrade.
If this is not possible in your case ( I hope it is) ,you could look at
the 2.3.1 source code for the needed changes. See:
http://svn.apache.org/repos/asf/james/server/branches/v2.3/src/java/org/apache/james/transport/mailets/RemoteDelivery.java
Search for authUser ;-)
bye
Norman
Metcalf, Jeffrey M schrieb:
> 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.
>
> Best regards,
>
> Jeffrey M. Metcalf
> Senior Advisor
> Technology Engineering
> Worldwide Technology and Business Innovation
> Pfizer Inc
> E-Mail: Jeffrey.M.Metcalf@pfizer.com
> Office: (860) 686-1796
>
> ----------------------------------------------------------------------
> LEGAL NOTICE
> Unless expressly stated otherwise, this message is confidential and may be privileged. It is intended for the addressee(s) only. Access to this E-mail by anyone else is unauthorized. If you are not an addressee, any disclosure or copying of the contents of this E-mail or any action taken (or not taken) in reliance on it is unauthorized and may be unlawful. If you are not an addressee, please inform the sender immediately.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
> For additional commands, e-mail: server-dev-help@james.apache.org
>
>
> !DSPAM:1,463006ec324321016014554!
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
Re: Gateway SMTP server authentication patch for James 2.2.0
Posted by Stefano Bagnara <ap...@bago.org>.
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: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org