On Wed, Sep 03, 2025 at 11:34:25PM +0800, yueqr wrote:
(gdb) bt
...
that backtrace makes no sense at all; the stack is probably corrupted.
I've noticed some mention from mail list that varlingd may helped for more
information, but I need some more time to know how to work with varlingd.
va
On Thu, Jul 31, 2025 at 12:53:06PM +0200, Alan Schmitt wrote:
- is there a way to remove all these duplicate emails?
any message-id based method will work for most mails. the list archive
contains several related threads.
- for the last channel to migrate, how can I make sure emails are not
On Thu, Jul 24, 2025 at 10:10:31AM +0300, Evgeniy Berdnikov wrote:
On Wed, Jul 23, 2025 at 04:57:51PM +0200, Antoine Fauchié wrote:
I've just reinstalled mbsync on a new Debian installation (12), and I
can't get mbsync/isync to work on 1.5.1 version.
The error message:
Error: mbsync built wit
On Thu, Jul 17, 2025 at 10:33:36PM +0200, Daniel Tameling wrote:
mv $(mlist ./INBOX | mpick -t 'from =~ "@github"') ./github/cur
this will preserve the ,U=nnn infixes of the files, which is a very bad
idea.
___
isync-devel mailing list
isync-devel
On Wed, Jul 16, 2025 at 09:37:51AM +0200, Peter P. wrote:
Can isync sync emails through such connections as well?
yes.
you can run an imap server on the ssh host and have ssh forward the port
to your local host, which you then connect via isync.
Is the "Tunnel" commenad the way to go?
al
On Mon, Jun 30, 2025 at 09:58:01PM +0200, kohn...@gmx.com wrote:
For example, it should move like this.
~/Mail/x...@gmx.com/INBOX/cur/1750696320.159179_1.shuttle-fedora,U=1:2,S
~/Mail/x...@gmx.com/Spam/cur/1750696320.159179_1.shuttle-fedora
well, and there is your problem. when you throw away t
On Sun, Jun 29, 2025 at 11:39:13PM +0200, kohnish--- via isync-devel wrote:
Is there a way to send SEEN command when a mail is moved to another
folder?
there is no such command.
however, isync synchronizes the \Seen flag by default, so things should
just work.
presumably, something is wrong w
On Mon, Jun 02, 2025 at 07:43:35PM +0200, Jonathan Schöbel wrote:
I filed that change against 1.3.0 since that is what I have installed
on Debian 11. If it is going to be packaged it would be nice to also
provide another backport for this Debian version.
if you're building from source, you ca
On Wed, Mar 26, 2025 at 12:35:34PM +0100, inwit wrote:
On 26/03/2025, 12:30, Oswald Buddenhagen via isync-devel wrote:
yes, due to the re-consolidation of the output format, there is now no
distinction between "would" and "did" in the output, as it's just
numbers.
On Wed, Mar 26, 2025 at 12:23:55PM +0100, inwit wrote:
On 26/03/2025, 11:49, Oswald Buddenhagen via isync-devel wrote:
such a bug was fixed in 1.5.1.
Is it possible that in this last version it doesn't explicitly say what "would
have" done in the final summary?
assuming i
On Wed, Mar 26, 2025 at 11:08:26AM +0100, inwit wrote:
I'm observing a disturbing behaviour of mbsync, both in v1.5.0 and in
v1.5.1. When I add the --dry-run flag, mbsync ignores it and does alter
my mailboxes, both far and near.
such a bug was fixed in 1.5.1.
did you confirm with `mbsync -v` t
On Wed, Mar 19, 2025 at 07:53:38PM -0700, Christopher Snowhill wrote:
I am attempting to move messages between folders, and it is deleting
from the inbox and uploading to the Archive folder. However, while the
upload works, deletion is failing:
IMAP command 'UID STORE 13345 +FLAGS.SILENT (\Delet
On Fri, Mar 14, 2025 at 02:33:35PM -0400, Amulya Mohan wrote:
I am using aerc for viewing the emails, and the emails display -- there
is simply a large gap in what emails were being fetched.
i'm assuming you're talking about your client side here.
for debugging, you need to access the imap mai
On Thu, Mar 13, 2025 at 11:11:23PM -0400, Amulya Mohan wrote:
How do I get the emails from between March 04 and 1 hour ago?
have you tried an interactive imap client (say, thunderbird) to see
whether the mails are exposed via email at all? if not, then there is
nothing isync can do about it.
if
On Mon, Jan 13, 2025 at 04:33:32PM -0800, Hong Xu wrote:
However, consumer-grade hardware is prone to RAM bit flips, at a higher
rate than what most people probably think. The most recent research I
knew is discussed on Wikipedia [2], which shows the error rate was on
the magnitude of 1 bit error
On Mon, Jan 13, 2025 at 01:33:54AM -0800, Hong Xu wrote:
Does isync perform any checks (like some checksum) to prevent data loss
in an event of RAM error?
no, and the idea doesn't even make much sense. there would have to be a
checksum to compare to, and that couldn't be calculated before the d
On Fri, Dec 20, 2024 at 10:08:29AM +0100, Peter P. wrote:
Can someone possibly confirm that these
messages are not transferred by mbsync from an imap server?
isync transfers everything it sees on imap, and that doesn't even have
to be messages (though objects not compliant with rfc822 would get
On Wed, Dec 18, 2024 at 10:53:23PM +0100, Bence Ferdinandy wrote:
F: >>> 2 AUTHENTICATE PLAIN
Now for Ubuntu I know I had to mess around SASL and even build
moriyoshi/cyrus-sasl-xoauth2.git manually to make things work,
but this doesn't look like an issue with that.
but it totally does.
On Wed, Dec 18, 2024 at 02:33:51PM +0100, Bence Ferdinandy wrote:
it was probably not the best idea, but I moved computers, by coping all
my
maildir and isync config, but not the isync state (in retrospect, I probably
should have done that).
yeah ...
I ran isync (1.5.0) and some emails got du
On Sun, Dec 08, 2024 at 09:23:11AM +0100, Johannes Kastl wrote:
Error: channel XXX: near side box INBOX/20140102_BACKUP cannot be opened.
I can send the log directly, if it is any help?
yes, but let's go for the complete set:
- your config file
- cd ; find -type d
- mbsync -D -ls
- mbsync -D
On Fri, Dec 06, 2024 at 05:07:49PM -0800, Robin Lee Powell via isync-devel
wrote:
mbsync: socket.c:957: socket_read: Assertion `min_len <= max_len' failed.
this is already fixed in master as of a few days ago.
___
isync-devel mailing list
isync-dev
On Wed, Dec 04, 2024 at 11:15:29AM -0500, Paymon wrote:
spoke to early; it's git-branch that returns something like this:
* (HEAD detached at refs/git-r3/HEAD)
that escapes our regex.
i would pass `--always` unconditionally to be defensive about it; what do you
think?
i did that, with a force
On Wed, Dec 04, 2024 at 10:50:43AM -0500, Paymon wrote:
+++ b/version.sh
@@ -22,7 +22,7 @@ else
# find out whether we have local work, and if so, collapse it into
# a single suffix. otherwise, we'd cause pointless rebuilds during
# development.
- gver=$(git describe
On Tue, Dec 03, 2024 at 04:12:09PM +, Sabahattin Gucukoglu via isync-devel
wrote:
So my question is this: is it expected behaviour that timeouts occur
because of long local operations,
yes, sort of.
and is it *correct* or desirable behaviour?
certainly not desirable.
Isn’t the “right
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 created
locally and the sync succeeded. On the next run the error above was shown.
weird. try 'mbsync -l
On Fri, Nov 29, 2024 at 06:21:45PM -0500, Paymon MARANDI wrote:
any feedback?
yeah, sorry, i've been procrastinating and then it went out of view ...
i don't like it, because it makes the version info useless, which would
make worse log files. adding --always to the describe command seems less
On Tue, Nov 19, 2024 at 06:26:06PM -0800, Akshay Hegde wrote:
Like most new UIs, my initial reaction was 'oh I don't like that', but
perhaps I just need to get used to it.
i thought that myself, but i'm at the point where i've concluded that it
was simply a stupid idea.
On Wed, Nov 20, 2024 at
On Mon, Nov 18, 2024 at 08:22:21PM -0800, Akshay Hegde via isync-devel wrote:
I updated to isync 1.5.0 recently and noticed that my console logs from
mbsync are now a more verbose, and to me personally-harder to read at
a glance:
Processed 40 box(es) in 1 channel(s),
pulled 0 new message(s
On Mon, Nov 18, 2024 at 09:51:53PM -0600, Liam Hupfer wrote:
now my desktop seems to move them back when syncing.
no idea why it would do that.
add -Ds to the command line and try to make sense of what it says.
___
isync-devel mailing list
isync-dev
On Thu, Nov 14, 2024 at 12:44:50PM +1100, sourcefo...@plast.id.au wrote:
I assume this is the way that I can fix my problem? I can grep through
all my `.mbsyncstate` files for `0` in the first field, then delete the
corresponding messages. I'm not entirely sure what the `0` means; do
you think it
On Wed, Nov 13, 2024 at 10:34:58AM +1100, sourcefo...@plast.id.au wrote:
The local side was also previously expunged. None of the files have a T
flag, including the "local only" messages.
ok.
have you tried the MaxPushedUid reset hack after expunging?
if that doesn't help, add -D to the comman
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 ...
Which means I have a lot of duplicates in that mailbox now.
.. but not that.
so if you actually have dupes, they likely
On Wed, Nov 13, 2024 at 08:56:54PM +1100, sourcefo...@plast.id.au wrote:
I've attached the log.
you forgot to drop the list. but never mind, the log was small.
I'm not sure if helpful, but one of the messages that exists on my local system
and not the remote system is named
1730960491.4006
On Tue, Nov 12, 2024 at 10:41:29PM +1100, sourcefo...@plast.id.au wrote:
I thought it might be expunge related, so I went into the server and
expunged everything manually. This made no difference.
as it's the local side that seems to have excess messages, it is the one
that would need expunging
On Tue, Nov 12, 2024 at 12:34:07PM +1100, sourcefo...@plast.id.au wrote:
$ mbsync -V --pull foo:INBOX
On some systems, the near side has *more* emails than the far side.
that's entirely expected when you only ever use --pull.
another thing to check would be whether you're expunging.
___
On Wed, Nov 06, 2024 at 06:50:39PM +0100, Henrik Frisk wrote:
* 126 FETCH (UID 37160 BODY[] {2012973}
=== (10 bytes omitted)
=== (10 bytes omitted)
=== (10 bytes omitted)
Socket error: receive buffer full. Probably protocol error.
are you _sure_ you're running the actual 1.5.0 rele
2024. nov. 2. 11:11:53 Henrik Frisk :
I decided to give this a try again (see my message from April 1).
please include an archive link for readers' convenience:
https://sourceforge.net/p/isync/mailman/isync-devel/thread/CAO0LSb6H8trfEJnkP5Va5xvoNg-d6qrBJbrnk_vf0BJWJNUqEQ%40mail.gmail.com/#msg58
On Tue, Oct 29, 2024 at 08:30:47AM -0400, Britt Anderson wrote:
On upgrading from isync 1.5.0.1 to 1.5.0.2 I now get this message. I am
using the ArchLinux package. I do have an AltMap yes in my config. On
downgrading to 1.5.0.1 everything works fine.
given that these versions don't even exist
On Mon, Oct 14, 2024 at 03:16:36PM +0100, Dom (shymega) Rodriguez wrote:
On 23.09.2024 10:34, Oswald Buddenhagen via isync-devel wrote:
On Sun, Sep 22, 2024 at 06:09:06PM +0200, Dom (shymega) Rodriguez wrote:
As well as that, I find OWA has the dates in the wrong order after
syncing. I have
On Tue, Oct 08, 2024 at 09:40:43AM +0200, Jan Eden via isync-devel wrote:
Is there anything I can do to debug?
when you report problems, always include your config file.
as a first test, try `mbsync -l ...` to see which boxes isync thinks are
present.
if it's there, search the list archive fo
On Sun, Sep 29, 2024 at 12:18:14PM +, Behnam Lal Moghaddam wrote:
I just didn't bother to change the name ever, so that pseudonym has
been used more often than my real name.
heh, ok.
i made a few fixups. unless you see something wrong with it, i'll push
this version at some point.
From 33b
On Sat, Sep 28, 2024 at 11:54:56PM +, Behnam Lal Moghaddam wrote:
On 24/09/28 02:03PM, Oswald Buddenhagen via isync-devel wrote:
a few suggestions:
I rewrote the patch according to your suggestions.
ok. i see you removed the port config entirely, which is fair enough.
however, i don&#
On Sat, Sep 28, 2024 at 05:17:55PM +, Ludovico Gerardi wrote:
The problem is that I still have the older outgoing messages in the
renamed file, and I don't know how to convert those into the format that
mbsync uses, with the right UID etc. Could anyone help me please?
you don't need to worr
On Sat, Sep 28, 2024 at 09:23:49AM +, Behnam Lal Moghaddam wrote:
I want to share a patch that allows mbsync-get-cert script to support
STARTTLS and custom port.
thanks!
a few suggestions:
- use true/false for $STARTTLS - then you can evaluate it without
running it through `test`
- don't
On Sun, Sep 22, 2024 at 06:09:06PM +0200, Dom (shymega) Rodriguez wrote:
As well as that, I find OWA has the dates in the wrong order after
syncing. I have `CopyArrivalDates` set as true.
you mean, the pull causes the server to re-stamp the messages? that's
just weird ...
I'm not sure how com
On Fri, Sep 20, 2024 at 11:55:19AM +0100, Edd Barrett wrote:
And if you re-run it again, I see the same discrepancy between the
mesage
counts on hte near and far sides. So it's still not syncing.
After those two runs, I notice that MaxPulledUid and MaxPushedUid remain zero.
Is that right?
iirc
On Fri, Sep 20, 2024 at 09:04:57AM +0100, Edd Barrett wrote:
However I notice that after a sync, mailboxes can be of differing sizes
on
different hosts. For example last night, the Inbox folder had:
- 5826 messages on the IMAP server
- 5860 messages on the desktop
- 5833 messages on the laptop
On Sat, Sep 14, 2024 at 01:20:25PM +0200, Tamás Gulácsi via isync-devel wrote:
Patterns "!Trash !Conversation !Deleted !Drafts !Junk !Outbox !RSS !Scheduled"
Patterns "!\"Conversation History\" !\"Deleted Items\""
Patterns "!\"Junk Email\""
Patterns "!\"RSS Feeds\""
fwiw, you have a level of qu
On Fri, Sep 13, 2024 at 07:00:02AM +, jordan--- via isync-devel wrote:
I found a report on Reddit that looks like a similar problem, but with
no resolution:
https://www.reddit.com/r/commandline/comments/1d9ik8a/mbsync_not_downloading_all_messages/
Do you have any suggestions on what I might
On Thu, Aug 29, 2024 at 03:57:39PM +0200, Alan Schmitt wrote:
F: >>> 7 UID FETCH 1949470 (BODY.PEEK[])
F: * 14550 FETCH (UID 1949470 BODY[] "")
IMAP error: malformed FETCH response from : BODY is no literal
Is there a way to ignore the problematic message and synchronize the
other ones?
On Sun, Aug 18, 2024 at 08:33:06PM +0900, Norbert Preining wrote:
Do you have any suggestions how to deal with this issue?
first you could check whether this is a "real" issue or "just" fallout
from having legacy folders. that is, do a (partial) sync from scratch
into a temporary folder. if tha
On Sun, Aug 18, 2024 at 12:24:09AM +0200, Felix Fontein via isync-devel wrote:
I upgraded to isync 1.5.0 today and noticed a bug.
yep, https://sourceforge.net/p/isync/bugs/77/
___
isync-devel mailing list
isync-devel@lists.sourceforge.net
https://l
On Fri, Aug 16, 2024 at 10:14:10PM +0200, Jan Eden via isync-devel wrote:
I get three different results when specifying the channels directly,
depending on their order: [...]
it might be helpful if you mention which case used which arguments.
I installed isync via homebrew (slightly altering
On Fri, Aug 16, 2024 at 10:46:22AM +0200, Jan Eden via isync-devel wrote:
Although I found a practical solution (i.e. a working order), I would
be
grateful if someone could explain what is going on here.
a bug, rather obviously.
is the problem reproducible with `mbsync -ls`?
if not, with `mbsy
On Thu, Aug 15, 2024 at 08:15:34AM -0400, Laurent Michel wrote:
Gotcha. Though, I must say I did not have a “.mbsync” folder. That
is still mysterious to me (I compilde isync from the git repo directly,
main branch).
git master since two years (and now 1.5.0) defaults to
$XDG_STATE_HOME/isync/
On Thu, Aug 08, 2024 at 11:07:38AM +0900, Norbert Preining wrote:
On Thu, 08 Aug 2024, Norbert Preining wrote:
Maildir store '-local': Path cannot be nested under Inbox
The respective entry in .mbsyncrc is:
MaildirStore -local
Path ~/Maildir//
Adding
On Wed, Aug 07, 2024 at 06:27:35AM +0700, Louis A. Turk via isync-devel wrote:
Error: Cannot resolve server 'mail.firmanelohim.org/': Name or service not
known.
Is my .mbsyncrc correct?
no:
Host mail.fm.org/
that trailing slash makes no sense at all.
maybe you got confused by the requirem
On Mon, Oct 31, 2022 at 03:43:28PM +, Edd Barrett wrote:
On Fri, Oct 28, 2022 at 05:04:10PM +0200, Oswald Buddenhagen wrote:
i need the full log. in fact, of two consecutive runs, as this is an
inter-run problem. you can limit it on the command line to the affected
mailbox, and send me the l
On Fri, Jul 26, 2024 at 09:12:54AM +0200, Alan Schmitt wrote:
Running using --verbose made me realize there is a significant
difference in the number of messages in the local and remote sides:
Opening far side box INBOX...
Opening near side box INBOX...
Loading far side box...
Loading near side
On Tue, Jul 16, 2024 at 04:55:22PM +, Johan Parin wrote:
So are you saying this is an Exchange problem or a DavMail problem?
davmail. that's why i'm strongly suggesting that you try "native"
exchange imap (it's not really native; it's also just a translation
layer, but at least it's directl
On Tue, Jul 16, 2024 at 01:44:50PM +, Johan Parin wrote:
That pulled around 2.5K messages. Now I can see on Outlook web my Inbox
has 19077 items. With notmuch I get after 'notmuch new':
$ notmuch count folder:work/INBOX
19074
I guess that is close enough.
well, that probably means that
On Tue, Jul 16, 2024 at 05:10:11AM +, Johan Parin wrote:
So what I'm doing is I have copied the settings from Evolution
(including tenantID) from Linux users in the company (as Linux &
Evolution is a supported configuration in our IT policy), so I pretend
I'm using Evolution.
yes, that's pa
On Sun, Jul 14, 2024 at 03:09:58PM +, Johan Parin via isync-devel wrote:
I have a setup at work where the company is using MS Exchange +
OAUTH2. I use DavMail to deal with OAUTH2 and then mbsync to connect to
DavMail. As MUA I use notmuch.
This was working OK for a while I think but then I s
On Wed, Jul 10, 2024 at 11:34:59AM +, Thomas Bergheim wrote:
Everything works great, except for this bug.
isync just thinks it already synced everything it should have. the log
merely reflects a static state, so it doesn't help with figuring out how
this happened.
you can work around the s
On Mon, Jul 08, 2024 at 09:48:27AM -0400, Paymon wrote:
On Mon, Jul 08, 2024 at 09:44:27AM GMT, Paymon wrote:
my case is the opposite of that^; i.e. i have a very small quota on
the server
and a fairly big amount incoming messages (mailing lists). i want to archive
the mailing list locally where
On Sun, Jul 07, 2024 at 02:28:54PM +0800, Runxi Yu wrote:
Could this be made into the next release?
yes, of course. but don't expect this to happen very soon (someone needs
to figure out what exactly is wrong with commit 859b7dd7).
___
isync-devel m
On Thu, Jul 04, 2024 at 02:00:30PM +0800, runxiyu-ld/isync--- via isync-devel
wrote:
Note that I only experience this error when ~/.local/share/mail/runxiyu
is empty. If I have a successful previous run, subsequent syncs work.
Running it causes a segfault.
[...]
thanks for the thorough repor
On Mon, Jun 10, 2024 at 09:45:37AM +0200, Henrik Frisk wrote:
So sorry this dragged out.
well, _i_ am in no hurry ...
I would be so happy if you have the time to take
a look at these files attached which are the logs from mbsync and
DavMail.
somewhat guessing here, but this seems to be a ge
On Sun, Jun 09, 2024 at 12:52:26PM -0600, Steve Mayer wrote:
Thanks Oswald! I’ve attached the output of ‘mbsync —debug
iCloud’.
that's not useful, as it is from an obviously stable state. you need to
"catch it in the act". if you can't repro it differently, start from
scratch, logging both the
On Sun, Jun 09, 2024 at 09:40:08AM -0600, Steve Mayer via isync-devel wrote:
Any ideas as to what might be going on?
not really. i suppose the server might be doing funny things.
re-run with -D and send me the log - maybe i can spot something.
___
i
On Thu, May 16, 2024 at 12:18:36PM +0200, Henrik Frisk wrote:
Despite my best efforts, trying the things suggested here and a bunch
of
other stuff to do with the configuration of davmail and mbsync I can't get
this to work. I guess my main question to this list is if this is a davmail
problem or
On Mon, Apr 01, 2024 at 09:09:16PM +0200, Oswald Buddenhagen via isync-devel
wrote:
[...] mail me the logs.
so with the logs at hand it really looks like the imap server is acting
up:
first run:
F: >>> 10 APPEND "Folders/Test2" (\Seen) {6229}
F: + Ready
F: * 1 EXISTS
F:
On Mon, Apr 01, 2024 at 08:03:22PM +0200, laburnumT wrote:
When I look at my settings in Gmail it is set to Auto-Expunge off -
Wait
for the client to update the server.
that's weird, because the log shows somewhat clearly that a message is
expunged before an expunge or close command is issued.
On Mon, Apr 01, 2024 at 01:37:57PM +0200, laburnumT wrote:
Sorry that the file is in a 7z format. It was the first compression
format I had the could get the file below the size limit for sending to
this mailing list.
that's fine, though i guess i should have been more specific - when you
send
On Sat, Mar 30, 2024 at 09:32:02PM +0100, laburnumT wrote:
I have looked at the logs if run with --debug-sync,
--debug-net would be likely more helpful in this case, but usually it's
actually better to just not limit the debug categories at all.
but couldn't figure out what I had done wrong.
On Fri, Mar 22, 2024 at 01:09:58PM +0100, Henrik Frisk wrote:
Sorry for my lack of knowledge here, but based on what information do
I best identify the message in the debugging output ?
i presume that any message being skipped is a problem, so that's the
only thing to look for in the log. if it
On Fri, Mar 22, 2024 at 10:29:28AM +0100, Henrik Frisk wrote:
After a long time of working flawlessly my sync process now skips certain
messages. I have not been able to see how/if the skipped messages relate.
it's pretty hopeless to figure this out unless you can catch it in the
act with debug
On Fri, Mar 15, 2024 at 07:42:32AM +0100, Peter P. wrote:
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?
in that case you ca
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.
I am interested how/why these heade
On Mon, Mar 04, 2024 at 05:03:04AM -0500, agarttha--- via isync-devel wrote:
mbsync 1.4.4 sporadically stopped exiting after mail retrieval. The
debug log (3) is below. Often mbsync will hang after OK LOGOUT.
Perhaps it's a server side change? Or my mbsync configuration is
wrong after updating
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 c
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
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 mess
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
(and you got very lucky by u
On Sun, Feb 04, 2024 at 04:03:40PM +0100, Peter P. wrote:
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 serv
On Tue, Jan 23, 2024 at 05:05:00PM +, jos...@breatheoutbreathe.in wrote:
I haven't done the nuclear option of deleting INBOX, and I'm not sure
what this means in practice:
hacking MaxPulledUID in .mbsyncstate would probably do.
that should become clear after some careful reading of the
On Sun, Jan 21, 2024 at 09:30:19AM -0800, Joseph Turner via isync-devel wrote:
I am experiencing the same issue as Oswald.
you mean mark.
anyway, the way i read his mail was that inbox isn't synced at all,
rather than that just some mails are missing. but in retrospect, that's
not necessaril
On Sat, Jan 20, 2024 at 05:27:33PM +, Mark Johnno via isync-devel wrote:
$ mbsync -v
isync 1.3.0
that's a tad old. i think i fixed a related bug in 1.4.x.
other than that, the interesting part is what the listing returns for
the M side. INBOX always exists, but may be hidden by the namesp
On Wed, Jan 10, 2024 at 09:59:07AM +0100, Bence Ferdinandy wrote:
On Thu Aug 17, 2023 at 14:45, Oswald Buddenhagen
wrote:
On Thu, Aug 17, 2023 at 07:59:09AM -0400, brittanderson--- via isync-devel
wrote:
>The error has reoccured. It is:
>
>Socket error: receive buffer full. Probably protocol
On Fri, Jan 05, 2024 at 09:04:26AM -0500, Jason Cox wrote:
On Fri Jan 5, 2024 at 5:10 AM EST, Oswald Buddenhagen via isync-devel wrote:
hacking MaxPulledUID in .mbsyncstate would probably do.
I assume I would just decrement it by the number of messages that aren't being
downloaded?
no.
On Thu, Jan 04, 2024 at 08:50:17PM -0500, Jason Cox via isync-devel wrote:
Eventually I just deleted the inbox and did a fresh sync to get the
missing messages. Is there a better way to resolve this issue?
hacking MaxPulledUID in .mbsyncstate would probably do.
as to why the situation arised i
The branch 'wip/gpl-exception' has been created at 28a4636.
___
isync-devel mailing list
isync-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/isync-devel
commit 65cd4429bb04fafadaed702cff342b7a96678fd0
Author: Oswald Buddenhagen
Date: Sat Jul 9 08:26:01 2022 +0200
document defaults of referenced XDG env vars
so users don't have to google the spec.
src/mbsync.1 | 8 +---
1 file changed, 5 insertions(+), 3 deletions(-)
diff --g
commit 8648d7a47965f4b9fd185247a3638746cada631e
Author: Oswald Buddenhagen
Date: Tue Jul 5 11:40:54 2022 +0200
remove duplicate contributor entry
anton khirnov is already in the main section, no need to have him in the
honorary section as well.
on a completely unrelate
commit ec50c55c36887b86b0143a265acae4b22d117fe9
Author: Oswald Buddenhagen
Date: Mon Jul 4 12:50:17 2022 +0200
make DNS lookup asynchronous
true asynchronicity is actually fairly useless, as it's unlikely that
both Stores in a Channel use IMAP, and both host resolutions take
commit b9a4746b54cd4159941e4bb4650d75cb26a84a25
Author: Oswald Buddenhagen
Date: Mon Jul 4 18:03:24 2022 +0200
don't refresh progress counters pointlessly
the mainloop-based refresh timer keeps spinning even if there is no
update. overload stats_steps to signal whether a refres
commit ced20ad0d962a8809f53cbd214313cad13ad5fab
Author: Oswald Buddenhagen
Date: Sun Jul 3 11:52:20 2022 +0200
fix Tunnel leaving behind zombies
this generally went unnoticed, as the tunnel usually terminates right
before we exit anyway. however, if multiple Channels are synced
commit b84137482765c90ce0578b56e9fe322474bf4771
Author: Oswald Buddenhagen
Date: Sun Jul 3 11:40:42 2022 +0200
fix broken Tunnel potentially causing SIGPIPE
we need to ignore the signal, so the regular error handling can kick in.
src/main.c | 2 ++
1 file changed, 2 insertions(+)
commit 460bfbb8ac1eb3cb106bd816566f93ff66d2190f
Author: Oswald Buddenhagen
Date: Fri Jul 1 14:54:24 2022 +0200
abort channel sync when a store is fubar
this got lost in d5a5da947.
this also simplifies a nested condition, where the logic has previously
been, but isn't a
commit f6ccf9c4f5f343e4a1f457d3432134e7c61beb4a
Author: Oswald Buddenhagen
Date: Fri Jul 1 12:14:14 2022 +0200
fix lineup of --ext-exit in help output
src/main.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/main.c b/src/main.c
index 4607f5d..82da1ea 100644
--- a
1 - 100 of 712 matches
Mail list logo
