[ http://issues.apache.org/jira/browse/JAMES-304?page=all ]
     
Stefano Bagnara resolved JAMES-304:
-----------------------------------

    Fix Version: 3.0
     Resolution: Fixed

In my understanding this has been solved by Javamail 1.3.2.
Can you update your javamail and check again?
Please report an update (reopen this issue, or a new one, if needed)

> secure remote delivery opportunistically or even allow make TLS mandatory
> -------------------------------------------------------------------------
>
>          Key: JAMES-304
>          URL: http://issues.apache.org/jira/browse/JAMES-304
>      Project: James
>         Type: Improvement
>   Components: Remote Delivery
>     Versions: 2.1.3
>  Environment: all - I use RH Linux 9
>     Reporter: Ralf Hauser
>      Fix For: 3.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 is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


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

Reply via email to