Sample sketches issue an error at 8266 ESP12 #335
-
Hi there
|
Beta Was this translation helpful? Give feedback.
Replies: 4 comments 4 replies
-
You should see the latest library examples and follow it because the breaking changes of API since v3.0.0. For small memory device as ESP8266, you should be aware of it requires 16k+ memory reserved for BearSSL engine to work with iMAP protocol that fragmentation does not support. This left only 10k+ remaining heap for your other code. You should consider to use ESP32 or RaspberryPi Pico W that has much memory. |
Beta Was this translation helpful? Give feedback.
-
For all IMAP examples with ESP8266 test, it can run without the any issue in Wemos D1 mini and NodeMCU. Then the answer to your question is no. |
Beta Was this translation helpful? Give feedback.
-
You can choose "Generic ESP8266 Module" instead. You can check the free heap anywhere in your code or using this helper class to track your free heap to check the memory leaks situation. The option to store the IMAP result temporary in IMAP session. ESP-Mail-Client/examples/IMAP/Search_And_Read/Search_And_Read.ino Lines 157 to 172 in bda5e84 In some critical case, you can disable those options (left only header to be stored) and store the result in flash or sd instead. I don't know what happen in your case, but I test with Wemos D1 mini pro and it works fine with all example code without any option modification unless the WiFi and login credentials. |
Beta Was this translation helpful? Give feedback.
-
After investigation, it is my false that I ever though that SSL fragmentation in IMAP is not support or not possible once testing many years ago since v3.x,x development. The issue at that time may be related to the core sdk instead of SSL fragmentation issue as I understand. Now you can set the SSL buffer size lower than the default IMAP setting value (16k) to gain more free memory. You can use
|
Beta Was this translation helpful? Give feedback.
After investigation, it is my false that I ever though that SSL fragmentation in IMAP is not support or not possible once testing many years ago since v3.x,x development.
The issue at that time may be related to the core sdk instead of SSL fragmentation issue as I understand.
Now you can set the SSL buffer size lower than the default IMAP setting value (16k) to gain more free memory.
You can use
setSSLBufferSize (<rx_buffer_size>, <tx_buffer_size>)
beforeimap.connect
in the setup like the following.imap.setSSLBufferSize(2048, 1024);