Journeyman

Using a Google Nexus Pixel 4a and gMTP 3.11 (Debian package) I cannot upload files with a question mark in the name. Here what I see in the console: $ gmtp Device 0 (VID=18d1 and PID=4ee1) is a Google Inc Nexus/Pixel (MTP). Android device detected, assigning default bug flags Error sending file /home/me/file?.txt. Error 2: PTP Layer error 2002: LIBMTP_Send_File_From_File_Descriptor(): Could not send object. Error 2: Error 2002: PTP General Error Renaming the file and removing the '?' before uploading...

i can't imagine that this error was actually not printed. maybe you redirected only stdout and forgot about stderr? I stand corrected. You're right, the error appears on stderr. I guess I got confused and didn't notice. note that the Store's Path is expected to exist; only actual mailboxes are created on demand. ok, now I understand. My expectation was that mbsync could create the entire tree of directories starting from the root ~/.local/mail. Fair enough. thanks for your quick and detailed help!...

i can't imagine that this error was actually not printed. maybe you redirected only stdout and forgot about stderr? I stand corrected. You're right, the error appears on stderr. I guess I got confused and didn't notice. note that the Store's Path is expected to exist; only actual mailboxes are created on demand. ok, now I understand. My expectation was that mbsync could create the entire tree of directories starting from the root ~/.local/mail. Fair enough. thanks for your quick and detailed hel...

ah thanks for the tip. Running with --debug showed and interesting error: $ src/mbsync --debug --create --config ~/.config/isync/mbsyncrc -a Reading configuration file /home/$USER/.config/isync/mbsyncrc Notice: Master/Slave are deprecated; use Far/Near instead. Channel catchall-mydomain.com-inbox Opening far side store catchall-mydomain.com-remote... F: [ 1] Enter connect_store Resolving mail.mydomain.com... ok Connecting to mail.mydomain.com (a.b.c.d:993)... F: [ 1] Leave connect_store Opening near...

ah thanks for the tip. Running with --debug showed and interesting error: $ src/mbsync --debug --create --config ~/.config/isync/mbsyncrc -a Reading configuration file /home/$USER/.config/isync/mbsyncrc Notice: Master/Slave are deprecated; use Far/Near instead. Channel catchall-mydomain.com-inbox Opening far side store catchall-mydomain.com-remote... F: [ 1] Enter connect_store Resolving mail.mydomain.com... ok Connecting to mail.mydomain.com (a.b.c.d:993)... F: [ 1] Leave connect_store Opening near...

ah thanks for the tip. Running with --debug showed and interesting error: $ src/mbsync --debug --create --config ~/.config/isync/mbsyncrc -a Reading configuration file /home/$USER/.config/isync/mbsyncrc Notice: Master/Slave are deprecated; use Far/Near instead. Channel catchall-mydomain.com-inbox Opening far side store catchall-mydomain.com-remote... F: [ 1] Enter connect_store Resolving mail.mydomain.com... ok Connecting to mail.mydomain.com (a.b.c.d:993)... F: [ 1] Leave connect_store Opening near...

If you spot anything else weird in my config, please let me know. It's the first time I use mbsync.

ah thanks for the tip. Running with --debug showed and interesting error: $ src/mbsync --debug --create --config ~/.config/isync/mbsyncrc -a Reading configuration file /home/$USER/.config/isync/mbsyncrc Notice: Master/Slave are deprecated; use Far/Near instead. Channel catchall-mydomain.com-inbox Opening far side store catchall-mydomain.com-remote... F: [ 1] Enter connect_store Resolving mail.mydomain.com... ok Connecting to mail.mydomain.com (a.b.c.d:993)... F: [ 1] Leave connect_store Opening near...