From: Paul Franklin <paul@cs.washington.edu>
Subject: Re: POP3 and SMTP...
Date: 28 Feb 1997 12:27:28 -0800 [thread overview]
Message-ID: <r9qbu94ekwf.fsf@fester.cs.washington.edu> (raw)
In-Reply-To: Donald Hunter's message of Fri, 28 Feb 1997 12:53:48 +0100
>>>>> Donald Hunter writes:
> I've got a hack similar to Rich Pieri's nnmail-pop3-movemail to
> get pop3-movemail working with nnmail. The problem is that my
> spool is set up like this:
> (setq nnmail-spool-file
> '("/var/mail/dhunter" "po:atlserver"))
> Nnmail tries to use pop3-movemail to do the standard mail as
> well, of course. My cursory glance at the code suggests that a
> fair bit of nnmail.el would have to be rewritten to support
> different movemails for different spools. Could this go on the
> requested feature list ?
If Lars doesn't do this, I'm sure someone else (maybe me) will; I
sketched one idea for doing this a while back which basically creates
mail spool backends, and I'm not the only one to mutter about doing
similar changes in the next development cycle.
--Paul
next prev parent reply other threads:[~1997-02-28 20:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-02-28 11:53 Donald Hunter
1997-02-28 20:27 ` Paul Franklin [this message]
1997-03-01 0:02 ` Lars Magne Ingebrigtsen
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=r9qbu94ekwf.fsf@fester.cs.washington.edu \
--to=paul@cs.washington.edu \
/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).