Re: gmail-trash master cannot be opened

2022-02-18 Thread Oswald Buddenhagen
On Fri, Feb 18, 2022 at 03:15:42PM -0500, David Denton wrote: Here is the result with the new channel: you need to actually use it in the command invocation ... ___ isync-devel mailing list isync-devel@lists.sourceforge.net https://lists.sourceforge

Re: gmail-trash master cannot be opened

2022-02-18 Thread David Denton
Here is the result with the new channel: Reading configuration file /home/david/.mbsyncrc Channel gmail-trash Opening master store gmail-remote... M: [ 1] Enter connect_store Resolving imap.gmail.com... ok Connecting to imap.gmail.com (172.253.63.109:993)... M: [ 1] Leave connect_store Opening sl

Re: gmail-trash master cannot be opened

2022-02-18 Thread Oswald Buddenhagen
On Fri, Feb 18, 2022 at 11:07:41AM -0500, David Denton wrote: The output from mbsync -D -l gmail-trash is attached. ok, that was of course a stupid request from me, as the output was predictable. instead, create a channel like this: Channel gmail-fake Master :gmail-remote: Slave :gmail-local

Re: gmail-trash master cannot be opened

2022-02-18 Thread David Denton
Please find my config, below. The output from mbsync -D -l gmail-trash is attached. Thank you. David # mbsyncrc based on # http://www.ict4g.net/adolfo/notes/2014/12/27/EmacsIMAP.html # ACCOUNT INFORMATION IMAPAccount gmail # Address to connect to Host imap.gmail.com User my_email_addr...@gmail

Re: gmail-trash master cannot be opened

2022-02-18 Thread Oswald Buddenhagen
On Fri, Feb 18, 2022 at 07:17:40AM -0500, David Denton wrote: Error: channel gmail-trash: master [Gmail]/Bin cannot be opened. This problem arrived suddenly, for no apparent reason, after my present set-up had been working well for a couple of months. well, obviously, *something* must have c

gmail-trash master cannot be opened

2022-02-18 Thread David Denton
Hello, I am getting the following error message with mbsync -a: Error: channel gmail-trash: master [Gmail]/Bin cannot be opened. I have had this for several days, and mail marked for deletion in mu4e is accumulating. This problem arrived suddenly, for no apparent reason, after my present set-