Re: Finding offending message that breaks the Sender/From requirement

Oswald Buddenhagen writes: > On Sun, Jul 16, 2023 at 02:05:51AM +, hus...@alshehhi.io wrote: >> Is there a way to find the offending message? > probably the easiest way is to add -DN to the mbsync arguments. then you > can directly grep for the message's content. Thank you. -DN does the

Re: Finding offending message that breaks the Sender/From requirement

On Sun, Jul 16, 2023 at 02:05:51AM +, hus...@alshehhi.io wrote: Is there a way to find the offending message? probably the easiest way is to add -DN to the mbsync arguments. then you can directly grep for the message's content. regards ___

Re: Finding offending message that breaks the Sender/From requirement

Hello. On Sun, Jul 16, 2023 at 02:05:51AM +, hus...@alshehhi.io wrote: > Warning: lost track of 39 pushed message(s) BTW, this is a hit about sync problems... > Synchronizing... > Notice: far side store does not support flag(s) 'P'; not propagating. > C: 0/1 B: 1/7 F: +0/39 *0/0 #0/0

Finding offending message that breaks the Sender/From requirement

Hello, When running mbsync -a --verbose I am receiving the following message: $ mbsync -a --verbose Reading configuration file /home/husain/.mbsyncrc C: 0/1 B: 0/0 F: +0/0 *0/0 #0/0 N: +0/0 *0/0 #0/0 Channel Opening far side store ... Resolving ... ok Connecting to ()... Opening near side