PassCmd: gpg piped into awk results in 'NO backend/credentials: incorrect password' error

[Lander M. K. <lan...@pr...>]

I'm using isync version 1.4.4 on Arch Linux.

The following is the relevant chunk of my .mbsyncrc:

IMAPAccount use...@ma...
Host imap.host.domain
Port 1143
User use...@ma...
PassCmd "gpg -q -d ~/.authinfo.gpg | awk 'FNR == 1 {printf $8}'"
AuthMechs Login
SSLType NONE

mbsync -a currently returns the following:

IMAP command 'LOGIN <user> <pass>' returned an error: NO backend/credentials: incorrect password

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.

I have seen a user with a similar issue get things working with sed, but it appeared to be an issue with escapes. I took this clue and replaced what was previously a 'print' command in my awk with a 'printf' command on suspicion that a newline character might be causing my trouble, but I still get the same error.