From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: ideas needed for nnmail-pop3-movemail
Date: 25 Oct 1997 00:36:12 +0200 [thread overview]
Message-ID: <m34t66kcv7.fsf@sparky.gnus.org> (raw)
In-Reply-To: Stainless Steel Rat's message of "20 Oct 1997 18:57:26 -0400"
Stainless Steel Rat <ratinox@peorth.gweep.net> writes:
> The one grating "flaw" in (nnmail-)pop3-movemail is that it cannot handle
> multiple sources for incoming mail. Getting it to understand multiple POP
> mailboxes is accomplished easilly enough; just loop around an alist.
But do we need this? I think pop3-movemail works fine as it does
now. In the future, people'll specify the maildrops with something
like:
'((file :type mbox :location "/usr/spool/mail/larsi")
(pop :host "somewhere" :function pop3-movemail))
(and so on), which means that pop3-movemail won't have to worry about
these things.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
next parent reply other threads:[~1997-10-24 22:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <x74t6c2gbt.fsf@peorth.gweep.net>
1997-10-24 22:36 ` Lars Magne Ingebrigtsen [this message]
[not found] ` <x7bu0elgtx.fsf@peorth.gweep.net>
1997-10-25 3:20 ` Christian Limpach
[not found] ` <x7lnzhm9dk.fsf@peorth.gweep.net>
1997-10-26 18:05 ` Christian Limpach
[not found] ` <x73elo467n.fsf@peorth.gweep.net>
1997-10-27 13:47 ` Christian Limpach
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=m34t66kcv7.fsf@sparky.gnus.org \
--to=larsi@gnus.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).