From: Ding Lei <dinglei@ipanel.cn>
Subject: fetchmail+procmail+gnus, mailsource or secondary-select-methods?
Date: Fri, 28 May 2004 10:37:34 +0800 [thread overview]
Message-ID: <20040528023734.GA30134@ipanel.cn> (raw)
Hi ...
I am currently using the fetchmail & procmail combo. The manual saids
that you need to specify an mail backend for the "mail-source" which gnus
fetches mails from, which in my case fetchmail & procmail done that already.
So which variable shall I set to tell Gnus read those mails from the
specified maildir: /data/emails/company, /data/emails/gnus-list, /data/emacs-list ...
Whether secondary-select-methods or mail-source?
Please reply with corresponding lisp expression to write in .gnus.el ..
Thanks!
--
Yours,
<<<::::: D i n g L e i ::::::>>
|| ||
|| Ext: 8106 ||
|| Email: <dinglei [A] ipanel [O] cn> ||
|| Dept. Of Technology/Engineering ||
|| Embedded Information Services Inc. ||
|| ||
<(((((( ===================== )))))>>>
You can't start worrying about what's going to happen. You get spastic
enough worrying about what's happening now.
-- Lauren Bacall
next reply other threads:[~2004-05-28 2:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-28 2:37 Ding Lei [this message]
2004-05-28 5:08 ` fetchmail+procmail+gnus, mailsource or Kai Grossjohann
2004-05-28 5:46 ` 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=20040528023734.GA30134@ipanel.cn \
--to=dinglei@ipanel.cn \
/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).