From: Andreas Jaeger <aj@suse.de>
Subject: Re: Using different backends
Date: Tue, 29 Apr 2003 07:45:32 +0200 [thread overview]
Message-ID: <u8wuhdj1qb.fsf@gromit.moeb> (raw)
In-Reply-To: <m3ptn6fnzf.fsf@multivac.cwru.edu> (Paul Jarc's message of "Mon, 28 Apr 2003 14:58:06 -0400")
prj@po.cwru.edu (Paul Jarc) writes:
> Andreas Jaeger <aj@suse.de> wrote:
>> I'm currently trying to use different backends for different
>> mailfolders. Mails are split via procmail into one directory:
>>
>> (setq mail-sources
>> '(
>> (directory :path "/mail-aj/Mail/procmail-work/"
>> :plugged t
>> :suffix ".spool")
>> ))
>>
>> And I'd like to use - depending on the folder - either nnmaildir or
>> nnfolder for incoming mails.
>
> I'd suggest reconfiguring procmail so that messages destined for
> nnmaildir are delivered directly to your nnmaildir groups (maildirs)
> by procmail. (That's safe with nnmaildir, but not other backends.)
Ok, but then I need to use duplicate suppresion in procmail and not in
Gnus since nnmaildir does not support it.
> Whatever's left can then be delivered to procmail-work as it is now,
> and then split by nnfolder.
>
>> (setq gnus-secondary-select-methods '((nnmaildir "gromit"
>> (directory "/mail-aj/Maildirs/")
>> (get-new-mail t)
>> )
>> (nnml "")
>> (nnfolder "archive")))
>
> The default for nnml and nnfolder is to do mail splitting, so this
> means that all three will do mail splitting, which isn't what you
> want. It's generally not useful to Have more than one server do
> splitting, because whichever one does it first will get all the mail.
So, this is broken by design ;-).
> Along with the above change, I think you should remove get-new-mail
> for nnmaildir and explicitly add (nnml-get-new-mail nil) for nnml.
And then I could use nnmaildir and nnfolder in parallel. But I fear
there's no possibility to use all three in parallel with getting new
mail? What a pity...
Thanks,
Andreas
--
Andreas Jaeger
SuSE Labs aj@suse.de
private aj@arthur.inka.de
http://www.suse.de/~aj
next prev parent reply other threads:[~2003-04-29 5:45 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-27 12:22 Andreas Jaeger
2003-04-27 15:25 ` Kai Großjohann
2003-04-27 19:06 ` Andreas Jaeger
2003-05-02 13:03 ` Michael Teichgräber
2003-05-02 13:30 ` Kai Großjohann
2003-05-02 14:26 ` Michael Teichgräber
2003-05-02 14:47 ` Kai Großjohann
2003-05-02 15:15 ` Michael Teichgräber
2003-05-03 15:51 ` mail-sources backend specific? (was: Using different backends) Michael Teichgräber
2003-05-03 17:25 ` mail-sources backend specific? Kai Großjohann
2003-05-03 20:00 ` Michael Teichgräber
2003-05-03 20:57 ` Kai Großjohann
2003-05-04 2:40 ` Michael Teichgräber
2003-05-04 13:29 ` Kai Großjohann
2003-05-05 16:38 ` Paul Jarc
2003-05-06 16:31 ` Kai Großjohann
2003-05-06 19:55 ` Paul Jarc
2003-05-29 14:27 ` Kai Großjohann
2003-05-29 16:14 ` Paul Jarc
2003-10-18 12:53 ` Lars Magne Ingebrigtsen
2003-05-03 17:21 ` Using different backends Kai Großjohann
2003-05-03 19:00 ` Michael Teichgräber
2003-05-03 20:00 ` Kai Großjohann
2003-04-28 18:58 ` Paul Jarc
2003-04-29 5:45 ` Andreas Jaeger [this message]
2003-04-29 15:23 ` Paul Jarc
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=u8wuhdj1qb.fsf@gromit.moeb \
--to=aj@suse.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).