Note that there are some explanatory texts on larger screens.

plurals
  1. POTLS issue when sending to gmail through JavaMail
    primarykey
    data
    text
    <p>Turns out that JavaMail is a bit more frustrating than I thought it would be. I've looked at several examples online on how to send a simple SMTP email through Gmail's servers (but not through SSL). After trying several different examples of code, I keep concluding to the same example exception when I call <code>transport.connect()</code>. I keep getting this stack trace: </p> <pre><code>Exception in thread "main" com.sun.mail.smtp.SMTPSendFailedException: 530 5.7.0 Must issue a STARTTLS command first. l10sm302158wfk.21 at com.sun.mail.smtp.SMTPTransport.issueSendCommand(SMTPTransport.java:2057) at com.sun.mail.smtp.SMTPTransport.mailFrom(SMTPTransport.java:1580) at com.sun.mail.smtp.SMTPTransport.sendMessage(SMTPTransport.java:1097) at SendEmail.main(SendEmail.java:47) </code></pre> <p>Can someone please tell me what I should add or do to fix this?</p> <p>Here is my code:</p> <pre><code> Properties props = new Properties(); props.put("mail.transport.protocol", "smtp"); props.put("mail.host", "smtp.gmail.com"); props.put("mail.user", "blahblah@gmail.com"); props.put("mail.password", "blah"); props.put("mail.port", "587"); Session mailSession = Session.getDefaultInstance(props, null); Transport transport = mailSession.getTransport(); MimeMessage message = new MimeMessage(mailSession); message.setSubject("This is a test"); message.setContent("This is a test", "text/plain"); message.addRecipient(Message.RecipientType.TO, new InternetAddress("blahblah2@gmail.com")); transport.connect(); transport.sendMessage(message, message.getRecipients(Message.RecipientType.TO)); transport.close(); </code></pre>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload