commit 9b72e1032026215cbce2daa0bce9bfe342eac58b
parent 3aead3300865b33b086f12961621d655a16bd6c2
Author: Oswald Buddenhagen <ossi@users.sf.net>
Date: Thu, 5 May 2022 11:33:08 +0200
make IMAP error messages less confusing
don't print the status, as the user doesn't really care whether it's
NO or BAD. more importantly, "NO LOGIN failed" is a rather misleading
thing to report.
Diffstat:
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/src/drv_imap.c b/src/drv_imap.c
@@ -1904,13 +1904,13 @@ imap_socket_read( void *aux )
resp = RESP_CANCEL;
}
}
- error( "IMAP command '%s' returned an error: %s %s\n",
+ error( "IMAP command '%s' returned an error: %s\n",
starts_with( cmdp->cmd, -1, "LOGIN", 5 ) ?
"LOGIN <user> <pass>" :
starts_with( cmdp->cmd, -1, "AUTHENTICATE PLAIN", 18 ) ?
"AUTHENTICATE PLAIN <authdata>" :
cmdp->cmd,
- arg, cmd ? cmd : "" );
+ cmd ? cmd : "<unspecified>" );
}
doresp:
if ((resp2 = parse_response_code( ctx, cmdp, cmd )) > resp)