From: Eric Gerlach <eric+sup-talk@gerlach.ca>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] not moving msgs to /cur in Maildir?
Date: Mon, 19 Jul 2010 22:15:17 -0400 [thread overview]
Message-ID: <1279591667-sup-6537@gerlach.ca> (raw)
In-Reply-To: <1279590966-sup-4411@hero>
Excerpts from David Rysdam's message of Mon Jul 19 22:00:22 -0400 2010:
> I'm new to Maildir, so I'm not sure how this should be working.
>
> I've got getmail fetching my POP3 mail to a Maildir and I've got sup
> pointed at that (as an additional source, not the primary one).
>
> Just tonight, I noticed that most of my mail is in /new rather than
> /cur. Because sup isn't moving it?
>
> Also, every message in /new is repeated dozens of times. getmail has
> been fetching my entire 30-day-long mailbox every time. Like I said,
> I'm not sure how Maildir is supposed to work, so maybe getmail is
> doing the right thing (i.e. "fetch everything after the last thing in
> /cur") or not.
>
> I'm on a fairly old version of sup: 0.10.2.
I've also just started with sup, and though I don't know about sup's
behaviour (I think it should be moving mail from new/ to cur/ as well)
I do, however, have experience with POP and Maildirs, and it sounds like
you might have getmail misconfigured. Is it set to delete messages from
the server?
Cheers,
Eric
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
next prev parent reply other threads:[~2010-07-20 2:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-20 2:00 David Rysdam
2010-07-20 2:15 ` Eric Gerlach [this message]
2010-07-20 2:46 ` Ben Walton
2010-07-20 9:51 ` Sven Moritz Hallberg
2010-07-20 11:07 ` Damien Leone
2010-07-20 14:37 ` Sven Moritz Hallberg
2010-07-20 14:52 ` David Rysdam
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=1279591667-sup-6537@gerlach.ca \
--to=eric+sup-talk@gerlach.ca \
--cc=sup-talk@rubyforge.org \
/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