Re: AW: AW: URGENT HELP: Backport STARTTLS from 3.0 to 2.3.2 [unsigned]

2016-07-04 Thread Mahesh Sivarama Pillai
Thanks for the inputs..I will explore 3.0 beta..

On 04-Jul-2016 12:49 PM, "Bernd Waibel" <bwai...@intarsys.de> wrote:

> Hello Mahesh,
>
> we are using 2.3.2 till now. We are currently switching to 3.0 beta4, but
> I do not have information about STARTTLS stability.
>
> One reason for switching is STARTTLS. We do not want to implement it on
> our own.
> The other reason is: 2.3.2 is very old. There are some other problems,
> which are more crititcal to us.
> For example, handling of attachment parameters is done by java mail, the
> mail.jar is very old, and does have problems.
> We replaced mail.jar with a newer version for that. The JDK is very old
> (Java6), we need newer versions.
> We have also implemented some extension (allowing 8bit-MIME, logging AUTH
> IP Address, some EHLO, HELO, RCPT and VRFY Extensions). But 2.3.2 has
> stopped, so no future bug fixing will follow.
>
> Independend of this:
> There will be a point in future, when you have to switch to 3.0.
> The architecure and the configuration has changed a lot, so if you start
> now with 2.3.2, it may be easier to start with 3.0, instead doing the
> migration later on.
>
> I would recommend to switch to 3.0beta4, instead coding it your own.
> But that are just my thoughts.
>
>
> Best regards
> Bernd Waibel
>
> -Ursprüngliche Nachricht-
> Von: Mahesh Sivarama Pillai [mailto:srm...@gmail.com]
> Gesendet: Montag, 4. Juli 2016 08:59
> An: James Users List <server-user@james.apache.org>
> Betreff: Re: AW: URGENT HELP: Backport STARTTLS from 3.0 to 2.3.2
>
> Thank a lot Bernd...I will look at the handlers. The current requirement is
> to act as a receiver.. One more question. I see James 3 SMTP implementation
> is mentioned as stable. Is this true for STARTTLS as well ?
>
> On 04-Jul-2016 12:20 PM, "Bernd Waibel" <bwai...@intarsys.de> wrote:
>
> > Hello Mahesh,
> >
> > i think there is no backport.
> >
> > For STARTTLS there should be two sides:
> > - James acting as receiver
> > - James acting as sender
> >
> > You have the option to use TLS in James, by configuring a
> > "org.apache.avalon.cornerstone.blocks.sockets.TLSServerSocketFactory".
> > But this is for strict TLS binding, not a STARTTLS. But it may be worth
> to
> > look at.
> >
> > For the receiving side:
> > If you want to implement it in james, you need a handler for that.
> > Have a look at org.apache.james.smtpserver package.
> > There are the handlers for the low-level protocols.
> >
> > I think you need to extend or change one of the handler classes.
> > Then you need to register your own handler class, by
> > - including the "james-smtphandlerchain.xml" into your config.xml
> > - change the class name inside the james-smtphandlerchain.xml.
> > - change the EhloCmdHandler.java, to announce the STARTTLS option
> > (esmtpextensions.add("STARTTLS");)
> >
> > The StartTLS is implemented in James3, have a look at:
> > org.apache.james.protocols.smtp.core.esmtp. StartTlsCmdHandler;
> >
> > For the sending side:
> > You need to change or expand the RemoteDelivery Mailet.
> > In James3 this is done, have a look at.
> >
> > Just theory.
> > I am not sure, if I would recommend to implement it. You need to test it,
> > too.
> > Maybe you could use James 3 beta4, which is long released version, and is
> > used by some servers.
> >
> >
> > Greetings
> > Bernd
> >
> > -Ursprüngliche Nachricht-
> > Von: Mahesh Sivarama Pillai [mailto:srm...@gmail.com]
> > Gesendet: Montag, 4. Juli 2016 04:31
> > An: James Users List <server-user@james.apache.org>
> > Betreff: Re: URGENT HELP: Backport STARTTLS from 3.0 to 2.3.2
> >
> > Hi,
> >
> >  Can someone suggest how to go about this please ?
> >
> > Thanks
> > Mahesh
> >
> > On Thu, Jun 30, 2016 at 11:26 AM, Mahesh Sivarama Pillai <
> srm...@gmail.com
> > >
> > wrote:
> >
> > > Hi All,
> > >
> > > Did someone backport *STARTTLS* feature from 3.0 beta to 2.3.2 ? We
> have
> > > 2.3.2 running in production and there is a requirement to support
> > STARTTLS.
> > > Since 3.0 is in beta, the team is not comfortable in putting into
> > > production.
> > >
> > > If the porting is not done, can someone please guide on how to
> implement
> > > this in 2.3.2 ? I can give it a try.
> > >
> > > Thanks
> > > Mahesh
> > >
> >
>


AW: AW: URGENT HELP: Backport STARTTLS from 3.0 to 2.3.2 [unsigned]

2016-07-04 Thread Bernd Waibel
Hello Mahesh,

we are using 2.3.2 till now. We are currently switching to 3.0 beta4, but I do 
not have information about STARTTLS stability.

One reason for switching is STARTTLS. We do not want to implement it on our own.
The other reason is: 2.3.2 is very old. There are some other problems, which 
are more crititcal to us.
For example, handling of attachment parameters is done by java mail, the 
mail.jar is very old, and does have problems.
We replaced mail.jar with a newer version for that. The JDK is very old 
(Java6), we need newer versions.
We have also implemented some extension (allowing 8bit-MIME, logging AUTH IP 
Address, some EHLO, HELO, RCPT and VRFY Extensions). But 2.3.2 has stopped, so 
no future bug fixing will follow.

Independend of this:
There will be a point in future, when you have to switch to 3.0.
The architecure and the configuration has changed a lot, so if you start now 
with 2.3.2, it may be easier to start with 3.0, instead doing the migration 
later on.

I would recommend to switch to 3.0beta4, instead coding it your own.
But that are just my thoughts.


Best regards
Bernd Waibel

-Ursprüngliche Nachricht-
Von: Mahesh Sivarama Pillai [mailto:srm...@gmail.com] 
Gesendet: Montag, 4. Juli 2016 08:59
An: James Users List <server-user@james.apache.org>
Betreff: Re: AW: URGENT HELP: Backport STARTTLS from 3.0 to 2.3.2

Thank a lot Bernd...I will look at the handlers. The current requirement is
to act as a receiver.. One more question. I see James 3 SMTP implementation
is mentioned as stable. Is this true for STARTTLS as well ?

On 04-Jul-2016 12:20 PM, "Bernd Waibel" <bwai...@intarsys.de> wrote:

> Hello Mahesh,
>
> i think there is no backport.
>
> For STARTTLS there should be two sides:
> - James acting as receiver
> - James acting as sender
>
> You have the option to use TLS in James, by configuring a
> "org.apache.avalon.cornerstone.blocks.sockets.TLSServerSocketFactory".
> But this is for strict TLS binding, not a STARTTLS. But it may be worth to
> look at.
>
> For the receiving side:
> If you want to implement it in james, you need a handler for that.
> Have a look at org.apache.james.smtpserver package.
> There are the handlers for the low-level protocols.
>
> I think you need to extend or change one of the handler classes.
> Then you need to register your own handler class, by
> - including the "james-smtphandlerchain.xml" into your config.xml
> - change the class name inside the james-smtphandlerchain.xml.
> - change the EhloCmdHandler.java, to announce the STARTTLS option
> (esmtpextensions.add("STARTTLS");)
>
> The StartTLS is implemented in James3, have a look at:
> org.apache.james.protocols.smtp.core.esmtp. StartTlsCmdHandler;
>
> For the sending side:
> You need to change or expand the RemoteDelivery Mailet.
> In James3 this is done, have a look at.
>
> Just theory.
> I am not sure, if I would recommend to implement it. You need to test it,
> too.
> Maybe you could use James 3 beta4, which is long released version, and is
> used by some servers.
>
>
> Greetings
> Bernd
>
> -Ursprüngliche Nachricht-----
> Von: Mahesh Sivarama Pillai [mailto:srm...@gmail.com]
> Gesendet: Montag, 4. Juli 2016 04:31
> An: James Users List <server-user@james.apache.org>
> Betreff: Re: URGENT HELP: Backport STARTTLS from 3.0 to 2.3.2
>
> Hi,
>
>  Can someone suggest how to go about this please ?
>
> Thanks
> Mahesh
>
> On Thu, Jun 30, 2016 at 11:26 AM, Mahesh Sivarama Pillai <srm...@gmail.com
> >
> wrote:
>
> > Hi All,
> >
> > Did someone backport *STARTTLS* feature from 3.0 beta to 2.3.2 ? We have
> > 2.3.2 running in production and there is a requirement to support
> STARTTLS.
> > Since 3.0 is in beta, the team is not comfortable in putting into
> > production.
> >
> > If the porting is not done, can someone please guide on how to implement
> > this in 2.3.2 ? I can give it a try.
> >
> > Thanks
> > Mahesh
> >
>


