Apologies, upon further investigation, this issue turned out to be an issue with the IMAP/SMTP bridge application that my mail provider requires. It had changed credentials during my testing for reasons I don't yet understand, and I will continue that investigation off this list. After securing new credentials, isync works as expected. Thank you for your time.
------- Original Message ------- On Wednesday, April 20th, 2022 at 4:59 PM, Oswald Buddenhagen <oswald.buddenha...@gmx.de> wrote: > > > On Wed, Apr 20, 2022 at 08:29:35PM +0000, Lander M. Kerbey via isync-devel > wrote: > > > Let's say that the password in plaintext is PASSWORD. The command > > quoted for PassCmd will, when entered in my terminal, print PASSWORD to > > stdout. I have also confirmed, by replacing the PassCmd line with the > > following . . . > > > > Pass PASSWORD > > > > . . . that PASSWORD indeed works: with that configuration in place, > > mbsync -a syncs with the account with no problems. I've tried running > > isync both within and after gpg's caching period to see if it was the > > passphrase requirement on my gpg key that was the issue, and the > > behavior is the same. > > dunno. try strace'ing the whole thing (maybe with -f for better effect). _______________________________________________ isync-devel mailing list isync-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/isync-devel
