day, January 09, 2007 12:49 PM
> To: Bron Gondwana
> Cc: Info Cyrus
> Subject: Re: Patches used at FastMail.FM
>
> Bron Gondwana wrote:
> > It's been a while since I posted our list of patches, and there have
> been
> > a couple of changes since then.
> >
>
On 1/8/07, Robert Banz <[EMAIL PROTECTED]> wrote:
On Jan 8, 2007, at 21:08, Rob Mueller wrote:
>> We are using 2.3.7 on Debian Sarge.
>> We will maybe move to solaris because of the features of ZFS.
>
> Does anyone know the status of ZFS + fsync performance problems?
>
> http://www.irbs.net/int
Rob Mueller wrote:
Ok, I thought that 'post' pre-dated lmtp and was the IMAP function to
write a message into the folder.
i.e. a program like imapsync would need the 'p' permission to write
the messages, (but would need other permissions to check for messages,
set flags, etc)
I think the on
Rob Mueller wrote:
but this is in conflict with the the idea that in a large installation
of people who don't know each other the 'anyone' permission doesn't
make sense.
what is really desired for + addressing is to say that messages that
arrive via the lmtp interface are allowed to write to
Ok, I thought that 'post' pre-dated lmtp and was the IMAP function to
write a message into the folder.
i.e. a program like imapsync would need the 'p' permission to write the
messages, (but would need other permissions to check for messages, set
flags, etc)
I think the only way to add a mess
On Wed, 10 Jan 2007, Rob Mueller wrote:
but this is in conflict with the the idea that in a large installation of
people who don't know each other the 'anyone' permission doesn't make
sense.
what is really desired for + addressing is to say that messages that arrive
via the lmtp interface ar
but this is in conflict with the the idea that in a large installation of
people who don't know each other the 'anyone' permission doesn't make
sense.
what is really desired for + addressing is to say that messages that
arrive via the lmtp interface are allowed to write to all folders (not
ju
On Wed, 10 Jan 2007, Rob Mueller wrote:
the usual reason for allowing the "anyone" ACL is to allow for + addressing
to
work.
is there another way to do this?
The admin user can still set the anyone acl, it's just non-admin users can't
change/set it. The way we do this to allow + addressin
the usual reason for allowing the "anyone" ACL is to allow for +
addressing to
work.
is there another way to do this?
The admin user can still set the anyone acl, it's just non-admin users can't
change/set it. The way we do this to allow + addressing is when we create
the users top level f
On Tue, 09 Jan 2007 08:52:21 -0500, "Ken Murchison" <[EMAIL PROTECTED]> said:
>
> http://cyrus.brong.fastmail.fm/cyrus-plainsync-2.3.3.diff
>
> Why not just run 'sync_server -p 2' ? I believe that I added the 'p'
> option to all services for just this reason.
It didn't work in my testing for
On Tue, 9 Jan 2007, Ken Murchison wrote:
Disable "anyone" ACL
the usual reason for allowing the "anyone" ACL is to allow for + addressing to
work.
is there another way to do this?
in most cases I think that a global 'allow + addressing' config option is really
more appropriate then havi
On Tue, 09 Jan 2007 12:49:25 -0500, "Ken Murchison" <[EMAIL PROTECTED]> said:
> Bron Gondwana wrote:
> > It's been a while since I posted our list of patches, and there have been
> > a couple of changes since then.
> >
> > I'm generating the site from a script and a bunch of patch description fil
Bron Gondwana wrote:
On Tue, 09 Jan 2007 08:52:21 -0500, "Ken Murchison" <[EMAIL PROTECTED]> said:
http://cyrus.brong.fastmail.fm/cyrus-plainsync-2.3.3.diff
Why not just run 'sync_server -p 2' ? I believe that I added the 'p'
option to all services for just this reason.
It didn't work in my
Bron Gondwana wrote:
It's been a while since I posted our list of patches, and there have been
a couple of changes since then.
I'm generating the site from a script and a bunch of patch description files
now, so I should be able to keep it up to date.
Feel free to use any of these patches, and
http://cyrus.brong.fastmail.fm/cyrus-plainsync-2.3.3.diff
Why not just run 'sync_server -p 2' ? I believe that I added the 'p'
option to all services for just this reason.
--
Kenneth Murchison
Systems Programmer
Project Cyrus Developer/Maintainer
Carnegie Mellon University
Cyrus Home Pa
On Jan 8, 2007, at 21:08, Rob Mueller wrote:
We are using 2.3.7 on Debian Sarge.
We will maybe move to solaris because of the features of ZFS.
Does anyone know the status of ZFS + fsync performance problems?
http://www.irbs.net/internet/info-cyrus/0610/0058.html
Supposedly fixed in Solaris
Jeff and I have already discussed pushing out a 2.3 release soon -- as
soon as we iron out all of the wrinkles in our 2.3 deployment on campus.
We found a few small buglets in the IMAP proxy code that we didn't
expect. Either nobody else has a 2.3 Murder running, or they didn't
notice the random
We are using 2.3.7 on Debian Sarge.
We will maybe move to solaris because of the features of ZFS.
Does anyone know the status of ZFS + fsync performance problems?
http://www.irbs.net/internet/info-cyrus/0610/0058.html
Rob
Cyrus Home Page: http://cyrusimap.web.cmu.edu/
Cyrus Wiki/FAQ: ht
On Mon, 08 Jan 2007 11:23:50 -0500, "Ken Murchison" <[EMAIL PROTECTED]> said:
> Bron Gondwana wrote:
> > It's been a while since I posted our list of patches, and there have been
> > a couple of changes since then.
> >
> > I'm generating the site from a script and a bunch of patch description fil
On 08 Jan 2007, at 11:23, Ken Murchison wrote:
We found a few small buglets in the IMAP proxy code that we didn't
expect. Either nobody else has a 2.3 Murder running, or they
didn't notice the random (infrequent) core dumps.
We're (UMich) continuing to run 2.3 replicated backends with 2.2
Farzad FARID wrote:
king coredump.
I too wonder who runs Cyrus IMAP 2.3 Murder, because hardly anybody ever
answers my questions here and I have to reply to myself ;)
Our site is planning to migrate to the Murder setup. But I haven't
gotten to it yet. Currently we have about 41955 accounts
On Mon, 8 Jan 2007, Farzad FARID wrote:
Hi,
on 08.01.2007 17:23 Ken Murchison said the following:
Jeff and I have already discussed pushing out a 2.3 release soon -- as
soon as we iron out all of the wrinkles in our 2.3 deployment on campus.
We found a few small buglets in the IMAP proxy cod
Hi,
on 08.01.2007 17:23 Ken Murchison said the following:
>
> Jeff and I have already discussed pushing out a 2.3 release soon -- as
> soon as we iron out all of the wrinkles in our 2.3 deployment on campus.
>
> We found a few small buglets in the IMAP proxy code that we didn't
> expect. Either n
Ben Poliakoff wrote:
* Ken Murchison <[EMAIL PROTECTED]> [20070108 08:34]:
Jeff and I have already discussed pushing out a 2.3 release soon -- as
soon as we iron out all of the wrinkles in our 2.3 deployment on campus.
We found a few small buglets in the IMAP proxy code that we didn't
expect.
* Ken Murchison <[EMAIL PROTECTED]> [20070108 08:34]:
>
> Jeff and I have already discussed pushing out a 2.3 release soon -- as
> soon as we iron out all of the wrinkles in our 2.3 deployment on campus.
>
> We found a few small buglets in the IMAP proxy code that we didn't
> expect. Either no
Simon Matter wrote:
It's been a while since I posted our list of patches, and there have been
a couple of changes since then.
I'm generating the site from a script and a bunch of patch description
files
now, so I should be able to keep it up to date.
Feel free to use any of these patches, and
Bron Gondwana wrote:
It's been a while since I posted our list of patches, and there have been
a couple of changes since then.
I'm generating the site from a script and a bunch of patch description files
now, so I should be able to keep it up to date.
Feel free to use any of these patches, and
> It's been a while since I posted our list of patches, and there have been
> a couple of changes since then.
>
> I'm generating the site from a script and a bunch of patch description
> files
> now, so I should be able to keep it up to date.
>
>
> Feel free to use any of these patches, and Ken - f
I guess it would be polite to send the URL again! Oops.
http://cyrus.brong.fastmail.fm/
Regards,
Bron.
--
Bron Gondwana
[EMAIL PROTECTED]
Cyrus Home Page: http://cyrusimap.web.cmu.edu/
Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki
List Archives/Info: http://asg.web.cmu.edu/cyrus
It's been a while since I posted our list of patches, and there have been
a couple of changes since then.
I'm generating the site from a script and a bunch of patch description files
now, so I should be able to keep it up to date.
Feel free to use any of these patches, and Ken - feel free to inc
Robert Mueller wrote:
accept the message, store it "as is" and ignore the stuff you don't
understand when building indexes.
And ignore it when using the indexes. Yes, but where's the patch to do
that?
I'll have a guess that something like this already happens. My guess is
that the charset m
At Mon, 29 May 2006 23:27:10 +0200 (CEST),
Simon Matter wrote:
>
> Stop, are you joking? Did you ever work in the corporate world? Did you
> ever have a boss in a large international company? Did you ever tell him
> that the server you installed _rejects_ mail?
Indeed. Many times.
In store-and-
> At Sat, 27 May 2006 11:56:38 +1000,
> Robert Mueller wrote:
>>
>> >> Comments on the non-local ones:
>> >> - cyrus-8bit-2.3.3.diff
>> >
>> > Was it not the position held by CMU in the last five years or so that
>> one
>> > such patch would *have* do to it properly and re-encode the header to
>> s
At Sat, 27 May 2006 11:56:38 +1000,
Robert Mueller wrote:
>
> >> Comments on the non-local ones:
> >> - cyrus-8bit-2.3.3.diff
> >
> > Was it not the position held by CMU in the last five years or so that one
> > such patch would *have* do to it properly and re-encode the header to some
> > default
accept the message, store it "as is" and ignore the stuff you don't
understand when building indexes.
And ignore it when using the indexes. Yes, but where's the patch to do
that?
I'll have a guess that something like this already happens. My guess is that
the charset mapping tables ignore 8-
On Sat, 27 May 2006, Ken Murchison wrote:
> Henrique, do you recall if SEARCH dies, or just doesn't get any useful
> hits on non-tagged 8-bit headers?
I don't recall this either. But if you did accept the patch, I think it is
time to go over IMAP SEARCH and make sure it doesn't do stupid things
Henrique de Moraes Holschuh wrote:
On Fri, 26 May 2006, Ken Murchison wrote:
Comments on the non-local ones:
- cyrus-8bit-2.3.3.diff
As I said in my reply to the CVS commit (which I noticed before this mail),
I am quite surprised by this patch being accepted.
Was it not the position held by C
On Sat, 27 May 2006, Bron Gondwana wrote:
> > > 4. Recode correctly in MIME encoding based on the message charset - Would
> > > be great but:
> >
> > Nah, just according to some site-wide config option from imap.conf would
> > be
> > more than good enough.
>
> Wow, I'm glad you know enough about
On Sat, 27 May 2006 02:06:20 -0300, "Henrique de Moraes Holschuh" <[EMAIL
PROTECTED]> said:
> On Sat, 27 May 2006, Robert Mueller wrote:
> > I think having this as an *option* is perfectly reasonable. There are
>
> So do I, Debian has this patch for three or four years now. It comes with
> a
>
On 05/26/06 20:37, Simon Matter wrote:
Hij
- cyrus-fromheader-2.3.3.diff
Outlook sucks. I hate to have to commit yet another M$ workaround. How
widespread are these non-RFC2822-compliant messages?
I do not think it is just outlook. I've also seen problems with notes
doing stuff like this.
I
On Sat, 27 May 2006, Carlos Horowicz wrote:
> I was just asking to the list if Fastmail's cyrus-8bit-2.3.3.diff would
> let avoid rejections due to "Message contains NUL chars"
No it won't, and you *really* don't want to store anything with embedded
NULs, you have to at least remove them, as repl
On Sat, 27 May 2006, Robert Mueller wrote:
> I think having this as an *option* is perfectly reasonable. There are
So do I, Debian has this patch for three or four years now. It comes with a
big warning to the likes of "You are stupid to enable this and still wonder
why multi-language search is n
Andreas Hasenack wrote:
On Fri, May 26, 2006 at 05:35:30PM -0300, Carlos Horowicz wrote:
Andreas Hasenack wrote:
On Fri, May 26, 2006 at 05:02:25PM -0300, Carlos Horowicz wrote:
Hi
I get only a daily few of "Message contains invalid header" but a couple
of thousand per d
Comments on the non-local ones:
- cyrus-8bit-2.3.3.diff
Was it not the position held by CMU in the last five years or so that one
such patch would *have* do to it properly and re-encode the header to some
default charset, in order not to corrupt the store with lack of charset
information (for
On Fri, May 26, 2006 at 05:35:30PM -0300, Carlos Horowicz wrote:
>
> Andreas Hasenack wrote:
>
> >On Fri, May 26, 2006 at 05:02:25PM -0300, Carlos Horowicz wrote:
> >
> >
> >>Hi
> >>
> >>I get only a daily few of "Message contains invalid header" but a couple
> >>of thousand per day of "Message
Andreas Hasenack wrote:
On Fri, May 26, 2006 at 05:02:25PM -0300, Carlos Horowicz wrote:
Hi
I get only a daily few of "Message contains invalid header" but a couple
of thousand per day of "Message contains NUL characters" from lmtpd ...
What version of cyrus? There was a bug that
On Fri, May 26, 2006 at 05:02:25PM -0300, Carlos Horowicz wrote:
> Hi
>
> I get only a daily few of "Message contains invalid header" but a couple
> of thousand per day of "Message contains NUL characters" from lmtpd ...
What version of cyrus? There was a bug that caused the NUL error with long
On Fri, 26 May 2006, Ken Murchison wrote:
> Comments on the non-local ones:
> - cyrus-8bit-2.3.3.diff
As I said in my reply to the CVS commit (which I noticed before this mail),
I am quite surprised by this patch being accepted.
Was it not the position held by CMU in the last five years or so tha
Hi
I get only a daily few of "Message contains invalid header" but a couple
of thousand per day of "Message contains NUL characters" from lmtpd ...
I've read through all threads both in postfix and cyrus lists about
this, but didn't find any conclusion on how to avoid the bounces ... has
the
> Hij
>> - cyrus-fromheader-2.3.3.diff
>>
>> Outlook sucks. I hate to have to commit yet another M$ workaround. How
>> widespread are these non-RFC2822-compliant messages?
>
> I do not think it is just outlook. I've also seen problems with notes
> doing stuff like this.
>
> I get errors like this
On Fri, May 26, 2006 at 08:14:51PM +0200, Tarjei Huse wrote:
> Hij
> >- cyrus-fromheader-2.3.3.diff
> >
> >Outlook sucks. I hate to have to commit yet another M$ workaround. How
> >widespread are these non-RFC2822-compliant messages?
>
> I do not think it is just outlook. I've also seen problem
Hij
- cyrus-fromheader-2.3.3.diff
Outlook sucks. I hate to have to commit yet another M$ workaround. How
widespread are these non-RFC2822-compliant messages?
I do not think it is just outlook. I've also seen problems with notes
doing stuff like this.
I get errors like this one in my logs
Quoting Ken Murchison ([EMAIL PROTECTED]):
>
> - cyrus-fromheader-2.3.3.diff
>
> Outlook sucks. I hate to have to commit yet another M$ workaround. How
> widespread are these non-RFC2822-compliant messages?
Its not an Outlook issue. Its other IMAP providers that deliver
non-standard headers
Bron Gondwana wrote:
I've finally split out all the patches that we use here into
individual items.
Comments on the non-local ones:
- cyrus-8bit-2.3.3.diff
Applied to CVS.
- cyrus-anyone-2.3.3.diff
If you want to complete the documentation, I'll consider applying the patch.
- cyrus-comma
I know we discussed this in the past, but I can't seem to find the thread.
What part of the existing STATUS code causes the bottleneck?
Is it STATUS_RECENT and STATUS_UNSEEN?
It's a combination of both. The main things are:
1. Status UNSEEN and RECENT both have to loop over the cyrus.index fi
--On May 23, 2006 10:34:20 PM +1000 Robert Mueller <[EMAIL PROTECTED]> wrote:
Statuscache also piqued my interestDoes it give any win for POP3
clients? We've a *HUGE* number of Outlook users that have the terribly
wrong idea that they just MUST poll every minute. That along with the
se
Robert Mueller wrote:
Cool, some of the patches look really interesting and I'm considering to
include one or the other into my rpm packages. For example the
statuscache
patch seems very nice. Just to be sure, are there any license
restrictions
on the patches?
No, no license restrictions.
John Madden wrote:
I'm in the process of porting a couple of patches from UMich into 2.3
and then I'm going to make a release which includes a fix for an easily
exploitable buffer overflow in pop3d.
Ehm? Does this affect the 2.2.x branch as well?
No. The exploit is in a feature added in 2
> I'm in the process of porting a couple of patches from UMich into 2.3
> and then I'm going to make a release which includes a fix for an easily
> exploitable buffer overflow in pop3d.
Ehm? Does this affect the 2.2.x branch as well?
John
--
John Madden
Sr. UNIX Systems Engineer
Ivy Tech
Ken Murchison wrote:
Bron Gondwana wrote:
I've finally split out all the patches that we use here into
individual items.
I know some people were interested in the "don't allow users to
set the anyone ACL" patch as well.
http://cyrus.brong.fastmail.fm/
Ken - I'd love to work with you on gettin
Bron Gondwana wrote:
I've finally split out all the patches that we use here into
individual items.
I know some people were interested in the "don't allow users to
set the anyone ACL" patch as well.
http://cyrus.brong.fastmail.fm/
Ken - I'd love to work with you on getting as many as possible
Statuscache also piqued my interestDoes it give any win for POP3
clients? We've a *HUGE* number of Outlook users that have the terribly
wrong idea that they just MUST poll every minute. That along with the
seen state stuff would be a good thing for us.
No, it's only for IMAP clients an
Cool, some of the patches look really interesting and I'm considering to
include one or the other into my rpm packages. For example the statuscache
patch seems very nice. Just to be sure, are there any license restrictions
on the patches?
No, no license restrictions. We'd love these to get bac
--On May 23, 2006 8:37:45 AM +0200 Simon Matter
<[EMAIL PROTECTED]> wrote:
Cool, some of the patches look really interesting and I'm considering to
include one or the other into my rpm packages. For example the statuscache
patch seems very nice. Just to be sure, are there any license restric
> I've finally split out all the patches that we use here into
> individual items.
>
> I know some people were interested in the "don't allow users to
> set the anyone ACL" patch as well.
>
> http://cyrus.brong.fastmail.fm/
>
> Ken - I'd love to work with you on getting as many as possible of these
I've finally split out all the patches that we use here into
individual items.
I know some people were interested in the "don't allow users to
set the anyone ACL" patch as well.
http://cyrus.brong.fastmail.fm/
Ken - I'd love to work with you on getting as many as possible of these
into upstream,
66 matches
Mail list logo
