Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Marcus Frings <iam-est-hora-surgere@despammed.com>
Subject: Re: To IMAP or not to IMAP
Date: Tue, 20 Jul 2004 20:46:24 +0200	[thread overview]
Message-ID: <vita-brevis-breviter-in-brevi-finietur-mors-venit-velociter-quae-neminem-veretur-86ekn68qkf.fsf@shodan.gothgoose.net> (raw)
In-Reply-To: <87k6wyu1dm.fsf@amalthea.paradoxical.net>

* Josh Huber <huber+news@alum.wpi.edu> wrote:

> I really enjoy using Cyrus as my home IMAP server.  It's really
> fast, has built-in filtering support (through sieve), and has
> been really stable.  Of course, it may be overkill with only 7
> regular users, but I figured it would be a good learning
> experience at the same time!

Cyrus was my first IMAP server I have ever used (IIRC from a SuSE 6.0)
and as I said I do really think that it's a very great thing and cool if
you run a large site but especially because of my home usage I thought I
should better run a smaller IMAPd and so I came to Courier IMAP some
years ago which usually runs "out of the box". However, I have tweaked
it a little. :-)

Regards,
Marcus
-- 
"Enter that room, insect, and it will become your grave!"
                                 (Shodan in System Shock)


  parent reply	other threads:[~2004-07-20 18:46 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87pt6ya8at.fsf@phiwumbda.org>
     [not found] ` <86llhllqfb.fsf@rumba.de.uu.net>
2004-07-16 17:38   ` Steven E. Harris
     [not found]   ` <87llhlwuw5.fsf@phiwumbda.org>
     [not found]     ` <87acy0gc3e.fsf@bigriver.doilywood.lan>
     [not found]       ` <87r7rbu5w5.fsf@phiwumbda.org>
     [not found]         ` <86iscm1f7k.fsf@rumba.de.uu.net>
     [not found]           ` <87ekn9sd5q.fsf@phiwumbda.org>
2004-07-19 13:50             ` David Magda
     [not found]               ` <874qo3xc1i.fsf@phiwumbda.org>
2004-07-20 18:42                 ` Marcus Frings
     [not found]                 ` <ilufz7eww99.fsf@latte.josefsson.org>
     [not found]                   ` <vita-brevis-breviter-in-brevi-finietur-mors-venit-velociter-quae-neminem-veretur-86smbetxpj.fsf@shodan.gothgoose.net>
     [not found]                     ` <iluacxmvaoi.fsf@latte.josefsson.org>
2004-07-26 22:09                       ` Marcus Frings
     [not found]             ` <vita-brevis-breviter-in-brevi-finietur-mors-venit-velociter-quae-neminem-veretur-86658lfgvw.fsf@shodan.gothgoose.net>
     [not found]               ` <871xj9rtgy.fsf@phiwumbda.org>
2004-07-18 21:34                 ` Christopher Browne
2004-07-19 12:35                   ` Jesse F. Hughes
2004-07-19 21:42                 ` Richard Watson
     [not found]               ` <87k6wyu1dm.fsf@amalthea.paradoxical.net>
2004-07-20 18:46                 ` Marcus Frings [this message]
     [not found]   ` <w4r7r540rb.fsf@mid.packer.its.vanderbilt.edu>
2004-07-22 13:43     ` Chris Green
2004-08-02 12:10     ` Kai Grossjohann

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=vita-brevis-breviter-in-brevi-finietur-mors-venit-velociter-quae-neminem-veretur-86ekn68qkf.fsf@shodan.gothgoose.net \
    --to=iam-est-hora-surgere@despammed.com \
    --cc=protagonist@gmx.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).