Hi all,
On 04.12.24 06:43 Johannes Kastl wrote:
> Hi Oswald,
>
> On 02.12.24 11:28 Oswald Buddenhagen via isync-devel wrote:
>> On Sun, Dec 01, 2024 at 08:47:48PM +0100, Johannes Kastl wrote:
>>>> Error: channel YYY: near side box INBOX/XXX cannot be opened.
>>
Hi Oswald,
On 02.12.24 11:28 Oswald Buddenhagen via isync-devel wrote:
> On Sun, Dec 01, 2024 at 08:47:48PM +0100, Johannes Kastl wrote:
>>> Error: channel YYY: near side box INBOX/XXX cannot be opened.
>>
>>Funnily enough, in one case this happened after the folder was c
Dear all,
today I noticed that some of my mbsync calls are returning errors.
> Error: channel YYY: near side box INBOX/XXX cannot be opened.
Funnily enough, in one case this happened after the folder was created
locally and the sync succeeded. On the next run the error above was shown.
The comm
Hi Oswald,
On 13.11.24 13:00 Oswald Buddenhagen via isync-devel wrote:
> On Wed, Nov 13, 2024 at 12:14:43PM +0100, Johannes Kastl wrote:
>>Due to a network timeout I had to retry, and mbsync "lost track of X
>>pulled messages".
>>
> that is expected ...
>
>
On 13.11.24 12:58 Bence Ferdinandy wrote:
> 2024. nov. 13. 12:40:59 Johannes Kastl :
>> Does anyone have a recommendation for a tool to cleanup such
>> duplicates?
>>
>> Linux CLI or something for Thunderbird would both be great.
>>
>
> I use mdedup
Hi all,
slightly offtopic:
I recently used mbsync to transfer a mailbox to another provider.
Mostly without hiccups, so big thank you!
Due to a network timeout I had to retry, and mbsync "lost track of X
pulled messages". Which means I have a lot of duplicates in that
mailbox now.
Does anyone h
On 22.07.22 02:28 Vikas Rawal wrote:
> I think it is working at the moment. But it stops every now and then. As
> you would see below, mbsync.service also ends with an error. There is no
> such error when I run mbsync -V daily myself. Is this error makes systemd
> stop running it repeatedly?
In ad
On 21.07.22 18:20 Vikas Rawal wrote:
> I have modified the scripts slightly based on recommendations on this
> thread. But this still does not work. I am just looking for mbsync to run
> every two minutes. What do most people use?
>
> It is crazy that something so obvious should be so difficult
Hi Oswald, hi Norbert,
On 28.01.22 11:44 Norbert Preining wrote:
>> though ... if you use *only* --pull-new, then you *might* get away with two
> [...]
>> if it doesn't work, just use fetchmail, which was designed for that use
>
> I think this is the core point. If one wants to put all the emai
Good morning Oswald,
On 28.01.22 00:22 Oswald Buddenhagen wrote:
> On Thu, Jan 27, 2022 at 09:09:06PM +0100, Johannes Kastl wrote:
>>Can I use mbsync/isync to collect mail from multiple mail accounts into
>>one central IMAP account?
>>
> yes, you can, as the manual kin
Good evening everyone,
maybe I am missing the right search terms, but: Can I use mbsync/isync
to collect mail from multiple mail accounts into one central IMAP account?
I find lots of explanations and tutorials for using local MailDir
folders and mutt and things like that, but either no one ever
Hi all,
I have prepared a working configuration that syncs my GMX mailbox to a
Hetzner account. It is using the Path solution I got in the other
thread (Two IMAPAccounts, each having one ImapStore without and one
with Path being set).
All channels work fine when I call them separately:
mbsync -c
Hi all,
On 21.03.21 12:36 Johannes Kastl wrote:
> On 19.03.21 18:31 Oswald Buddenhagen wrote:
>> On Fri, Mar 19, 2021 at 05:18:55PM +0100, Johannes Kastl wrote:
>>>Can someone enlighten me where my error is?
>>>
>> you need to use uppercase INBOX/ for Path.
>
On 19.03.21 18:31 Oswald Buddenhagen wrote:
> On Fri, Mar 19, 2021 at 05:18:55PM +0100, Johannes Kastl wrote:
>>Can someone enlighten me where my error is?
>>
> you need to use uppercase INBOX/ for Path.
Ah yes, thanks that did the trick. I was hoping it was something
obvious
Hi all,
taking this back to the list, Oswald was kind enough to help me and
recommended to go a two-step approach. The mail server's layouts are
too different, to find a solution in one go.
On 15.03.21 16:14 Oswald Buddenhagen wrote:
[ Sync of subfolders of the Inbox fails]
If I understood Oswal
On 13.03.21 20:01 Oswald Buddenhagen wrote:
> which version of mbsync exactly are you using? 1.3.4 fixed a related bug
> (which was introduced in 1.3.2, and other related issues existed before
> that).
1.3.5
> other than that, the debugging instructions are the same as last time
> [...]
> Op
Hi all,
I tested a one-way sync from GMX to HETZNER IMAP mailboxes.
The HETZNER one needs "Path INBOX." to get it working, apparently.
The first sync went well, all folders were created and synced. But
apparently something is fishy on the second sync.
All subfolders of the original GMX INBOX ar
Hi Oswald,
On 10.03.21 22:45 Oswald Buddenhagen wrote:
> On Wed, Mar 10, 2021 at 10:19:28PM +0100, Johannes Kastl wrote:
>>IMAP warning: ignoring INBOX in INBOX.GMX.
>>
> that's weird. please post the output of mbsync -D -l -a.
The relevant parts should be this:
&
Hi all,
for some reason my offlineimap setup (long long ago) synced one IMAP
account into another one, but into a subfolder ("GMX").
I tried to recreate this in mbsync and almost succeeded, but I have on
error message left that I still cannot get rid of.
Basically it boils down to this setting o
Hi all,
just to make sure I understood the documentation properly:
If I have a one-way sync and folders on the master get deleted, I get
a warning during sync but the folders will not be removed from the
slave? Even though "Remove Slave" is set?
Or is this only if the initial sync happens with a
20 matches
Mail list logo
