Ignore "ERR_APPEND"

[ggrigon]

Hello,

I'm doing a transfer where there are a lot of ERR_APPEND.

But once it happens, the transfer stops like:

Err 1/1: - msg INBOX/61713 {13144100} could not append ( Subject:[ENC: XPTO], Date:["11-Jul-2023 21:06:07 -0300"], Size:[13144100], Flags:[\Seen] ) to folder INBOX: Error appending message: Write failed 'Connection reset by peer'
The most frequent error is ERR_APPEND.
Exiting with return value 114 (EXIT_ERR_APPEND) 1/50 nb_errors/max_errors PID 481136
Removing pidfile /tmp/imapsync.pid

I didn't find out a way to just ignore these errors and keep the transfer running.

[gilleslamiral]

Does the transfer stop just after this error?

[ggrigon]

Yes, it keeps running for a while (some minutes, then stop).

Trying another approach and using --debugimap1 I found it's related to the max size on the destination server.
But even increasing the max size for messagens on the host2 (Exim Server), keep getting this error:

- msg INBOX/63869 {1946602} could not append ( Subject:[MANUAL], Date:["27-Sep-2023 10:58:25 -0300"], Size:[1946602], Flags:[\Seen] ) to folder INBOX: Error appending message: Write failed 'Connection reset by peer'

By default, even with this error, it shouldn't keep running, until reach the max errors (default 50)?

[ggrigon]

There's a more complete log for the error:

Received ret=1460 18320080 of 18326510
Received ret=2920 18323000 of 18326510
Received ret=3510 18326510 of 18326510
Read:   * 1 FETCH (UID 1 BODY[]         )
        22 OK FETCH completed.
internal date from host1: [28-Mar-2022 15:07:47 -0300]
internal date from host1: ["28-Mar-2022 15:07:47 -0300"] (fixed)
Host1: flags init msg INBOX.XXXXX/1 date ["28-Mar-2022 15:07:47 -0300"] flags [\Seen] size [18326510]
Host1: flags filt msg INBOX.XXXXXX/1 date ["28-Mar-2022 15:07:47 -0300"] flags [\Seen] size [18326510]
- msg INBOX.XXXXX/1 {18326510} could not append ( Subject:[XXXXX.], Date:["28-Mar-2022 15:07:47 -0300"], Size:[18326510], Flags:[\Seen] ) to folder INBOX.XXXXX: Error appending message: Write failed 'Connection reset by peer'
++++ End looping on each folder
Time: 155.521941900253 s
0.65 + 0.22 + 0.01 + 0.05 = 0.93 ~ 0.93
cpu_percent: 0.6
cpu_percent_global: 0.0
++++ Statistics
Transfer started on                     : Monday 04 March 2024-03-04 21:20:17 -0300 -03
Transfer ended on                       : Monday 04 March 2024-03-04 21:23:03 -0300 -03
Transfer time                           : 166.6 sec
Folders synced                          : 3/242 synced
Messages transferred                    : 0
Messages skipped                        : 8
Messages found duplicate on host1       : 3
Messages found duplicate on host2       : 0
Messages found crossduplicate on host2  : 0
Messages void (noheader) on host1       : 0
Messages void (noheader) on host2       : 0
Messages found in host1 not in host2    : 397 messages
Messages found in host2 not in host1    : 5 messages
Messages deleted on host1               : 0
Messages deleted on host2               : 0
Total bytes transferred                 : 0 (0.000 KiB)
Total bytes skipped                     : 1035204 (0.987 MiB)
Message rate                            : 0.0 messages/s
Average bandwidth rate                  : 0.0 KiB/s
Reconnections to host1                  : 0
Reconnections to host2                  : 2
Memory consumption at the end           : 232.1 MiB (*time 10.7 MiB*h) (started with 163.5 MiB)
System load: 0.40 0.47 0.53 4/1221
Load end is                             : 0.40 0.47 0.53 4/1221 on 16 cores
CPU time and %cpu                       : 0.93 sec 0.6 %cpu 0.0 %allcpus
Biggest message transferred             : 0 bytes (0.000 KiB)
Memory/biggest message ratio            : NA
nb_keys h1_folders_of_md5 397
nb_keys h2_folders_of_md5 5
The sync is not finished, there are 397 among 397 identified messages in host1 that are not on host2.
There is no unidentified message on host1.
The sync is not strict, there are 5 among 5 identified messages in host2 that are not on host1. Use --delete2 and sync again to delete them and have a strict sync.
Detected 1 errors
Check if a new imapsync release is available by adding --releasecheck
Homepage: https://imapsync.lamiral.info/
++++ Listing 1 errors encountered during the sync ( avoid this listing with --noerrorsdump ).
Err 1/1: - msg INBOX.XXXXX/1 {18326510} could not append ( Subject:[XXXXX.], Date:["28-Mar-2022 15:07:47 -0300"], Size:[18326510], Flags:[\Seen] ) to folder INBOX.XXXXX: Error appending message: Write failed 'Connection reset by peer'
The most frequent error is ERR_APPEND.
Sending: 23 LOGOUT
Sent 11 bytes
Read:   * BYE Courier-IMAP server shutting down
        23 OK LOGOUT completed

[gilleslamiral]

Trying another approach and using --debugimap1 I found it's related to the max size on the destination server.

Ok, but you're good because --debugimap1 debugs the IMAP source server dialog with imapsync, --debugimap2 debugs the destination dialog.