[jira] Closed: (JAMES-39) James config file TLS support erroneous in 2.0a3

[ji...@apache.org]

Message:

   The following issue has been closed.

---------------------------------------------------------------------
View the issue:
  http://issues.apache.org/jira/browse/JAMES-39

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: JAMES-39
    Summary: James config file TLS support erroneous in 2.0a3
       Type: Bug

     Status: Closed
 Resolution: FIXED

    Project: James
 Components: 
             James Core

   Assignee: 
   Reporter: Stephen Cuppett

    Created: Wed, 5 Jun 2002 1:42 PM
    Updated: Sun, 6 Jun 2004 2:41 PM
Environment: Operating System: Windows NT/2K
Platform: PC

Description:
In the default config.xml file that is packaged with James 2.0a3, the command 
on all servers is <useTLS>TRUE</useTLS>; however, this will not cause it to 
look for the "ssl" socket manager on NT 4.0 and perhaps other systems.  Only 
<useTLS>true</useTLS> will work.  Otherwise, it will continue to look 
for "plain" even when it is uncommented.

You can fix it by either defining your secure socket with the name "plain" or 
changing TRUE to all lowercase letters.


---------------------------------------------------------------------
JIRA INFORMATION:
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

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


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