/ to report issues, join in
the
deliberations of new features for the next Cyrus IMAP release, and to
contribute to the documentation.
On behalf of the Cyrus team,
Kind regards,
Ellie Timoney
Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http://lists.andrew.cmu.edu
/ to report issues, join in
the
deliberations of new features for the next Cyrus IMAP release, and to
contribute to the documentation.
On behalf of the Cyrus team,
Kind regards,
Ellie Timoney
Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http://lists.andrew.cmu.edu
/ to report issues, join in
the
deliberations of new features for the next Cyrus IMAP release, and to
contribute to the documentation.
On behalf of the Cyrus team,
Kind regards,
Ellie Timoney
Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http://lists.andrew.cmu.edu
/ to report issues, join in
the deliberations of new features for the next Cyrus IMAP release,
and to contribute to the documentation.
On behalf of the Cyrus team,
Kind regards,
Ellie Timoney
Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http://lists.andrew.cmu.edu/pipermail
at https://git.cyrus.foundation/ to report issues, join in
the deliberations of new features for the next Cyrus IMAP release,
and to contribute to the documentation.
On behalf of the Cyrus team,
Kind regards,
Ellie Timoney
Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http
://git.cyrus.foundation/ to report issues, join in
the deliberations of new features for the next Cyrus IMAP release,
and to contribute to the documentation.
On behalf of the Cyrus team,
Kind regards,
Ellie Timoney
Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http
Hi Sergey,
The official git moved from cyrusimap.org to cyrus.foundation some time
ago -- prior to the release of 2.5.0, I believe.
The repositories (and their urls for git clone) can be browsed here:
https://git.cyrus.foundation/diffusion/
Clicking through from there to e.g. the cyrus-imapd re
Hi Shaheen,
> What is the difference between 2.4 and 2.5 (why are there three versions
> all being updated?).
2.5 is the current stable version.
2.4, while old, still has significant numbers of installations in the
wild. The new release was due to the security fixes. The other bug
fixes were i
of the Cyrus team,
Kind regards,
Ellie Timoney
Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
To Unsubscribe:
https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus
/ to report issues, join in
the deliberations of new features for the next Cyrus IMAP release, and
to contribute to the documentation.
On behalf of the Cyrus team,
Kind regards,
Ellie Timoney
Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http://lists.andrew.cmu.edu/pipermail
/ to report issues, join in
the deliberations of new features for the next Cyrus IMAP release, and
to contribute to the documentation.
On behalf of the Cyrus team,
Kind regards,
Ellie Timoney
Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http://lists.andrew.cmu.edu/pipermail
Hi Patrick,
> Second, where is this coming from?
>
>Sep 19 05:44:54 toad cyrus/master[22860]: setrlimit: Unable to set
> file descriptors limit to -1: Operation not permitted
This one is interesting.
Resource limits have a "current" and a "maximum" value. Processes with
suitable capabilit
finite file descriptors, but we didn't anyway, and we also no longer
log an error about it at every startup.
I'm cherry picking this fix onto the 2.5 branch, so it will be in 2.5.7,
whenever that comes about (no ETA yet).
On Mon, Sep 21, 2015, at 11:27 AM, ellie timoney wrote:
> Hi Pa
Hi Paul,
I have no insight into Andrea's original problem; I'm commenting
specifically on the /dev/shm thing.
> >Aug 24 08:50:25 kolab imap/imaps[7782]: IOERROR: bogus filename
> > "/dev/shm//tls_sessions.db" in proc_foreach
> > [...]
> > The Point to look at is "/dev/shm//tls_sessions.d
Hi Artyom,
Yeah wow, this is really gross.
I'm pretty sure the gibberish in those "??Default.script.bc"
filenames is just whatever junk was in the (uninitialised)
sieve_script_dir variable.
I've had a rummage around, and there's a user_sieve_path() function in
imap/user.c that does the heavy
t.script.bc.NEW. Unknown error Oct 7
> 16:54:10 imapsync cyrus/imap[4062]: autocreate_sieve: User root,
> default sieve script creation failed No one files/folders are
> creating.
>
> On Tue, Oct 6, 2015 at 3:51 AM, ellie timoney
> wrote:
>> __
>> Hi Artyom,
>>
>&
s down. Thanks for sending through these reports! :)
Cheers,
ellie
On Fri, Oct 9, 2015, at 08:41 AM, ellie timoney wrote:
>> First I guest we need NOT here (?)
>
> Doh!
>
>> And second creating are failing with follow logs (yes I use 'root'
>> user for te
ause no one directory/files is creating
> under */var/spool/sieve/r *directory But tmp files gone from
> */var/lib/cyrus/*
>
> On Fri, Oct 9, 2015 at 2:36 AM, ellie timoney
> wrote:
>> __
>> Hi again,
>>
>> A couple more patches:
>>
>>
>>>
On Fri, Oct 16, 2015, at 10:34 AM, Bron Gondwana wrote:
> @Ellie - let's add this, it's plainly the right thing to do.
>
Yeah, agreed.
> On Fri, Oct 16, 2015, at 02:54, Wolfgang Breyha wrote:
> > I patched it a while ago for my local RPMs:
This is now in git on cyrus-imapd-2.5 and master branch
Hi Sergey,
Do you have pkg-config installed on your system? If not, does
installing it help?
Does your pcre library support utf8? Cyrus depends on a utf8-enabled
pcre library. If your pcre library does not appear to support utf-8,
then the configure script will find the headers but will decide
> Test: badservice ...lt-unit: threads.c:342: krb5int_key_register:
> Assertion `destructors_set[keynum] == 0' failed.
> /bin/sh: line 10: 791 Aborted $vg ./unit $f
This looks like it's related to krb5 somehow, which I know nothing
about. Can someone who uses or has used Cyr
On Fri, Feb 17, 2017, at 09:42 AM, Kenneth Marshall wrote:
> On Thu, Feb 16, 2017 at 04:14:38PM -0600, Dan White wrote:
> > On 02/16/17 16:10 -0600, Kenneth Marshall wrote:
> > >We are running version cyrus-imapd-2.5.10, and even though no databases
> > >in imapd.conf default to berkeleydb, somethi
the Cyrus team,
Kind regards,
ellie timoney
Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
To Unsubscribe:
https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus
.
On behalf of the Cyrus team,
Kind regards,
ellie timoney
Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
To Unsubscribe:
https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus
Hi Paolo,
It is "20 most recently deleted mailboxes with the same path"
So if someone delete/create/deletes "user/bovik/some_folder" over and
over again, there will only be a maximum of 20
"DELETED/user/bovik/some_folder/" mailboxes on disk. The
older ones are discarded.
> 1) what happens
Thanks! :)
On Sat, Mar 18, 2017, at 04:04 AM, Hajimu UMEMOTO wrote:
> Hi,
>
> >>>>> On Fri, 17 Mar 2017 17:04:52 +1100
> >>>>> ellie timoney said:
>
> ellie> The Cyrus team is proud to announce the immediate availability of
> the
> elli
ons of new features for the next
Cyrus IMAP release, and to contribute to the documentation.
On behalf of the Cyrus team,
Kind regards,
ellie timoney
Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
To Unsubscr
> Received: from storage.mail ([unix socket])
> by storage.mail (Cyrus v2.3.16-Fedora-RPM-2.3.16-13.el6_6) with
> LMTPA;
> Mon, 03 Apr 2017 21:27:35 +0200
> X-Sieve: CMU Sieve 2.3
Wild guess, is your script using sieve features that are not available
in 2.3.16? 2.3.16 was released
Hi Olaf,
I think this is expected behaviour. Mailbox annotations in the
"/private/" namespace are per user -- such that if multiple users have
access to the same mailbox, they can each have their own annotations on
it.
So, when you log into this account with IMAP and set /private/specialuse
ann
,
ellie timoney
Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
To Unsubscribe:
https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus
Hi István,
Historically, Cyrus has been a source-only distribution. Deb packages
have been provided by the Debian team, and similarly for other package
management systems.
We're planning to start distributing a basic deb package (mostly, I
think, to act as a guide/reference for official packagers
If you run it from the EVENTS section of cyrus.conf, it won't run when
Cyrus itself isn't running. Depending on your expectation at the time,
that might be an advantage or disadvantage
On Mon, May 1, 2017, at 07:19 PM, Sebastian Hagedorn wrote:
> > What advantages / disadvantages to running squat
team,
Ellie Timoney
Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
To Unsubscribe:
https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus
/cyrusimap/cyrus-imapd to report
issues, join in the deliberations of new features for the next Cyrus
IMAP release, and to contribute to the documentation.
On behalf of the Cyrus team,
Ellie Timoney
Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http://lists.andrew.cmu.edu
join us at https://github.com/cyrusimap/ to report issues, join in
the deliberations of new features for the next Cyrus IMAP release, and
to contribute to the documentation.
On behalf of the Cyrus team,
Ellie Timoney
Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http
On Sat, May 20, 2017, at 05:59 PM, Simon Matter wrote:
> > This is the point where the wrong path is taken.
> >
> >
> > r = mlookup(namebuf, &server, NULL, NULL);
> > if (!r && server) {
> > /* remote mailbox */
> > proxy_adddest(&dlist, rcpt, n, server, authuser);
> > status[n] = no
On Mon, May 22, 2017, at 03:55 PM, Simon Matter wrote:
> Hi Ellie,
>
> Thanks for looking into it.
>
> Unfortunately with your new version of the patch I only get this:
>
> lmtpunix[23046]: FATAL: Internal error: assertion failed: append.c: 368:
> stage != NULL && stage->parts[0] != '\0'
>
> Re
On Wed, May 24, 2017, at 04:17 PM, Don Lewis wrote:
> This first version of the patch worked for me. A problem with
>
> the second version of the patch is that mlookup() gets called in
>
> a bunch of different places and the server variable would need
>
> to be initialized in all of them. In v
On Wed, May 24, 2017, at 05:57 PM, Don Lewis wrote:
> On 24 May, ellie timoney wrote:
> > On Wed, May 24, 2017, at 04:17 PM, Don Lewis wrote:
> >> This first version of the patch worked for me. A problem with
> >>
> >> the second version of the pa
Thanks, a similar commit already existed on the 3.0 and master branches.
I've renamed "struct sched_param" on 2.5 to "struct caldav_sched_param"
for consistency:
https://github.com/cyrusimap/cyrus-imapd/commit/e26a822ed6e20f4d5a1fd7c89f2c3b4db80d5647
Cheers,
ellie
On Thu, Jun 1, 2017, at 12:20
Hi Stephan,
Did you mean this link?
https://lists.gnu.org/archive/html/bug-libtool/2016-06/msg1.html
The ltmain.sh file in the release tarballs is generated by libtool --
it's not a file we maintain manually. Looks like there's a bug in some
version of libtool that makes it generate the bad
I've cherry-picked this commit to the 3.0 branch, so it will be included
in the next 3.0 release
On Fri, Aug 4, 2017, at 04:27 AM, Ken Murchison wrote:
> We shouldn't be requiring PCRE in order for LIST to work. This bug is
> fixed in Git:>
> https://github.com/cyrusimap/cyrus-imapd/commit/fa6ff
team,
Kind regards,
ellie timoney
Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
To Unsubscribe:
https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus
Hi :)
We've been talking about how we manage Cyrus releases, and the
increasing gulf between the 3.0 series and the master branch --
accompanied by vague second-hand memories of the 2.4->2.5->3.0
transitions...
As of now, we're switching to an odd-even release cycle.
The 3.0.x series will contin
://cyrusimap.org/imap/download/release-notes/2.4/x/2.4.20.html
And join us at https://github.com/cyrusimap/ to report issues, join in
the deliberations of new features for the next Cyrus IMAP release, and
to contribute to the documentation.
On behalf of the Cyrus team,
Ellie Timoney
Cyrus Home Page: http
what exactly is the problem you experience when the maxchild value is
reached? what do you mean by "overtime"?
cyrus imapd processes are designed to be long-lived, and to serve
multiple clients before exiting. if your imap client users are few
and their connections are long lived, then i would ex
This is now merged, and will be in the next Cyrus release. Thanks all!
Cheers,
ellie
On Fri, Nov 3, 2017, at 11:18 AM, Bron Gondwana wrote:
> I have created https://github.com/cyrusimap/cyrus-imapd/issues/2191 to
> track this. Thanks for the patch!>
> Cheers,
>
> Bron.
>
>
> On Fri, 3 Nov
> - Reconstruct the databases using *reconstruct -rf user/** (got no
>output from this);
What's your value for the "unixhierarchysep" setting in imapd.conf? If
it's not there, or is 0, then I think you will need to use a dot, not a
slash, in your reconstruct argument: "reconstruct -rf user.*"
report
issues, join in the deliberations of new features for the next Cyrus IMAP
release, and to contribute to the documentation.
On behalf of the Cyrus team,
Kind regards,
ellie timoney
Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info
Hi Hiago,
Nice sleuthing, I'm glad you figured it out!
Have you seen/read the following (legacy) document?
https://www.cyrusimap.org/docs/cyrus-imapd/2.5.10/install-virtdomains.php
It should also be present in your local installation somewhere (look for
"install-virtdomains.html" or similar, thou
Hi all :)
We've decided to remove the experimental JMAP support from the stable Cyrus
IMAPd 3.0.x series. This is a minimally-invasive change, which won't affect
other aspects of the software.
The motivation for this is the rapid evolution of the JMAP specification as it
moves toward formal s
(re-sending this for the list, because I sent from the wrong address and it got
eaten, doh!)
On Thu, Feb 15, 2018, at 1:32 PM, ellie timoney wrote:
> The change in the install directories for binaries occurred at the start
> of the 3.0 series, and is documented in the 3.0.0 release
Hi,
Does the "sievec" compiler report any errors if you try to compile your sieve
scripts by hand?
Its manpage is here:
https://www.cyrusimap.org/imap/reference/manpages/systemcommands/sievec.html
Cheers,
ellie
On Thu, Feb 15, 2018, at 5:28 AM, rfk wrote:
> Hello,
>
> recently I updated my
On Fri, Feb 16, 2018, at 4:02 AM, Lists Nethead wrote:
> Some more observations,
>
> - When placed in START section, "squatter cmd="squatter -R -n
> squatter", the process does the log and then just vanishes and does
> nothing more while the "squatter" log just grows.
Hmm. I suspect the -R a
On Mon, Feb 19, 2018, at 11:38 AM, ellie timoney wrote:
> Hmm. I suspect the -R and -n options are mutually exclusive. -n is a
> one-shot run of the named channel (as you see); -R is the rolling mode
> (with no way to specify the channel). And it looks like, as you've
> d
Hi,
> cyrus-imad 2.6
Is this a typo? There is no cyrus-imapd 2.6. I'm going to carry on
assuming you meant "2.5", but please advise if otherwise.
> I tried to set up a shared mailbox using a howto found here:
> http://wiki.linuxwall.info/doku.php/en:ressources:dossiers:cyrus:shared_mailbox
That
Hi,
> [4:11pm] hagedose: user.testuser-clotho1.diesisteintest 16 (null)
This sounds like it's the tombstone entry for the deleted mailbox (i.e. a
record that there used to be a mailbox with that name). I believe tombstones
are relatively new, in which case the master server might not hav
Hi Gabriele,
Which version have you upgraded from? (I'm not sure if this makes a
difference, but it might)
The annotation you're using looks correct to me. Do the users have the
's' ACL permission on the mailboxes?
Cheers,
ellie
On Wed, Mar 7, 2018, at 2:14 AM, Gabriele Bulfon wrote:
> Hi,
>
everyone has ACLs with "all"
> flags, including 's'.>
>
> *Sonicle S.r.l. *: http://www.sonicle.com[1]
> *Music: *http://www.gabrielebulfon.com[2]
> *Quantum Mechanics : *http://www.cdbaby.com/cd/gabrielebulfon
>
>
>
> *Da:* ellie timoney *A:*
Hi John,
This was already fixed in 2.5.0 and later [1], but a lot changed to enable it,
so that fix was too invasive to backport.
Your patch looks like a good solution for 2.4! It's now on the cyrus-imapd-2.4
branch :)
Cheers,
ellie
[1]
https://github.com/cyrusimap/cyrus-imapd/commit/f0a
I believe it's an integer bitmask of the OPT_* values that are defined in
imap/mailbox.h in the source.
The sparse documentation suggests it's for developer, rather than normal
administrator use, maybe for rigging up tests? It's included in the imapd.conf
man page because that man page is auto
Thanks for the report, will pass this along to the maintainer of the FTP server
and see what's up.
In the meantime, Cyrus downloads are also available over HTTPS, here:
https://www.cyrusimap.org/releases/
I've also CC'd this to the info-cyrus mailing list for others' info.
Cheers,
ellie
On Su
On Sun, Apr 15, 2018, at 9:53 AM, David J. Weller-Fahy wrote:
> It may be useful to include a reference to those locations, but
> I'll find an email address for the website to send that recommendation.
This mailing list is the right spot for that, thanks. You're right, the
download page should
On Thu, Apr 19, 2018, at 2:53 AM, Jason L Tibbitts III wrote:
> > "JD" == Jean-Christophe Delaye
> > writes:
>
> JD> Is Libical 3.0.0 supported with 3.0.5 ? Any idea ?
>
> It is not, but you can apply
> https://github.com/cyrusimap/cyrus-imapd/commit/1966c22fc4249a1157a4d4c1224138ce786
release, and to contribute to the documentation.
On behalf of the Cyrus team,
Kind regards,
ellie timoney
Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
To Unsubscribe:
https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus
Hi Chen,
> So, the question : is it possible to set specific ACLs on autocreated
> folders ? (i.e., ACLs, different from those defined by defaultacl in
> imapd.conf).
I believe the autocreate mechanism has no particular knowledge of ACLs all all.
It just uses the standard Cyrus policy for assi
administrative
>> user* (and access control is accomplished by controlling access to
>> the socket).>
> But it doesn't say anything about the "-a:*Preauthorize connections
> initiated on an internet socket*, instead of requiring LMTP AUTH."
> (https://www.cyrus
> Something like: autocreate_acl (multiple
> autocreate_acl entries could be specified)
That's roughly what I'd expect such a feature to look like (without
having thought about it in much depth). It seems like it would be very
useful for admins who don't already have their own provisioning
i
, join in the deliberations of new features for the next Cyrus IMAP
release, and to contribute to the documentation.
On behalf of the Cyrus team,
Kind regards,
ellie timoney
Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
To
Hi Albert,
The main logical difference between ordinary replication and the experimental
backup system in Cyrus 3.0 is that in a replicated system, the replica is a
copy of the account's current state (as of the last replication). The backup
system is a historical record, not just a current st
Hi Sven,
Are you able to provide a sample mailboxes.db entry (using cyr_dbtool as
Bron describes below) for a mailbox which is affected by this?
I'm trying to determine if the cause is bad data getting into the
database, or good data that's being misread for some reason. An example
would help a l
On Mon, Jun 4, 2018, at 7:23 PM, Jean-Christophe Delaye wrote:
> Note, if I choose login mech , it works !
I feel like I've seen something like this before. If I recall correctly, the
DIGEST-MD5 mech doesn't support proxy authentication, so if anything in your
stack has this enabled (possibly
Hi Edda,
Thanks for the patch! I've added your email below to the GitHub issue
for this: https://github.com/cyrusimap/cyrus-imapd/issues/2362
I'll review the patch and if it looks good, will include it in the next
3.0 release. I'll also forward-port it to master if necessary.
Let me know if you
ne - we can fix that later :)>
What are you seeing that I'm missing?
I can see that this bug was not just "other users", but any
common/solo list pattern with a hiersep in it, but this patch is
general enough to fix both.
> Best regards,
> Edda
>
> Am 05.06.18 um
Hi Jean-Christophe,
On Fri, Jun 15, 2018, at 5:49 PM, Jean-Christophe Delaye wrote:
> So this is why the first part of my
> question was to known if there are many running murder systems running
> on Solaris (11) and why I can't find specifics notes about
> compiling/installing Cyrus imapd on this
Hi Paul,
On Fri, Jun 15, 2018, at 6:26 PM, Paul van der Vlis wrote:
> So xlist is removed in 2.5, and the new implementation is not there?
> So no support in Cyrus 2.5.10.
So, there's a few parts being mixed up here.
* The RFC 6154 IMAP LIST Extension for Special-Use Mailboxes is supported in
2
Hi,
This sounds like a problem in the package you're using.
lock_nonblocking() is a macro defined in lib/cyr_lock.h, which just
calls lock_setlock(). If it's trying to resolve "lock_nonblocking" as a
symbol, that suggests something has gone awry in the build.
The locking method is chosen by co
Hi,
The "defaultdomain" is the domain that's assumed by Cyrus for users that
are uid only. Any other domain needs to be explicitly specified in the
user (this applies to login, delivery, etc). So, if you have:
defaultdomain: foo.com
then "user" and "u...@foo.com" are the same account (and
Hi Rudolf,
Have you checked the output from quota(8) to see if the quota database
contents look sensible?
What value do you have for the unixhierarchysep imapd.conf setting?
Cheers,
ellie
On Tue, Jul 10, 2018, at 11:30 PM, Rudolf Gabler wrote:
> Hi,
>
> On the stable release 3.0.7 (self-compil
On Tue, Jul 17, 2018, at 3:37 AM, Heiler Bemerguy wrote:
> Em 06/07/2018 00:10, ellie timoney escreveu:
>
>> Hi,
>>
>> The "defaultdomain" is the domain that's assumed by Cyrus for users
>> that are uid only. Any other domain needs to be explici
Starting with the obvious, but did the user you login to cyradm as have admin
privileges? Are they listed in "admins:" in your imapd.conf?
If you logged into cyradm as a regular user, you would only see mailboxes that
your user had been granted access to... ;)
On Tue, Jul 17, 2018, at 2:09 AM,
On Thu, Jul 19, 2018, at 12:27 AM, James B. Byrne via Info-cyrus wrote:
>
> On Mon, July 16, 2018 22:23, ellie timoney wrote:
> > Starting with the obvious, but did the user you login to cyradm as
> > have admin privileges? Are they listed in "admins:" in your
&g
Hi,
This was an lmtpd bug in earlier versions of 3.0. It was fixed in 3.0.6, and
this was noted in the release notes:
https://www.cyrusimap.org/imap/download/release-notes/3.0/x/3.0.6.html:
> Fixed Issue #2303: lmtpd(8) now looks for sieve scripts in the same
> directories as the rest of cyrus
Hi,
Which version of Cyrus are you using?
Cheers,
ellie
On Thu, Jul 19, 2018, at 12:31 AM, Hiago Prata wrote:
> Hi, many users have been complaining about their quota usage being
> displayed wrongly. When trying to solve that using *quota -f*, the
> command returned a System I/O Error due to th
ew features for the next Cyrus IMAP
release, and to contribute to the documentation.
On behalf of the Cyrus team,
Kind regards,
ellie timoney
Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
To Unsubscribe:
https://lists.andrew.
Hi Sergey,
On Thu, Sep 13, 2018, at 10:26 PM, Sergey wrote:
> Hello.
>
> I attempted to run unit tests and got error:
>
> Suite: command
> Test: run ...FAILED
> 1. cunit/unit.c:115 - CU_FAIL_FATAL("Code under test exited")
>
> This is result of wrong path to touch in my distro in cunit/c
Interesting, that sounds like the backend suite has some state that's not being
cleaned up/reinitialised properly between tests! Thanks for the report :)
I've raised this as https://github.com/cyrusimap/cyrus-imapd/issues/2526
On Sat, Sep 15, 2018, at 9:27 PM, Sergey wrote:
> On Monday 19 Octob
Does this patch help?
https://github.com/cyrusimap/cyrus-imapd/commit/1cd8e90305093970d5d5953138a2ef8a723ea96f
On Mon, Sep 17, 2018, at 1:21 PM, ellie timoney wrote:
> Interesting, that sounds like the backend suite has some state that's
> not being cleaned up/reinitialised prope
On Sat, Sep 29, 2018, at 8:59 AM, Paul van der Vlis wrote:
> Op 28-09-18 om 15:34 schreef Michael Menge:
> >
> > Quoting Paul van der Vlis :
> >
> >> Hello,
> >>
> >> I am using Cyrus-imapd from Debian stable (2.5.10-3), and starting up
> >> takes very long. I see processes starting, but no im
On Mon, Oct 1, 2018, at 12:32 PM, ellie timoney wrote:
> You could use the tls_sessions_db_path imapd.conf(5) option to put this
> database onto faster storage?
>
> > tls_sessions_db_path:
> > The absolute path to the TLS sessions db file. If not
&g
umentation.
On behalf of the Cyrus team,
Kind regards,
ellie timoney
Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
To Unsubscribe:
https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus
Hi Kristian,
The "A5" and "A7" are just the "tags" associated with the client's search
commands, they have no semantic value. The client prefixes each command with
some tag, and then the server uses the same tag in the response (so that you
can identify which response applies to which command)
Thanks Sergey, these have been corrected and should update automatically in the
next 15 minutes or so :)
On Sun, Nov 25, 2018, at 11:14 PM, Sergey wrote:
> On Tuesday 20 November 2018, Ken Murchison wrote:
>
> > I'm pleased to announce the release of the long-awaited SASL 2.1.27
> > which can be
> Would be fine if Bron, Ellie or someone at Fastmail could tell
> something about it to us :) :)
Cheeky! Thing is, at FM our production servers more or less track the
master branch, so we were running "3.0" from the moment 2.5 forked off,
and so our upgrade process only ever really needs to deal
Hi Binarus,
> Could anybody please shortly explain why? What exactly are the
> techniques and mechanisms cyradm's xfer uses to do its thing? I had been
> quite sure that it just uses the IMAP protocol, but there seems to be
> more to it ...
You're right, but missing a detail. The XFER command
Hi Binarus,
> Could anybody please tell me what I might do wrong here?
This kind of smells like maybe your system has two versions of perl installed
(or two versions of Term::ReadLine, or maybe even two versions of
Cyrus::IMAP::Shell), and they're getting in each other's way?
I'm having a quic
Hi Binarus,
Looks like the documentation for the authenticate() function is pretty
incomplete...
> Well, this man page "documents" the method by exactly one line
> (identically in two places):
>
> $client->authenticate;
>From my read of the documentation, this is enough. It will figure out o
ient
for a real ReadLine implementation. Sounds like we've found our bug!
I'll have a bit of a play with it and see if I can find/fix the discrepancy
between the interfaces :)
Cheers,
ellie
On Wed, Dec 19, 2018, at 5:00 AM, Binarus wrote:
> Dear ellie,
>
> On 17.12.2018
Hi Miguel,
On Sat, Jan 19, 2019, at 8:20 AM, Miguel Mucio Santos Moreira wrote:
> Hi folks!
>
> I've had a problem with some huge mailboxes, with a lot of folders and
> subfolders. Problably thousand of folders.> The access on these mailboxes is
> too slow, if you change from INBOX to
> another
Hi Michael,
On Wed, Jan 16, 2019, at 10:12 PM, Michael Menge wrote:
> Hi,
>
> because conversations db seems to be required for search indexes, I
> enabled this option
> on our production servers today and tried to rebuild the conversations
> db for all users with
>
> ctl_conversationsdb -v
1 - 100 of 241 matches
Mail list logo
