From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Subject: Re: Different values of mail-sources for different nnml backends?
Date: 14 Jul 1999 17:41:03 +0200 [thread overview]
Message-ID: <vafvhbnp7cg.fsf@petty.cs.uni-dortmund.de> (raw)
In-Reply-To: Paul Stodghill's message of "14 Jul 1999 10:44:43 -0400"
Paul Stodghill <stodghil@CS.Cornell.EDU> writes:
> Now, what I would like to do is have (nnml "") get its new mail from popsrv
> and (nnml "lists") get its new mail from postoffice. This way I can dial in
> and download my personal messages without downloading the list message.
This sounds kinda difficult, but you could run fetchmail instead.
Fetchmail can write its mail to some file, and you could configure
fetchmail to write stuff from popsrv into one file and mail from
postoffice into another. Then you put both files in mail-sources and
Bob's your uncle: you get to decide via fetchmail which mail to fetch
and Gnus reads whatever you have fetched.
kai
--
Life is hard and then you die.
next prev parent reply other threads:[~1999-07-14 15:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-07-14 14:44 Paul Stodghill
1999-07-14 15:41 ` Kai Großjohann [this message]
1999-07-15 15:42 ` Jack Vinson
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=vafvhbnp7cg.fsf@petty.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).