1 /***************************************************************************
3 * Project ___| | | | _ \| |
5 * | (__| |_| | _ <| |___
6 * \___|\___/|_| \_\_____|
8 * Copyright (C) 1998 - 2017, Daniel Stenberg, <daniel@haxx.se>, et al.
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.
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.
18 * This software is distributed on an "AS IS" basis, WITHOUT WARRANTY OF ANY
19 * KIND, either express or implied.
21 ***************************************************************************/
24 * Send e-mail with SMTP
30 #include <curl/curl.h>
33 * For an SMTP example using the multi interface please see smtp-multi.c.
36 /* The libcurl options want plain addresses, the viewable headers in the mail
37 * can very well get a full name as well.
39 #define FROM_ADDR "<sender@example.org>"
40 #define TO_ADDR "<addressee@example.net>"
41 #define CC_ADDR "<info@example.org>"
43 #define FROM_MAIL "Sender Person " FROM_ADDR
44 #define TO_MAIL "A Receiver " TO_ADDR
45 #define CC_MAIL "John CC Smith " CC_ADDR
47 static const char *payload_text[] = {
48 "Date: Mon, 29 Nov 2010 21:54:29 +1100\r\n",
49 "To: " TO_MAIL "\r\n",
50 "From: " FROM_MAIL "\r\n",
51 "Cc: " CC_MAIL "\r\n",
52 "Message-ID: <dcd7cb36-11db-487a-9f3a-e652a9458efd@"
53 "rfcpedant.example.org>\r\n",
54 "Subject: SMTP example message\r\n",
55 "\r\n", /* empty line to divide headers from body, see RFC5322 */
56 "The body of the message starts here.\r\n",
58 "It could be a lot of lines, could be MIME encoded, whatever.\r\n",
63 struct upload_status {
67 static size_t payload_source(void *ptr, size_t size, size_t nmemb, void *userp)
69 struct upload_status *upload_ctx = (struct upload_status *)userp;
72 if((size == 0) || (nmemb == 0) || ((size*nmemb) < 1)) {
76 data = payload_text[upload_ctx->lines_read];
79 size_t len = strlen(data);
80 memcpy(ptr, data, len);
81 upload_ctx->lines_read++;
92 CURLcode res = CURLE_OK;
93 struct curl_slist *recipients = NULL;
94 struct upload_status upload_ctx;
96 upload_ctx.lines_read = 0;
98 curl = curl_easy_init();
100 /* This is the URL for your mailserver */
101 curl_easy_setopt(curl, CURLOPT_URL, "smtp://mail.example.com");
103 /* Note that this option isn't strictly required, omitting it will result
104 * in libcurl sending the MAIL FROM command with empty sender data. All
105 * autoresponses should have an empty reverse-path, and should be directed
106 * to the address in the reverse-path which triggered them. Otherwise,
107 * they could cause an endless loop. See RFC 5321 Section 4.5.5 for more
110 curl_easy_setopt(curl, CURLOPT_MAIL_FROM, FROM_ADDR);
112 /* Add two recipients, in this particular case they correspond to the
113 * To: and Cc: addressees in the header, but they could be any kind of
115 recipients = curl_slist_append(recipients, TO_ADDR);
116 recipients = curl_slist_append(recipients, CC_ADDR);
117 curl_easy_setopt(curl, CURLOPT_MAIL_RCPT, recipients);
119 /* We're using a callback function to specify the payload (the headers and
120 * body of the message). You could just use the CURLOPT_READDATA option to
121 * specify a FILE pointer to read from. */
122 curl_easy_setopt(curl, CURLOPT_READFUNCTION, payload_source);
123 curl_easy_setopt(curl, CURLOPT_READDATA, &upload_ctx);
124 curl_easy_setopt(curl, CURLOPT_UPLOAD, 1L);
126 /* Send the message */
127 res = curl_easy_perform(curl);
129 /* Check for errors */
131 fprintf(stderr, "curl_easy_perform() failed: %s\n",
132 curl_easy_strerror(res));
134 /* Free the list of recipients */
135 curl_slist_free_all(recipients);
137 /* curl won't send the QUIT command until you call cleanup, so you should
138 * be able to re-use this connection for additional messages (setting
139 * CURLOPT_MAIL_FROM and CURLOPT_MAIL_RCPT as required, and calling
140 * curl_easy_perform() again. It may not be a good idea to keep the
141 * connection open for a very long time though (more than a few minutes
142 * may result in the server timing out the connection), and you do want to
143 * clean up in the end.
145 curl_easy_cleanup(curl);