mail not visible immediately after offlineimap -o

1 view
Skip to first unread message

Johannes Altmanninger

unread,
Jan 23, 2025, 6:48:52 AM1/23/25
to mbl...@googlegroups.com
I like the flexibility of mblaze to categorize mail, so I run this
command every few minutes:

offlineimap -o
magrep /:foo ~/mail/somefolder |
mrefile ~/mail/special-filing-cabinet

For some reason magrep sometimes finds no matches even if they must
be there, based on offlineimap logs and "mutt -f ~/mail/somefolder".

Re-running the commands after a while seems to make it work. I'm not
yet sure if it's about timing or offlineimap/mutt/magrep stepping on
each others' toes.

Any pointers on how to debug this?

I guess I'll try to reproduce on a mailbox that I never open in mutt
(I hope "mutt -f some-other-mailbox" does not influence this!).

I'm not super attached to offlineimap or mutt;
open to suggestions on battle-tested alternatives.

Johannes Altmanninger

unread,
Jan 27, 2025, 12:54:07 AM1/27/25
to mbl...@googlegroups.com
On Thu, Jan 23, 2025 at 12:48:50PM +0100, Johannes Altmanninger wrote:
> I like the flexibility of mblaze to categorize mail, so I run this
> command every few minutes:
>
> offlineimap -o
> magrep /:foo ~/mail/somefolder |

it's visible to "mlist" but not to "magrep" -- looks like magrep
only looks at the "cur" directory and ignores "new". (seg.c::iterdir
«char *m = "/cur";»). Looks like I need to use "minc" (or open
and close mutt). Nice.

Leah Neukirchen

unread,
Jan 28, 2025, 5:23:19 AM1/28/25
to Johannes Altmanninger, mbl...@googlegroups.com
Good catch. You can also pass the /new dir directly:

magrep /:foo ~/mail/somefolder/cur ~/mail/somefolder/new

--
Leah Neukirchen <le...@vuxu.org> https://leahneukirchen.org/
Reply all
Reply to author
Forward
0 new messages