DatuX

I think this is the problem in /usr/local/bin/imapsync_runner.pl ``` ... ($timeout1 gt "0" ? () : ('--timeout1', $timeout1)), ($timeout2 gt "0" ? () : ('--timeout2', $timeout2)), ... ``` It does...

i'm talking about the sync jobs via mailcow GUI (which in turn starts imapsync)

That default field is igored as well. So its 120s (imapsyncs default ), which is too slow for my 800.000 mail source server.

If its not planned, then remove the option!

oh oops i didnt pay attention, only saw the mail and a "not planned" :)

i'm also trying to do this. i tried to unpack the .apk and .aia files , but i couldnt find anything usefull.

i think the lowlevel stuff is in de esp32, but the app has the id's etc. it would be nice if someone would have a list of al the ID's...

Thats a good point, we will add that.

yeah, the buffer was designed to be the last in the pipe, never expecting this usecase. :) its documented here: https://github.com/psy0rz/zfs_autobackup/wiki/Piping#putting-it-all-together i have to think about it, it might be...

You could also solve this by using multiple —send-pipe commands? And have the first one be mbuffer (and omit —buffer)