|
4 | 4 |
|
5 | 5 |  
|
6 | 6 |
|
7 |
| -The fast and lightweight async Email client library for Arduino. |
| 7 | +The fast and lightweight async email client library for Arduino. |
8 | 8 |
|
9 | 9 | This library seamlessly works in async and await modes. The chunk data is processed for decodings, encodings, parsing, uploading and downloading.
|
10 | 10 |
|
11 |
| -For sending Email, the typical inline images and attachments plus the RFC 822 messages are supported. |
| 11 | +For sending email, the typical inline images and attachments plus the RFC 822 messages are supported. |
12 | 12 |
|
13 |
| -For fetching Email, this library provides the ready to use decoded data (headers, text body and attchments) for downloading and post processing. |
| 13 | +For fetching email, this library provides the ready to use decoded data (headers, text body and attchments) for downloading and post processing. |
14 | 14 |
|
15 | 15 | This library supports all 32-bit `Arduino` devices e.g. `STM32`, `SAMD`, `ESP32`, `ESP8266`, `Raspberry Pi RP2040`, and `Renesas` devices except for 8-bit `Atmel's AVR` devices.
|
16 | 16 |
|
17 | 17 |
|
18 |
| -## Email Sending |
| 18 | +## Send Email |
19 | 19 |
|
20 |
| -To send an Email message, user needs to defined the `SMTPClient` and `SMTPMessage` class objects. |
| 20 | +To send an email message, user needs to defined the `SMTPClient` and `SMTPMessage` class objects. |
21 | 21 |
|
22 |
| -The one of SSL client if you are sending Email over SSL/TLS or basic network client should be set for the `SMTPClient` class constructor. |
| 22 | +The one of SSL client if you are sending email over SSL/TLS or basic network client should be set for the `SMTPClient` class constructor. |
23 | 23 |
|
24 | 24 | Note that the SSL client or network client assigned to the `SMTPClient` class object should be lived in the `SMTPClient` class object usage scope otherwise the error can be occurred.
|
25 | 25 |
|
@@ -146,7 +146,7 @@ In some Arduino devices that work with `WiFiNINA/WiFi101` firmwares, use `SMTPMe
|
146 | 146 |
|
147 | 147 | **Half Line-Break**
|
148 | 148 |
|
149 |
| -Depending on server policy, some SMTP server may reject the Email sending when the Lf (line feed) was used for line break in the content instead of CrLf (Carriage return + Line feed). |
| 149 | +Depending on server policy, some SMTP server may reject the email sending when the Lf (line feed) was used for line break in the content instead of CrLf (Carriage return + Line feed). |
150 | 150 |
|
151 | 151 | Then we recommend using CrLf instead of Lf in the content to avoid this issue.
|
152 | 152 |
|
@@ -229,9 +229,13 @@ The `SMTPCommandResponse::statusCode` value provides the SMTP server response co
|
229 | 229 | The [Command.ino](/examples/Sending/Command/Command.ino) example showed how to use `SMTPClient::sendCommand()` to work with flags, message and folder or mailbox.
|
230 | 230 |
|
231 | 231 |
|
232 |
| -## Email Reading |
| 232 | +## Receive Email |
233 | 233 |
|
234 |
| -To receive or fetch the Email, only `IMAPClient` calss object is required. |
| 234 | +The IMAP protocol supports fetching, searching and idling. The idle and fetch functions can be used to get the incoming email alert. |
| 235 | +
|
| 236 | +While serach function with keywords also provides the mean to get the specific messages that match the search criteria e.g. unread, new, and flagged messages. |
| 237 | +
|
| 238 | +To search, receive or fetch the email, only `IMAPClient` calss object is required. |
235 | 239 |
|
236 | 240 | The `IMAPDataCallback` and `FileCallback` functions can be assigned to the `IMAPClient::fetch` and `IMAPClient::fetchUID` functions.
|
237 | 241 |
|
@@ -292,7 +296,7 @@ if (imap.isConnected())
|
292 | 296 |
|
293 | 297 | The library provides the simple IMAP APIs for idling (mailbox polling), searching and fetching the messages. If additional works are needed e.g. setting and deleting flags, or creating, moving and deleting folder, or copying, moving and deleting mssage etc., those taks can be done through the `IMAPClient::sendCommand()`.
|
294 | 298 |
|
295 |
| -The [Command.ino](/examples/Reading/Command/Command.ino) example show how to do those works. The server responses from sending the command will be discussed in the [IMAP Custom Comand Processing Information](#imap-custom-comand-processing-information) section below. |
| 299 | +The [Command.ino](/examples/Reading/Command/Command.ino) example shows how to do those works. The server responses from sending the command will be discussed in the [IMAP Custom Comand Processing Information](#imap-custom-comand-processing-information) section below. |
296 | 300 |
|
297 | 301 |
|
298 | 302 | ### IMAP Processing Information
|
|
0 commit comments