[jira] [Closed] (JAMES-304) secure remote delivery opportunistically or even allow make TLS mandatory

["Ioan Eugen Stan (Jira)" <se...@james.apache.org>]

     [ https://issues.apache.org/jira/browse/JAMES-304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ioan Eugen Stan closed JAMES-304.
---------------------------------
    Resolution: Abandoned

Please reopen if relevant. I'm on a cleaning spree.
This is for a very old release. It's no longer maintained by us.

> secure remote delivery opportunistically or even allow make TLS mandatory
> -------------------------------------------------------------------------
>
>                 Key: JAMES-304
>                 URL: https://issues.apache.org/jira/browse/JAMES-304
>             Project: James Server
>          Issue Type: Sub-task
>          Components: Remote Delivery
>    Affects Versions: 2.1.3
>         Environment: all - I use RH Linux 9
>            Reporter: Ralf Hauser
>            Assignee: Robert Burrell Donkin
>            Priority: Major
>             Fix For: 3.0.0
>
>
> It would be great to have james at least opportunistically attempt to secure its user's outgoing mails with STARTTLS.
> How would one do this?
> 1) first a delivery-host must be found that can do this:
>    --> see http://tlstest.sf.net
>    The ch/zhwin/tlstest/TLSTestAPI.java.canDomainTLS() can do this (in v1.2)
> 2) The real delivery still needs to be secured - unfortunately, so far, I only see a broken idea how to do this in http://www.portaljava.com/home/modules.php?name=Forums&file=viewtopic&p=20492
> anybody with better ideas (especially since there, they mess a lot with system-wide properties, so I am afraid that afterwards, the secure pop and smtp to MUA will no longer work)



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org