From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: pop :program change
Date: 19 Feb 1999 22:30:28 +0100 [thread overview]
Message-ID: <m31zjmjd3f.fsf@quimbies.gnus.org> (raw)
In-Reply-To: Stainless Steel Rat's message of "19 Feb 1999 16:11:33 -0500"
Stainless Steel Rat <ratinox@peorth.gweep.net> writes:
> One of the nice features of fetchmail is that it has 'preconnect' and
> 'postconnect' options for each server polled.
[...]
> Something like this in mail-source would be especially useful.
So should all the mail sources allow :preconnect and :postconnect (or
whatever) keywords? They could be format strings, like the :program
keyword. (They should have better names though. And perhaps allow
elisp functions as well.)
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
next prev parent reply other threads:[~1999-02-19 21:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-02-03 16:08 Lars Magne Ingebrigtsen
1999-02-12 7:36 ` Urban Engberg
1999-02-19 12:15 ` Lars Magne Ingebrigtsen
[not found] ` <m3vhgyyu7u.fsf@peorth.gweep.net>
1999-02-19 21:30 ` Lars Magne Ingebrigtsen [this message]
[not found] ` <m390duyqst.fsf@peorth.gweep.net>
1999-02-20 16:36 ` Lars Magne Ingebrigtsen
1999-02-22 7:42 ` Urban Engberg
1999-02-23 0:52 ` Aaron M. Ucko
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=m31zjmjd3f.fsf@quimbies.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).