aboutsummaryrefslogtreecommitdiff
path: root/docs/examples/smtp-mail.c
diff options
context:
space:
mode:
authorSteve Holme <steve_holme@hotmail.com>2014-01-05 17:50:14 +0000
committerSteve Holme <steve_holme@hotmail.com>2014-01-05 17:51:18 +0000
commit149e0c8d104bf6b924e68902c2029c009b6be93d (patch)
treecce10fa4fe65a2c2ae98ffecadff91ac3dc8e746 /docs/examples/smtp-mail.c
parent0f4bf77bd378e51f0c51de5444dfd396c23ee6bf (diff)
Examples: Renamed SMTP MAIL example to match other email examples
Diffstat (limited to 'docs/examples/smtp-mail.c')
-rw-r--r--docs/examples/smtp-mail.c94
1 files changed, 94 insertions, 0 deletions
diff --git a/docs/examples/smtp-mail.c b/docs/examples/smtp-mail.c
new file mode 100644
index 000000000..a76af2289
--- /dev/null
+++ b/docs/examples/smtp-mail.c
@@ -0,0 +1,94 @@
+/***************************************************************************
+ * _ _ ____ _
+ * Project ___| | | | _ \| |
+ * / __| | | | |_) | |
+ * | (__| |_| | _ <| |___
+ * \___|\___/|_| \_\_____|
+ *
+ * Copyright (C) 1998 - 2014, Daniel Stenberg, <daniel@haxx.se>, et al.
+ *
+ * This software is licensed as described in the file COPYING, which
+ * you should have received as part of this distribution. The terms
+ * are also available at http://curl.haxx.se/docs/copyright.html.
+ *
+ * You may opt to use, copy, modify, merge, publish, distribute and/or sell
+ * copies of the Software, and permit persons to whom the Software is
+ * furnished to do so, under the terms of the COPYING file.
+ *
+ * This software is distributed on an "AS IS" basis, WITHOUT WARRANTY OF ANY
+ * KIND, either express or implied.
+ *
+ ***************************************************************************/
+#include <stdio.h>
+#include <string.h>
+#include <curl/curl.h>
+
+/* This is a simple example showing how to send mail using libcurl's SMTP
+ * capabilities. For an exmaple of using the multi interface please see
+ * smtp-multi.c.
+ */
+
+int main(void)
+{
+ CURL *curl;
+ CURLcode res;
+ struct curl_slist *recipients = NULL;
+
+ /* value for envelope reverse-path */
+ static const char *from = "<bradh@example.com>";
+
+ /* this becomes the envelope forward-path */
+ static const char *to = "<bradh@example.net>";
+
+ curl = curl_easy_init();
+ if(curl) {
+ /* This is the URL for your mailserver */
+ curl_easy_setopt(curl, CURLOPT_URL, "smtp://mail.example.com");
+
+ /* Note that this option isn't strictly required, omitting it will result in
+ * libcurl will sent the MAIL FROM command with no sender data. All
+ * autoresponses should have an empty reverse-path, and should be directed
+ * to the address in the reverse-path which triggered them. Otherwise, they
+ * could cause an endless loop. See RFC 5321 Section 4.5.5 for more details.
+ */
+ curl_easy_setopt(curl, CURLOPT_MAIL_FROM, from);
+
+ /* Note that the CURLOPT_MAIL_RCPT takes a list, not a char array. */
+ recipients = curl_slist_append(recipients, to);
+ curl_easy_setopt(curl, CURLOPT_MAIL_RCPT, recipients);
+
+ /* You provide the payload (headers and the body of the message) as the
+ * "data" element. There are two choices, either:
+ * - provide a callback function and specify the function name using the
+ * CURLOPT_READFUNCTION option; or
+ * - just provide a FILE pointer that can be used to read the data from.
+ * The easiest case is just to read from standard input, (which is available
+ * as a FILE pointer) as shown here.
+ */
+ curl_easy_setopt(curl, CURLOPT_READDATA, stdin);
+ curl_easy_setopt(curl, CURLOPT_UPLOAD, 1L);
+
+ /* send the message (including headers) */
+ res = curl_easy_perform(curl);
+
+ /* Check for errors */
+ if(res != CURLE_OK)
+ fprintf(stderr, "curl_easy_perform() failed: %s\n",
+ curl_easy_strerror(res));
+
+ /* free the list of recipients */
+ curl_slist_free_all(recipients);
+
+ /* curl won't send the QUIT command until you call cleanup, so you should be
+ * able to re-use this connection for additional messages (setting
+ * CURLOPT_MAIL_FROM and CURLOPT_MAIL_RCPT as required, and calling
+ * curl_easy_perform() again. It may not be a good idea to keep the
+ * connection open for a very long time though (more than a few minutes may
+ * result in the server timing out the connection), and you do want to clean
+ * up in the end.
+ */
+ curl_easy_cleanup(curl);
+ }
+
+ return 0;
+}