[JAMES-39] James config file TLS support erroneous in 2.0a3

• Type: Bug
• Status: Closed
• Resolution: Fixed
• Component/s: James Core
• Environment: Operating System: Windows NT/2K; Platform: PC
• Bugzilla Id: 9628
• Assignee: Unassigned
• Reporter: Stephen Cuppett
• Created: 05/Jun/02 20:42
• Updated: 06/Jun/04 21:41
• Resolved: 06/Jun/04 21:41

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.