From: Wes hardaker <hardaker@calwest.net>
Subject: Re: a true pop3 backend?
Date: 22 Oct 1997 08:16:21 -0700 [thread overview]
Message-ID: <x7afg1su9l.fsf@mail.calwest.net> (raw)
In-Reply-To: Stainless Steel Rat's message of "21 Oct 1997 22:19:44 -0400"
>>>>> On 21 Oct 1997 22:19:44 -0400, Stainless Steel Rat <ratinox@peorth.gweep.net> said:
Rat> That is because you want a full-blown IMAP client. I did not
Rat> write a full-blown IMAP client, I wrote a low-level interface
Rat> layer for POP3.
Ok, agreed, IMAP would certainly be better. Of course, I don't have
an IMAP server (as many other people don't)...
Anyway, I do truely understand your points, and know you are a lot
more knowlegable in thea area than me. I still disagree, but will
assume you're right.
Cheers,
Wes
--
"Ninjas aren't dangerous. They're more afraid of you than you are of them."
next prev parent reply other threads:[~1997-10-22 15:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-10-21 20:58 Wes hardaker
[not found] ` <x7sotuzreb.fsf@peorth.gweep.net>
1997-10-22 0:02 ` Wes hardaker
[not found] ` <x7lnzmpmin.fsf@peorth.gweep.net>
1997-10-22 15:16 ` Wes hardaker [this message]
1997-10-22 5:05 ` Current status of nnimap? (Was: a true pop3 backend?) 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=x7afg1su9l.fsf@mail.calwest.net \
--to=hardaker@calwest.net \
/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).