On Wed, May 29, 2019 at 11:43:28AM -0500, Chip Senkbeil wrote:
> I'm assuming there is no configuration that can be set to ignore this
> violation, right?
>
there isn't.
once upon a time someone posted a patch to deal with some kind of invlid
messages, and it could have been about that. however, t
Great! Removing the Yubico emails (others had the same issue) resolved my
problem. I'll contact them later to let them know about the problem, but not
sure if I'll get any response from them.
I'm assuming there is no configuration that can be set to ignore this
violation, right? I have a path I
On Tue, May 28, 2019 at 05:57:04PM -0500, Chip Senkbeil wrote:
> I've attached the log, which dumps a large HTML blob where I've
> removed my address and such.
>
there is an @import line near the top which contains two null
characters, which certainly got there due to automatic hard line
wrapping
Seems to land on a purchase from Yubico I made as the latest culprit.
This is from running PipelineDepth of 1 and using -DN --push with my
channel of Personal-INBOX.
I've attached the log, which dumps a large HTML blob where I've
removed my address and such.
Specifically ran `mbsync -DN --push Pe
On Tue, May 28, 2019 at 09:32:30AM -0500, Chip Senkbeil wrote:
> M: >>> 7 APPEND "INBOX" {35145}
> [...]
> M: + go ahead
> M: * BYE Invalid character in literal
> IMAP error: unexpected BYE response: Invalid character in literal
>
the local message it is trying to upload contains a character that's