Re: AW: URGENT HELP: Backport STARTTLS from 3.0 to 2.3.2

2016-07-04 Thread Mahesh Sivarama Pillai
Thank a lot Bernd...I will look at the handlers. The current requirement is
to act as a receiver.. One more question. I see James 3 SMTP implementation
is mentioned as stable. Is this true for STARTTLS as well ?

On 04-Jul-2016 12:20 PM, "Bernd Waibel" <bwai...@intarsys.de> wrote:

> Hello Mahesh,
>
> i think there is no backport.
>
> For STARTTLS there should be two sides:
> - James acting as receiver
> - James acting as sender
>
> You have the option to use TLS in James, by configuring a
> "org.apache.avalon.cornerstone.blocks.sockets.TLSServerSocketFactory".
> But this is for strict TLS binding, not a STARTTLS. But it may be worth to
> look at.
>
> For the receiving side:
> If you want to implement it in james, you need a handler for that.
> Have a look at org.apache.james.smtpserver package.
> There are the handlers for the low-level protocols.
>
> I think you need to extend or change one of the handler classes.
> Then you need to register your own handler class, by
> - including the "james-smtphandlerchain.xml" into your config.xml
> - change the class name inside the james-smtphandlerchain.xml.
> - change the EhloCmdHandler.java, to announce the STARTTLS option
> (esmtpextensions.add("STARTTLS");)
>
> The StartTLS is implemented in James3, have a look at:
> org.apache.james.protocols.smtp.core.esmtp. StartTlsCmdHandler;
>
> For the sending side:
> You need to change or expand the RemoteDelivery Mailet.
> In James3 this is done, have a look at.
>
> Just theory.
> I am not sure, if I would recommend to implement it. You need to test it,
> too.
> Maybe you could use James 3 beta4, which is long released version, and is
> used by some servers.
>
>
> Greetings
> Bernd
>
> -Ursprüngliche Nachricht-----
> Von: Mahesh Sivarama Pillai [mailto:srm...@gmail.com]
> Gesendet: Montag, 4. Juli 2016 04:31
> An: James Users List <server-user@james.apache.org>
> Betreff: Re: URGENT HELP: Backport STARTTLS from 3.0 to 2.3.2
>
> Hi,
>
>  Can someone suggest how to go about this please ?
>
> Thanks
> Mahesh
>
> On Thu, Jun 30, 2016 at 11:26 AM, Mahesh Sivarama Pillai <srm...@gmail.com
> >
> wrote:
>
> > Hi All,
> >
> > Did someone backport *STARTTLS* feature from 3.0 beta to 2.3.2 ? We have
> > 2.3.2 running in production and there is a requirement to support
> STARTTLS.
> > Since 3.0 is in beta, the team is not comfortable in putting into
> > production.
> >
> > If the porting is not done, can someone please guide on how to implement
> > this in 2.3.2 ? I can give it a try.
> >
> > Thanks
> > Mahesh
> >
>


WG: URGENT HELP: Backport STARTTLS from 3.0 to 2.3.2 [unsigned]

2016-07-04 Thread Bernd Waibel
Hello Mahesh,

i think there is no backport.

For STARTTLS there should be two sides:
- James acting as receiver
- James acting as sender

You have the option to use TLS in James, by configuring a 
"org.apache.avalon.cornerstone.blocks.sockets.TLSServerSocketFactory".
But this is for strict TLS binding, not a STARTTLS. But it may be worth to look 
at.

For the receiving side:
If you want to implement it in james, you need a handler for that.
Have a look at org.apache.james.smtpserver package. 
There are the handlers for the low-level protocols.

I think you need to extend or change one of the handler classes.
Then you need to register your own handler class, by 
- including the "james-smtphandlerchain.xml" into your config.xml
- change the class name inside the james-smtphandlerchain.xml.
- change the EhloCmdHandler.java, to announce the STARTTLS option 
(esmtpextensions.add("STARTTLS");)

The StartTLS is implemented in James3, have a look at:
org.apache.james.protocols.smtp.core.esmtp. StartTlsCmdHandler;

For the sending side:
You need to change or expand the RemoteDelivery Mailet.
In James3 this is done, have a look at.

Just theory.
I am not sure, if I would recommend to implement it. You need to test it, too.
Maybe you could use James 3 beta4, which is long released version, and is used 
by some servers.


Greetings
Bernd

