From: Michael Welsh Duggan <md5i@md5i.com>
To: ding@gnus.org
Subject: Re: Returning to ticks on read-only imap servers
Date: Tue, 05 Oct 2010 17:01:45 -0400 [thread overview]
Message-ID: <87aams5p6u.fsf@maru.md5i.com> (raw)
In-Reply-To: <87eic4jsjx.fsf@dod.no> (Steinar Bang's message of "Tue, 05 Oct 2010 22:25:22 +0200")
Steinar Bang <sb@dod.no> writes:
>>>>>> Michael Welsh Duggan <md5i@md5i.com>:
>
>> I'd like to revisit the issue of ticks on read-only nnimap servers.
>
> My personal opinion is that read-only nnimap servers isn't such a hot
> idea. NNTP access to whatever would have been better.
>
> However...
Yeah. This used to be a server with read/write access to personal
groups, and read-only access to public groups. Then for some reason
*cough* government clients *cough* our personal mail stuff got switched
to the-never-to-be-damned-enough Exchange.
>> I need non-seen ticks to be handled by the client on this server.
>
> ...a fallback to storing ticks in the .newsrc.eld is probably the
> expected behaviour (ie. if things are to work as transparently across
> backends as possible)...?
I agree that this is probably the correct fallback.
--
Michael Welsh Duggan
(md5i@md5i.com)
next prev parent reply other threads:[~2010-10-05 21:01 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-05 19:16 Michael Welsh Duggan
2010-10-05 20:25 ` Steinar Bang
2010-10-05 21:01 ` Michael Welsh Duggan [this message]
2010-10-07 18:59 ` Lars Magne Ingebrigtsen
2010-10-07 21:37 ` Michael Welsh Duggan
2010-10-07 22:40 ` Lars Magne Ingebrigtsen
2010-10-08 15:07 ` James Cloos
2010-10-08 17:00 ` Lars Magne Ingebrigtsen
2010-10-08 18:22 ` Julien Danjou
2010-10-08 18:26 ` Lars Magne Ingebrigtsen
2010-10-08 18:28 ` Julien Danjou
2010-10-08 18:49 ` Lars Magne Ingebrigtsen
2010-10-08 19:34 ` Julien Danjou
2010-10-08 21:32 ` Dan Christensen
2010-10-09 6:57 ` Julien Danjou
2010-10-09 8:10 ` Michael Welsh Duggan
2010-10-09 8:26 ` Julien Danjou
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=87aams5p6u.fsf@maru.md5i.com \
--to=md5i@md5i.com \
--cc=ding@gnus.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;
as well as URLs for NNTP newsgroup(s).