From: David Rysdam <david@rysdam.org>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] not moving msgs to /cur in Maildir?
Date: Tue, 20 Jul 2010 10:52:42 -0400 [thread overview]
Message-ID: <1279637473-sup-2420@hero> (raw)
In-Reply-To: <1279590966-sup-4411@hero>
An agent or agents purporting to be David Rysdam said:
> 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.
OK, I've looked at this a little more. I think getmail is either
misbehaving or misconfigured. The POP3 behavior can't be predicated
on what is in the Maildir for multiple reasons, therefore sup's
behavior in the Maildir (right or wrong) can't be the source of this
issue.
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
prev parent reply other threads:[~2010-07-20 14:56 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
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 [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=1279637473-sup-2420@hero \
--to=david@rysdam.org \
--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