The Cyrus team is proud to announce the immediate availability of a new
version of Cyrus IMAP: 2.5.7
This is a bug fix release for the 2.5 series.
Download URLs:
http://www.cyrusimap.org/releases/cyrus-imapd-2.5.7.tar.gz
http://www.cyrusimap.org/releases/cyrus-imapd-2.5.7.tar.gz.sig
ftp:
Hi Tim,
Yeah, those are the correct two commits.
>> My other concern was that, honestly, I'm not all that sure what the
>> true risk and capability to exploit is for these bugs. I've read the
>> CVE's, and associated discussions on the a few lists - but it hasn't
>> enlightened me as much as I'v
> Ellie, can you please fix the listen statement to accept correctly
> bracketed ipv6 and backport to at least 2.5 and 2.4, shouldn't be many
> changes in that code.
I don't think there's anything to fix here. The code looks fine as is,
just docs missing. Unless we want to explicitly *not* accep
Hi Sebastian,
> > Sebastian, is there anything you tried that *didn't* work, and if so,
> > what happened?
>
> The only thing I tried that didn't work was to add a IPv6 listener and to
> HUP the master process. The manpage for master reads (in my version):
>
>Cyrus-master rereads its co
Hi Sebastian,
> after thinking about it, I think it's like this: I added a service that
> was
> configured to listen on a privileged port. But master has dropped
> privileges by that point, so it can't add such a listener. I just
> double-checked that I *can* add a listener at run-time if it's
On Sat, Apr 9, 2016, at 08:04 AM, Wolfgang Breyha via Info-cyrus wrote:
> On 08/04/16 23:28, Wolfgang Breyha via Info-cyrus wrote:
> > Is it save to remove this limitation from mboxname.c?
>
> https://bugzilla.cyrusimap.org/show_bug.cgi?id=3693
>
> This patch was reverted in "some" releases, but
The Cyrus team is proud to announce the immediate availability of the
second beta from the Cyrus IMAP 3.0 series: 3.0.0-beta2.
As this is a beta release it is not considered stable for production
usage. Interfaces, APIs, features, etc are likely to change.
Download URLs:
http://www.cyrusima
Thanks for tracking that down. It's now on the cyrus-imapd-2.5 branch,
and will be in the next release.
Cheers,
ellie
On Fri, Apr 22, 2016, at 11:11 PM, Wolfgang Breyha via Info-cyrus wrote:
> rsto--- via Info-cyrus wrote on 21/04/16 22:51:
> > P.S.: I am based in Vienna as well, so feel free t
The Cyrus team is proud to announce the immediate availability of a new
version of Cyrus IMAP: 2.5.8
This is a bug fix release for the 2.5 series.
Download URLs:
http://www.cyrusimap.org/releases/cyrus-imapd-2.5.8.tar.gz
http://www.cyrusimap.org/releases/cyrus-imapd-2.5.8.tar.gz.sig
ftp:/
Hi Johan,
What revision are these patches against?
The Makefile.am patch is unnecessary, and doesn't apply cleanly anyway,
so I suspect you're looking at an old revision.
I haven't studied the httpd patch in depth yet.
Cheers,
ellie
On Thu, Jun 23, 2016, at 12:59 AM, Johan Hattne via Info-cyr
diawiki/index.php/Contribute#Anonymous_GIT_Access;
> the text indicates that development is actually happening elsewhere, but
> it has never been clear to me what the relationship between the
> repositories is.
>
> // Best wishes; Johan
>
> > On Jun 23, 2016, at 19:08, ell
t;
> > On Fri, Jun 24, 2016, at 11:33 PM, Johan Hattne wrote:
> >> Hi Ellie;
> >>
> >> $ git remote show origin | head -n 4
> >> * remote origin
> >>Fetch URL: git://git.cyrusimap.org/cyrus-imapd
> >> Push URL: git://git
The Cyrus team is proud to announce the immediate availability of the
third beta from the Cyrus IMAP 3.0 series: 3.0.0-beta3.
As this is a beta release it is not considered stable for production
usage. Interfaces, APIs, features, etc are likely to change.
Download URLs:
http://www.cyrusimap
On Fri, Jul 15, 2016, at 11:08 PM, Bron Gondwana via Info-cyrus wrote:
>
> It's in the cyrus-imapd-2.5 branch on git, so it will be in 2.5.9. I'll
> talk with Ellie on Monday about releasing that. I hope to have a fix for
> the other issue as well.
>
> Bron.
I was already planning on releasing
The Cyrus team is proud to announce the immediate availability of a new
version of Cyrus IMAP: 2.5.9
This is a bug fix release for the 2.5 series.
Download URLs:
http://www.cyrusimap.org/releases/cyrus-imapd-2.5.9.tar.gz
http://www.cyrusimap.org/releases/cyrus-imapd-2.5.9.tar.gz.sig
ftp:/
I don't have a 2.3.x environment handy to try to reproduce this from the
outside in, so I'm starting at the error code and working outwards...
> > <1469384361 > >1469384362>a0080 NO Mailbox format corruption detected
"Mailbox format corruption detected" corresponds with
IMAP_MAILBOX_CHECKSUM
Thi
On Mon, Jul 25, 2016, at 10:53 PM, Kenneth Marshall wrote:
> On Mon, Jul 25, 2016 at 03:53:43PM +1000, ellie timoney wrote:
> > I don't have a 2.3.x environment handy to try to reproduce this from the
> > outside in, so I'm starting at the error code and working outwards...
> >
> > > > <1469384361
Hi Jason,
That sounds pretty reasonable, thanks for the patch. I'll try to get it
tested and merged this week.
Cheers,
ellie
On Tue, Jul 26, 2016, at 06:25 AM, Jason Englander via Info-cyrus wrote:
> If you have a source installed OpenSSL under /usr/local/ssl on a 64-bit
> system, you probabl
e84d2f58afac0ff2e7d71bb0efb2a5ad7cb04a93
Cheers,
ellie
On Tue, Jul 26, 2016, at 09:54 AM, ellie timoney via Info-cyrus wrote:
> Hi Jason,
>
> That sounds pretty reasonable, thanks for the patch. I'll try to get it
> tested and merged this week.
>
> Cheers,
>
> ellie
The master branch has a commit to address this exact (like, literally
"TEXT.MIME") issue:
https://github.com/cyrusimap/cyrus-imapd/commit/f7b95b93
I've just cherry-picked it onto the cyrus-imapd-2.4 branch and it
applied cleanly first time, so it's upstream now. (It's already in 2.5,
and has bee
Thanks for passing these reports on!
Initial impression, I don't think this one is as straightforward as the
last one was, unfortunately. :(
Here's the chunk of code that produces those "guid mismatch" SYNCERRORs:
https://git.io/v6JWK
(wait a moment for it to load and it will jump to the lines I
I've been under the impression that Ken's mailboxes were version 10,
which seems like they *should* have guids in them. If this is the
case, then it's interesting that the replica is coming up with zeroed
ones.
If his mailboxes are older than version 10, then it all makes sense,
nothing to see h
fo-cyrus
> wrote:
> > Yeah, could be. In that case then the mailbox needs a reconstruct -G first
> > :(
> > Version 10 mailboxes have a GUID space available, but I guess they could
> > wind up zero depending on how they got upgraded in the past.
> >
> >
On Tue, Aug 2, 2016, at 02:14 PM, Kenneth Marshall via Info-cyrus wrote:
> On Tue, Aug 02, 2016 at 12:34:13PM +1000, Bron Gondwana wrote:
> > 2.3.2 wasn't version 10, it was version 7! It would have upgraded through
> > 8, 9, 10 - and maybe you needed to reconstruct to get GUIDs for those
> > ve
On Sat, Aug 13, 2016, at 03:12 AM, Kenneth Marshall wrote:
> On Wed, Aug 10, 2016 at 12:30:03PM +1000, ellie timoney wrote:
> > On Tue, Aug 2, 2016, at 02:14 PM, Kenneth Marshall via Info-cyrus wrote:
> > > On Tue, Aug 02, 2016 at 12:34:13PM +1000, Bron Gondwana wrote:
> > > > 2.3.2 wasn't versio
Isn't this already fixed on the 2.5 branch?
On Mon, Aug 22, 2016, at 02:17 AM, Ken Murchison via Info-cyrus wrote:
> I'm guessing we should steal json_support.h from master and add it to
> the 2.5 branch.
>
>
> On 08/20/2016 10:40 AM, Wolfgang Breyha via Info-cyrus wrote:
> > After modifying my
is a tool used in the build process only, it
shouldn't get installed anywhere (nor should its source). Will see if I
can reproduce it and work out why it happens.
Cheers,
ellie
On Mon, Aug 22, 2016, at 09:14 AM, ellie timoney via Info-cyrus wrote:
> Isn't this already fixed on the
hanging around from some
earlier version? Before it got moved to tools/, the htmlstrip.c file
used to live in doc/text/ -- the same directory as the plain text docs
that it was used to generate (from html sources). It's entirely
plausible that some previous version would then install it alon
On Sat, Aug 13, 2016, at 03:12 AM, Kenneth Marshall wrote:
> Hi Ellie,
>
> I tried the patch and it did print the warnings on the replica.
> Unfortunately,
> it looked like it was looping on the master (sync_client) and the updates
> that
> could be made were not. I had to rollback to the dying ve
Do you have "lmtp" defined in /etc/services?
On Thu, Aug 25, 2016, at 08:44 AM, Andy Dorman via Info-cyrus wrote:
> We have a cluster of servers that provide external email security
> filtering and then postfix delivers the safe email via lmtp to mailboxes
> on the various servers in the cluster
oked at the lmtpengine.c source on github and did not see an obvious
> source for this particular log output...but I am not a C programmer and
> could be completely missing what is going on here.
>
> Andy Dorman
>
> On 08/25/2016 06:19 PM, ellie timoney via Info-cyrus wrote:
&g
> We now have 4 of the 14 servers where the number of imapd processes
> slowly grows and usually within 12-14 hours reaches the imapd process
> limit (currently set to 100).
How many user accounts are on these servers? Each client connection
constitutes one imapd process on the server.
It's my
their
> settings in case I completely misunderstood how these work.
>
> In the meantime I am going to bump my max processes up to 200 and my
> monitoring warning level to 150 see how that works.
>
> Thanks for all the help everyone.
>
> Andy
>
> On 09/11/2016 11:05 PM, el
ls
the server it's Idle, and then waits for the server to tell it about any
new activity.
But understanding how the service is actually being used will do a lot
to calibrate your expectations of how the server should be behaving
(such as, how many concurrent connections/imapd processes you
ow this user so I will ask her what email client she is using and
> > how often it is set to check email.
>
> How often it is set to check email won't make much difference in this
> case. That is more for servers that don't support Idle, so the client
> has to keep askin
ations in the meantime.)
Cheers,
ellie
On Sat, Oct 1, 2016, at 12:00 AM, Andy Dorman via Info-cyrus wrote:
> On 09/28/2016 09:59 AM, Andy Dorman wrote:
> > On 09/27/2016 07:08 PM, ellie timoney via Info-cyrus wrote:
> >> I wonder if we can see what the old processes are actually do
On Tue, Oct 4, 2016, at 12:46 AM, Andy Dorman via Info-cyrus wrote:
> On 10/02/2016 06:57 PM, ellie timoney via Info-cyrus wrote:
> > Hi Andy,
> >
> > Thanks very much for the detailed information. It may take me a while
> > to digest this, but it looks like it will
The Cyrus team is proud to announce the immediate availability of a new
version of Cyrus IMAP: 2.5.10
This is a bug fix release for the 2.5 series.
Download URLs:
http://www.cyrusimap.org/releases/cyrus-imapd-2.5.10.tar.gz
http://www.cyrusimap.org/releases/cyrus-imapd-2.5.10.tar.gz.sig
ft
On Sat, Oct 22, 2016, at 10:25 AM, Rob N ★ via Info-cyrus wrote:
> The docs suggest this feature is in the currently-unreleased Cyrus 3.0
> series. That's probably true, but I can't be sure (FastMail runs the
> current dev/master branch, so we're ahead of 3.0). It'll be well worth
> the upgrade whe
> accept failed: Software caused connection abort
Some sleuthing suggests that "Software caused connection abort"
corresponds with "ECONNABORTED".
The man page on my system for accept(2) unhelpfully defines this as:
>ECONNABORTED
> A connection has been aborted.
But some d
eers,
ellie
On Wed, Oct 26, 2016, at 10:04 AM, ellie timoney via Info-cyrus wrote:
> > accept failed: Software caused connection abort
>
> Some sleuthing suggests that "Software caused connection abort"
> corresponds with "ECONNABORTED".
>
> The ma
The Cyrus team is proud to announce the immediate availability of the
fourth beta from the Cyrus IMAP 3.0 series: 3.0.0-beta4.
As this is a beta release it is not considered stable for production
usage. Interfaces, APIs, features, etc are likely to change.
Download URLs:
http://www.cyrusima
On Tue, Nov 8, 2016, at 05:01 AM, Eric Cunningham wrote:
> Nov 7 10:18:19 imap1 lmtpunix[58768]: unable to setsocketopt(TCP_KEEPCNT):
> Invalid argument
> Nov 7 10:18:19 imap1 lmtpunix[58768]: unable to setsocketopt(TCP_KEEPIDLE):
> Invalid argument
> Nov 7 10:18:19 imap1 lmtpunix[58768]: unab
The Cyrus team is proud to announce the immediate availability of the
fifth beta from the Cyrus IMAP 3.0 series: 3.0.0-beta5.
As this is a beta release it is not considered stable for production
usage. Interfaces, APIs, features, etc are likely to change.
Download URLs:
http://www.cyrusimap
Hi Nels,
The autocreate code in 2.5 is full of LOG_DEBUG syslogs -- I guess you
don't have this turned on, or you're logging that log level to a
different file. It would be helpful to see this output.
I think you can turn this logging on in Cyrus by adding "debug: yes" to
your imapd.conf. You m
On Tue, Dec 13, 2016, at 07:04 AM, Nels Lindquist via Info-cyrus wrote:
> On 2016/12/12 4:06 AM, ellie timoney wrote:
>
> >> Any ideas?
> >
> > No, unfortunately.
> >
> > We have some basic syslog instructions (aimed at developers setting up a
> > Cyrus development environment), but it sounds like
Oh awesome, thanks for the update :)
On Tue, Dec 13, 2016, at 07:23 AM, Nels Lindquist via Info-cyrus wrote:
> Okay I figured it out.
>
> I was working with the Kolab packages, and went back and checked their
> distributed .spec file again, and the --enable-autocreate option was not
> present i
The Cyrus team is proud to announce the immediate availability of the
sixth beta from the Cyrus IMAP 3.0 series: 3.0.0-beta6.
As this is a beta release it is not considered stable for production
usage. Interfaces, APIs, features, etc are likely to change.
Download URLs:
http://www.cyrusimap
The Cyrus team is proud to announce the immediate availability of the
first release candidate from the Cyrus IMAP 3.0 series: 3.0.0-rc1.
As a release candidate, it is considered near-stable for production
usage. Interfaces, APIs, features, etc are not likely to change
between now and the full re
For what it's worth, looking at commit history, it looks like it went
away sometime before 2.4.0
On Tue, Jan 17, 2017, at 09:41 AM, Bron Gondwana via Info-cyrus wrote:
> Yep, it's gone away - sha1 is the only mode right now. We're going to
> want to look at blake2 soon though I reckon.
>
> Bron.
nfo-cyrus wrote:
> > Thanks for the heads-up. We'll get this fixed, it is the man page which
> > is correct.
> > -nic
> >
> > On 01/16/2017 10:19 AM, Andy Dorman via Info-cyrus wrote:
> > > On 01/13/2017 12:07 AM, ellie timoney via Info-cyrus wrot
The Cyrus team is proud to announce the immediate availability of the
second release candidate from the Cyrus IMAP 3.0 series: 3.0.0-rc2.
As a release candidate, it is considered near-stable for production
usage. Interfaces, APIs, features, etc are not likely to change
between now and the full r
52 matches
Mail list logo
