From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: Enrico Scholz <enrico.scholz@informatik.tu-chemnitz.de>
Cc: info-gnus-english@gnu.org
Subject: Re: imap acl editing broken
Date: Fri, 02 Aug 2013 15:00:40 +0200 [thread overview]
Message-ID: <m3fvusz1qf.fsf@stories.gnus.org> (raw)
In-Reply-To: <87txj8788p.fsf@kosh.bigo.ensc.de> (Enrico Scholz's message of "Fri, 02 Aug 2013 11:27:34 +0200")
Enrico Scholz <enrico.scholz@informatik.tu-chemnitz.de> writes:
> IMAP ACLs are described in http://tools.ietf.org/html/rfc4314 and their
> modification worked already with previous gnus versions.
Hm... I skimmed the first section of the RFC, and it still didn't tell
me what ACLs are. >"?
> Unfortunately, the gnus version is both v5.13 in working and
> non-working case, but the MUA (gnus v5.13 bundled with emacs-23.1 from
> RHEL 6.4) I am writing the current message with, supports modification
> of ACLs. but other MUAs (gnus v5.13 bundled with emacs-24.3 from
> Fedora 19) fail with message above.
Yes, nnimap was rewritten for Emacs 24, and the ACL stuff went AWOL
because 1) I have no idea what it is and 2) nobody seemed to be using
it. You're the first person to mention it, and it's been gone a year...
The code could be resurrected, of course, but it would have to be by
someone who could test it. Patches are welcome.
--
(domestic pets only, the antidote for overdose, milk.)
No Gnus T-Shirt for sale: http://ingebrigtsen.no/no.php
next prev parent reply other threads:[~2013-08-02 13:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.16867.1357582045.855.info-gnus-english@gnu.org>
2013-08-01 13:03 ` Lars Magne Ingebrigtsen
2013-08-02 9:27 ` Enrico Scholz
2013-08-02 13:00 ` Lars Magne Ingebrigtsen [this message]
2013-08-02 14:17 ` Enrico Scholz
2013-08-03 11:40 ` Lars Magne Ingebrigtsen
2013-01-07 17:49 Enrico Scholz
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=m3fvusz1qf.fsf@stories.gnus.org \
--to=larsi@gnus.org \
--cc=enrico.scholz@informatik.tu-chemnitz.de \
--cc=info-gnus-english@gnu.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).