From: patroclo7@gmail.com (Giorgio Lando)
Subject: [sup-talk] sup not seeing new messages in a maildir
Date: Thu, 17 Jan 2008 22:38:03 +0100 [thread overview]
Message-ID: <1200605584-sup-5549@clarabella.clarabella> (raw)
In-Reply-To: <1200598009-sup-5063@archie>
> I've been running sup for a while from gmail imap, and sup is great, but it was
> miserably slow. Yesterday I switched to using offlineimap, and pointed sup at
> the maildir.
I can only confirm that this happened to me too, not with maildir in
general, but with only a giant maildir generated syncing an imap folder
with offlineimap. For the reasons explained in another thread, I then
stopped to experiment with it, and actually I did not investigate the
reasons of this behaviour (also for me the options -a and -c for
sup-sync ere the only way to find the new mails). Since I am now using
successfully sup with big maildirs generated by other tools, one could
suspect that the problem is just in the interplay with offlineimap and
the flags offlineimap gives to the synced emails.
--
Giorgio Lando <patroclo7 at gmail dot com>
prev parent reply other threads:[~2008-01-17 21:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-17 19:27 Jeff Balogh
2008-01-17 21:38 ` Giorgio Lando [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1200605584-sup-5549@clarabella.clarabella \
--to=patroclo7@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox