From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Subject: Re: where to add code to make it possible to "encode" the mail folder
Date: 22 Mar 2000 13:46:05 +0100 [thread overview]
Message-ID: <vaf1z53qik2.fsf@lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: Jonas Steverud's message of "22 Mar 2000 10:54:25 +0100"
I think that mail-sources is the wrong place to add this stuff: Gnus
reads from a mail source and writes to a group. From your wording,
you want to support encryption and compression when storing messages.
I think you want to have a look at the various backends nnfolder, nnml
and so on. I think you don't want to replicate the code, so you'd
need to change all the backends to use a common interface for writing
files (or for naming files?).
Hm. Yes, that would make sense: you could frob the backends so that
they write the file foo.gz rather than foo, and then you could let
auto-compression-mode take over.
kai
--
~/.signature: No such file or directory
next parent reply other threads:[~2000-03-22 12:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <wtnaejrpbxq.fsf@bayta.dtek.chalmers.se>
2000-03-22 12:46 ` Kai Großjohann [this message]
[not found] ` <wtnityeub5i.fsf@licia.dtek.chalmers.se>
2000-03-22 20:30 ` Kai Großjohann
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=vaf1z53qik2.fsf@lucy.cs.uni-dortmund.de \
--to=kai.grossjohann@cs.uni-dortmund.de \
/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).