|
As written this throws an exception when using recent (e.g. 1.5. releases of Sun JRE, since the com.sun.net.ssl.internal.ssl.Provider() is subject to an access restriction. It should not be necessary to add this provider; since about Java 1.3 it should be pre-loaded by the stock security property settings.
I hacked out the addProvider() call and the mail goes through. Hi Mark,
My Java 1.6 installations have no problem with this. However, as you say the mail.ssl.enable code seems to be redundant. Am happy to remove it if you want? Thanks, Stuart Code updated, removed unrequired code and config:
# If you are connecting to a TLS/SSL protected email server, enable this setting, # and possibly extra settings below #mail.ssl.enable = true Just caught this needed to be added to Configuration documentation. Done.
|
||||||||||||||||||||||||||||||||||||||||||||||||||||
 |
|
Improvement
Closed
Minor
Configurable passing of Javamail parameter settings
Adds new options in dspace.cfg:
# If you are connecting to a TLS/SSL protected email server, enable this setting,
# and possibly extra settings below
#mail.ssl.enable = true
# Pass extra settings to the Java mail library. Comma separated, equals sign between
# the key and the value.
#mail.extraproperties = mail.smtp.socketFactory.port=465, \
# mail.smtp.socketFactory.class=javax.net.ssl.SSLSocketFactory, \
# mail.smtp.socketFactory.fallback=false