curl:perform_imap_queries_using_curl
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revision | |||
| curl:perform_imap_queries_using_curl [2020/09/25 13:00] – 192.168.1.1 | curl:perform_imap_queries_using_curl [2020/09/25 13:02] (current) – 192.168.1.1 | ||
|---|---|---|---|
| Line 36: | Line 36: | ||
| Here we see that we've connected, and received a list of folders, including " | Here we see that we've connected, and received a list of folders, including " | ||
| - | If your mail-server is running over SSL then instead of using **imap://** you should set the schema to **imaps:// | + | If your mail-server is running over SSL then instead of using **< |
| This would look like so: | This would look like so: | ||
| Line 48: | Line 48: | ||
| ===== Discovering Messages ===== | ===== Discovering Messages ===== | ||
| - | With the previous example we looked at listing mailboxes. | + | With the previous example we looked at listing mailboxes. |
| + | |||
| + | To fetch a message we need the identifier of the message to fetch - so we need to find out how many messages exist, as message-IDs are sequential. | ||
| To see how many messages exist in the folder " | To see how many messages exist in the folder " | ||
| Line 134: | Line 136: | ||
| The reason for avoiding custom-requests where possible is that when you're using the curl API programatically you'll discover that responses are not decoded - which is a known issue. | The reason for avoiding custom-requests where possible is that when you're using the curl API programatically you'll discover that responses are not decoded - which is a known issue. | ||
| - | In the example above we'd have received zero output unless/ | + | In the example above we'd have received zero output unless/ |
| ---- | ---- | ||
curl/perform_imap_queries_using_curl.1601038819.txt.gz · Last modified: 2020/09/25 13:00 by 192.168.1.1