Gnus development mailing list
 help / color / mirror / Atom feed
From: Wes Hardaker <wjhardaker@ucdavis.edu>
Cc: ding@hpc.uh.edu
Subject: Re: Offline and IMAP (was: Re: Lars:  You're hardest challenge yet)
Date: 01 Oct 1998 15:36:03 -0700	[thread overview]
Message-ID: <sdr9wrc3l8.fsf@oakdale.ucdavis.edu> (raw)
In-Reply-To: Mikael MC Cardell's message of "01 Oct 1998 21:36:36 +0200"

>>>>> On 01 Oct 1998 21:36:36 +0200, Mikael MC Cardell <mc@hack.org> said:

>> Actually, I'm probably going to switch to imap soon, but I don't like
>> th server's I've played with so far...

Mikael> Neither do I. When I started hacking some on nnimap, I
Mikael> constantly ran my head into the UofW IMAP server. Gaaah! I had
Mikael> a look at the Cyrus server ages ago, but people tell me it's
Mikael> better now. Perhaps I'll have another look.

The biggest problem is configuration.  My ideal case would be a imap
server that allows me to specify the location in which I want to place 
folders.  The UofW software opens every file in your home directory
looking for folders?  That's the impression I got by trying to run it
once and finally hitting C-g 10 minutes later.  Running it against a
fake user on my linux box with nothing in it's home directory is much
better...

>From my glances at the Cyrus software, it didn't have this option
either (and since it was designed for use on systems where the users
didn't have log-in shells, I'm assume it does something equally as
stupid).

Actually, I want procmail to deliver mail into my imap folders, but I
think this is a pipe-dream at this point...  sigh...

Mikael> I've had plans of writing my own IMAP server a long time
Mikael> now. I've been thinking about things such as a IMAP frontend
Mikael> for INN or something. Anyone want to help out?

I'd love to, but I'm swamped with more projects than I can even count...

-- 
"Ninjas aren't dangerous.  They're more afraid of you than you are of them."


  reply	other threads:[~1998-10-01 22:36 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-09-29  3:23 Lars: You're hardest challenge yet Wes Hardaker
1998-09-29  4:18 ` Jason L Tibbitts III
1998-09-29  7:46   ` Steinar Bang
1998-09-29 15:56   ` Justin Sheehy
     [not found]   ` <6f4str9vxm.fsf@dna.lth.se>
1998-09-29 21:00     ` Wes Hardaker
1998-10-01 19:36       ` Offline and IMAP (was: Re: Lars: You're hardest challenge yet) Mikael MC Cardell
1998-10-01 22:36         ` Wes Hardaker [this message]
1998-10-01 22:43           ` C. R. Oldham
1998-10-01 23:36             ` Wes Hardaker
1998-10-02 11:48               ` mdorman-ding
1998-10-02 16:07                 ` Wes Hardaker
1998-10-02 15:18             ` Justin Sheehy
1998-10-07 15:56             ` Offline and IMAP Jochen_Hayek
1998-10-07 18:03               ` Mark Moll
1998-10-02 15:29           ` Offline and IMAP (was: Re: Lars: You're hardest challenge yet) Justin Sheehy
1998-10-02 16:04             ` Steinar Bang
1998-10-03 12:36               ` Simon Josefsson
1998-10-07 15:57             ` Offline and IMAP Jochen_Hayek
1998-10-07 18:47               ` Wes Hardaker
1998-10-07 15:58           ` Jochen_Hayek
1998-10-07 18:46             ` Wes Hardaker
1998-10-02 15:26         ` Offline and IMAP (was: Re: Lars: You're hardest challenge yet) Justin Sheehy

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=sdr9wrc3l8.fsf@oakdale.ucdavis.edu \
    --to=wjhardaker@ucdavis.edu \
    --cc=ding@hpc.uh.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).