> (un-CCed CERT, they don't care!)
>
> On Wed, Sep 09, 2009 at 10:20:33PM +0200, Simon Matter wrote:
>> > I'd like to announce the releases of Cyrus IMAPd 2.2.13p1 and 2.3.15.
>> > These releases should both be considered production quality. These
>> > releases are being made at this time to fix t
(un-CCed CERT, they don't care!)
On Wed, Sep 09, 2009 at 10:20:33PM +0200, Simon Matter wrote:
> > I'd like to announce the releases of Cyrus IMAPd 2.2.13p1 and 2.3.15.
> > These releases should both be considered production quality. These
> > releases are being made at this time to fix the poten
On Wed, Sep 09, 2009 at 07:31:51PM +0200, Sebastian Hagedorn wrote:
> -- David R Bosso is rumored to
> have mumbled on 9. September 2009 10:07:31 -0700 regarding Re: Cyrus
> IMAPd 2.2.13p1 & 2.3.15 Released:
>
> >Is there a specific reason the patch for bug #3159 wasn't included? I've
> >been ad
> I'd like to announce the releases of Cyrus IMAPd 2.2.13p1 and 2.3.15.
> These releases should both be considered production quality. These
> releases are being made at this time to fix the potential buffer
> overflow vulnerability described in CERT VU#336053:
> http://www.kb.cert.org/vuls/id/336
On Tue, 2009-07-21 at 11:57 -0400, Matt Selsky wrote:
> On Jul 21, 2009, at 10:43 AM, Carsten Hoeger wrote:
>
> > attached the patch to add regex pattern matching to folders for
> > ipurge.
>
> Can you add this to bugzilla for tracking?
Was this ever uploaded to the bugzilla?
Cyrus Home
On Wed, 2009-09-09 at 09:47 -0400, Ken Murchison wrote:
> I'd like to announce the releases of Cyrus IMAPd 2.2.13p1 and 2.3.15.
> These releases should both be considered production quality. These
> releases are being made at this time to fix the potential buffer
> overflow vulnerability descri
-- David R Bosso is rumored to have
mumbled on 9. September 2009 10:07:31 -0700 regarding Re: Cyrus IMAPd
2.2.13p1 & 2.3.15 Released:
Is there a specific reason the patch for bug #3159 wasn't included? I've
been adding it locally and just wondering if should continue to do so.
While we're
Is there a specific reason the patch for bug #3159 wasn't included? I've
been adding it locally and just wondering if should continue to do so.
Thanks.
-David
--On September 9, 2009 9:47:14 AM -0400 Ken Murchison
wrote:
> I'd like to announce the releases of Cyrus IMAPd 2.2.13p1 and 2.3.15
I'd like to announce the releases of Cyrus IMAPd 2.2.13p1 and 2.3.15.
These releases should both be considered production quality. These
releases are being made at this time to fix the potential buffer
overflow vulnerability described in CERT VU#336053:
http://www.kb.cert.org/vuls/id/336053
Th
On Wed, 2009-09-09 at 14:51 +1000, Rob Mueller wrote:
> > - cyrus-imapd-2.3.7 (from RHEL5/CentOS-5) with some minor patches in the
> > popd (UUID format and an enhancement to the authentication - both
> > shouldn't have any impact on the storage part)
>
> As I'm sure others will mention, this is
Hi all!
We need something like a caching imap proxy.
If an imap client accesses the proxy, instead of delegating the client
to the real server, the proxy should first try to serve the request out
of its cache. So that, if several clients access the proxy and ask for
the contents of the same messa
Quoting Bernd Petrovitsch :
On Tue, 2009-09-08 at 16:56 +0200, Michael Menge wrote:
[...]
Quoting Bernd Petrovitsch :
[...]
> We are running cyrus-imapd with all files (mailboxes, Berkeley-DB,
> mmap()ed files) on an ext3 filesystem (with data=ordered) on a iSCSI
> block device (and the actua
Quoting Georg Stich :
Hi!
Thank you.
I added the lines to my Sieve.php (/usr/share/pear/Net/Sieve.php)
Now ingo freezes.
No information in the logs.
We use Net_Sieve 1.1.6 with the Patch form the
Horde Bug-Tracker and Ingo 1.2.1
Does the logfiles indecate that the ingo session was auth
>This error comes from pear Net_Sieve, and indicates that the Connection is
>not in an Authenticated state. In this state you can upload scripts
>for a syntax check, but you can't do much more.
>
>As one of the mails in the ingo Mailinglist indicates, this problem does not
>exist in 2.3.11. The CAP
14 matches
Mail list logo
