Обсуждение: [ams@oryx.com: [ANNOUNCE] Archiveopteryx 1.10 released]

So... since we all *love* the current archive engine (and it's search)
so much...

What about switching over to this? It appears it should work fine with
majordomo, and I'd bet we could get someone from Archiveopteryx to help
with this.

----- Forwarded message from Abhijit Menon-Sen <ams@oryx.com> -----

X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on noel.decibel.org
X-Spam-Level:
X-Spam-Status: No, score=-2.5 required=5.0 tests=AWL,BAYES_00,
    DNS_FROM_RFC_ABUSE autolearn=no version=3.1.0
X-Greylist: delayed 00:24:12.294704 by SQLgrey-
X-Greylist: domain auto-whitelisted by SQLgrey-1.7.3
Date: Fri, 1 Sep 2006 09:12:19 +0530
From: Abhijit Menon-Sen <ams@oryx.com>
To: pgsql-announce@postgresql.org
Cc: info@oryx.com
Subject: [ANNOUNCE] Archiveopteryx 1.10 released
X-Mailing-List: pgsql-announce
Precedence: bulk

We are happy to announce the release of Archiveopteryx 1.10.

    http://www.archiveopteryx.org/1.10.html

Archiveopteryx (formerly Oryx Mailstore) is a mail archive server that
stores normalized mail in a PostgreSQL database, and serves it using
IMAP/POP. It has now been used in production for several months, and
is available both on commercial terms and as open source.

This release comes sooner than planned, because we feel the deployment
of privilege separation is important enough to justify it.

Changes since 1.09:

- Privilege separation: the server can't destroy the database.
- "aox vacuum" permanently removes deleted mail after 7 days.
- Installer creates user/group aox/aox by default.
- RFC 2180 compliance for mailboxes accessed by multiple clients.
- A few IMAP and message parsing bug fixes.
- Added UTF-16/UTF-16BE/UTF16-LE codecs.

Please let us know if you find any problems.

The next release is expected on 2006-09-24.

Please join the mailstore-announce list if you want to be notified of
future releases; and mailstore-users to discuss Archiveopteryx.

    http://www.archiveopteryx.org/lists.html

Bug reports, questions, and suggestions to info@oryx.com.

--
Abhijit Menon-Sen
Oryx Mail Systems GmbH

---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?

               http://www.postgresql.org/docs/faq


----- End forwarded message -----

--
Jim Nasby                                            jim@nasby.net
EnterpriseDB      http://enterprisedb.com      512.569.9461 (cell)

-----Original Message-----
From: "Jim C. Nasby" <jim@nasby.net>
To: "pgsql-www@postgresql.org" <pgsql-www@postgresql.org>
Sent: 19/09/06 22:45
Subject: [pgsql-www] [ams@oryx.com: [ANNOUNCE] Archiveopteryx 1.10 released]


> What about switching over to this? It appears it should work fine with
> majordomo, and I'd bet we could get someone from Archiveopteryx to help
> with this.

To do what exactly? It says it's pop/imap server!?

Regards, Dave

Jim C. Nasby wrote:
> So... since we all *love* the current archive engine (and it's search)
> so much...
>
> What about switching over to this? It appears it should work fine with
> majordomo, and I'd bet we could get someone from Archiveopteryx to help
> with this.

It also has a Tsearch2 interface :)


Joshua D. Drake

>
> ----- Forwarded message from Abhijit Menon-Sen <ams@oryx.com> -----
>
> X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on noel.decibel.org
> X-Spam-Level:
> X-Spam-Status: No, score=-2.5 required=5.0 tests=AWL,BAYES_00,
>     DNS_FROM_RFC_ABUSE autolearn=no version=3.1.0
> X-Greylist: delayed 00:24:12.294704 by SQLgrey-
> X-Greylist: domain auto-whitelisted by SQLgrey-1.7.3
> Date: Fri, 1 Sep 2006 09:12:19 +0530
> From: Abhijit Menon-Sen <ams@oryx.com>
> To: pgsql-announce@postgresql.org
> Cc: info@oryx.com
> Subject: [ANNOUNCE] Archiveopteryx 1.10 released
> X-Mailing-List: pgsql-announce
> Precedence: bulk
>
> We are happy to announce the release of Archiveopteryx 1.10.
>
>     http://www.archiveopteryx.org/1.10.html
>
> Archiveopteryx (formerly Oryx Mailstore) is a mail archive server that
> stores normalized mail in a PostgreSQL database, and serves it using
> IMAP/POP. It has now been used in production for several months, and
> is available both on commercial terms and as open source.
>
> This release comes sooner than planned, because we feel the deployment
> of privilege separation is important enough to justify it.
>
> Changes since 1.09:
>
> - Privilege separation: the server can't destroy the database.
> - "aox vacuum" permanently removes deleted mail after 7 days.
> - Installer creates user/group aox/aox by default.
> - RFC 2180 compliance for mailboxes accessed by multiple clients.
> - A few IMAP and message parsing bug fixes.
> - Added UTF-16/UTF-16BE/UTF16-LE codecs.
>
> Please let us know if you find any problems.
>
> The next release is expected on 2006-09-24.
>
> Please join the mailstore-announce list if you want to be notified of
> future releases; and mailstore-users to discuss Archiveopteryx.
>
>     http://www.archiveopteryx.org/lists.html
>
> Bug reports, questions, and suggestions to info@oryx.com.
>
> --
> Abhijit Menon-Sen
> Oryx Mail Systems GmbH
>
> ---------------------------(end of broadcast)---------------------------
> TIP 3: Have you checked our extensive FAQ?
>
>                http://www.postgresql.org/docs/faq
>
>
> ----- End forwarded message -----
>


--

    === The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
    Providing the most comprehensive  PostgreSQL solutions since 1997
              http://www.commandprompt.com/

On Tue, Sep 19, 2006 at 11:03:03PM +0100, Dave Page wrote:
> -----Original Message-----
> From: "Jim C. Nasby" <jim@nasby.net>
> To: "pgsql-www@postgresql.org" <pgsql-www@postgresql.org>
> Sent: 19/09/06 22:45
> Subject: [pgsql-www] [ams@oryx.com: [ANNOUNCE] Archiveopteryx 1.10 released]
>
>
> > What about switching over to this?  It appears it should work fine
> > with majordomo, and I'd bet we could get someone from
> > Archiveopteryx to help with this.
>
> To do what exactly?  It says it's pop/imap server!?

The name *Archive*opteryx would be a little hint. ;)

Cheers,
D
--
David Fetter <david@fetter.org> http://fetter.org/
phone: +1 415 235 3778        AIM: dfetter666
                              Skype: davidfetter

Remember to vote!

> -----Original Message-----
> From: David Fetter [mailto:david@fetter.org]
> Sent: 20 September 2006 00:45
> To: Dave Page
> Cc: Jim C. Nasby; pgsql-www@postgresql.org
> Subject: Re: [pgsql-www] [ams@oryx.com: [ANNOUNCE]
> Archiveopteryx 1.10 released]
>
> > > What about switching over to this?  It appears it should work fine
> > > with majordomo, and I'd bet we could get someone from
> > > Archiveopteryx to help with this.
> >
> > To do what exactly?  It says it's pop/imap server!?
>
> The name *Archive*opteryx would be a little hint. ;)

I have a optical drive designed for archiving - it doesn't mean that it
has an interface that users can search and view data through.

/D

> -----Original Message-----
> From: pgsql-www-owner@postgresql.org
> [mailto:pgsql-www-owner@postgresql.org] On Behalf Of Joshua D. Drake
> Sent: 19 September 2006 23:12
> To: Jim C. Nasby
> Cc: pgsql-www@postgresql.org
> Subject: Re: [pgsql-www] [ams@oryx.com: [ANNOUNCE]
> Archiveopteryx 1.10 released]
>
> Jim C. Nasby wrote:
> > So... since we all *love* the current archive engine (and
> it's search)
> > so much...
> >
> > What about switching over to this? It appears it should
> work fine with
> > majordomo, and I'd bet we could get someone from
> Archiveopteryx to help
> > with this.
>
> It also has a Tsearch2 interface :)

Meaning what exactly? I'm sure any one of us is capable of writing a
small script that could catch the mail messages from each list, and
store them in a tsearch enabled database. The difficult bit is adding a
good *web* interface to it with all the appropriate thread links and
index pages, and without breaking all those pesky legacy URLs. There are
also tens of thousands of documents in the search index that aren't
emails that would also need to be handled.

If you want to move to a new tsearch search engine (which I'm not
against btw) then using our existing crawler script as a basis for a
generic indexer would bypass all those problems, leaving just a web
interface to tsearch to build.

Regards, Dave.

On Wed, 20 Sep 2006, Dave Page wrote:

>
>
>> -----Original Message-----
>> From: pgsql-www-owner@postgresql.org
>> [mailto:pgsql-www-owner@postgresql.org] On Behalf Of Joshua D. Drake
>> Sent: 19 September 2006 23:12
>> To: Jim C. Nasby
>> Cc: pgsql-www@postgresql.org
>> Subject: Re: [pgsql-www] [ams@oryx.com: [ANNOUNCE]
>> Archiveopteryx 1.10 released]
>>
>> Jim C. Nasby wrote:
>>> So... since we all *love* the current archive engine (and
>> it's search)
>>> so much...
>>>
>>> What about switching over to this? It appears it should
>> work fine with
>>> majordomo, and I'd bet we could get someone from
>> Archiveopteryx to help
>>> with this.
>>
>> It also has a Tsearch2 interface :)
>
> Meaning what exactly? I'm sure any one of us is capable of writing a
> small script that could catch the mail messages from each list, and
> store them in a tsearch enabled database. The difficult bit is adding a
> good *web* interface to it with all the appropriate thread links and
> index pages, and without breaking all those pesky legacy URLs. There are
> also tens of thousands of documents in the search index that aren't
> emails that would also need to be handled.
>
> If you want to move to a new tsearch search engine (which I'm not
> against btw) then using our existing crawler script as a basis for a
> generic indexer would bypass all those problems, leaving just a web
> interface to tsearch to build.

Stupid question here, but haven't Oleg and crew not already done this?

----
Marc G. Fournier           Hub.Org Networking Services (http://www.hub.org)
Email . scrappy@hub.org                              MSN . scrappy@hub.org
Yahoo . yscrappy               Skype: hub.org        ICQ . 7615664

> -----Original Message-----
> From: Marc G. Fournier [mailto:scrappy@postgresql.org]
> Sent: 20 September 2006 13:33
> To: Dave Page
> Cc: Joshua D. Drake; Jim C. Nasby; pgsql-www@postgresql.org
> Subject: Re: [pgsql-www] [ams@oryx.com: [ANNOUNCE]
> Archiveopteryx 1.10 released]
>
> > If you want to move to a new tsearch search engine (which I'm not
> > against btw) then using our existing crawler script as a basis for a
> > generic indexer would bypass all those problems, leaving just a web
> > interface to tsearch to build.
>
> Stupid question here, but haven't Oleg and crew not already done this?

Yes, I believe so.

/D

>> If you want to move to a new tsearch search engine (which I'm not
>> against btw) then using our existing crawler script as a basis for a
>> generic indexer would bypass all those problems, leaving just a web
>> interface to tsearch to build.
>
> Stupid question here, but haven't Oleg and crew not already done this?

Yes and they have also offered to do it for us, once 8.2 is out. They
want GIN on the new interface.

Joshua D. Drake

>
> ----
> Marc G. Fournier           Hub.Org Networking Services (http://www.hub.org)
> Email . scrappy@hub.org                              MSN . scrappy@hub.org
> Yahoo . yscrappy               Skype: hub.org        ICQ . 7615664
>


--

    === The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
    Providing the most comprehensive  PostgreSQL solutions since 1997
              http://www.commandprompt.com/