Re: duplicates due to X-TUID headers

[Peter P.]

* Bence Ferdinandy  [2024-03-15 08:41]:
> 2024. márc. 15. 8:16:53 Evgeniy Berdnikov :
> 
> > On Fri, Mar 15, 2024 at 07:42:32AM +0100, Peter P. wrote:
> > > Do you have any recommendataion how I could de-duplicate messages with
> > > missing message-ids?
> > 
> > You have better to remove them all.
> > 
> > for f in /path/to/mailbox/* ; do
> >  if [ ! grep -is '^Message-id:' $f ] ; then
> >     rm -f $f
> >  fi
> > done
> > --
> > Eugene Berdnikov
> 
> I think you can tell mail dedup to not use message-id-s when checking
> duplicates
> 
> https://github.com/kdeldycke/mail-deduplicate

Thank you Oswald, Evgeniy, Bence,

I will look at your recommendations and report back in a while.

best, Peter



___
isync-devel mailing list
isync-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/isync-devel

Re: duplicates due to X-TUID headers

[Peter P.]

* Oswald Buddenhagen via isync-devel  
[2024-03-13 12:57]:
> On Wed, Mar 13, 2024 at 12:40:21PM +0100, Peter P. wrote:
> > These duplicates are not detected by (neo)mutt's ~= filter since some
> > of these messages contain a X-TUID header, others do not.
> > 
> that's just wrong. mutt goes by the message-id header and nothing else.
Thanks for correcting me Oswald! 

I re-checked and the duplicated messages are in fact lacking a message-id
header. I don't know why and how they got removed.

Do you have any recommendataion how I could de-duplicate messages with
missing message-ids?

Much appreciated,
Peter


___
isync-devel mailing list
isync-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/isync-devel

duplicates due to X-TUID headers

[Peter P.]

Hi list,

I just discovered that I am having lotsa duplicate emails in my near
side folders after some heavy re-syncing with mbsync. These duplicates
are not detected by (neo)mutt's ~= filter since some of these messages
contain a X-TUID header, others do not.

I am interested how/why these headers got introduced, and how I can
avoid this in the future.

Furthermore, some webpages suggest some sed magic[1] to remove these
X-TUID headers to be able to remove duplicates. Will mbsync have any
issues when these headers are removed, and duplicates are removed on the
near side?

Thank you!
Peter

[1]
https://edd.salkield.uk/blog/2022/11/09/deduplicating_your_mbsync_maildir.html
https://0xc0ffee.ca/blog/deduping-mutt/
https://gist.github.com/lewisthompson/bb0e0399254c90cf36dba03956bd2ff0


___
isync-devel mailing list
isync-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/isync-devel

Re: How to synchronize all messages in a folder from the near to the far side?

[Peter P.]

* Oswald Buddenhagen via isync-devel  
[2024-02-20 10:33]:
> On Tue, Feb 20, 2024 at 10:04:57AM +0100, Peter P. wrote:
> > * Peter P.  [2024-02-20 10:01]:
> > > What is the best way to completely sync a far side folder to the near
> > > side without keeping any previous near side messages?
> > > 
> depends on what you mean by that.
> do you just want to get rid of the near-side copies, so you won't have
> dupes when you re-sync?
Yep, that's my intention.

> or are you done with them and don't want to fetch them any more? that
> sounds more like a job for fetchmail. or maybe isync's mail expiration
> feature.
> 
> > So either deleting the near side folder completely,
> > 
> (including the state file.)
> yes, starting from scratch always works fine.
Noted, thanks!
 
> > or running mbsync --pull without removing the near side state file is
> > preferable(?).
> > 
> selective syncing to avoid terminally destructive actions always bears
> the risk that you accidentally run a full sync.
Indeed (wiping sweaty hands)!

Thanks!
P


___
isync-devel mailing list
isync-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/isync-devel

Re: How to synchronize all messages in a folder from the near to the far side?

[Peter P.]

Repying to myself below:

* Peter P.  [2024-02-20 10:01]:
> Thanks Oswald for you replies below, everything worked fine in the end.
> 
> What is the best way to completely sync a far side folder to the near
> side without keeping any previous near side messages?
> 
> -Delete the folder off the near side filesystem and let it be re-created
> as part of the next sync?
> 
> -Delete the near side .mbsyncstate and run mbsync --pull ?
This second way seems bad, as deleting near side .mbsyncstate, pulling
in all changes and THEN running a bi-directional sync may create
duplicates on the far side, as described by Oswald in one of his last
replies as:
"remember to clear the far side again after removing the state file, or
you'll get duplicates for the few new mails that did get synced.

So either deleting the near side folder completely, or running mbsync
--pull without removing the near side state file is preferable(?).


___
isync-devel mailing list
isync-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/isync-devel

Re: How to synchronize all messages in a folder from the near to the far side?

[Peter P.]

Thanks Oswald for you replies below, everything worked fine in the end.

What is the best way to completely sync a far side folder to the near
side without keeping any previous near side messages?

-Delete the folder off the near side filesystem and let it be re-created
as part of the next sync?

-Delete the near side .mbsyncstate and run mbsync --pull ?

best, 
P

* Oswald Buddenhagen via isync-devel  
[2024-02-20 09:40]:
> On Mon, Feb 19, 2024 at 07:07:07PM +0100, Peter P. wrote:
> > Socket error: secure read from -whatever- : error:0A000126:SSL
> > routines::unexpected eof while reading
> > 
> that's just generic flakiness of the connection. don't worry.
> 
> > and on the next run I do get:
> > Warning: lost track of XXX pushed message(s).
> > 
> that's ignorable, too. i already removed it in master.
> 
> > Does this message mean I will end up with duplicates on the far side as
> > well and will I have to clear the far side every time a full sync does
> > not go through due to errors?
> > 
> no.
> 
> 
> ___
> isync-devel mailing list
> isync-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/isync-devel


___
isync-devel mailing list
isync-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/isync-devel

Re: How to synchronize all messages in a folder from the near to the far side?

[Peter P.]

* Oswald Buddenhagen via isync-devel  
[2024-02-19 18:18]:
> On Mon, Feb 19, 2024 at 06:07:18PM +0100, Peter P. wrote:
> > * Oswald Buddenhagen via isync-devel
> >  [2024-02-19 18:03]:
> > > On Mon, Feb 19, 2024 at 05:09:43PM +0100, Peter P. wrote:
> > > > And no messages get synced to the far side.
> > > >
> > > > In an earlier attempt with the same command, only a few messages were
> > > > copied to the far side:
> > > >
> > > it looks very much like you still have an old state file lying around
> > Do you mean .mbsyncstate on the near side? So I would try to remove that
> > file?
> > 
> yes. or maybe you have one in ~/.mbsync or ~/.local/local/state/isync,
> depending on the box' SyncState config.
Thanks, yes, removing the corresponding .mbsyncstate file makes it work.

> remember to clear the far side again after removing the state file, or
> you'll get duplicates for the few new mails that did get synced.
Allright!

Now the sync is interrupted at times due to the following SSL error:

Socket error: secure read from -whatever- : error:0A000126:SSL 
routines::unexpected eof while reading

and on the next run I do get:
Warning: lost track of XXX pushed message(s).

Does this message mean I will end up with duplicates on the far side as
well and will I have to clear the far side every time a full sync does
not go through due to errors?

Much appreciated Oswald!
P


___
isync-devel mailing list
isync-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/isync-devel

Re: How to synchronize all messages in a folder from the near to the far side?

[Peter P.]

(replied to Oswald off-list, so here is a copy of my reply, now to the
list)

* Oswald Buddenhagen via isync-devel  
[2024-02-19 18:03]:
> On Mon, Feb 19, 2024 at 05:09:43PM +0100, Peter P. wrote:
> > And no messages get synced to the far side.
> > 
> > In an earlier attempt with the same command, only a few messages were
> > copied to the far side:
> > 
> it looks very much like you still have an old state file lying around
Do you mean .mbsyncstate on the near side? So I would try to remove that
file?

> (and you got very lucky by using --push, as otherwise you'd have nuked
> your local mails by pulling in the deletions).

Thanks!
P


___
isync-devel mailing list
isync-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/isync-devel

How to synchronize all messages in a folder from the near to the far side?

[Peter P.]

Hi list, dear Oswald,

I am trying to propagate all messages from the near side "Sent" folder
(laptop harddisk) to the far side "Sent" folder (imap server). I emptied
the "Sent" folder on the far side befor running on the near side:

$ mbsync -V --push myaccount:Sent

[...]

Opening far side box Sent...
Opening near side box Sent...
Loading far side box...
far side: 0 messages, 0 recent
Loading near side box...
near side: 4913 messages, 14 recent
Synchronizing...
C: 1/1  B: 1/1  F: +0/0 *0/0 #0/0  N: +0/0 *0/0 #0/0

And no messages get synced to the far side. 

In an earlier attempt with the same command, only a few messages were
copied to the far side:

Opening far side box Sent...
Opening near side box Sent...
Loading far side box...
Loading near side box...
near side: 4913 messages, 14 recent
far side: 61 messages, 0 recent
Synchronizing...
C: 1/1  B: 1/1  F: +0/0 *0/0 #0/0  N: +0/0 *0/0 #0/0

How can I achieve this?

I still don't get my head around these things ... and am grateful for
any help in easy language if possible.

Thank you!
Peter


___
isync-devel mailing list
isync-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/isync-devel

filter duplicates?

[Peter P.]

Hi list,

I am using mutt as MTA on two differet computers, each syncing to and
from an imap server. Sometimes I end up with duplicate messages in
folders and use mutt's tagging feature to tag duplicates, which I then
purge.
I learn to understand that although these messages appear identical to
me (and to mutt), isync might nevertheless give them different IDs?

So if I am unlucky and mutt on computer1 deletes MessageA as a duplicate
of MessageB...
and
mutt on computer2 deletes messageB as a duplicate of messageA
I might end up with both messageA and messageB being synced back up to
the imap server?

If this is the case, how can I get out of this situation? Even if I
would use --pull on one of the two computers, it will not delete the
respective other message that is already in place, no?

Thanks for all hints, it is very appreciated!
best, P


___
isync-devel mailing list
isync-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/isync-devel

Re: Sudden UTHENTICATE failed.

[Peter P.]

* Marton Balazs  [2024-01-29 12:55]:
> Thanks All, this is my page :-) great to see it's useful. While it still 
> works fine on my work machine running Ubuntu 20.04, some update on my Arch at 
> home broke something (I don't know what exactly) so at home I'm now following 
> Bence's excellent guides from a previous email on this thread with mailctl 
> instead of oauth2ms. 

I just noticed that installing oauth2ms requirements.txt via pip as
described on [1] might fail, at least on Debian, as they updated their
policy regarding python package management without setting up explicit
environments.

So I installed these via Debian's apt as python3-xdg python3-msal
python3-gnupg.

thanks again for the guide Márton!

[1] https://github.com/harishkrupo/oauth2ms


___
isync-devel mailing list
isync-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/isync-devel

Re: Sudden UTHENTICATE failed.

[Peter P.]

* Henrik Frisk  [2024-01-29 10:47]:
> [...] Anyway, I
> fought hard to setup OAuth2 on my system a year or so ago and in the end I
> found another solution (forwarding all email to a free office365 account).
What OS are you on? I just succeeded using oauth2 on Debian with mbsync
following instructions from
https://people.maths.bris.ac.uk/~mb13434/linux_m_uob/o365_imap_smtp.html

best, Peter


___
isync-devel mailing list
isync-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/isync-devel

Re: Sudden UTHENTICATE failed.

[Peter P.]

Henrik,

what is your authentication method? Microsoft only allows 
AuthMechs XOAUTH2
since a few months. A startpage.com search for "mbsync office365" might
yield additional hints.

best, P

* Henrik Frisk  [2024-01-29 08:50]:
> Hi,
> 
> Well aware this is not a question for the devel list I'm taking my chances.
> After no configuration change my mbsync command started returning this
> error (not every time, but farily often):
> 
> IMAP command 'AUTHENTICATE PLAIN ' returned an error:
> AUTHENTICATE failed.
> 
> Any ideas that might have caused this? The server is an Office365.
> 
> Best,
> Henrik


> ___
> isync-devel mailing list
> isync-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/isync-devel



___
isync-devel mailing list
isync-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/isync-devel

a more general question

[Peter P.]

Hi,

a problem with my near-side email folders prompts me to ask the followig
more general question:

My setup is:
farside IMAP server
nearside A laptop
nearside B laptop

I am hoping to get all three to hold identical emails by syncing nearA
and farside, as well as nearB and farside, all bidirectional.

Is this supposed to keep email on all three computers in sync? If yes, is this
also the case for a folder that is present on all three but that I use
as a trash from withing mutt (on both nearsides)? Because I discover
emails in this folder on nearB that are not present on dearA.

None of the trash-options are set in my .mbsyncrc.

Thank you for any pointers here,
Peter


___
isync-devel mailing list
isync-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/isync-devel

SSL routines::unexpected eof while reading

[Peter P.]

Hi,
running into this error
https://sourceforge.net/p/isync/bugs/68/
as well using isync 1.4.4 on Android/Termux with two different imap
servers which are not gmail. 

These are servers where I have to set
 SSLType IMAPS

For one server I tried switching the 
 SSLVersions
config variable, getting the following errors:
TLSv1   SSL routines::internal error
TLSv1.1 SSL routines::internal error
TLSv1.2 SSL routines::unexpected eof while reading
TLSv1.3 SSL routines::sslv3 alert handshake failure
SSLv3   SSL routines::no protocols available

This connection works fine with isync 1.3.0 on my Debian/stable laptop
and the following SSL version settings:
TLSv1   SSL routines:ssl3_read_bytes:sslv3 alert handshake failure
TLSv1.1 SSL routines:ssl3_read_bytes:sslv3 alert handshake failure
TLSv1.2 -works-
SSLv3   SSL routines::sslv3 alert handshake failure

As far as I understand it, this error happens when the connection is
closed? Is there a workaround or can this only be fixed in a newer
version of the isync package?

Thank you so much!
Peter


___
isync-devel mailing list
isync-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/isync-devel

internaldate parsing error on fastmail

[Peter P.]

Hi,

I am trying to run mbsync on my cell phone under Termux. When trying to
sync a fastmail account I am getting the error
IMAP error: unable to parse INTERNALDATE format
A possibly related issue has been described here
https://vxlabs.com/2021/03/21/mbsync-copyarrivaldate-yes/
but I have set CopyArrivalDate to yes.

What can I try next? Thank you!
Peter


___
isync-devel mailing list
isync-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/isync-devel

Re: Fatal: buffer too small

[Peter P.]

Hi Michal,

just on the side, could you let me know how you are using XOAUTH2 with
mbsync? Very interesting...

best, P

* Michal Sojka via isync-devel  [2022-11-07 
01:02]:
> Hi,
> 
> I'm currently trying to use mbsync with XOAUTH2 authentication (needed
> for Office365 mailboxes) and I encounter "Fatal: buffer too small.
> Please report a bug." error.
> 
> Debugging with GDB revealed that the access token used for the LOGIN
> command does not fit into the imap_vprintf buffer, which is currently
> 1000 characters long. In my case, I needed the buffer to hold at least
> 2000 characters.
> 
> I see that in the current master, the size of the buffer can be
> increased by defining QPRINTF_BUFF during compilation, but for the
> latest released version 1.4.4, I'm using the following patch. To make
> the size of the buffer more future-proof, I increase the buffer size to
> 4000 characters. Maybe, somebody will find it useful.
> 
> Best regards,
> -Michal
> 
> From e8a3a20aed135272a9ec0103f4055411c075f043 Mon Sep 17 00:00:00 2001
> From: Michal Sojka 
> Date: Mon, 7 Nov 2022 00:07:22 +0100
> Subject: [PATCH] Increase imap_vprintf buffer size
> ---
>  src/drv_imap.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/src/drv_imap.c b/src/drv_imap.c
> index c5a7aed..7847192 100644
> --- a/src/drv_imap.c
> +++ b/src/drv_imap.c
> @@ -528,7 +528,7 @@ imap_vprintf( const char *fmt, va_list ap )
>   uint totlen = 0;
>   const char *segs[MAX_SEGS];
>   uint segls[MAX_SEGS];
> - char buf[1000];
> + char buf[4000];
>  
>   d = buf;
>   ed = d + sizeof(buf);
> -- 
> 2.38.1
> 
> 
> ___
> isync-devel mailing list
> isync-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/isync-devel


___
isync-devel mailing list
isync-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/isync-devel

Re: prevent imap timeout while syncing large mailboxes?

[Peter P.]

* Oswald Buddenhagen  [2022-09-18 15:10]:
> On Sun, Sep 18, 2022 at 09:29:45AM +0200, Peter P. wrote:
> > * Oswald Buddenhagen  [2022-09-18 08:53]:
> > > On Sat, Sep 17, 2022 at 09:58:48PM +0200, Peter P. wrote:
> > > > Hi, I am trying to sync a rather huge mailbox ~50k messages to a slave
> > > > that has a rather slow CPU (RaspberryPi).
> > > > a pi isn't slow by any means as fas as isync is concerned.
> > > which isync version are you using?
> > Thanks Oswald, this is isync 1.3.0 from the Debian package
> > 1.3.0-2.2+deb11u1
> > 
> that's basically stone age. 1.4 has this bug fixed (and you may use git
> master just as well when you build yourself).
Thank you! 1.4 indeed runs without that error and tells me that the box
has synced successfully. 

Had to use apt pinning to install the Debian testing version of isync on
an otherwise stable machine, including upgrades to libc and friends.
Such a pity that there is no 1.4 version in Debian backports... whom
would I need to bribe to get one? Pierre-Elliott Bécue packaged 1.4.4-3
for Debian testing...

cheers, P


___
isync-devel mailing list
isync-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/isync-devel

Re: prevent imap timeout while syncing large mailboxes?

[Peter P.]

* Oswald Buddenhagen  [2022-09-18 08:53]:
> On Sat, Sep 17, 2022 at 09:58:48PM +0200, Peter P. wrote:
> > Hi, I am trying to sync a rather huge mailbox ~50k messages to a slave
> > that has a rather slow CPU (RaspberryPi).
> > 
> a pi isn't slow by any means as fas as isync is concerned.
> which isync version are you using?
Thanks Oswald, this is isync 1.3.0 from the Debian package
1.3.0-2.2+deb11u1


___
isync-devel mailing list
isync-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/isync-devel

prevent imap timeout while syncing large mailboxes?

[Peter P.]

Hi, I am trying to sync a rather huge mailbox ~50k messages to a slave
that has a rather slow CPU (RaspberryPi). But I am getting frequent
timeout errors at the following point
 C: 0/1  B: 0/1  M: +0/0 *0/0 #0/0  S: +0/41711 *0/0 #0/0
 Socket error on imap.whatever ([:XXX::XX]:143): timeout.

I assume that it takes mbsync a while to calculate which messages to
sync and that the imap server closes the connection? Is there a
workaround for this problem?

Thank you so much!
Peter


___
isync-devel mailing list
isync-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/isync-devel

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

[Peter P.]

* Oswald Buddenhagen  [2022-04-20 23:00]:
> On Wed, Apr 20, 2022 at 08:29:35PM +, 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).

Oh, I just had a problem that may be related. The password command was
also piped into awk since there multiple account passwords are stored in
one encrypted file. And akw was apparently blocked by apparmor, which
was installed by default on this debian stable system.


___
isync-devel mailing list
isync-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/isync-devel

Re: --dry-run?

[Peter P.]

* Oswald Buddenhagen  [2022-03-06 19:48]:
> On Sun, Mar 06, 2022 at 05:55:03PM +0100, Peter P. wrote:
> > for debugging purposes and to better understand what mbsync would do, it
> > would be awesome™ to have a dry-run flag where the program would show
> > what it would do without actually performing the sync.
> > 
> deja vu? https://sourceforge.net/p/isync/mailman/message/37393490/

Ah darn, entschuldige Oswald,  and thanks for reminding me. Looking
forward!
P


___
isync-devel mailing list
isync-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/isync-devel

--dry-run?

[Peter P.]

Hi,

for debugging purposes and to better understand what mbsync would do, it
would be awesome™ to have a dry-run flag where the program would show
what it would do without actually performing the sync.

cheersz, P


___
isync-devel mailing list
isync-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/isync-devel

Re: push messages?

[Peter P.]

* Peter P.  [2021-11-30 16:48]:
[...]
> Now I have set MaxPushedUid to zero and synced. A good part, but not all
> messages from the local computer have been pushed to the server. But
> still there is a difference:
> 
> $ mbsync -V --push account:INBOX/Trash
> 
> Loading master...
> master: 39769 messages, 0 recent
> Loading slave...
> slave: 41299 messages, 0 recent
> Synchronizing...
> C: 1/1  B: 1/1  M: +0/0 *0/0 #0/0  S: +0/0 *0/0 #0/0
> 
> $ head .imapMail_mbsync/account/INBOX.Trash/.mbsyncstate 
> MasterUidValidity 1095335204
> SlaveUidValidity 1522667764
> MaxPulledUid 730384
> MaxPushedUid 0

[...]

Anyway I accidentally ran a sync without neither --pull nor --push and
now the extra ~2k messages on the local store are gone after this has 
happened:
 C: 0/1  B: 14/15  M: +2/2 *2/2 #0/0  S: +0/0 *1530/1530 #0/0

I can't seem to understand the point when something is synced. Neither --pull 
nor
--push did something I intended as described (to have the same messages
on the server and locally), but running mbsync without either flags
deleted the local messages unexpectedly.
I am starting to suspect the imap server needing 5 minutes or so to
actually process the changes, is this possible?

thanks, P


___
isync-devel mailing list
isync-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/isync-devel

Re: push messages?

[Peter P.]

* Oswald Buddenhagen  [2021-11-30 15:58]:
> On Tue, Nov 30, 2021 at 03:51:19PM +0100, Peter P. wrote:
> > * Oswald Buddenhagen  [2021-11-30 15:35]:
> > > did you hack the second replica's state file as well?
> > Not yet, do you want me to investigate anything in that file or send you
> > -D logs before I hack it?
> > 
> no, now i already know that the problem is the too high MaxPushedUid.  the
> question is how we got there, but for that we'd need logs from the past (or
> from the future, if the problem re-appears after successfully syncing up).

Now I have set MaxPushedUid to zero and synced. A good part, but not all
messages from the local computer have been pushed to the server. But
still there is a difference:

$ mbsync -V --push account:INBOX/Trash

Loading master...
master: 39769 messages, 0 recent
Loading slave...
slave: 41299 messages, 0 recent
Synchronizing...
C: 1/1  B: 1/1  M: +0/0 *0/0 #0/0  S: +0/0 *0/0 #0/0

$ head .imapMail_mbsync/account/INBOX.Trash/.mbsyncstate 
MasterUidValidity 1095335204
SlaveUidValidity 1522667764
MaxPulledUid 730384
MaxPushedUid 0

Will send you a -D log off-list now.


signature.asc
Description: PGP signature
___
isync-devel mailing list
isync-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/isync-devel

Re: push messages?

[Peter P.]

Dear Oswald,

* Oswald Buddenhagen  [2021-11-30 15:35]:
> On Tue, Nov 30, 2021 at 03:02:50PM +0100, Peter P. wrote:
> > Now I am trying to sync the same folder with another laptop. What
> > puzzles me still is that I can't get the two to hold the same messages.
> > Regardless if I try mbsync -V --push account:INBOX/Trash
> > or
> > mbsync -V --pull account:INBOX/Trash
> > 
> > the server will hold 40465 messages and the local laptop 41300.
> 
> did you hack the second replica's state file as well?
Not yet, do you want me to investigate anything in that file or send you
-D logs before I hack it?

best, P


signature.asc
Description: PGP signature
___
isync-devel mailing list
isync-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/isync-devel

Re: push messages?

[Peter P.]

* Oswald Buddenhagen  [2021-11-30 15:15]:
> On Tue, Nov 30, 2021 at 01:45:27PM +0100, Peter P. wrote:
> > * Oswald Buddenhagen  [2021-11-29 19:22]:
> > > try hacking that box' .mbsyncstate: set MaxPushedUid to 0.
> > 
> > Thanks Oswald, setting it to zero made the sync work!
> > 
> ok. it would be interesting to know how you got into that state, as there
> was clearly something not quite as expected. maybe keep an eye on it, and if
> it happens again try to remember as many circumstances as you can.
My other email message about two folders not holding the same number of
messages might be related (see there). It is with the same server folder
trying to sync it to another computer.

> > One thing puzzles me still, why did the following command sync the
> > server contents despite me giving the --noop flag?
> > 
> > mbsync -V --noop --push account:INBOX/Trash
> > 
> because you specified --push ...
> it's actually a nonsensical combination, and it would be preferable if it
> errored out instead of "letting push win", but the command merging code
> borders on black magic, and i don't feel masochistic enough to touch it
> again. :'-D
Ok, that makes it more clear. I thought there would be a flag that would
tell me what would happen (like rsync's --dry-run) before actually
running a "push" sync. Is there another way to predict what would
happen here?

much appreciated,
P


___
isync-devel mailing list
isync-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/isync-devel

Re: push messages?

[Peter P.]

Now I am trying to sync the same folder with another laptop. What
puzzles me still is that I can't get the two to hold the same messages.
Regardless if I try 
 mbsync -V --push account:INBOX/Trash
or
 mbsync -V --pull account:INBOX/Trash

the server will hold 40465 messages and the local laptop 41300. Is this
intentional? I think I still don't understand how messages are synced...

thanks for any hints!
P


signature.asc
Description: PGP signature
___
isync-devel mailing list
isync-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/isync-devel

Re: push messages?

[Peter P.]

* Oswald Buddenhagen  [2021-11-29 19:22]:
> On Mon, Nov 29, 2021 at 05:53:31PM +0100, Peter P. wrote:
> > please see below the relevant sections from the config file.
> > 
> ok, nothing obviously wrong with it.
> try hacking that box' .mbsyncstate: set MaxPushedUid to 0.
> if that doesn't help, send me the log from a run with -D.

Thanks Oswald, setting it to zero made the sync work!
One thing puzzles me still, why did the following command sync the
server contents despite me giving the --noop flag?

 mbsync -V --noop --push account:INBOX/Trash

best, P


___
isync-devel mailing list
isync-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/isync-devel

Re: push messages?

[Peter P.]

* Oswald Buddenhagen  [2021-11-29 19:22]:
> On Mon, Nov 29, 2021 at 05:53:31PM +0100, Peter P. wrote:
> > please see below the relevant sections from the config file.
> > 
> ok, nothing obviously wrong with it.
> try hacking that box' .mbsyncstate: set MaxPushedUid to 0.
> if that doesn't help, send me the log from a run with -D.
Will try, thanks!
Just as extra possibility: That box resides on an ntfs file system
mounted via fuse. Afaikt there are no weird filenames there (not sure if
the hint about it in [1] is still up to date. I am on Debian
nevertheless with isync 1.3.0).

[1]
https://wiki.archlinux.org/title/isync#Using_Path_and/or_Inbox_on_NTFS_partitions


___
isync-devel mailing list
isync-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/isync-devel

Re: push messages?

[Peter P.]

* Oswald Buddenhagen  [2021-11-29 17:29]:
> On Mon, Nov 29, 2021 at 04:51:25PM +0100, Peter P. wrote:
> > What can I read/try next?
> > 
> post your config file.
> 
> a wild guess is that you abuse mbsync's trash functionality, as people seem
> to do that relatively often.

Thanks Oswald, please see below the relevant sections from the config
file. Best, P

IMAPAccount myaccount
Host imap.myaccount.com
User myself

IMAPStore myaccount-remote
Account myaccount
# Path INBOX
UseNamespace no

MaildirStore myaccount-local
Path ~/.imapMail_mbsync/myaccount/
Inbox ~/.imapMail_mbsync/myaccount/INBOX
Flatten .

Channel myaccount
Master :myaccount-remote:
Slave :myaccount-local:
Patterns * !INBOX/Junk 
# Create Slave
# Sync Pull
SyncState *
Expunge Both
CopyArrivalDate yes


___
isync-devel mailing list
isync-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/isync-devel

push messages?

[Peter P.]

Hi,

I am struggling to understand the following:

I have more messages in my laptop's Trash store than on the server and want
to send them to the server. If I issue a sync with the --pull flag as

 mbsync -V --push account:INBOX/Trash

I am being told that
 Loading master...
 master: 36651 messages, 0 recent
 Loading slave...
 slave: 42287 messages, 9944 recent
 Synchronizing...
 C: 1/1  B: 1/1  M: +0/0 *0/0 #0/0  S: +0/0 *0/0 #0/0

that no messages are synced. So I am possibly not understanding the
concept of mbsync properly. What can I read/try next?

Thanks! Peter


signature.asc
Description: PGP signature
___
isync-devel mailing list
isync-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/isync-devel

Re: any problem with multiple instance of mbsync?

[Peter P.]

* Oswald Buddenhagen  [2019-03-04 23:19]:
> On Mon, Mar 04, 2019 at 03:41:44PM +0100, Marc Chantreux wrote:
> > i would like to know if it's dangerous to [parallelize] to make my
> > mail sync faster. i fear something like caching corruption.
I do run GNU parallel with separate instances of mbsync for each
mailbox, this way they don't interefere on the filesystem level.


___
isync-devel mailing list
isync-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/isync-devel

Re: mailbox name Inbox contains server's hierarchy delimiter

[Peter P.]

* Oswald Buddenhagen  [2019-02-28 17:49]:
> On Thu, Feb 28, 2019 at 04:25:12PM +0100, Peter P. wrote:
> > $ mbsync -V myAccount:INBOX
> > 
> -D is the new -V ...
> 
> > The respective entry in my .mbsyncrc holds 
> > Flatten .
> > 
> it might be more of a case of PathDelimiter being missing/wrong, but
> we'll see that in the debug output.

Thank you! The debug output is

mbsync -D myAccount:INBOX
Reading configuration file /home/peter/.mbsyncrc
Channel myAccount
Opening master store myAccount-remote...
M: [ 1] Enter connect_store

[...]

M: [ 1] Leave connect_store
Opening slave store myAccount-local...
S: [ 2] Enter connect_store
S: [ 2] Callback enter connect_store, sts=0
S: [ 2] Callback leave connect_store
S: [ 2] Leave connect_store
Connection is now encrypted
M: * OK [CAPABILITY IMAP4rev1 STARTTLS AUTH=PLAIN AUTH=XGWTRUSTEDAPP
UNSELECT XGWEXTENSIONS] Server Ready
Logging in...
Authenticating with SASL mechanism PLAIN...

[...]

M: 1 OK AUTHENTICATE completed
M: [ 1] Callback enter connect_store, sts=0
M: Enter select_box, name=INBOX
M: Leave select_box, ret=0
S: Enter select_box, name=INBOX
S: Leave select_box, ret=0
S: Called get_box_path, ret=/home/peter/.imapMail_mbsync/myAccount/Inbox
reading sync state /home/peter/.imapMail_mbsync/myAccount/Inbox/.mbsyncstate
...
  entry (775,658,12,)
  entry (894,773,8,)
  entry (3489,2836,8,)
  entry (4146,3414,8,)
  entry (4224,3488,8,)
  entry (4321,3576,12,)
  entry (4325,3580,8,)
  entry (4349,3602,8,)
  entry (4353,3606,8,)
  entry (4361,3614,8,)
  entry (4386,3639,12,)
  entry (4387,3640,8,)
  entry (4399,3652,8,)
  entry (4524,3763,8,)
  entry (4525,3764,12,)
  entry (4526,3765,8,)
  entry (4528,3767,12,)
  entry (4541,3779,8,)
  entry (4543,3781,0,)
Opening master box INBOX...
M: [ 3] Enter open_box
IMAP error: mailbox name INBOX contains server's hierarchy delimiter
M: [ 3] Callback enter open_box, sts=2, uidvalidity=-1
M: [ 3] Callback leave open_box
M: [ 3] Leave open_box
Opening slave box INBOX...
S: [ 4] Enter open_box
S: [ 4] Callback enter open_box, sts=0, uidvalidity=1415380095
Error: channel myAccount: master INBOX cannot be opened.
S: [ 4] Callback leave open_box
S: [ 4] Leave open_box
M: [ 5] Enter cancel_cmds
M: [ 5] Callback enter cancel_cmds
M: Enter free_store
M: Leave free_store
M: [ 5] Callback leave cancel_cmds
M: [ 5] Leave cancel_cmds
S: [ 6] Enter cancel_cmds
S: [ 6] Callback enter cancel_cmds
S: Enter free_store
S: Leave free_store
S: [ 6] Callback leave cancel_cmds
S: [ 6] Leave cancel_cmds
M: >>> 2 LOGOUT
M: [ 1] Callback leave connect_store
M: * BYE IMAP4rev1 Server Disconnect
M: 2 OK LOGOUT completed


___
isync-devel mailing list
isync-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/isync-devel

mailbox name Inbox contains server's hierarchy delimiter

[Peter P.]

Forgive me if this has been discussed to death, but a quick web search
does not help nor did the manpage.

I have an IMAP store that holds amongst others a folder called INBOX.
This is the output of

$ mbsync -l myAccount
INBOX
...

Now if I try to sync only that folder using
$ mbsync -V myAccount:INBOX

I get the error message 

Opening master box INBOX...
IMAP error: mailbox name INBOX contains server's hierarchy delimiter
Opening slave box INBOX...
Error: channel myAccount: master INBOX cannot be opened.

and I get the same message when using
$ mbsync -V myAccount/INBOX

The respective entry in my .mbsyncrc holds 
Flatten .

Now which piece of knowledge am I missing, or missing to find so that I
can make this work?

Thanks for any pointers!

P


___
isync-devel mailing list
isync-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/isync-devel

Re: Error: incompatible journal version (got 2, expected 3)

[Peter P.]

Hi Oswald,

* Oswald Buddenhagen <oswald.buddenha...@gmx.de> [2018-02-16 11:37]:
> On Sat, Feb 10, 2018 at 12:20:18PM +0100, Peter P. wrote:
> > Now here is a thing that puzzles me. On that channel's imap server there
> > appears to exist folders
> > /Drafts
> > /Junk
> > /SPAM
> > /Sent
> > in addition to the ones known to me and synced by me
> > INBOX/Drafts
> > INBOX/Junk
> > INBOX/SPAM
> > INBOX/Sent
> >
> > [...]
> > Can this first group of folders be server-side duplicates of the
> > INBOX/... ones as the seem to hold the same content.
> >
> i expect these to be artifacts from the previous behavior change when
> you updated to mbsync 1.2.
You are correct, they were created locally when I updated without care.
I deleted these folders and all is fine, thank you for your kind help.

> that would imply that the contents aren't actually the same - the bogus
> folders should lack the more recent messages.
> 
> > Strangely they are not detected as folders by thunderbird, nor are
> > they visible in a Horde webmail interface.
> > 
> these certainly use the default namespace, so they don't see anything
> outside INBOX.
And I discovered that they are (were)local folders only. 

cheers, P

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
isync-devel mailing list
isync-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/isync-devel

Re: Error: incompatible journal version (got 2, expected 3)

[Peter P.]

* Oswald Buddenhagen <oswald.buddenha...@gmx.de> [2018-02-09 23:32]:
> On Fri, Feb 09, 2018 at 08:11:28PM +0100, Peter P. wrote:
> > IMAPAccount mychannel
> > Host imap.whatever
> > User whoever
> > Pass whatever
> > 
> > IMAPStore mychannel-remote
> > Account mychannel
> > # Path INBOX
> > UseNamespace no
> > 
> > Channel mychannel
> > Master :mychannel-remote:
> > Slave :mychannel-local:
> > Patterns * !INBOX/Junk
> > Create Slave
> > SyncState *
> > Expunge Both
> > CopyArrivalDate yes
> > 
> 
> looks reasonable. try the -D option.

I figured out that it is the mailbox
\Sent 
which causes this error. With
 $mbsync -V -Dsm mychannel:/Sent
I get the error reported as:
[...]
Connection is now encrypted
Logging in...
Authenticating with SASL mechanism PLAIN...
recovering journal ...
Error: incompatible journal version (got 2, expected 3)
without further information.

On another Debian testing computer I do not get the "incompatible journal
version" error with the same config and mbsync 1.3.0.
Let me know if you want me to invenstigate further, possibly comparing
journal files etc...

Now here is a thing that puzzles me. On that channel's imap server there
appears to exist folders
/Drafts
/Junk
/SPAM
/Sent
in addition to the ones known to me and synced by me
INBOX/Drafts
INBOX/Junk
INBOX/SPAM
INBOX/Sent
This first group of folders are the ones causing errors:
Error: channel mychannel: master /Drafts cannot be opened.
Error: channel mychannel: master /Junk cannot be opened.
Error: channel mychannel: master /SPAM cannot be opened.
and /Sent is causing the aforementioned
Error: incompatible journal version (got 2, expected 3)

If I add the first group of folders to the Patterns to avoid as 
Patterns !/Drafts !/Junk !/SPAM !/Sent
all four errors go away.

Can this first group of folders be server-side duplicates of the
INBOX/... ones as the seem to hold the same content. Strangely they are
not detected as folders by thunderbird, nor are they visible in a Horde
webmail interface.

On the (local) slave I discovered these folders as unix hidden folders
.Drafts
.Sent
.Junk
.SPAM
I would be fine with deleting them from my slave and excluding them as
Pattern as I don't want to sync them, but wonder if this is due to my
mistake or if it's something in 1.3.0 that might have triggered this.

Thank you for your time and help, it is greatly appreciated!

Peter

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
isync-devel mailing list
isync-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/isync-devel

Re: Error: incompatible journal version (got 2, expected 3)

[Peter P.]

* Oswald Buddenhagen <oswald.buddenha...@gmx.de> [2018-02-08 20:01]:
> On Thu, Feb 08, 2018 at 07:32:17PM +0100, Peter P. wrote:
> > Trying to apply what you recomment I am noticing the following
> > dicrepancy between Debian's 1.2.1-2 and 1.3.0-1: [...]
> > 
> that looks related to one NEWS item ... for 1.2.0.
> i'd need to see the full config to make a call.
Here it is:

IMAPAccount mychannel
Host imap.whatever
User whoever
Pass whatever

IMAPStore mychannel-remote
Account mychannel
# Path INBOX
UseNamespace no

Channel mychannel
Master :mychannel-remote:
Slave :mychannel-local:
Patterns * !INBOX/Junk
Create Slave
SyncState *
Expunge Both
CopyArrivalDate yes

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
isync-devel mailing list
isync-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/isync-devel

Re: Error: incompatible journal version (got 2, expected 3)

[Peter P.]

* Oswald Buddenhagen <oswald.buddenha...@gmx.de> [2018-02-08 18:44]:
> On Thu, Feb 08, 2018 at 12:28:15PM +0100, Peter P. wrote:
> > upgrading from to on a Debian testing box I do get the following for one
> > of my channels:
> > 
> >  Error: incompatible journal version (got 2, expected 3)
> > 
> that means that mbsync didn't properly finish syncing some box(es),
> possibly already for a long time.
> 
> the upgrade path is to get the latest 1.2 code and run it on the
> boxes in question. if you see it failing, try with --noop.
> once it finishes successfully, you can start using 1.3.

Thank you Oswald! 
Trying to apply what you recomment I am noticing the following
dicrepancy between Debian's 1.2.1-2 and 1.3.0-1:

With 1.3.0-1 I do get the following errors running: 

$ mbsync mychannel

C: 0/1  B: 12/16  M: +0/0 *0/0 #0/0  S: +0/0 *0/0 #0/0
Error: channel mychannel: master /Drafts cannot be opened.
C: 0/1  B: 13/16  M: +0/0 *0/0 #0/0  S: +0/0 *0/0 #0/0
Error: channel mychannel: master /Junk cannot be opened.
C: 0/1  B: 14/16  M: +0/0 *0/0 #0/0  S: +0/0 *0/0 #0/0
Error: channel mychannel: master /SPAM cannot be opened.
C: 0/1  B: 15/16  M: +0/0 *0/0 #0/0  S: +0/0 *0/0 #0/0
Error: incompatible journal version (got 2, expected 3)
C: 1/1  B: 16/16  M: +0/0 *0/0 #0/0  S: +0/0 *0/0 #0/0

While these do not appear with 1.2.1-2 at all. 

Thanks!
P

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
isync-devel mailing list
isync-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/isync-devel

Error: incompatible journal version (got 2, expected 3)

[Peter P.]

Hi list,

upgrading from to on a Debian testing box I do get the following for one
of my channels:

 Error: incompatible journal version (got 2, expected 3)

The mailing list archive doesn't seem to know about it so far.

thanks!
P


signature.asc
Description: PGP signature
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
isync-devel mailing list
isync-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/isync-devel

Re: status line explanation?

[Peter P.]

* Oswald Buddenhagen <oswald.buddenha...@gmx.de> [2018-02-06 16:31]:
> On Tue, Feb 06, 2018 at 01:18:23PM +0100, Peter P. wrote:
> > since many years I wonder how to read mbsync's status line, eg
> > C: 7/7  B: 41/41  M: +0/0 *0/0 #0/0  S: +1/1 *1/1 #3048/3048
> > Is there an explanation in the docs? I can't seem to find some.
> > 
> "CONSOLE OUTPUT"? it's been there for a while ...

Thanks Oswald,

I searched the man page and /usr/share/doc/isync on my
Debian testing box but not the online manpage which holds this section
http://isync.sourceforge.net/mbsync.html#CONSOLE%20OUTPUT
please excuse me.

P

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
isync-devel mailing list
isync-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/isync-devel

status line explanation?

[Peter P.]

Hi list,

since many years I wonder how to read mbsync's status line, eg
C: 7/7  B: 41/41  M: +0/0 *0/0 #0/0  S: +1/1 *1/1 #3048/3048
Is there an explanation in the docs? I can't seem to find some.

Thank you for all hints!
P

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
isync-devel mailing list
isync-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/isync-devel

Re: libssl1.1

[Peter P.]

* Evgeniy Berdnikov <b...@protva.ru> [2017-08-15 12:52]:
> On Tue, Aug 15, 2017 at 12:24:30PM +0200, Peter P. wrote:
> > Hi,
> > 
> > isync 1.2.1 from Debian testing package with libssl1.1 Debian package 
> > version 1.1.0f-4
> > throws: 
> > 
> > Socket error: secure connect to mail.messagingengine.com (66.111.4.51:993): 
> > error:141640BF:SSL routines:tls_construct_client_hello:no protocols 
> > available
> > 
> > It works with libssl1.1 version 1.1.0f-3.
> > 
> > The older isync 1.1.2 Debian package does work with libssl1.1 1.1.0f-4.
> 
>  The "SSLVersions TLSv1.2" in ~/.mbsyncrc helps me.
Great hint Evgeniy! Indeed it fixes this problem for most of my accounts
except for the following one:

$mbsync -D aol
[...]
Channel aol
Opening master store aol-remote...
Resolving imap.aol.com... ok
Connecting to imap.aol.com (64.12.88.130:993)... 
Opening slave store aol-local...
pattern '*' (effective '*'): Path, no INBOX
got mailbox list from slave:
  Drafts
  INBOX
  Trash
  Sent
  Spam
Socket error: secure connect to imap.aol.com (64.12.88.130:993): 
error:14171102:SSL routines:tls_process_server_hello:unsupported protocol

For that account I now have in my config:

IMAPAccount aol
Host imap.aol.com
User [...]
PassCmd [...]
SSLType IMAPS
SSLVersions TLSv1.2
AuthMechs LOGIN

Thanks for all hints!
Peter

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
isync-devel mailing list
isync-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/isync-devel

libssl1.1

[Peter P.]

Hi,

isync 1.2.1 from Debian testing package with libssl1.1 Debian package version 
1.1.0f-4
throws: 

Socket error: secure connect to mail.messagingengine.com (66.111.4.51:993): 
error:141640BF:SSL routines:tls_construct_client_hello:no protocols available

It works with libssl1.1 version 1.1.0f-3.

The older isync 1.1.2 Debian package does work with libssl1.1 1.1.0f-4.

How can I help to fix?
Thanks!
P

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
isync-devel mailing list
isync-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/isync-devel

SourceForge Mailing List Reconfirmation?

[Peter P.]

Hi list,

like possibly most of you I have received the annoying email from
SourceForge to reconfirm my mailing list subscriptions of which
isync-devel is one. Apart from trying not to complain about the way SF
has developed in the last years some other lists affected are moving
away from SF and to other mailing list servers. Apart from the
convenient feature that updates to the SF repository are automatically
propagated to this list I wanted to spur a discussion if such a move
would be possible for isync-devel as well.

Thank you for your consideration and feedback. And of course for
maintaining isync/mbsync.

Peter

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
isync-devel mailing list
isync-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/isync-devel

explanation of status line

[Peter P.]

Hi amazing isync project!

I have always been curious if there is an explanation for the status
line I am seeing when syncing mail, eg
M: +157/185 *216/216 #0/0  S: +0/302 *81/81 #0/0

Thanks for all pointers!
P

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
___
isync-devel mailing list
isync-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/isync-devel

Re: Sasl: No worthy mechs found

[Peter P.]

* Oswald Buddenhagen  [2016-12-03 17:38]:
> On Fri, Dec 02, 2016 at 12:40:34PM +, david wen riccardi-zhu wrote:
> > Connection is now encrypted
> > * OK IMAP4 ready
> > >>> 1 CAPABILITY
> > * CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS IDLE AUTH=PLAIN
> > 1 OK completed
> > Logging in...
> > IMAP error: authentication mechanism PLAIN is not supported 
> > 
> i fixed this in the 1.2 branch.
> 
> peter's oringinal problem is probably actually expected behavior: when
> the connection is not encrypted, LOGIN will be used only when explicitly
> specified, not via *. i suppose i could make the messages more explicit ...
Again thank you! That could be a good idea. 

cheers, P

--
Check out the vibrant tech community on one of the world's most 
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
___
isync-devel mailing list
isync-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/isync-devel

Re: different behavior between 1.2.1 and 1.1.2

[Peter P.]

Hi Oswald,

* Oswald Buddenhagen <oswald.buddenha...@gmx.de> [2016-12-02 10:30]:
> On Thu, Dec 01, 2016 at 12:14:21PM +0100, Peter P. wrote:
> > I assume that the way the config options have changed,
> >
> yes, there is this item in the NEWS file:
> 
> > > An IMAP Path/NAMESPACE rooted in INBOX won't be handled specially
> > > any more.  This means that some Patterns may need adjustment.
Thank you! I should have had checked that in /usr/share/doc please
excuse me.
 
> from the first look it seems that this is exactly what is hitting you.
> 
> > IMAPStore box-remote
> > Account box
> 
> > Path INBOX
> > 
> an entirely wild guess is that you just need to remove this. running
> with -l will tell you.
> if it doesn't help, try adding 'UseNamespace no' as well.
both, removing "Path INBOX" and setting "UseNamespace no" were required
to fix my problem. As well as getting me the correct output from -l as
described in my other email with subject "empty line in output of -l".

Thank you for your quick response, and, as always, for mbsync.

cheers, P

--
Check out the vibrant tech community on one of the world's most 
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
___
isync-devel mailing list
isync-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/isync-devel

Re: Sasl: No worthy mechs found

[Peter P.]

* dwrz  [2016-12-01 16:19]:
> Hi Peter,
> 
> Just a shot in the dark -- have you tried setting AuthMechs to LOGIN?

And back from the dark I report that this works. Please excuse me, I did
misunderstand the manpage saying approximately that "AuthMechs defaults
to * and all mechanismes deemed secure enough for the given SSL method."
(of which I thought LOGIN was included). This is on imap.aol.com btw.

Thanks dwrz!
P

--
___
isync-devel mailing list
isync-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/isync-devel

different behavior between 1.2.1 and 1.1.2

[Peter P.]

Hi list,

after upgrading isync to 1.2.1 via its Debain testing package i am
getting the following different behavior:

On 1.2.1
 $ mbsync -l channelname
 INBOX/drafts
 INBOX/Trash
 INBOX/Sent
 INBOX/SPAM
 INBOX

On 1.2.2 (no local stores created yet) I get
 $ mbsync -l channelname

 /SPAM
 /Sent
 /Trash
 /drafts
 SPAM
 Sent
 Trash
 drafts

and the INBOX itself is missing. 

I assume that the way the config options have changed, and the above is
configured in .mbsyncrc as follows (the Account section is not given
here):

IMAPStore box-remote
Account box
Path INBOX

MaildirStore box-local
Path ~/.imapMail_mbsync/box/
Inbox ~/.imapMail_mbsync/box/INBOX
Flatten .

Channel box
Master :box-remote:
Slave :box-local:
Patterns *
Create Slave
Sync Pull
SyncState *
Expunge Both
CopyArrivalDate yes

Yes I do use mutt and that's why I have been flattening the hierachies
with the . delimiter.

This different behavior is present in four different stores and renders
my email system unusable in its current state and fills up the
harddisk with duplicates of folders.

I would be grateful for any advice on how to solve this!
Thank you and thanks to Oswald for his work!

Peter

--
___
isync-devel mailing list
isync-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/isync-devel

empty line in output of -l

[Peter P.]

Hi list,

I am trying to understand the output of 
 mbsync -l channelname
which lists some folders above and below an empty line. For one server I
get for example

 INBOX
 INBOX/Drafts
 INBOX/SPAM
 INBOX/Sent
 INBOX/Trash

 /Drafts
 /Junk
 /SPAM
 /Sent
 /Trash

The two versions of each folder were not shown with mbsync -l version 1.1.2
and I am curious about what has changed.

Thank you for any advice
Peter

--
___
isync-devel mailing list
isync-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/isync-devel

Re: no login, every 3rd attempt

[Peter P.]

* Oswald Buddenhagen <oswald.buddenha...@gmx.de> [2016-03-07 17:52]:
> On Mon, Mar 07, 2016 at 02:30:40PM +0100, Peter P. wrote:
> > IMAP command 'AUTHENTICATE PLAIN ' returned an error: NO 
> > AUTHENTICATE GroupWise login failed
> > 
> at this point i don't know what else to do. :(
> complain to the server's sysadmins, maybe they manage to improve something.

Thanks Oswald, this is much appreciated nevertheless!
best, P

--
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://makebettercode.com/inteldaal-eval
___
isync-devel mailing list
isync-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/isync-devel

Re: no login, every 3rd attempt

[Peter P.]

Dear Oswald, list,

* Oswald Buddenhagen <oswald.buddenha...@gmx.de> [2016-03-07 09:45]:
> On Sun, Mar 06, 2016 at 08:59:21PM +0100, Peter P. wrote:
> > * OK [CAPABILITY IMAP4rev1 STARTTLS LOGINDISABLED] GroupWise Server
> > >>> 1 STARTTLS
> > 1 OK Begin TLS negotiation
> > >>> 2 CAPABILITY
> > * CAPABILITY IMAP4rev1 AUTH=PLAIN AUTH=XGWTRUSTEDAPP UNSELECT
> > 2 OK CAPABILITY completed
> > >>> 3 LOGIN  
> > [then after some time]
> > IMAP command 'LOGIN  ' returned an error: NO LOGIN 
> > GroupWise login failed
> > 
> > Every third time or so I would get beyond that point with
> > 3 OK LOGIN completed
> > and so on and so forth.
> > 
> > Is there anything I could try to get more stable logins? Is it me,
> > mbsync or the mail server?
> > 
> to me it seems that the server forgets to internally re-enable LOGIN
> after TLS negotiation despite reporting that it has done so.
Thank you for this idea!

> you can try UseIMAPS to work around that apparent server bug.
Which sadly didn't help.

> you can also try AuthMech PLAIN when you upgrade to isync 1.2.1 from
> experimental (or build it yourself).
I did build it myself but, witch AuthMech PLAIN in my config's
IMAPAccount section, it still doesn't work. I am now getting:
[...]
Connection is now encrypted
Logging in...
Authenticating with SASL mechanism PLAIN...
IMAP command 'AUTHENTICATE PLAIN ' returned an error: NO
AUTHENTICATE GroupWise login failed

cheers, 
P

--
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://makebettercode.com/inteldaal-eval
___
isync-devel mailing list
isync-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/isync-devel

no login, every 3rd attempt

[Peter P.]

Hi list,

there is a strange thing that is happening with one of my email accounts
and mbsync/isync 1.1.2 on Debian testing. The error message with the
verbose flag is:

* OK [CAPABILITY IMAP4rev1 STARTTLS LOGINDISABLED] GroupWise Server
* Ready
>>> 1 STARTTLS
1 OK Begin TLS negotiation
>>> 2 CAPABILITY
* CAPABILITY IMAP4rev1 AUTH=PLAIN AUTH=XGWTRUSTEDAPP UNSELECT
* XGWEXTENSIONS
2 OK CAPABILITY completed
>>> 3 LOGIN  
[then after some time]
IMAP command 'LOGIN  ' returned an error: NO LOGIN 
GroupWise login failed

Every third time or so I would get beyond that point with
3 OK LOGIN completed
and so on and so forth.

Is there anything I could try to get more stable logins? Is it me,
mbsync or the mail server?

Thank you so much for any advice, and for your kind support!
best, Peter

--
___
isync-devel mailing list
isync-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/isync-devel

Re: ssl3 error

[Peter P.]

Dear list,

* Peter P. <peterpar...@fastmail.com> [2016-01-25 18:39]:
> Hi list,
> 
> since today I am getting the following error in mbsync with one of
> multiple webservers:
> 
> Syncing mailboxes and sending mail. Socket error: secure connect to 
> mail.someplace.com (192.192.192.192:143): error:14090086:SSL 
> routines:ssl3_get_server_certificate:certificate verify failed

I am replying to myself. I was able to connect to the server by
specifying 
UseIMAPS yes
in my config file. Still wondering what act (on the server / admin side)
might have had made this necessary.

cheers, P

--
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=267308311=/4140
___
isync-devel mailing list
isync-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/isync-devel

Re: office365 unexpected EOF

[Peter P.]

Dear Oswald,

* Oswald Buddenhagen <oswald.buddenha...@gmx.de> [2016-01-18 11:30]:
> On Mon, Jan 18, 2016 at 11:32:44AM +0300, Evgeniy Berdnikov wrote:
> > On Mon, Jan 18, 2016 at 01:05:15AM +0100, Peter P. wrote:
> > > Socket error: secure connect to outlook.office365.com 
> > > (132.245.34.242:993): unexpected EOF
> > > 
> > > Running mbsync -D for debugging messages did not produce any other
> > > lines.
> > > 
> > > Thappens every tenth sync or so. Could there be a particular reason for
> > > it, and possibly even a cure?
> > 
> >  Probably microsoft server is overloaded, so it randomly drops new 
> > connections.
> > 
> no, it drops connections in any state. there are several modes of
> failure, but it all boils down to the server(s) being crap.
Seems to be so indeed.
 
> i'm thinking of adding an auto-reconnect mechanism, but i don't consider
> it too urgent - the next sync is always just five minutes away, and will
> _probably_ succeed.
In my case I am querying the exit status of mbloop to inform the user
(myself) of anything that has not succeeded. These office666.com errors
do trigger a bad exit status, and I go looking...
Would be great, really great, Oswald, if your auto-reconnect could make
it into master indeed.

Thank you so much!
have a nice week!
P

--
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=267308311=/4140
___
isync-devel mailing list
isync-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/isync-devel

unexpecteg tag, and uidvalidity changes

[Peter P.]

Hi list,

I am happily syncing about ten different email accounts with mbsync.
Strangely a few of them do change their uidvalidity almost once every
three months.

Now when re-syncing, the process stops after a few synced mails with the
message:

IMAP error: unexpected tag XYZ

where XYZ is any random gibberish, sometimes parts out of email headers
and bodies. Upon re-running the same sync, the contents of XYZ change.

This is currently on a Microsoft Exchange IMAP4 server, and has also
happened on a Groupwise server in the last days, with isync isync 1.1.2

On a more general scope, as I do have to delete the affected folder's
.mbsyncstate files, and re-sync/delete duplicates every time, I wonder:

What could be common reasons for the servers to change their
uidvalidity?
Why is this an issue to me with mbsync, but not with something like
thunderbird, or mutt-accessing-imapServer-directly?
Is there any better, yet still safe and simple, way to work around
changed uidvalidities, or even more permanent fixes?

Thanks for all ideas and comments!

cheers, P

--
___
isync-devel mailing list
isync-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/isync-devel

Re: Create Slave versus Pattern precedence?

[Peter P.]

Hallo Oswald,

* Oswald Buddenhagen <oswald.buddenha...@gmx.de> [2015-11-04 08:19]:
> On Tue, Nov 03, 2015 at 02:08:12PM +0100, Peter P. wrote:
> > * Oswald Buddenhagen <oswald.buddenha...@gmx.de> [2015-10-23 13:59]:
> > > On Thu, Oct 22, 2015 at 06:04:00PM -0400, Peter P. wrote:
> > > > Hi list,
> > > > 
> > > > I don't want to sync a certain folder, hence I have set
> > > > Patterns * !CertainFolder
> > > > and delete the folder off my disk on the local store.
> > > > 
> > > > Am I correct to assume that it nevertheless gets re-created unless I
> > > > unset 'Create Slave' as well? 
> > > > 
> > > no. that would be a bug.
> > Ok, I tried once more and having 
> > 
> > Patterns *!CertainFolder !INBOX.CertainFolder
> >
> that would have to use a slash, not a dot.
I see, and the folder does not get created when I specify 
Patterns * !INBOX/CertainFolder

So the problem is solved, thank you so much! Excuse me for the fuss.

best, P

--
___
isync-devel mailing list
isync-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/isync-devel

Deleting/expunging mails

[Peter P.]

Hi list,

I am ending up with duplicates in my trash folders regularly, and would
like to avoid them. Perhaps this is a mutt issue, but let me ask here
first.

I run the identical setup of (mutt + mbsync) on two computers, and when
I delete a message on one machine using mutt, it is moved to a trash
folder. These changes are propagated to the server.

Now when I go to the second computer, and do a sync, the above deleted
message is also in the second computer's trash folder. But it
message shows up in the original folder in mutt, with the deleted "D"
flag set. When I change folders in this mutt, or use the 'x' expunge
shortcut, this message gets moved to the trash folder again, causing a
duplicate.

This happens regardless of the .mbsynrc option 'Trash' being set or not.

I tried the mbsync options "TrashNewOnly" or "TrashRemoteNew", but they
don't help (and I haven't understood them properly I am afraid).

My mutt has the Trash-patch compiled in (it is Debian's packaged mutt),
and has the following option:   set trash="+INBOX.Trash"
which points to the correct trash folder.

If anyone has an idea about what I could try next I'd be happy to know.

Thank you so much!
Peter

--
___
isync-devel mailing list
isync-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/isync-devel

Create Slave versus Pattern precedence?

[Peter P.]

Hi list,

I don't want to sync a certain folder, hence I have set
Patterns * !CertainFolder
and delete the folder off my disk on the local store.

Am I correct to assume that it nevertheless gets re-created unless I
unset 'Create Slave' as well? 

It could be nice to have the Patterns option also prevent the creation
of a local folder, but I am happy to live with the current behavior. I
just want to make sure I am understanding things correctly.

Thanks for any comments,
Peter

--
___
isync-devel mailing list
isync-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/isync-devel

Trash folder changes not synced back to server?

[Peter P.]

Hi list,

I am trying to understand why changes of messages deleted and expunged
from a local Trash folder are not propagated back to the server's
Trash folder.

I am using mutt with the Trash-patch and messages deleted by the user
are moved to .imapMail/account1/INBOX.Trash/
When deleting and expunging messages from that Trash folder, these
changes are not propagated to the Imap server. I am trying to
understand why.

When I run mbsync I get an unsuspiciously looking
Synchronizing...
Selecting master INBOX/Trash...
Selecting slave INBOX/Trash...
Loading master...
Loading slave...
slave: 282 messages, 118 recent
master: 1304 messages, 0 recent
Synchronizing...

I have not set any Trash... options in my .mbsyncrc. The respective
configs for that account look like

[...]
IMAPStore account1-remote
Account account1
Path INBOX
[...]

MaildirStore account1-local
Path ~/.imapMail/account1/
Inbox ~/.imapMail/account1/INBOX
Flatten .

[...]
Channel account1
Master :account1-remote:
Slave :account1-local:
Patterns * !Archive
Create Slave
SyncState *

Thank you for any hints helping me to understand this problem.

best, Peter

--
___
isync-devel mailing list
isync-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/isync-devel

Re: Trash folder changes not synced back to server?

[Peter P.]

Hi list,

following up to my last mail, below.

* Peter P. peterpar...@fastmail.com [2015-07-23 12:19]:
 Hi list,
 
 I am trying to understand why changes of messages deleted and expunged
 from a local Trash folder are not propagated back to the server's
 Trash folder.
 
 I am using mutt with the Trash-patch and messages deleted by the user
 are moved to .imapMail/account1/INBOX.Trash/
 When deleting and expunging messages from that Trash folder, these
 changes are not propagated to the Imap server. I am trying to
 understand why.

I ran mbsync from a different machine which has its own local storage,
and there the Trash was propagated correctly to the server. The config
files on the two machines are identical. So that leaves the question
open, and the problem resolved for now.

Thanks,
Peter

--
___
isync-devel mailing list
isync-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/isync-devel

multiple instances of mbsync at the same time: dangerous?

[Peter P.]

Hi list,

I am running mbsync periodically from a script within an endless loop.
Nevertheless I would sometimes force a sync by executing mbloop manually
as well. I could start to have my script write lockfiles while syncing,
so that no two mbsync processes would be syncing the same mailbox, but
would this actually be necessary? Is there an inherent danger in having
two mbsyncs do their work at the same time, could they somehow conflict?

Thank you for your advice,
Peter

--
One dashboard for servers and applications across Physical-Virtual-Cloud 
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
___
isync-devel mailing list
isync-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/isync-devel

Re: incomplete journal entry

[Peter P.]

* Oswald Buddenhagen oswald.buddenha...@gmx.de [2015-04-27 16:15]:
 On Mon, Apr 27, 2015 at 07:53:51AM -0400, Peter P. wrote:
  * Oswald Buddenhagen oswald.buddenha...@gmx.de [2015-04-27 03:36]:
   On Sun, Apr 26, 2015 at 08:45:48PM -0400, Peter P. wrote:
Hi list,

I do get 

Error: incomplete journal entry at 
/home/user/mbsyncdir/account/INBOX/.mbsyncstate.journal:2

when running mbsync, and have not found anything about it online. Am not
out of disk space.

   head -5 .mbsyncstate.journal
   ?
  
  MasterUidValidity 1126786399
  SlaveUidValidity 1429562496
  MaxPulledUid 75856
  MaxPushedUid 0
  
 that looks like the state file itself, not the journal. if this *is*
 your journal, then i'd start worrying about file system integrity.

Sorry, my mistake. The contents of the .mbsyncstate.journal are
2

thanks for considering this and providing your help and support!
best, P

--
One dashboard for servers and applications across Physical-Virtual-Cloud 
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
___
isync-devel mailing list
isync-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/isync-devel

incomplete journal entry

[Peter P.]

Hi list,

I do get 

Error: incomplete journal entry at 
/home/user/mbsyncdir/account/INBOX/.mbsyncstate.journal:2

when running mbsync, and have not found anything about it online. Am not
out of disk space.

Thanks for any pointers, they are very welcome!
best, Peter

--
One dashboard for servers and applications across Physical-Virtual-Cloud 
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
___
isync-devel mailing list
isync-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/isync-devel

triangle sync?

[Peter P.]

Dear list,

please excuse this perhaps trivial question, but what would happen if I
run mbsync on two computers, each syncing from and to the same mail server?

For example I sync both boxes, then I delete one mail on the first box,
a different mail on the second box, and then I sync them again in any
random order. What would the resulting state be? Would, after the next
sync, both mails be deleted on both boxes?

Thank you for your advice!
P

--
BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT
Develop your own process in accordance with the BPMN 2 standard
Learn Process modeling best practices with Bonita BPM through live exercises
http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_
source=Sourceforge_BPM_Camp_5_6_15utm_medium=emailutm_campaign=VA_SF
___
isync-devel mailing list
isync-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/isync-devel