smtp-tls.c 6.2 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171
  1. /***************************************************************************
  2. * _ _ ____ _
  3. * Project ___| | | | _ \| |
  4. * / __| | | | |_) | |
  5. * | (__| |_| | _ <| |___
  6. * \___|\___/|_| \_\_____|
  7. *
  8. * Copyright (C) 1998 - 2016, Daniel Stenberg, <daniel@haxx.se>, et al.
  9. *
  10. * This software is licensed as described in the file COPYING, which
  11. * you should have received as part of this distribution. The terms
  12. * are also available at https://curl.haxx.se/docs/copyright.html.
  13. *
  14. * You may opt to use, copy, modify, merge, publish, distribute and/or sell
  15. * copies of the Software, and permit persons to whom the Software is
  16. * furnished to do so, under the terms of the COPYING file.
  17. *
  18. * This software is distributed on an "AS IS" basis, WITHOUT WARRANTY OF ANY
  19. * KIND, either express or implied.
  20. *
  21. ***************************************************************************/
  22. /* <DESC>
  23. * SMTP example using TLS
  24. * </DESC>
  25. */
  26. #include <stdio.h>
  27. #include <string.h>
  28. #include <curl/curl.h>
  29. /* This is a simple example showing how to send mail using libcurl's SMTP
  30. * capabilities. It builds on the smtp-mail.c example to add authentication
  31. * and, more importantly, transport security to protect the authentication
  32. * details from being snooped.
  33. *
  34. * Note that this example requires libcurl 7.20.0 or above.
  35. */
  36. #define FROM "<sender@example.org>"
  37. #define TO "<addressee@example.net>"
  38. #define CC "<info@example.org>"
  39. static const char *payload_text[] = {
  40. "Date: Mon, 29 Nov 2010 21:54:29 +1100\r\n",
  41. "To: " TO "\r\n",
  42. "From: " FROM " (Example User)\r\n",
  43. "Cc: " CC " (Another example User)\r\n",
  44. "Message-ID: <dcd7cb36-11db-487a-9f3a-e652a9458efd@"
  45. "rfcpedant.example.org>\r\n",
  46. "Subject: SMTP TLS example message\r\n",
  47. "\r\n", /* empty line to divide headers from body, see RFC5322 */
  48. "The body of the message starts here.\r\n",
  49. "\r\n",
  50. "It could be a lot of lines, could be MIME encoded, whatever.\r\n",
  51. "Check RFC5322.\r\n",
  52. NULL
  53. };
  54. struct upload_status {
  55. int lines_read;
  56. };
  57. static size_t payload_source(void *ptr, size_t size, size_t nmemb, void *userp)
  58. {
  59. struct upload_status *upload_ctx = (struct upload_status *)userp;
  60. const char *data;
  61. if((size == 0) || (nmemb == 0) || ((size*nmemb) < 1)) {
  62. return 0;
  63. }
  64. data = payload_text[upload_ctx->lines_read];
  65. if(data) {
  66. size_t len = strlen(data);
  67. memcpy(ptr, data, len);
  68. upload_ctx->lines_read++;
  69. return len;
  70. }
  71. return 0;
  72. }
  73. int main(void)
  74. {
  75. CURL *curl;
  76. CURLcode res = CURLE_OK;
  77. struct curl_slist *recipients = NULL;
  78. struct upload_status upload_ctx;
  79. upload_ctx.lines_read = 0;
  80. curl = curl_easy_init();
  81. if(curl) {
  82. /* Set username and password */
  83. curl_easy_setopt(curl, CURLOPT_USERNAME, "user");
  84. curl_easy_setopt(curl, CURLOPT_PASSWORD, "secret");
  85. /* This is the URL for your mailserver. Note the use of port 587 here,
  86. * instead of the normal SMTP port (25). Port 587 is commonly used for
  87. * secure mail submission (see RFC4403), but you should use whatever
  88. * matches your server configuration. */
  89. curl_easy_setopt(curl, CURLOPT_URL, "smtp://mainserver.example.net:587");
  90. /* In this example, we'll start with a plain text connection, and upgrade
  91. * to Transport Layer Security (TLS) using the STARTTLS command. Be careful
  92. * of using CURLUSESSL_TRY here, because if TLS upgrade fails, the transfer
  93. * will continue anyway - see the security discussion in the libcurl
  94. * tutorial for more details. */
  95. curl_easy_setopt(curl, CURLOPT_USE_SSL, (long)CURLUSESSL_ALL);
  96. /* If your server doesn't have a valid certificate, then you can disable
  97. * part of the Transport Layer Security protection by setting the
  98. * CURLOPT_SSL_VERIFYPEER and CURLOPT_SSL_VERIFYHOST options to 0 (false).
  99. * curl_easy_setopt(curl, CURLOPT_SSL_VERIFYPEER, 0L);
  100. * curl_easy_setopt(curl, CURLOPT_SSL_VERIFYHOST, 0L);
  101. * That is, in general, a bad idea. It is still better than sending your
  102. * authentication details in plain text though. Instead, you should get
  103. * the issuer certificate (or the host certificate if the certificate is
  104. * self-signed) and add it to the set of certificates that are known to
  105. * libcurl using CURLOPT_CAINFO and/or CURLOPT_CAPATH. See docs/SSLCERTS
  106. * for more information. */
  107. curl_easy_setopt(curl, CURLOPT_CAINFO, "/path/to/certificate.pem");
  108. /* Note that this option isn't strictly required, omitting it will result
  109. * in libcurl sending the MAIL FROM command with empty sender data. All
  110. * autoresponses should have an empty reverse-path, and should be directed
  111. * to the address in the reverse-path which triggered them. Otherwise,
  112. * they could cause an endless loop. See RFC 5321 Section 4.5.5 for more
  113. * details.
  114. */
  115. curl_easy_setopt(curl, CURLOPT_MAIL_FROM, FROM);
  116. /* Add two recipients, in this particular case they correspond to the
  117. * To: and Cc: addressees in the header, but they could be any kind of
  118. * recipient. */
  119. recipients = curl_slist_append(recipients, TO);
  120. recipients = curl_slist_append(recipients, CC);
  121. curl_easy_setopt(curl, CURLOPT_MAIL_RCPT, recipients);
  122. /* We're using a callback function to specify the payload (the headers and
  123. * body of the message). You could just use the CURLOPT_READDATA option to
  124. * specify a FILE pointer to read from. */
  125. curl_easy_setopt(curl, CURLOPT_READFUNCTION, payload_source);
  126. curl_easy_setopt(curl, CURLOPT_READDATA, &upload_ctx);
  127. curl_easy_setopt(curl, CURLOPT_UPLOAD, 1L);
  128. /* Since the traffic will be encrypted, it is very useful to turn on debug
  129. * information within libcurl to see what is happening during the transfer.
  130. */
  131. curl_easy_setopt(curl, CURLOPT_VERBOSE, 1L);
  132. /* Send the message */
  133. res = curl_easy_perform(curl);
  134. /* Check for errors */
  135. if(res != CURLE_OK)
  136. fprintf(stderr, "curl_easy_perform() failed: %s\n",
  137. curl_easy_strerror(res));
  138. /* Free the list of recipients */
  139. curl_slist_free_all(recipients);
  140. /* Always cleanup */
  141. curl_easy_cleanup(curl);
  142. }
  143. return (int)res;
  144. }