Gnus development mailing list
 help / color / mirror / Atom feed
From: Steinar Bang <sb@metis.no>
Subject: Re: IAMP4 Support Available?
Date: 23 Jul 1998 14:51:14 +0200	[thread overview]
Message-ID: <whww94zq65.fsf@viffer.oslo.metis.no> (raw)
In-Reply-To: Jochen_Hayek@ACM.org's message of "Thu, 23 Jul 1998 12:38:46 GMT"

>>>>> Jochen_Hayek@ACM.org:

>>>>> "JC" == Jake Colman <colman@ppllc.com> writes:

JC> Can/does Emacs 20.x support IMAP4 protocol?

JC> We are switching to a M$ Exchange Server for mail and they
JC> would prefer I use IMAP4 instead of POP.

> Use the stand alone tool `fetchmail' to fetch your e-mail to your
> box, then use what ever you want to read you e-mail.  .

	<URL:http://earthspace.net/~esr/fetchmail/>


  reply	other threads:[~1998-07-23 12:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-06-16 13:54 Jake Colman
1998-06-16 14:12 ` Justin Sheehy
1998-07-23 12:38 ` Jochen_Hayek
1998-07-23 12:51   ` Steinar Bang [this message]
1998-07-23 14:49   ` William M. Perry
1998-07-23 15:07     ` Jake Colman
1998-07-23 15:12       ` Steinar Bang

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=whww94zq65.fsf@viffer.oslo.metis.no \
    --to=sb@metis.no \
    /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).