Gnus development mailing list
 help / color / mirror / Atom feed
From: Simon Josefsson <jas@extundo.com>
Cc: ding@gnus.org
Subject: Re: Sieve support?
Date: Sun, 04 Nov 2001 19:06:21 +0100	[thread overview]
Message-ID: <ilulmhm76n6.fsf@dhcp128.extundo.com> (raw)
In-Reply-To: <q6mofmi782k.fsf@spartacus.utdallas.edu> (Amos Gouaux's message of "Sun, 04 Nov 2001 11:35:31 -0600")

Amos Gouaux <amos+lists.ding@utdallas.edu> writes:

>>>>>> On Sun, 04 Nov 2001 15:49:22 +0100,
>>>>>> Steinar Bang <sb@dod.no> (sb) writes:
>
> sb> Hmm... looks like Cyrus 2 is on the way, for the one who waits
> sb>        <http://bugs.debian.org/108942>
>
> If not yet running 2.x, I would wait until 2.1 is released.  Many
> bugs have been fixed in this up-coming release.  I'd even say that
> 2.x out of CVS would be better than one of the 2.0 releases.
> Rapidly evolving stuff, but then folks here know all about that.

I've been running the same 2.x release for almost a year...

> Personally, I think folks are also better off doing the compiles
> themself instead of using pre-compiled packages.  Seems like many
> folks run into problems because the pre-compiled stuff isn't always
> in sync with the numerous dependencies, most particularly Berkeley DB.

Are you saying that if you compile the package yourself, you _won't_
get Berkeley DB problems?  Wow! :-)

(I'm stuck at the 2.x release I'm using just because of libdb
problems, all db utilities crash when I export the SASL db, and no
matter which version of libdb I compile with, the new Cyrus doesn't
like my current db.  I have working binaries but no way of compiling
new working ones.  Libdb is double-plus ungood.)




  reply	other threads:[~2001-11-04 18:06 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-21 13:01 Simon Josefsson
2001-10-21 14:02 ` Kai Großjohann
2001-10-22  1:21 ` Daniel Pittman
2001-11-01  0:53 ` Simon Josefsson
2001-11-01 16:08   ` Kai Großjohann
2001-11-01 16:50     ` Simon Josefsson
2001-11-02  8:25       ` Kai Großjohann
2001-11-02  8:50         ` Simon Josefsson
2001-11-02  9:14           ` Kai Großjohann
2001-11-02 12:39             ` Simon Josefsson
2001-11-02 16:24               ` Kai Großjohann
2001-11-02 17:52                 ` Amos Gouaux
2001-11-02 22:29                   ` Kai Großjohann
2001-11-04 14:49                     ` Steinar Bang
2001-11-04 17:35                       ` Amos Gouaux
2001-11-04 18:06                         ` Simon Josefsson [this message]
2001-11-04 18:44                           ` Amos Gouaux
2001-11-02 17:48         ` Amos Gouaux
2001-11-02 19:59           ` Simon Josefsson
2001-11-03  0:35       ` NAGY Andras
2001-11-03 18:58 ` possible gnus-sieve bug NAGY Andras
2001-11-03 19:06   ` Simon Josefsson
2001-11-04 13:17     ` NAGY Andras

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=ilulmhm76n6.fsf@dhcp128.extundo.com \
    --to=jas@extundo.com \
    --cc=ding@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).