-Ursprüngliche Nachricht-
Von: Mahesh Sivarama Pillai [mailto:srm...@gmail.com] 
Gesendet: Montag, 4. Juli 2016 04:31
An: James Users List <server-user@james.apache.org>
Betreff: Re: URGENT HELP: Backport STARTTLS from 3.0 to 2.3.2

Hi,

 Can someone suggest how to go about this please ?

Thanks
Mahesh

On Thu, Jun 30, 2016 at 11:26 AM, Mahesh Sivarama Pillai <srm...@gmail.com>
wrote:

> Hi All,
>
> Did someone backport *STARTTLS* feature from 3.0 beta to 2.3.2 ? We have
> 2.3.2 running in production and there is a requirement to support STARTTLS.
> Since 3.0 is in beta, the team is not comfortable in putting into
> production.
>
> If the porting is not done, can someone please guide on how to implement
> this in 2.3.2 ? I can give it a try.
>
> Thanks
> Mahesh
>


AW: URGENT HELP: Backport STARTTLS from 3.0 to 2.3.2

2016-07-04 Thread Bernd Waibel
Hello Mahesh,

i think there is no backport.

For STARTTLS there should be two sides:
- James acting as receiver
- James acting as sender

You have the option to use TLS in James, by configuring a 
"org.apache.avalon.cornerstone.blocks.sockets.TLSServerSocketFactory".
But this is for strict TLS binding, not a STARTTLS. But it may be worth to look 
at.

For the receiving side:
If you want to implement it in james, you need a handler for that.
Have a look at org.apache.james.smtpserver package. 
There are the handlers for the low-level protocols.

I think you need to extend or change one of the handler classes.
Then you need to register your own handler class, by 
- including the "james-smtphandlerchain.xml" into your config.xml
- change the class name inside the james-smtphandlerchain.xml.
- change the EhloCmdHandler.java, to announce the STARTTLS option 
(esmtpextensions.add("STARTTLS");)

The StartTLS is implemented in James3, have a look at:
org.apache.james.protocols.smtp.core.esmtp. StartTlsCmdHandler;

For the sending side:
You need to change or expand the RemoteDelivery Mailet.
In James3 this is done, have a look at.

Just theory.
I am not sure, if I would recommend to implement it. You need to test it, too.
Maybe you could use James 3 beta4, which is long released version, and is used 
by some servers.


Greetings
Bernd

-Ursprüngliche Nachricht-
Von: Mahesh Sivarama Pillai [mailto:srm...@gmail.com] 
Gesendet: Montag, 4. Juli 2016 04:31
An: James Users List <server-user@james.apache.org>
Betreff: Re: URGENT HELP: Backport STARTTLS from 3.0 to 2.3.2

Hi,

 Can someone suggest how to go about this please ?

Thanks
Mahesh

On Thu, Jun 30, 2016 at 11:26 AM, Mahesh Sivarama Pillai <srm...@gmail.com>
wrote:

> Hi All,
>
> Did someone backport *STARTTLS* feature from 3.0 beta to 2.3.2 ? We have
> 2.3.2 running in production and there is a requirement to support STARTTLS.
> Since 3.0 is in beta, the team is not comfortable in putting into
> production.
>
> If the porting is not done, can someone please guide on how to implement
> this in 2.3.2 ? I can give it a try.
>
> Thanks
> Mahesh
>


Re: URGENT HELP: Backport STARTTLS from 3.0 to 2.3.2

2016-07-03 Thread Mahesh Sivarama Pillai
Hi,

 Can someone suggest how to go about this please ?

Thanks
Mahesh

On Thu, Jun 30, 2016 at 11:26 AM, Mahesh Sivarama Pillai 
wrote:

> Hi All,
>
> Did someone backport *STARTTLS* feature from 3.0 beta to 2.3.2 ? We have
> 2.3.2 running in production and there is a requirement to support STARTTLS.
> Since 3.0 is in beta, the team is not comfortable in putting into
> production.
>
> If the porting is not done, can someone please guide on how to implement
> this in 2.3.2 ? I can give it a try.
>
> Thanks
> Mahesh
>


URGENT HELP: Backport STARTTLS from 3.0 to 2.3.2

2016-06-29 Thread Mahesh Sivarama Pillai
Hi All,

Did someone backport *STARTTLS* feature from 3.0 beta to 2.3.2 ? We have
2.3.2 running in production and there is a requirement to support STARTTLS.
Since 3.0 is in beta, the team is not comfortable in putting into
production.

If the porting is not done, can someone please guide on how to implement
this in 2.3.2 ? I can give it a try.

Thanks
Mahesh