SMTP SSL StartTLS Auth

I need / would like have the CFMX 6.1 admin default
connection to our SMTP server use either of these connection
methods:
SMTP AUTH over SSL on port 465
OR
STARTTLS on ports 587 or 25
Is this possible with CFMX 6.1 ?
... any assistance would be appreciated....
John

jeiBean wrote:
> I need / would like have the CFMX 6.1 admin default
connection to our SMTP
> server use either of these connection methods:
>
> SMTP AUTH over SSL on port 465
>
> OR
>
> STARTTLS on ports 587 or 25
>
> Is this possible with CFMX 6.1 ?
SMTP AUTH over SSL on port 465 can be done if you set up a
stunnel
http://www.stunnel.org/) and
then you don't need changes to your code.
In all other cases you need to change code to use some
component.
Jochem
Jochem van Dieten
Adobe Community Expert for ColdFusion

Similar Messages

Email sending Problem:smtps---SSL---TLS??

Hi,
I Have a Problem bei Sending a email with Attachement from extranet, I have writting my Programm which will send my email Through TLS, with Thunderbird
I can sending there alle emails through TLS, I have taking the seem Properties :
emai Server Name, Protocol:smtp port:25 und througt TLS, so Now I will show you my Code und the compile Failure, I appreciate so much your Help, I don't find any Help here in Forum.
My Code:
public void sendAttachment(String ausgangsMailServer, String user, String password,String sender, String receiver, String filename) throws MessagingException{
          Properties properties = System.getProperties();
          properties.put("mail.transport.protocol","smtps");
          properties.put("mail.smtps.ssl", "true");
          properties.put("mail.smtps.starttls.enable","true");
          properties.put("mail.smtps.auth", "true");
          properties.put("mail.smtps.debug", "true");
          properties.put("mail.smtps.socketFactory.port", "25");
          properties.put("mail.smtps.socketFactory.class", "javax.net.ssl.SSLSocketFactory");
          properties.put("mail.smtps.socketFactory.fallback", "false");
SecurityManager security = System.getSecurityManager();
          Session session = Session.getInstance(properties, new MailAuthenticator());
          Transport transport = session.getTransport("smtps");
          transport.connect(ausgangsMailServer, user, password);
          Message message = getMessage(session, sender, receiver,filename);
          message.saveChanges();
          transport.sendMessage(message, message.getAllRecipients());
          transport.close();
     public Message getMessage(Session session, String sender, String receiver, String filename) throws MessagingException{
     Message message = new MimeMessage(session);
message.setSubject("attachment");
     message.setFrom(new InternetAddress(sender));
     message.addRecipient(Message.RecipientType.TO, new InternetAddress(receiver));
     Multipart multipart = new MimeMultipart();
     BodyPart bp = new MimeBodyPart();
     bp.setText("Attachment Mail");
     multipart.addBodyPart(bp);
     bp = new MimeBodyPart();
     DataSource source = new FileDataSource(filename);
     bp.setDataHandler(new DataHandler(source));
     bp.setFileName(filename);
     multipart.addBodyPart(bp);
     message.setContent(multipart);
     return message;
     public class MailAuthenticator extends Authenticator{
          public MailAuthenticator(){
          public PasswordAuthentication getPasswordAuthentication(){
               return new PasswordAuthentication("radouane","mypaaword");
And I call the methode sendAttachment in a EJB Methode I Use Jboss als Server in my web application.
This is now my failure:
05:07:21,382 INFO [STDOUT] javax.mail.NoSuchProviderException: smtps
05:07:21,382 INFO [STDOUT] at javax.mail.Session.getService(Session.java:76
4)
05:07:21,382 INFO [STDOUT] at javax.mail.Session.getTransport(Session.java:
689)
05:07:21,382 INFO [STDOUT] at javax.mail.Session.getTransport(Session.java:
632)
05:07:21,382 INFO [STDOUT] at javax.mail.Session.getTransport(Session.java:
612)
I have Using a smtps protocol , by using smtp I Had this Failure:
14:15:11,164 INFO [STDOUT] javax.mail.MessagingException: Exception reading res
ponse;
nested exception is:
javax.net.ssl.SSLException: Unrecognized SSL message, plaintext connecti
on?
14:15:11,164 INFO [STDOUT] at com.sun.mail.smtp.SMTPTransport.readServerRes
ponse(SMTPTransport.java:1090)
14:15:11,164 INFO [STDOUT] at com.sun.mail.smtp.SMTPTransport.openServer(SM
TPTransport.java:986)
14:15:11,164 INFO [STDOUT] at com.sun.mail.smtp.SMTPTransport.protocolConne
ct(SMTPTransport.java:197)
14:15:11,164 INFO [STDOUT] at javax.mail.Service.connect(Service.java:233)
14:15:11,164 INFO [STDOUT] at javax.mail.Service.connect(Service.java:134)
For your help I say Thanks.
Radouane

Hi,
I want just writtefor you my javamail debug Infomationen by J2SE Application and bei J2EE application. By j2se was that sending successful, by j2ee application is a problem by TSL.
Hier Debug for j2se application:
DEBUG: setDebug: JavaMail version 1.4ea
DEBUG: getProvider() returning javax.mail.Provider[TRANSPORT,smtp,com.sun.mail.smtp.SMTPTransport,Sun Microsys
tems, Inc]
DEBUG SMTP: useEhlo true, useAuth true
DEBUG SMTP: useEhlo true, useAuth true
DEBUG SMTP: trying to connect to host "mail.cs.tu-berlin.de", port 25, isSSL false
220 mailhost.cs.tu-berlin.de ESMTP Postfix
DEBUG SMTP: connected to host "mail.cs.tu-berlin.de", port: 25
EHLO meknes
250-mailhost.cs.tu-berlin.de
250-PIPELINING
250-SIZE
250-VRFY
250-ETRN
250-STARTTLS
250-ENHANCEDSTATUSCODES
250 8BITMIME
DEBUG SMTP: Found extension "PIPELINING", arg ""
DEBUG SMTP: Found extension "SIZE", arg ""
DEBUG SMTP: Found extension "VRFY", arg ""
DEBUG SMTP: Found extension "ETRN", arg ""
DEBUG SMTP: Found extension "STARTTLS", arg ""
DEBUG SMTP: Found extension "ENHANCEDSTATUSCODES", arg ""
DEBUG SMTP: Found extension "8BITMIME", arg ""
STARTTLS
220 2.0.0 Ready to start TLS
EHLO meknes
250-mailhost.cs.tu-berlin.de
250-PIPELINING
250-SIZE
250-VRFY
250-ETRN
250-AUTH PLAIN LOGIN
250-ENHANCEDSTATUSCODES
250 8BITMIME
DEBUG SMTP: Found extension "PIPELINING", arg ""
DEBUG SMTP: Found extension "SIZE", arg ""
DEBUG SMTP: Found extension "VRFY", arg ""
DEBUG SMTP: Found extension "ETRN", arg ""
DEBUG SMTP: Found extension "AUTH", arg "PLAIN LOGIN"
DEBUG SMTP: Found extension "ENHANCEDSTATUSCODES", arg ""
DEBUG SMTP: Found extension "8BITMIME", arg ""
DEBUG SMTP: Attempt to authenticate
AUTH LOGIN
334 oioohbzfavsa7
mnhgvas8799800U=
30987hasabhsasa6
Y2hiijsasisas=
235 2.0.0 Authentication successful
DEBUG SMTP: use8bit false
MAIL FROM:<[email protected]>
250 2.1.0 Ok
RCPT TO:<[email protected]>
250 2.1.5 Ok
DEBUG SMTP: Verified Addresses
DEBUG SMTP: [email protected]
DATA
354 End data with <CR><LF>.<CR><LF>
From: [email protected]
To: [email protected]
Message-ID: <9971081.01168741860633.JavaMail.radouane@meknes>
Subject: attachment
MIME-Version: 1.0
Content-Type: multipart/mixed;
boundary="----=_Part_0_25199001.1168741860423"
------=_Part_0_25199001.1168741860423
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Attachment Mail
------=_Part_0_25199001.1168741860423
Content-Type: application/octet-stream; name=filename
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename=filename
Now by J2ee application---I use jboss:
2007-01-14 03:27:28,769 INFO [STDOUT] DEBUG: getProvider() returning javax.mail.Provider[TRANSPORT,smtp,com.sun.mail.smtp.SMTPTransport,Sun Microsystems, Inc]
2007-01-14 03:27:28,769 INFO [STDOUT] DEBUG SMTP: useEhlo true, useAuth true
2007-01-14 03:27:28,769 INFO [STDOUT] DEBUG SMTP: trying to connect to host "mail.cs.tu-berlin.de", port 25
2007-01-14 03:27:28,909 INFO [STDOUT] 220 mailhost.cs.tu-berlin.de ESMTP Postfix
2007-01-14 03:27:28,909 INFO [STDOUT] DEBUG SMTP: connected to host "mail.cs.tu-berlin.de", port: 25
2007-01-14 03:27:28,909 INFO [STDOUT] EHLO meknes
2007-01-14 03:27:28,979 INFO [STDOUT] 250-mailhost.cs.tu-berlin.de
250-PIPELINING
250-SIZE
250-VRFY
250-ETRN
250-STARTTLS
250-ENHANCEDSTATUSCODES
250 8BITMIME
2007-01-14 03:27:28,979 INFO [STDOUT] DEBUG SMTP: Found extension "PIPELINING", arg ""
2007-01-14 03:27:28,979 INFO [STDOUT] DEBUG SMTP: Found extension "SIZE", arg ""
2007-01-14 03:27:28,979 INFO [STDOUT] DEBUG SMTP: Found extension "VRFY", arg ""
2007-01-14 03:27:28,979 INFO [STDOUT] DEBUG SMTP: Found extension "ETRN", arg ""
2007-01-14 03:27:28,979 INFO [STDOUT] DEBUG SMTP: Found extension "STARTTLS", arg ""
2007-01-14 03:27:28,979 INFO [STDOUT] DEBUG SMTP: Found extension "ENHANCEDSTATUSCODES", arg ""
2007-01-14 03:27:28,979 INFO [STDOUT] DEBUG SMTP: Found extension "8BITMIME", arg ""
2007-01-14 03:27:28,979 INFO [STDOUT] DEBUG SMTP: use8bit false
2007-01-14 03:27:28,979 INFO [STDOUT] MAIL FROM:<[email protected]>
2007-01-14 03:27:29,049 INFO [STDOUT] 250 2.1.0 Ok
2007-01-14 03:27:29,049 INFO [STDOUT] RCPT TO:<[email protected]>
2007-01-14 03:27:29,159 INFO [STDOUT] 554 5.7.1 <[email protected]>: Recipient address rejected: Access denied
2007-01-14 03:27:29,159 INFO [STDOUT] DEBUG SMTP: Invalid Addresses
2007-01-14 03:27:29,159 INFO [STDOUT] DEBUG SMTP: [email protected]
2007-01-14 03:27:29,159 INFO [STDOUT] DEBUG SMTP: Sending failed because of invalid destination addresses
2007-01-14 03:27:29,159 INFO [STDOUT] RSET
2007-01-14 03:27:29,229 INFO [STDOUT] 250 2.0.0 Ok
2007-01-14 03:27:29,229 INFO [STDOUT] QUIT
2007-01-14 03:27:29,229 INFO [STDOUT] Error Sending:
2007-01-14 03:27:29,229 INFO [STDOUT] Sending failed;
nested exception is:
     class javax.mail.SendFailedException: Invalid Addresses;
nested exception is:
     class javax.mail.SendFailedException: 554 5.7.1 <[email protected]>: Recipient address rejected: Access denied
2007-01-14 03:27:29,229 INFO [STDOUT] java.lang.NullPointerException
can someone tell me, where is my problem by j2ee application, it's a ejb class -using jboss-.
Thanks ,
Radouane
Message was edited by:
radouane.marjani

An error occurred sending mail: The mail server sent an incorrect greeting: * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE STARTTLS AUTH

Hi, I am receiving emails but whenever I try and send I get the following message:
unable to send emails An error occurred sending mail: The mail server sent an incorrect greeting: * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE STARTTLS AUTH=PLAIN AUTH=LOGIN] Dovecot ready..

What are your settings in Tools(or AppMenu/Options)/Account Settings/Outgoing Server (SMTP)? The error message suggests you must have STARTTLS connection security and normal password authentication:
https://getsatisfaction.com/mozilla_messaging/topics/mail_preferences-t1xeq

SSL web auth equals encyrption?

If you use a self signed cert/SSL web auth page that uses LDAP usernames and passwords is the traffic there on considered encrypted or is it only my user name and password that gets encrypted ?

If there is no layer 2 encryption going on, then only the authentication piece is encrypted by SSL. After the user is authenticated, there's no more encrypted communication with the AP/controller. You'd need layer 2 encryption (AES, TKIP, WEP), VPN, or possibly some sort of SSL proxy for additional encryption.

SMTP with STARTTLS and/or Authentication

Hello,
I'm having trouble with an smtp sender.
I tried both setting authentication and/or starttls, but:
- authentication seem not to be issued if normal smtp is selected, even though I see the call on my Authenticator: the smtp server complains about no authentication.
- starttls seem not to be issued, as the SSL packages complains about a non ssl stream:
DEBUG: getProvider() returning javax.mail.Provider[TRANSPORT,smtp,com.sun.mail.smtp.SMTPTransport,Sun Microsystems, Inc]
DEBUG SMTP: useEhlo true, useAuth true
getPasswordAuthentication: ******** / ********
DEBUG SMTP: useEhlo true, useAuth true
DEBUG SMTP: trying to connect to host "sendm.pec.sonicle.com", port 25, isSSL false
DEBUG SMTP: exception reading response: javax.net.ssl.SSLException: Unrecognized SSL message, plaintext connection?
Her isSSL is false, because I want to use starttls instead of smtps, and the ssl stack complains...as if starttls was not issued.
Session debugging never show commands about starttls nor authentication.
As you can see from the code below, I need a separate Session with its own properties, because I may have more than one relay class running in the same VM, working with different smtp servers and different options.
Notice also that I run a Transport manually, call connect with no arguments, as they will all be found in properties and from the Authenticator.
The class is to be setup its public properties just after instantiation, then call initialize() to setup its session instance.
Then you can call its createMessage(InputStream data) to create a msg from, e.g., an eml file.
Or you can create the MimeMessage yourself, but beware to use the same session as the Relay on creation.
Finally run sendMessage(MimeMessage msg) to send it.
Where is my error?
Here is my code:
import java.io.InputStream;
import java.util.*;
import javax.mail.*;
import javax.mail.internet.*;
* @author gbulfon
public class Relay extends Authenticator {
public String sender;
public String host;
public int port=25;
public String protocol="smtp";
public boolean ssl=false;
public String username;
public String password;
Properties props;
Session session;
public void initialize() {
System.out.println("relay "+host+" uses "+protocol);
props=(Properties)System.getProperties().clone();
props.setProperty("mail."+protocol+".host", host);
props.setProperty("mail."+protocol+".port", ""+port);
if (ssl && protocol.equals("smtp")) {
props.put("mail.smtp.starttls.enable","true");
props.put("mail.smtp.socketFactory.port", port);
props.put("mail.smtp.socketFactory.class", "javax.net.ssl.SSLSocketFactory");
props.put("mail.smtp.socketFactory.fallback", "false");
if (username!=null) {
System.out.println("relay "+host+" is authenticated as "+username);
props.setProperty("mail."+protocol+".auth", "true");
session=javax.mail.Session.getInstance(props,this);
session.setDebug(true);
public Session getSession() {
return session;
@Override
protected PasswordAuthentication getPasswordAuthentication() {
System.out.println("getPasswordAuthentication: "+username+" / "+password);
return new PasswordAuthentication(username,password);
public void sendMessage(MimeMessage msg) throws MessagingException {
Transport transport=session.getTransport(protocol);
transport.connect();
transport.sendMessage(msg, msg.getAllRecipients());
transport.close();
public MimeMessage createMessage(InputStream data) throws AddressException, MessagingException {
MimeMessage msg=new MimeMessage(session, data);
return msg;
}

Thanx so much! And sorry for the CODE.......
Anyway I just discovered minutes ago that taking out three lines was going great:
if (ssl && protocol.equals("smtp")) {
            props.put("mail.smtp.starttls.enable","true");
            //props.put("mail.smtp.socketFactory.port", port);
            //props.put("mail.smtp.socketFactory.class", "javax.net.ssl.SSLSocketFactory");
            //props.put("mail.smtp.socketFactory.fallback", "false");
}just commented out those 3 lines, now it works ;)))

SMTP SSL - Don't know if it's working properly or not (newbie)

Mail is currently working. I can send and receive with no problems at all.
In Mail>Advanced>Security I have these settings: IMAP/POP "Require" for SSL and SMTP to "USE".
But, if I change SMTP to "Require", addresses outside my domain cannot send to me.
User receives "Delivery Notification Failed", Diagnostic code: smtp;530 5.7.0 Must issue a STARTTLS command first.
Addresses on my domain, however, can send with no problem.
I get these messages in IMAP>Log:
TLS server engine: cannot load CA data
and:
starttls: TLSv1 with cipher AES128-SHA (128/128 bits reused) no authentication
I don't know what to make of this or how to fix.

But, if I change SMTP to "Require", addresses outside my domain cannot send to me.
Sure. You can't expect every other mail server to support SSL. Those that don't (probably the majority) won't be able to send mail to your domain since they can't initiate an SSL session.
You should either have SSL set to 'USE' and trust that your clients are setup correctly, or use a different port for your clients and leave the public port set to 'Use'.
TLS server engine: cannot load CA data
This is a separate, unrelated issue. It isn't clear from your post whether this happens when the server starts, when specific clients connect, or when any client connects. Can you post more of the log?

Coldfusion 11 java/jre ssl mutual auth api calls. Help with coldfusion/java logs.

Hello,
I am here because I have exhausted my Coldfusion/Java ssl keystore certs trouble shooting abilities. Here is the issue. I am developing a Coldfusion 11 application that must make api calls to Chase payconnexion SOAP services. I am using the coldfusion cfhttp tags to do this, which is using the java jre 1.7.x to accomplish this. The problem, I am getting generic 500 internal server errors from Chase.   They claim that I am not sending a cert during the ssl exchange.    What I have done is:
- put our wildcard cert/key pair in the coldfusion keystore
- put our root and chain in the keystore
- put the chase server cert in the keystore
- converted the key/crt files to .pfx and make the calls
to chase with those, something like:
<cfset objSecurity = createObject("java", "java.security.Security") />
<cfset storeProvider = objSecurity.getProvider("JsafeJCE")/>
<cfset Application.sslfix = true />
<cfhttp url="#chase_api_server#/"
          result="http_response"
        method="post"
        port="1401" charset="utf-8"
        clientCert = "#cert_path#/#cert_file1#"
        clientCertPassword = "#cert_password#">
        <cfhttpparam type="header" name="SOAPAction" value="updateUserProfileRequest"/>
    <cfhttpparam type="header" name="Host" value="ws.payconnexion.com" />
    <cfhttpparam type="xml" value="#trim(my_xml)#"/>
    </cfhttp>
Here is what I see in the Cf logs, can anyone help me interpret what
is happening ??
Thanks,
Bob
=============================================================
found key for : 1
chain [0] = [
Version: V3
Subject: CN=*.payments.austintexas.gov, O=City of Austin, L=Austin, ST=Texas, C=US
Signature Algorithm: SHA1withRSA, OID = 1.2.840.113549.1.1.5
Key: Sun RSA public key, 2048 bits
modulus: <snip>
Validity: [From: Mon Aug 11 12:39:37 CDT 2014,
               To: Thu Sep 01 18:34:24 CDT 2016]
Issuer: CN=Entrust Certification Authority - L1C, OU="(c) 2009 Entrust, Inc.", OU=www.entrust.net/rpa is incorporated by reference, O="Entrust, Inc.", C=US
SerialNumber: [<snip>7]
Certificate Extensions: 9
[1]: ObjectId: 1.3.6.1.5.5.7.1.1 Criticality=false
AuthorityInfoAccess [
   accessMethod: ocsp
   accessLocation: URIName: http://ocsp.entrust.net
   accessMethod: caIssuers
   accessLocation: URIName: http://aia.entrust.net/2048-l1c.cer
[2]: ObjectId: 2.5.29.35 Criticality=false
AuthorityKeyIdentifier [
KeyIdentifier [
<snip>]
[3]: ObjectId: 2.5.29.19 Criticality=false
BasicConstraints:[
CA:false
PathLen: undefined
[4]: ObjectId: 2.5.29.31 Criticality=false
CRLDistributionPoints [
[DistributionPoint:
     [URIName: http://crl.entrust.net/level1c.crl]
[5]: ObjectId: 2.5.29.32 Criticality=false
CertificatePolicies [
[CertificatePolicyId: [1.2.840.113533.7.75.2]
[PolicyQualifierInfo: [
qualifierID: 1.3.6.1.5.5.7.2.1
qualifier: <snip>
[CertificatePolicyId: [2.23.140.1.2.2]
[6]: ObjectId: 2.5.29.37 Criticality=false
ExtendedKeyUsages [
serverAuth
clientAuth
[7]: ObjectId: 2.5.29.15 Criticality=false
KeyUsage [
DigitalSignature
Key_Encipherment
[8]: ObjectId: 2.5.29.17 Criticality=false
SubjectAlternativeName [
DNSName: *.payments.austintexas.gov
DNSName: payments.austintexas.gov
[9]: ObjectId: 2.5.29.14 Criticality=false
SubjectKeyIdentifier [
KeyIdentifier [
<snip>]
Algorithm: [SHA1withRSA]
Signature:
<snip>
chain [1] = [
Version: V3
Subject: CN=Entrust Certification Authority - L1C, OU="(c) 2009 Entrust, Inc.", OU=www.entrust.net/rpa is incorporated by reference, O="Entrust, Inc.", C=US
Signature Algorithm: SHA1withRSA, OID = 1.2.840.113549.1.1.5
Key: Sun RSA public key, 2048 bits
modulus: <snip>
public exponent: 65537
Validity: [From: Fri Nov 11 09:40:40 CST 2011,
               To: Thu Nov 11 20:51:17 CST 2021]
Issuer: CN=Entrust.net Certification Authority (2048), OU=(c) 1999 Entrust.net Limited, OU=www.entrust.net/CPS_2048 incorp. by ref. (limits liab.), O=Entrust.net
SerialNumber: [    <snip>]
Certificate Extensions: 7
[1]: ObjectId: 1.3.6.1.5.5.7.1.1 Criticality=false
AuthorityInfoAccess [
   accessMethod: ocsp
   accessLocation: URIName: http://ocsp.entrust.net
[2]: ObjectId: 2.5.29.35 Criticality=false
AuthorityKeyIdentifier [
KeyIdentifier [
<snip>]
[3]: ObjectId: 2.5.29.19 Criticality=true
BasicConstraints:[
CA:true
PathLen:0
[4]: ObjectId: 2.5.29.31 Criticality=false
CRLDistributionPoints [
[DistributionPoint:
     [URIName: http://crl.entrust.net/2048ca.crl]
[5]: ObjectId: 2.5.29.32 Criticality=false
CertificatePolicies [
[CertificatePolicyId: [2.5.29.32.0]
[PolicyQualifierInfo: [
qualifierID: 1.3.6.1.5.5.7.2.1
qualifier: <snip>
[6]: ObjectId: 2.5.29.15 Criticality=true
KeyUsage [
Key_CertSign
Crl_Sign
[7]: ObjectId: 2.5.29.14 Criticality=false
SubjectKeyIdentifier [
KeyIdentifier [
<snip>]
Algorithm: [SHA1withRSA]
Signature:
<snip>
chain [2] = [
Version: V3
Subject: CN=Entrust.net Certification Authority (2048), OU=(c) 1999 Entrust.net Limited, OU=www.entrust.net/CPS_2048 incorp. by ref. (limits liab.), O=Entrust.net
Signature Algorithm: SHA1withRSA, OID = 1.2.840.113549.1.1.5
Key: Sun RSA public key, 2048 bits
modulus: <snip>public exponent: 65537
Validity: [From: Fri Dec 24 11:50:51 CST 1999,
               To: Tue Jul 24 09:15:12 CDT 2029]
Issuer: CN=Entrust.net Certification Authority (2048), OU=(c) 1999 Entrust.net Limited, OU=www.entrust.net/CPS_2048 incorp. by ref. (limits liab.), O=Entrust.net
SerialNumber: [<snip>]
Certificate Extensions: 3
[1]: ObjectId: 2.5.29.19 Criticality=true
BasicConstraints:[
CA:true
PathLen:2147483647
[2]: ObjectId: 2.5.29.15 Criticality=true
KeyUsage [
Key_CertSign
Crl_Sign
[3]: ObjectId: 2.5.29.14 Criticality=false
SubjectKeyIdentifier [
KeyIdentifier [
<snip>]
Algorithm: [SHA1withRSA]
Signature:
<snip>
trustStore is: /opt/coldfusion11/jre/lib/security/cacerts
trustStore type is : jks
trustStore provider is :
init truststore
adding as trusted cert:
<snip 85 certs>
trigger seeding of SecureRandom
done seeding SecureRandom
Jan 23, 2015 13:15:37 PM Information [ajp-bio-8014-exec-7] - Starting HTTP request {URL='https://ws.payconnexion.com:1401/pconWS/9_5/', method='post'}
Ignoring unsupported cipher suite: TLS_DHE_DSS_WITH_AES_128_CBC_SHA256
Ignoring unsupported cipher suite: TLS_DHE_DSS_WITH_AES_256_CBC_SHA256
Ignoring unsupported cipher suite: TLS_DHE_RSA_WITH_AES_128_CBC_SHA256
Ignoring unsupported cipher suite: TLS_ECDH_RSA_WITH_AES_128_CBC_SHA256
Ignoring unsupported cipher suite: TLS_DHE_RSA_WITH_AES_256_CBC_SHA256
Ignoring unsupported cipher suite: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384
Ignoring unsupported cipher suite: TLS_ECDH_ECDSA_WITH_AES_256_CBC_SHA384
Ignoring unsupported cipher suite: TLS_RSA_WITH_AES_256_CBC_SHA256
Ignoring unsupported cipher suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256
Ignoring unsupported cipher suite: TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384
Ignoring unsupported cipher suite: TLS_ECDH_RSA_WITH_AES_256_CBC_SHA384
Ignoring unsupported cipher suite: TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256
Ignoring unsupported cipher suite: TLS_ECDH_ECDSA_WITH_AES_128_CBC_SHA256
Ignoring unsupported cipher suite: TLS_RSA_WITH_AES_128_CBC_SHA256
Allow unsafe renegotiation: true
Allow legacy hello messages: true
Is initial handshake: true
Is secure renegotiation: false
%% No cached client session
*** ClientHello, TLSv1
RandomCookie: GMT: 1405197529 bytes = { 191, 115, 95, 85, 79, 234, 145, 176, 62, 70, 36, 102, 168, 15, 127, 174, 88, 118, 4, 177, 226, 5, 254, 55, 108, 203, 80, 80 }
Session ID: {}
Cipher Suites: [TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA, TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA, TLS_RSA_WITH_AES_256_CBC_SHA, TLS_ECDH_ECDSA_WITH_AES_256_CBC_SHA, TLS_ECDH_RSA_WITH_AES_256_CBC_SHA, TLS_DHE_RSA_WITH_AES_256_CBC_SHA, TLS_DHE_DSS_WITH_AES_256_CBC_SHA, TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA, TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA, TLS_RSA_WITH_AES_128_CBC_SHA, TLS_ECDH_ECDSA_WITH_AES_128_CBC_SHA, TLS_ECDH_RSA_WITH_AES_128_CBC_SHA, TLS_DHE_RSA_WITH_AES_128_CBC_SHA, TLS_DHE_DSS_WITH_AES_128_CBC_SHA, TLS_ECDHE_ECDSA_WITH_RC4_128_SHA, TLS_ECDHE_RSA_WITH_RC4_128_SHA, SSL_RSA_WITH_RC4_128_SHA, TLS_ECDH_ECDSA_WITH_RC4_128_SHA, TLS_ECDH_RSA_WITH_RC4_128_SHA, TLS_ECDHE_ECDSA_WITH_3DES_EDE_CBC_SHA, TLS_ECDHE_RSA_WITH_3DES_EDE_CBC_SHA, SSL_RSA_WITH_3DES_EDE_CBC_SHA, TLS_ECDH_ECDSA_WITH_3DES_EDE_CBC_SHA, TLS_ECDH_RSA_WITH_3DES_EDE_CBC_SHA, SSL_DHE_RSA_WITH_3DES_EDE_CBC_SHA, SSL_DHE_DSS_WITH_3DES_EDE_CBC_SHA, SSL_RSA_WITH_RC4_128_MD5, TLS_EMPTY_RENEGOTIATION_INFO_SCSV]
Compression Methods: { 0 }
Extension elliptic_curves, curve names: {secp256r1, sect163k1, sect163r2, secp192r1, secp224r1, sect233k1, sect233r1, sect283k1, sect283r1, secp384r1, sect409k1, sect409r1, secp521r1, sect571k1, sect571r1, secp160k1, secp160r1, secp160r2, sect163r1, secp192k1, sect193r1, sect193r2, secp224k1, sect239k1, secp256k1}
Extension ec_point_formats, formats: [uncompressed]
Extension server_name, server_name: [host_name: ws.payconnexion.com]
ajp-bio-8014-exec-7, WRITE: TLSv1 Handshake, length = 191
ajp-bio-8014-exec-7, READ: TLSv1 Handshake, length = 81
*** ServerHello, TLSv1
RandomCookie: <snip>
Cipher Suite: TLS_RSA_WITH_AES_256_CBC_SHA
Compression Method: 0
Extension renegotiation_info, renegotiated_connection: <empty>
%% Initialized: [Session-5, TLS_RSA_WITH_AES_256_CBC_SHA]
** TLS_RSA_WITH_AES_256_CBC_SHA
ajp-bio-8014-exec-7, READ: TLSv1 Handshake, length = 4183
*** Certificate chain
chain [0] = [
Version: V3
Subject: CN=ws.payconnexion.com, OU=PayConnexion, O=JPMorgan Chase, L=New York, ST=New York, C=US
Signature Algorithm: SHA1withRSA, OID = 1.2.840.113549.1.1.5
Key: Sun RSA public key, 2048 bits
modulus: <snip>
public exponent: 65537
Validity: [From: Sun Apr 20 19:00:00 CDT 2014,
               To: Tue Jun 02 18:59:59 CDT 2015]
Issuer: CN=VeriSign Class 3 International Server CA - G3, OU=Terms of use at https://www.verisign.com/rpa (c)10, OU=VeriSign Trust Network, O="VeriSign, Inc.", C=US
SerialNumber: [   <snip>]
Certificate Extensions: 8
[1]: ObjectId: 1.3.6.1.5.5.7.1.1 Criticality=false
AuthorityInfoAccess [
   accessMethod: ocsp
   accessLocation: URIName: http://se.symcd.com
   accessMethod: caIssuers
   accessLocation: URIName: http://se.symcb.com/se.crt
[2]: ObjectId: 2.5.29.35 Criticality=false
AuthorityKeyIdentifier [
KeyIdentifier [
<snip>]
[3]: ObjectId: 2.5.29.19 Criticality=false
BasicConstraints:[
CA:false
PathLen: undefined
[4]: ObjectId: 2.5.29.31 Criticality=false
CRLDistributionPoints [
[DistributionPoint:
     [URIName: http://se.symcb.com/se.crl]
[5]: ObjectId: 2.5.29.32 Criticality=false
CertificatePolicies [
[CertificatePolicyId: [2.16.840.1.113733.1.7.54]
[PolicyQualifierInfo: [
qualifierID: 1.3.6.1.5.5.7.2.1
qualifier: <snip>
], PolicyQualifierInfo: [
qualifierID: 1.3.6.1.5.5.7.2.2
qualifier: <snip>
[6]: ObjectId: 2.5.29.37 Criticality=false
ExtendedKeyUsages [
serverAuth
clientAuth
2.16.840.1.113730.4.1
[7]: ObjectId: 2.5.29.15 Criticality=true
KeyUsage [
DigitalSignature
Key_Encipherment
[8]: ObjectId: 2.5.29.17 Criticality=false
SubjectAlternativeName [
DNSName: ws.payconnexion.com
Algorithm: [SHA1withRSA]
Signature:
<snip>
chain [1] = [
Version: V3
Subject: CN=VeriSign Class 3 International Server CA - G3, OU=Terms of use at https://www.verisign.com/rpa (c)10, OU=VeriSign Trust Network, O="VeriSign, Inc.", C=US
Signature Algorithm: SHA1withRSA, OID = 1.2.840.113549.1.1.5
Key: Sun RSA public key, 2048 bits
modulus: <snip>
public exponent: 65537
Validity: [From: Sun Feb 07 18:00:00 CST 2010,
               To: Fri Feb 07 17:59:59 CST 2020]
Issuer: CN=VeriSign Class 3 Public Primary Certification Authority - G5, OU="(c) 2006 VeriSign, Inc. - For authorized use only", OU=VeriSign Trust Network, O="VeriSign, Inc.", C=US
SerialNumber: [    <snip>]
Certificate Extensions: 10
[1]: ObjectId: 1.3.6.1.5.5.7.1.12 Criticality=false
Extension unknown: DER encoded OCTET string =
<snip>
[2]: ObjectId: 1.3.6.1.5.5.7.1.1 Criticality=false
AuthorityInfoAccess [
   accessMethod: ocsp
   accessLocation: URIName: http://ocsp.verisign.com
[3]: ObjectId: 2.5.29.35 Criticality=false
AuthorityKeyIdentifier [
KeyIdentifier [
<snip>]
[4]: ObjectId: 2.5.29.19 Criticality=true
BasicConstraints:[
CA:true
PathLen:0
[5]: ObjectId: 2.5.29.31 Criticality=false
CRLDistributionPoints [
[DistributionPoint:
     [URIName: http://crl.verisign.com/pca3-g5.crl]
[6]: ObjectId: 2.5.29.32 Criticality=false
CertificatePolicies [
[CertificatePolicyId: [2.16.840.1.113733.1.7.23.3]
[PolicyQualifierInfo: [
qualifierID: 1.3.6.1.5.5.7.2.1
qualifier: <snip>
], PolicyQualifierInfo: [
qualifierID: 1.3.6.1.5.5.7.2.2
qualifier: <snip>
[7]: ObjectId: 2.5.29.37 Criticality=false
ExtendedKeyUsages [
serverAuth
clientAuth
2.16.840.1.113730.4.1
2.16.840.1.113733.1.8.1
[8]: ObjectId: 2.5.29.15 Criticality=true
KeyUsage [
Key_CertSign
Crl_Sign
[9]: ObjectId: 2.5.29.17 Criticality=false
SubjectAlternativeName [
CN=VeriSignMPKI-2-7
[10]: ObjectId: 2.5.29.14 Criticality=false
SubjectKeyIdentifier [
KeyIdentifier [
<snip>]
Algorithm: [SHA1withRSA]
Signature:
<snip>
chain [2] = [
Version: V3
Subject: CN=VeriSign Class 3 Public Primary Certification Authority - G5, OU="(c) 2006 VeriSign, Inc. - For authorized use only", OU=VeriSign Trust Network, O="VeriSign, Inc.", C=US
Signature Algorithm: SHA1withRSA, OID = 1.2.840.113549.1.1.5
Key: Sun RSA public key, 2048 bits
modulus: <snip>
public exponent: 65537
Validity: [From: Tue Nov 07 18:00:00 CST 2006,
               To: Sun Nov 07 17:59:59 CST 2021]
Issuer: OU=Class 3 Public Primary Certification Authority, O="VeriSign, Inc.", C=US
SerialNumber: [<snip>]
Certificate Extensions: 8
[1]: ObjectId: 1.3.6.1.5.5.7.1.12 Criticality=false
Extension unknown: DER encoded OCTET string =
<snip>
[2]: ObjectId: 1.3.6.1.5.5.7.1.1 Criticality=false
AuthorityInfoAccess [
   accessMethod: ocsp
   accessLocation: URIName: http://ocsp.verisign.com
[3]: ObjectId: 2.5.29.19 Criticality=true
BasicConstraints:[
CA:true
PathLen:2147483647
[4]: ObjectId: 2.5.29.31 Criticality=false
CRLDistributionPoints [
[DistributionPoint:
     [URIName: http://crl.verisign.com/pca3.crl]
[5]: ObjectId: 2.5.29.32 Criticality=false
CertificatePolicies [
[CertificatePolicyId: [2.5.29.32.0]
[PolicyQualifierInfo: [
qualifierID: 1.3.6.1.5.5.7.2.1
qualifier: <snip>
[6]: ObjectId: 2.5.29.37 Criticality=false
ExtendedKeyUsages [
serverAuth
clientAuth
codeSigning
2.16.840.1.113730.4.1
2.16.840.1.113733.1.8.1
[7]: ObjectId: 2.5.29.15 Criticality=true
KeyUsage [
Key_CertSign
Crl_Sign
[8]: ObjectId: 2.5.29.14 Criticality=false
SubjectKeyIdentifier [
KeyIdentifier [
<snip>]
Algorithm: [SHA1withRSA]
Signature:
<snip>
Found trusted certificate:
Version: V3
Subject: CN=ws.payconnexion.com, OU=PayConnexion, O=JPMorgan Chase, L=New York, ST=New York, C=US
Signature Algorithm: SHA1withRSA, OID = 1.2.840.113549.1.1.5
Key: Sun RSA public key, 2048 bits
modulus:   public exponent: 65537
Validity: [From: Sun Apr 20 19:00:00 CDT 2014,
               To: Tue Jun 02 18:59:59 CDT 2015]
Issuer: CN=VeriSign Class 3 International Server CA - G3, OU=Terms of use at https://www.verisign.com/rpa (c)10, OU=VeriSign Trust Network, O="VeriSign, Inc.", C=US
SerialNumber: [ <snip>]
Certificate Extensions: 8
[1]: ObjectId: 1.3.6.1.5.5.7.1.1 Criticality=false
AuthorityInfoAccess [
   accessMethod: ocsp
   accessLocation: URIName: http://se.symcd.com
   accessMethod: caIssuers
   accessLocation: URIName: http://se.symcb.com/se.crt
[2]: ObjectId: 2.5.29.35 Criticality=false
AuthorityKeyIdentifier [
KeyIdentifier [
<snip>]
[3]: ObjectId: 2.5.29.19 Criticality=false
BasicConstraints:[
CA:false
PathLen: undefined
[4]: ObjectId: 2.5.29.31 Criticality=false
CRLDistributionPoints [
[DistributionPoint:
     [URIName: http://se.symcb.com/se.crl]
[5]: ObjectId: 2.5.29.32 Criticality=false
CertificatePolicies [
[CertificatePolicyId: [2.16.840.1.113733.1.7.54]
[PolicyQualifierInfo: [
qualifierID: 1.3.6.1.5.5.7.2.1
qualifier: <snip>
], PolicyQualifierInfo: [
qualifierID: 1.3.6.1.5.5.7.2.2
qualifier: <snip>
[6]: ObjectId: 2.5.29.37 Criticality=false
ExtendedKeyUsages [
serverAuth
clientAuth
2.16.840.1.113730.4.1
[7]: ObjectId: 2.5.29.15 Criticality=true
KeyUsage [
DigitalSignature
Key_Encipherment
[8]: ObjectId: 2.5.29.17 Criticality=false
SubjectAlternativeName [
DNSName: ws.payconnexion.com
Algorithm: [SHA1withRSA]
Signature:
<snip>
ajp-bio-8014-exec-7, READ: TLSv1 Handshake, length = 13
*** CertificateRequest
Cert Types: RSA, DSS
Cert Authorities:
<Empty>
*** ServerHelloDone
matching alias: 1
*** Certificate chain
chain [0] = [
Version: V3
Subject: CN=*.payments.austintexas.gov, O=City of Austin, L=Austin, ST=Texas, C=US
Signature Algorithm: SHA1withRSA, OID = 1.2.840.113549.1.1.5
Key: Sun RSA public key, 2048 bits
<snip>public exponent: 65537
Validity: [From: Mon Aug 11 12:39:37 CDT 2014,
               To: Thu Sep 01 18:34:24 CDT 2016]
Issuer: CN=Entrust Certification Authority - L1C, OU="(c) 2009 Entrust, Inc.", OU=www.entrust.net/rpa is incorporated by reference, O="Entrust, Inc.", C=US
SerialNumber: [<snip>]
Certificate Extensions: 9
[1]: ObjectId: 1.3.6.1.5.5.7.1.1 Criticality=false
AuthorityInfoAccess [
   accessMethod: ocsp
   accessLocation: URIName: http://ocsp.entrust.net
   accessMethod: caIssuers
   accessLocation: URIName: http://aia.entrust.net/2048-l1c.cer
[2]: ObjectId: 2.5.29.35 Criticality=false
AuthorityKeyIdentifier [
KeyIdentifier [
<snip>]
[3]: ObjectId: 2.5.29.19 Criticality=false
BasicConstraints:[
CA:false
PathLen: undefined
[4]: ObjectId: 2.5.29.31 Criticality=false
CRLDistributionPoints [
[DistributionPoint:
     [URIName: http://crl.entrust.net/level1c.crl]
[5]: ObjectId: 2.5.29.32 Criticality=false
CertificatePolicies [
[CertificatePolicyId: [1.2.840.113533.7.75.2]
[PolicyQualifierInfo: [
qualifierID: 1.3.6.1.5.5.7.2.1
qualifier: <snip>
[CertificatePolicyId: [2.23.140.1.2.2]
[6]: ObjectId: 2.5.29.37 Criticality=false
ExtendedKeyUsages [
serverAuth
clientAuth
[7]: ObjectId: 2.5.29.15 Criticality=false
KeyUsage [
DigitalSignature
Key_Encipherment
[8]: ObjectId: 2.5.29.17 Criticality=false
SubjectAlternativeName [
DNSName: *.payments.austintexas.gov
DNSName: payments.austintexas.gov
[9]: ObjectId: 2.5.29.14 Criticality=false
SubjectKeyIdentifier [
KeyIdentifier [
<snip>]
Algorithm: [SHA1withRSA]
Signature:
<snip>
chain [1] = [
Version: V3
Subject: CN=Entrust Certification Authority - L1C, OU="(c) 2009 Entrust, Inc.", OU=www.entrust.net/rpa is incorporated by reference, O="Entrust, Inc.", C=US
Signature Algorithm: SHA1withRSA, OID = 1.2.840.113549.1.1.5
Key: Sun RSA public key, 2048 bits
modulus: <snip>
public exponent: 65537
Validity: [From: Fri Nov 11 09:40:40 CST 2011,
               To: Thu Nov 11 20:51:17 CST 2021]
Issuer: CN=Entrust.net Certification Authority (2048), OU=(c) 1999 Entrust.net Limited, OU=www.entrust.net/CPS_2048 incorp. by ref. (limits liab.), O=Entrust.net
SerialNumber: [<snip>]
Certificate Extensions: 7
[1]: ObjectId: 1.3.6.1.5.5.7.1.1 Criticality=false
AuthorityInfoAccess [
   accessMethod: ocsp
   accessLocation: URIName: http://ocsp.entrust.net
[2]: ObjectId: 2.5.29.35 Criticality=false
AuthorityKeyIdentifier [
KeyIdentifier [
<snip>]
[3]: ObjectId: 2.5.29.19 Criticality=true
BasicConstraints:[
CA:true
PathLen:0
[4]: ObjectId: 2.5.29.31 Criticality=false
CRLDistributionPoints [
[DistributionPoint:
     [URIName: http://crl.entrust.net/2048ca.crl]
[5]: ObjectId: 2.5.29.32 Criticality=false
CertificatePolicies [
[CertificatePolicyId: [2.5.29.32.0]
[PolicyQualifierInfo: [
qualifierID: 1.3.6.1.5.5.7.2.1
qualifier: <snip>
[6]: ObjectId: 2.5.29.15 Criticality=true
KeyUsage [
Key_CertSign
Crl_Sign
[7]: ObjectId: 2.5.29.14 Criticality=false
SubjectKeyIdentifier [
KeyIdentifier [
<snip>]
Algorithm: [SHA1withRSA]
Signature:
<snip>
chain [2] = [
Version: V3
Subject: CN=Entrust.net Certification Authority (2048), OU=(c) 1999 Entrust.net Limited, OU=www.entrust.net/CPS_2048 incorp. by ref. (limits liab.), O=Entrust.net
Signature Algorithm: SHA1withRSA, OID = 1.2.840.113549.1.1.5
Key: Sun RSA public key, 2048 bits
modulus: <snip>public exponent: 65537
Validity: [From: Fri Dec 24 11:50:51 CST 1999,
               To: Tue Jul 24 09:15:12 CDT 2029]
Issuer: CN=Entrust.net Certification Authority (2048), OU=(c) 1999 Entrust.net Limited, OU=www.entrust.net/CPS_2048 incorp. by ref. (limits liab.), O=Entrust.net
SerialNumber: [<snip>]
Certificate Extensions: 3
[1]: ObjectId: 2.5.29.19 Criticality=true
BasicConstraints:[
CA:true
PathLen:2147483647
[2]: ObjectId: 2.5.29.15 Criticality=true
KeyUsage [
Key_CertSign
Crl_Sign
[3]: ObjectId: 2.5.29.14 Criticality=false
SubjectKeyIdentifier [
KeyIdentifier [
<snip>]
Algorithm: [SHA1withRSA]
Signature:
<snip>
*** ClientKeyExchange, RSA PreMasterSecret, TLSv1
ajp-bio-8014-exec-7, WRITE: TLSv1 Handshake, length = 3970
SESSION KEYGEN:
PreMaster Secret:
<snip>
CONNECTION KEYGEN:
Client Nonce:
<snip>
Server Nonce:
<snip>
Master Secret:
<snip>
Client MAC write Secret:
<snip>
Server MAC write Secret:
<snip>
Client write key:
<snip>
Server write key:
<snip>
Client write IV:
<snip>
Server write IV:
<snip>
*** CertificateVerify
ajp-bio-8014-exec-7, WRITE: TLSv1 Handshake, length = 262
ajp-bio-8014-exec-7, WRITE: TLSv1 Change Cipher Spec, length = 1
*** Finished
verify_data: { 51, 254, 40, 56, 247, 218, 130, 183, 112, 239, 95, 4 }
ajp-bio-8014-exec-7, WRITE: TLSv1 Handshake, length = 48
ajp-bio-8014-exec-7, READ: TLSv1 Change Cipher Spec, length = 1
ajp-bio-8014-exec-7, READ: TLSv1 Handshake, length = 48
*** Finished
verify_data: { 89, 182, 137, 178, 177, 31, 27, 115, 151, 90, 169, 49 }
%% Cached client session: [Session-5, TLS_RSA_WITH_AES_256_CBC_SHA]
ajp-bio-8014-exec-7, setSoTimeout(60000) called
ajp-bio-8014-exec-7, WRITE: TLSv1 Application Data, length = 1520
ajp-bio-8014-exec-7, READ: TLSv1 Application Data, length = 128
Jan 23, 2015 13:15:38 PM Information [ajp-bio-8014-exec-7] - HTTP request completed {Status Code=500 ,Time taken=1302 ms}
ajp-bio-8014-exec-7, READ: TLSv1 Application Data, length = 256
ajp-bio-8014-exec-7, READ: TLSv1 Alert, length = 32
ajp-bio-8014-exec-7, RECV TLSv1 ALERT: warning, close_notify
ajp-bio-8014-exec-7, called closeInternal(false)
ajp-bio-8014-exec-7, SEND TLSv1 ALERT: warning, description = close_notify
ajp-bio-8014-exec-7, WRITE: TLSv1 Alert, length = 32
ajp-bio-8014-exec-7, called closeSocket(selfInitiated)
ajp-bio-8014-exec-7, called close()
ajp-bio-8014-exec-7, called closeInternal(true)

Ok, apparently Chase person who said we were not sending the certs and achieving mutual auth
was incorrect.   The https calls were connecting, and mutual auth was taking place.   The 500
error was about a soap envelope being delivered, and NOT SSL as I directed to.   Everything
is working fine now.
Thanks,
Bob

Authenticated SMTP/SSL over port 465

Does Oracle E-mail support authenticated SMTP over SSL on port 465? - E

Yes,
both TLS and SSL are possible with 10.1.1. Tried myself. A little bit tweaking essmi's accordingly, applying certificates, and adjusting listener.ora for LISTENER_ES.
Note: essmi only.
- Torsten

SMTP SSL Settings for Windows Livemail 2011

Hi
I'm trying to set up my mum's email settings but can't send emails out. I get two messages when I check or uncheck the SSL authentication boxes under the Tools - Advanced tab. These are apparently conflicting error message 530 and 250 (see below) one telling me to check th ebox for SSL authntication and then one saying the BT server doesn't support SSL servers. I have tried various combinations of checks and unchecks under the Server and Advanced tabs. Broadband Desktop gives up and sulks with script errors when I tried autofix. Any suggestions?
UNCHECKED:
The message could not be sent because the server rejected the sender's e-mail address. The sender's e-mail address was '**********@btinternet.com'.
Subject 'Test 3'
Server Error: 530
Server Response: 530 authentication required - Your email could not be sent. To fix this you must make a simple change to your email (known as SMTP authentication). For advice visit www.btyahoo.com/smtp
Server: 'mail.btinternet.com'
Windows Live Mail Error ID: 0x800CCC78
Protocol: SMTP
Port: 25
Secure(SSL): No
CHECKED:
The server does not support a SSL connection.
Subject 'Test 3'
Server Error: 250
Server Response: 250 8BITMIME
Server: 'mail.btinternet.com'
Windows Live Mail Error ID: 0x800CCC7D
Protocol: SMTP
Port: 25
Secure(SSL): Yes
Solved!
Go to Solution.

Magenta wrote:
Hi
I'm trying to set up my mum's email settings but can't send emails out. I get two messages when I check or uncheck the SSL authentication boxes under the Tools - Advanced tab. These are apparently conflicting error message 530 and 250 (see below) one telling me to check th ebox for SSL authntication and then one saying the BT server doesn't support SSL servers. I have tried various combinations of checks and unchecks under the Server and Advanced tabs. Broadband Desktop gives up and sulks with script errors when I tried autofix. Any suggestions?
UNCHECKED:
The message could not be sent because the server rejected the sender's e-mail address. The sender's e-mail address was '**********@btinternet.com'.
Subject 'Test 3'
Server Error: 530
Server Response: 530 authentication required - Your email could not be sent. To fix this you must make a simple change to your email (known as SMTP authentication). For advice visit www.btyahoo.com/smtp
Server: 'mail.btinternet.com'
Windows Live Mail Error ID: 0x800CCC78
Protocol: SMTP
Port: 25
Secure(SSL): No
CHECKED:
The server does not support a SSL connection.
Subject 'Test 3'
Server Error: 250
Server Response: 250 8BITMIME
Server: 'mail.btinternet.com'
Windows Live Mail Error ID: 0x800CCC7D
Protocol: SMTP
Port: 25
Secure(SSL): Yes
Hi. Welcome to the forums.
You are indeed not clicking the correct item in Windows Live Mail. You need to set the Secure (SSL) to no (i.e. untick that option), but make sure that (in the Servers tab/Outgoing Mail Servers) My server requries authentication is ticked.
http://www.andyweb.co.uk/shortcuts
http://www.andyweb.co.uk/pictures

SMTP SSL

http://img112.imageshack.us/img112/4636/picture1za4.png
So I set up a self-signed SSL certificate for my IMAP email and it went pretty painless. Every time a launch mail.app I have to tell it to trust the cert, but otherwise it runs fine. And Eavesdrop confirms that things are very much encrypted now. I set it to Require SSL in IMAP, since I'm the only end user on this server.
Now I need to set up SSL on SMTP and I'm not sure what to use. As I understand it, SMTP uses SSL for SMTP-to-SMTP connections if it's available. My cert is self signed, so that probably isn't going to work? Is the mail server smart enough to know that if I choose 'Require', that I mean only for mail sent from my client to the SMTP server, and not incoming mail from other SMTP servers to my server?
The main thing I want out of this is to protect my login credentials when I'm connecting to my own mail server from my computers, especially my laptop when I could be sharing a wireless network with anyone.

It should be fine to "use" SSL, but not "require" as explained above.
With the setting at "use", clients can use SSL but it will not break standard smtp connections from other servers to yours.
Please note however: I'm not saying this is the case for the OP (don't his/her type of connection/account), but keep in mind that many - increasingly, most - ISPs will (in fact, do) block incoming "services" if you have a home-type account. IE: not a commercial account which typically costs more. This is distinct from return traffic for your own outgoing requests (eg: typical home-user email and web browsing).
They probably do have a very clear clause in your contract stipulating this, and in fact that if you violate it they can terminate your account/connection.
Something to keep in mind.

SMTP + SSL - eliminates possibility of being a spam relay?

Is it true that enabling SSL on the iPhone and the server side authenticates the sender and prevents an open SMTP relay from being used by 3rd party spammers - or does SSL just encrypt the traffic?
Thanks.

SSL is about encryption. Authenticated SMTP allows
for selective relay by authenticated parties without
interfering with SMTP transfers between servers.
I am not sure why you are asking however, as your
client cannot be configured as a relay. If you want
to insure that you can originate or reply to messages
outside your subnet, then you want to configure your
server and client for authenticated SMTP. If you do
not run your own server, then you want to pick and
electronic mail provider who will allow you to use
authenticated SMTP.
Sorry to be more clear - will using SSL + SMTP + Authentication (login credentials) eliminate the risk of our firm being used to as an SMTP relay for spammers looking for open SMTP servers. Seems it would?

Is SMTP SSL on port 587 possible ?

Hi,
I read that TLS is fully supported but is SMTP/S submission on port 587 possible ?
Thx for your help
Emmanuel

Have you specifically configured your mail server to use port 465?
By default, Mac OS X Server doesn't use this port.
Port 465 is used by SSMTP but Mac OS X Server doesn't implement this. It uses the more common SMTPS (SMTP w/ TLS).
The main difference is that SSMTP encrypts the entire connection (like HTTPS vs HTTP) whereas SMTPS starts off unencrypted and then switches to SSL when both the client and the server recognize that each other support it. SMTPS is far more widely implemented (and it's what Mail.app, amongst others, uses).

Complete working code for Gmail POP3 & SMTP with SSL - Java mail API

Finally, your code-hunt has come to an end!!!!
I am presenting you the complete solution (with code) to send and retrieve you mails to & from GMAIL using SMTP and POP3 with SSL & Authenticaion enabled. [Even starters & newbies like me, can easy try, test & understand - But first download & add JAR's of Java Mail API & Java Activation Framework to Netbeans Library Manager]
Download Java Mail API here
http://java.sun.com/products/javamail/
Read Java Mail FAQ's here
http://java.sun.com/products/javamail/FAQ.html
Download Java Activation Framework [JAF]
http://java.sun.com/products/javabeans/jaf/downloads/index.html
Also, The POP program retrieves the mail sent with SMTP program :) [MOST IMPORTANT & LARGELY IN DEMAND]okey.. first things first... all of your thanks goes to the following and not a s@!te to me :)
hail Java !!
hail Java mail API !!
hail Java forums !!
hail Java-tips.org !!
hail Netbeans !!
Thanks to all coders who helped me by getting the code to work in one piece.
special thanks to "bshannon" - The dude who runs this forum from 97!!I am just as happy as you will be when you execute the below code!! [my 13 hours of tweaking & code hunting has paid off!!]
Now here it is...I only present you the complete solution!!
START OF PROGRAM 1
SENDING A MAIL FROM GMAIL ACCOUNT USING SMTP [STARTTLS (SSL)] PROTOCOL OF JAVA MAIL APINote on Program 1:
1. In the code below replace USERNAME & PASSWORD with your respective GMAIL account username and its corresponding password!
2. Use the code to make your Gmail client [jsp/servlets whatever]
//Mail.java - smtp sending starttls (ssl) authentication enabled
//1.Open a new Java class in netbeans (default package of the project) and name it as "Mail.java"
//2.Copy paste the entire code below and save it.
//3.Right click on the file name in the left side panel and click "compile" then click "Run"
import javax.mail.*;
import javax.mail.internet.*;
import java.util.*;
public class Main
    String d_email = "[email protected]",
            d_password = "PASSWORD",
            d_host = "smtp.gmail.com",
            d_port = "465",
            m_to = "[email protected]",
            m_subject = "Testing",
            m_text = "Hey, this is the testing email.";
    public Main()
        Properties props = new Properties();
        props.put("mail.smtp.user", d_email);
        props.put("mail.smtp.host", d_host);
        props.put("mail.smtp.port", d_port);
        props.put("mail.smtp.starttls.enable","true");
        props.put("mail.smtp.auth", "true");
        //props.put("mail.smtp.debug", "true");
        props.put("mail.smtp.socketFactory.port", d_port);
        props.put("mail.smtp.socketFactory.class", "javax.net.ssl.SSLSocketFactory");
        props.put("mail.smtp.socketFactory.fallback", "false");
        SecurityManager security = System.getSecurityManager();
        try
            Authenticator auth = new SMTPAuthenticator();
            Session session = Session.getInstance(props, auth);
            //session.setDebug(true);
            MimeMessage msg = new MimeMessage(session);
            msg.setText(m_text);
            msg.setSubject(m_subject);
            msg.setFrom(new InternetAddress(d_email));
            msg.addRecipient(Message.RecipientType.TO, new InternetAddress(m_to));
            Transport.send(msg);
        catch (Exception mex)
            mex.printStackTrace();
    public static void main(String[] args)
        Main blah = new Main();
    private class SMTPAuthenticator extends javax.mail.Authenticator
        public PasswordAuthentication getPasswordAuthentication()
            return new PasswordAuthentication(d_email, d_password);
END OF PROGRAM 1-----
START OF PROGRAM 2
RETRIVE ALL THE MAILS FROM GMAIL INBOX USING Post Office Protocol POP3 [SSL] PROTOCOL OF JAVA MAIL APINote:
1.Log into your gmail account via webmail [http://mail.google.com/]
2.Click on "settings" and select "Mail Forwarding & POP3/IMAP"
3.Select "enable POP for all mail" and "save changes"
4.In the code below replace USERNAME & PASSWORD with your respective GMAIL account username and its corresponding password!
PROGRAM 2 - PART 1 - Main.java
//1.Open a new Java class file in the default package
//2.Copy paste the below code and rename it to Mail.java
//3.Compile and execute this code.
public class Main {
    /** Creates a new instance of Main */
    public Main() {
     * @param args the command line arguments
    public static void main(String[] args) {
        try {
            GmailUtilities gmail = new GmailUtilities();
            gmail.setUserPass("[email protected]", "PASSWORD");
            gmail.connect();
            gmail.openFolder("INBOX");
            int totalMessages = gmail.getMessageCount();
            int newMessages = gmail.getNewMessageCount();
            System.out.println("Total messages = " + totalMessages);
            System.out.println("New messages = " + newMessages);
            System.out.println("-------------------------------");
//Uncomment the below line to print the body of the message. Remember it will eat-up your bandwidth if you have 100's of messages.            //gmail.printAllMessageEnvelopes();
            gmail.printAllMessages();
        } catch(Exception e) {
            e.printStackTrace();
            System.exit(-1);
END OF PART 1
PROGRAM 2 - PART 2 - GmailUtilities.java
//1.Open a new Java class in the project (default package)
//2.Copy paste the below code
//3.Compile - Don't execute this[Run]
import com.sun.mail.pop3.POP3SSLStore;
import java.io.File;
import java.io.IOException;
import java.io.InputStream;
import java.util.Date;
import java.util.Properties;
import javax.mail.Address;
import javax.mail.FetchProfile;
import javax.mail.Flags;
import javax.mail.Folder;
import javax.mail.Message;
import javax.mail.MessagingException;
import javax.mail.Multipart;
import javax.mail.Part;
import javax.mail.Session;
import javax.mail.Store;
import javax.mail.URLName;
import javax.mail.internet.ContentType;
import javax.mail.internet.InternetAddress;
import javax.mail.internet.MimeBodyPart;
import javax.mail.internet.ParseException;
public class GmailUtilities {
    private Session session = null;
    private Store store = null;
    private String username, password;
    private Folder folder;
    public GmailUtilities() {
    public void setUserPass(String username, String password) {
        this.username = username;
        this.password = password;
    public void connect() throws Exception {
        String SSL_FACTORY = "javax.net.ssl.SSLSocketFactory";
        Properties pop3Props = new Properties();
        pop3Props.setProperty("mail.pop3.socketFactory.class", SSL_FACTORY);
        pop3Props.setProperty("mail.pop3.socketFactory.fallback", "false");
        pop3Props.setProperty("mail.pop3.port", "995");
        pop3Props.setProperty("mail.pop3.socketFactory.port", "995");
        URLName url = new URLName("pop3", "pop.gmail.com", 995, "",
                username, password);
        session = Session.getInstance(pop3Props, null);
        store = new POP3SSLStore(session, url);
        store.connect();
    public void openFolder(String folderName) throws Exception {
        // Open the Folder
        folder = store.getDefaultFolder();
        folder = folder.getFolder(folderName);
        if (folder == null) {
            throw new Exception("Invalid folder");
        // try to open read/write and if that fails try read-only
        try {
            folder.open(Folder.READ_WRITE);
        } catch (MessagingException ex) {
            folder.open(Folder.READ_ONLY);
    public void closeFolder() throws Exception {
        folder.close(false);
    public int getMessageCount() throws Exception {
        return folder.getMessageCount();
    public int getNewMessageCount() throws Exception {
        return folder.getNewMessageCount();
    public void disconnect() throws Exception {
        store.close();
    public void printMessage(int messageNo) throws Exception {
        System.out.println("Getting message number: " + messageNo);
        Message m = null;
        try {
            m = folder.getMessage(messageNo);
            dumpPart(m);
        } catch (IndexOutOfBoundsException iex) {
            System.out.println("Message number out of range");
    public void printAllMessageEnvelopes() throws Exception {
        // Attributes & Flags for all messages ..
        Message[] msgs = folder.getMessages();
        // Use a suitable FetchProfile
        FetchProfile fp = new FetchProfile();
        fp.add(FetchProfile.Item.ENVELOPE);
        folder.fetch(msgs, fp);
        for (int i = 0; i < msgs.length; i++) {
            System.out.println("--------------------------");
            System.out.println("MESSAGE #" + (i + 1) + ":");
            dumpEnvelope(msgs);
public void printAllMessages() throws Exception {
// Attributes & Flags for all messages ..
Message[] msgs = folder.getMessages();
// Use a suitable FetchProfile
FetchProfile fp = new FetchProfile();
fp.add(FetchProfile.Item.ENVELOPE);
folder.fetch(msgs, fp);
for (int i = 0; i < msgs.length; i++) {
System.out.println("--------------------------");
System.out.println("MESSAGE #" + (i + 1) + ":");
dumpPart(msgs[i]);
public static void dumpPart(Part p) throws Exception {
if (p instanceof Message)
dumpEnvelope((Message)p);
String ct = p.getContentType();
try {
pr("CONTENT-TYPE: " + (new ContentType(ct)).toString());
} catch (ParseException pex) {
pr("BAD CONTENT-TYPE: " + ct);
* Using isMimeType to determine the content type avoids
* fetching the actual content data until we need it.
if (p.isMimeType("text/plain")) {
pr("This is plain text");
pr("---------------------------");
System.out.println((String)p.getContent());
} else {
// just a separator
pr("---------------------------");
public static void dumpEnvelope(Message m) throws Exception {
pr(" ");
Address[] a;
// FROM
if ((a = m.getFrom()) != null) {
for (int j = 0; j < a.length; j++)
pr("FROM: " + a[j].toString());
// TO
if ((a = m.getRecipients(Message.RecipientType.TO)) != null) {
for (int j = 0; j < a.length; j++) {
pr("TO: " + a[j].toString());
// SUBJECT
pr("SUBJECT: " + m.getSubject());
// DATE
Date d = m.getSentDate();
pr("SendDate: " +
(d != null ? d.toString() : "UNKNOWN"));
static String indentStr = " ";
static int level = 0;
* Print a, possibly indented, string.
public static void pr(String s) {
System.out.print(indentStr.substring(0, level * 2));
System.out.println(s);
}END OF PART 2
END OF PROGRAM 2
P.S: CHECKING !!
STEP 1.
First compile and execute the PROGRAM 1 with your USERNAME & PASSWORD. This will send a mail to your own account.
STEP 2.
Now compile both PART 1 & PART 2 of PROGRAM 2. Then, execute PART 1 - Main.java. This will retrive the mail sent in step 1. njoy! :)
In future, I hope this is added to the demo programs of the Java Mail API download package.
This is for 3 main reasons...
1. To prevent a lot of silly questions being posted on this forum [like the ones I did :(].
2. To give the first time Java Mail user with a real time working example without code modification [code has to use command line args like the demo programs - for instant results].
3. Also, this is what google has to say..
"The Gmail Team is committed to making sure you always can access your mail. That's why we're offering POP access and auto-forwarding. Both features are free for all Gmail users and we have no plans to charge for them in the future."
http://mail.google.com/support/bin/answer.py?answer=13295
I guess bshannon & Java Mail team is hearing this....
Again, Hurray and thanks for helping me make it!! cheers & no more frowned faces!!
(: (: (: (: (: GO JCODERS GO!! :) :) :) :) :)
codeace
-----

Thanks for the reply,
I did checked by enabling session debuging and also checked pop settings it's enabled for all
mails, I tried deleting some very old messages and now the message count is changed to 310.
This may be the problem with gmail.
Bellow is the output i got,
DEBUG: setDebug: JavaMail version 1.4ea
DEBUG: getProvider() returning javax.mail.Provider[STORE,pop3,com.sun.mail.pop3.POP3Store,Sun Microsystems, Inc]
DEBUG POP3: connecting to host "pop.gmail.com", port 995, isSSL false
S: +OK Gpop ready for requests from 121.243.255.240 n22pf5432603pof.2
C: USER [email protected]
S: +OK send PASS
C: PASS my_password
S: +OK Welcome.
C: STAT
S: +OK 310 26900234
Custom output: messageCount : 310
C: QUIT
S: +OK Farewell.

MailAPI SMTP sending error: 'Could not convert socket to TLS'

I'm stucked with smtp authentication in a project.
The process works on port 25 with no STARTTLS, but unfortunately our company server uses port 587 and STARTTLS.
It seems that only the half of the authentication process could be successful, as the server accepts EHLO, but when it switches to secure the program fails with the exception:
'Could not convert socket to TLS'
The simplified code (from a sample app) is:
public void SendMail() throws Exception{
        Properties props = new Properties();
        props.setProperty("mail.transport.protocol", "smtp");
        props.setProperty("mail.smtp.host", "smtpserver");
        props.setProperty("mail.smtp.port", "587");
        props.setProperty("mail.smtp.auth", "true");
        props.setProperty("mail.smtp.auth.ntlm.domain", "codomain");
        props.setProperty("mail.smtp.starttls.required", "true");
        props.setProperty("mail.smtp.auth.mechanisms", "LOGIN NTLM");
        Session mailSession = Session.getDefaultInstance(props, null);
        mailSession.setDebug(true);
        Transport transport = mailSession.getTransport();
        MimeMessage message = new MimeMessage(mailSession);
        message.setSubject("My subject");
        message.setFrom(new InternetAddress("[email protected]"));
        message.setContent("<h1>Hello world</h1>", "text/html");
        message.addRecipient(Message.RecipientType.TO,
                            new InternetAddress("[email protected]"));
        transport.connect("smtpserver", 587, "CODOMAIN\\myaccount", "mypass");
        transport.sendMessage(message,
        message.getRecipients(Message.RecipientType.TO));
        transport.close();
   }

I'll copy the full message below:
+2010.06.29. 12:03:10 mailapi_2.Main main+
SEVERE: null
javax.mail.MessagingException: Could not convert socket to TLS;+
nested exception is:
javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
at com.sun.mail.smtp.SMTPTransport.startTLS(SMTPTransport.java:1652)
at com.sun.mail.smtp.SMTPTransport.protocolConnect(SMTPTransport.java:534)
at javax.mail.Service.connect(Service.java:291)
at mailapi_2.SimpleMail.SendMail1(SimpleMail.java:59)
at mailapi_2.Main.main(Main.java:23)
Caused by: javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
at com.sun.net.ssl.internal.ssl.Alerts.getSSLException(Alerts.java:174)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1591)
at com.sun.net.ssl.internal.ssl.Handshaker.fatalSE(Handshaker.java:187)
at com.sun.net.ssl.internal.ssl.Handshaker.fatalSE(Handshaker.java:181)
at com.sun.net.ssl.internal.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1035)
at com.sun.net.ssl.internal.ssl.ClientHandshaker.processMessage(ClientHandshaker.java:124)
at com.sun.net.ssl.internal.ssl.Handshaker.processLoop(Handshaker.java:516)
at com.sun.net.ssl.internal.ssl.Handshaker.process_record(Handshaker.java:454)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:884)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1096)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1123)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1107)
at com.sun.mail.util.SocketFetcher.configureSSLSocket(SocketFetcher.java:503)
at com.sun.mail.util.SocketFetcher.startTLS(SocketFetcher.java:443)
at com.sun.mail.smtp.SMTPTransport.startTLS(SMTPTransport.java:1647)
+... 4 more+
Caused by: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
at sun.security.validator.PKIXValidator.doBuild(PKIXValidator.java:285)
at sun.security.validator.PKIXValidator.engineValidate(PKIXValidator.java:191)
at sun.security.validator.Validator.validate(Validator.java:218)
at com.sun.net.ssl.internal.ssl.X509TrustManagerImpl.validate(X509TrustManagerImpl.java:126)
at com.sun.net.ssl.internal.ssl.X509TrustManagerImpl.checkServerTrusted(X509TrustManagerImpl.java:209)
Could not convert socket to TLS
at com.sun.net.ssl.internal.ssl.X509TrustManagerImpl.checkServerTrusted(X509TrustManagerImpl.java:249)
at com.sun.net.ssl.internal.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1014)
+... 14 more+
Caused by: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
at sun.security.provider.certpath.SunCertPathBuilder.engineBuild(SunCertPathBuilder.java:174)
at java.security.cert.CertPathBuilder.build(CertPathBuilder.java:238)
at sun.security.validator.PKIXValidator.doBuild(PKIXValidator.java:280)
+... 20 more+
And the output panel before the exception:
Sending mail...
DEBUG: setDebug: JavaMail version 1.4.3
+DEBUG: getProvider() returning javax.mail.Provider[TRANSPORT,smtp,com.sun.mail.smtp.SMTPTransport,Sun Microsystems, Inc]+
DEBUG SMTP: useEhlo true, useAuth true
DEBUG SMTP: trying to connect to host "smtpserver", port 587, isSSL false
+220 exch.plt.local Microsoft ESMTP MAIL Service ready at Tue, 29 Jun 2010 12:03:08 +0200+
DEBUG SMTP: connected to host "smtpserver", port: 587
EHLO machine.codomain.local
+250-smtpserver.codomain.local Hello [xxx.xxx.xxx.xxx]+
+250-SIZE 15728640+
+250-PIPELINING+
+250-DSN+
+250-ENHANCEDSTATUSCODES+
+250-STARTTLS+
+250-AUTH GSSAPI NTLM+
+250-8BITMIME+
+250-BINARYMIME+
+250 CHUNKING+
DEBUG SMTP: Found extension "SIZE", arg "15728640"
DEBUG SMTP: Found extension "PIPELINING", arg ""
DEBUG SMTP: Found extension "DSN", arg ""
DEBUG SMTP: Found extension "ENHANCEDSTATUSCODES", arg ""
DEBUG SMTP: Found extension "STARTTLS", arg ""
DEBUG SMTP: Found extension "AUTH", arg "GSSAPI NTLM"
DEBUG SMTP: Found extension "8BITMIME", arg ""
DEBUG SMTP: Found extension "BINARYMIME", arg ""
DEBUG SMTP: Found extension "CHUNKING", arg ""
STARTTLS
+220 2.0.0 SMTP server ready+

Gmail, Java Mail - SSL Mess

I've read many tutorials, as well as forums, and guides. Many are outdated or just didn't cover SSL at all. I think this SSL business with Gmail appears to be farely recent.
The most helpful guide I've found was here . The SSLNotes for the latest Java Mail.
Here's the code:
    private void sendTxt(String[] call_info) {
        Security.addProvider(new com.sun.net.ssl.internal.ssl.Provider());
        try {
            MailSSLSocketFactory sf = new MailSSLSocketFactory();
            sf.setTrustAllHosts(true);
            Properties props = System.getProperties();
            props.setProperty("mail.transport.protocol", "smtps");
            //props.setProperty("mail.host", "smtp.gmail.com");
            props.setProperty("mail.smtps.host", "smtp.gmail.com");
            props.put("mail.smtp.auth", "true");
            props.put("mail.smtp.port", "465");
            //props.put("mail.smtp.socketFactory.port", "465");
            //props.put("mail.smtp.socketFactory.class", "javax.net.ssl.SSLSocketFactory");
            //props.put("mail.smtp.socketFactory.fallback", "false");
            props.put("mail.user", "[email protected]");
            props.put("mail.smtp.starttls.enable","true");
            props.put("mail.smtp.ssl.enable", "true");
            props.put("mail.smtp.ssl.checkserveridentity", "true");
            props.put("mail.smtp.ssl.socketFactory", sf);
            Session session = Session.getDefaultInstance(props, new Authenticator() {
                @Override
            protected PasswordAuthentication getPasswordAuthentication() {
                    return new PasswordAuthentication
                    ("[email protected]", "*****");}});
            session.setProtocolForAddress("rfc822", "smtps");
            session.setDebug(true);
            Transport transport = session.getTransport();
            MimeMessage msg = new MimeMessage(session);
            msg.setSender(new InternetAddress("[email protected]"));
            msg.setSubject("subject");
            msg.setContent("body", "content");
            msg.addRecipient(Message.RecipientType.TO,
                    new InternetAddress("[email protected]"));
            transport.connect();
            Transport.send(msg);
            transport.close();
        } catch (MessagingException me) {
            System.err.println(me.getMessage());
            me.printStackTrace();
            System.exit(0);
        } catch (GeneralSecurityException gse) {
            System.err.println(gse.getMessage());
            gse.printStackTrace();
            System.exit(0);
    }here are the error messages
DEBUG SMTP: exception reading response: javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested targetAny guidance or opinions are always greatly appreciated.

bshannon, you were right, I cleaned it up. As soon as I found the MailSSLSocketFactory class,
and I could bypass the certificate nonsense it worked. Here it is.
public class TxtAlert {
    private final String host = "smtp.gmail.com";
    private final String from = "[email protected]";
    public TxtAlert(String[] data, String recipient) {
        try {
              // setup mail server
            MailSSLSocketFactory sf = new MailSSLSocketFactory();
            sf.setTrustAllHosts(true);
            // set system properties
            Properties props = System.getProperties();
            props.put("mail.smtps.ssl.socketFactory", sf);
            // get session
            Session session = Session.getDefaultInstance(props);
            session.setDebug(true);
            // define message
            MimeMessage msg = new MimeMessage(session);
            msg.setFrom(new InternetAddress(from));
            msg.addRecipient(Message.RecipientType.TO,
                    new InternetAddress(recipient));
            msg.setSubject("Hello JavaMail");
            msg.setText("Welcome to JavaMail");
            // send message
            SMTPSSLTransport transport = (SMTPSSLTransport)session.getTransport("smtps");
            transport.connect(host, from, "password");
            transport.sendMessage(msg, msg.getAllRecipients());
            System.err.println("txt has been sent");
        } catch (MessagingException me) {
            System.err.println(me.getMessage() );
            System.err.println("-------------------");
            me.printStackTrace();
            System.exit(0);
        } catch (GeneralSecurityException gse) {
            System.err.println(gse.getMessage() );
            System.err.println("-------------------");
            gse.printStackTrace();
            System.exit(0);
    }

SMTP SSL StartTLS Auth

Similar Messages

Maybe you are looking for