Description of problem: Mbsync is chatty even with -qq, making it unsuitable for running in cron jobs $ mbsync -a -qq > /dev/null IMAP warning: SSL support not available *** IMAP Warning *** Password is being sent in the clear IMAP error: malformed SEARCH response IMAP error: malformed SEARCH response IMAP warning: SSL support not available *** IMAP Warning *** Password is being sent in the clear IMAP warning: SSL support not available *** IMAP Warning *** Password is being sent in the clear IMAP warning: SSL support not available *** IMAP Warning *** Password is being sent in the clear IMAP warning: SSL support not available *** IMAP Warning *** Password is being sent in the clear Version-Release number of selected component (if applicable): isync-1.0.3-4.fc9.x86_64
Nicolas, Thanks for the report! Problem is that mbsync does not use getopt() for parsing command line arguments and treats '-qq' as single '-q'. Therefore the workaround for you is to use '-q -q' and mbsync should be quiet. Please let me know if it solved your problem and if mbsync is quiet then. I'll try to inspect how hard would it be to teach mbsync use getopt or modify it to understand multiple single letter options with a single dash, or eventually adjust the documentation.
Not. I shamelessly lied. mbsync was ignoring all but first one-letter option from the last argument. The fix is in CVS and is building in koji as isync-1.0.3-5.fc9 [1]. Please test the fix and confirm if it solves your problem and doesn't break anything else for you. Thanks! [1] http://koji.fedoraproject.org/koji/taskinfo?taskID=295913
This one is better but I still get $ mbsync -qq -a IMAP error: malformed SEARCH response And IIRC gmail is causing this, so it's going to hit a lot of people
Thanks for the feedback, Nicholas. I assume this is not to be quietened by -q as it is not a warning but an error. I do not have a gmail account and I am wondering if it really violates IMAP (I did not even know gmail supports IMAP), or mbsync just misunderstands something. Could you please run mbsync with -V argument and paste/attach the relevant part of the IMAP conversation? (Please don't forget to double check that it doesn't contain password and other private data before you paste, though mbsync should attempt to remove those from the log)
Nicolas: This problem seems like one that is reported in bug #420721. I'll close this bug now, make an updated package, and add a note there.