Re: Cyrus IMAP 3.2.2 (Re: cyrus imap 2.5.5 build in Linux: problem with pcre)

Hi Sergey, Quoting out of order, because it's a bit easier to explain that way: > And there is another problem that is not obvious. -lpcreposix is needed > in perl/imap/Makefile.PL and in perl/sieve/managesieve/Makefile.PL I seems. This bit sounds a lot like https://github.com/cyrusimap

Cyrus IMAP 3.2.2 (Re: cyrus imap 2.5.5 build in Linux: problem with pcre)

-I/usr/include/pcre Build is successful with CFLAGS="-I/usr/include/pcre" ./configure ... Except perl/imap: CFLAGS is not used by Makefile.PL. And there is another problem that is not obvious. -lpcreposix is needed in perl/imap/Makefile.PL and in perl/sieve/managesieve/Makefile.PL I see

Re: another problem with conversations db

est to add a check for the index version in ctl_conversationsdb I will monitor my log files if the IOERRORS will reappear, or if the wrong index version was the root of that problem too. @Bron Thanks for the help M.Menge

Re: another problem with conversations db

of the conversation_db worked fine after the Index was updated.. Do this did resolve the endless loop in ctl_conversationsdb. I would suggest to add a check for the index version in ctl_conversationsdb I will monitor my log files if the IOERRORS will reappear, or if the wrong index version

Re: another problem with conversations db

gt; lock dav archivecache > >> >> > > >> >> > Ooh, I haven't tested having cache and archivecache on the same > >> >> > location. That's really interesting. Again, I'd be in favour of > >> >> > separation here, give them

Re: another problem with conversations db

. That might be tricky >> > with ssd though, the way this is laid out. I assume you have some >> > kind of symlink farm going on? >> > >> >> I didn't know that there could be a problem with cache and archivecache. >> At the time we decided on the configura

Re: another problem with conversations db

hat would break anything. > >> > > >> > metapartition-ssd: /srv/cyrus-ssd-be/meta/ssd-part > >> > metapartition_files: header index cache expunge squat annotations > >> > lock dav archivecache > >> > > >> > Ooh,

Re: another problem with conversations db

ache on the same > location. That's really interesting. Again, I'd be in favour of > separation here, give them different paths. That might be tricky > with ssd though, the way this is laid out. I assume you have some > kind of symlink farm going on? > I didn't know that there

Re: another problem with conversations db

t; metapartition_files: header index cache expunge squat annotations > > lock dav archivecache > > > > Ooh, I haven't tested having cache and archivecache on the same > > location. That's really interesting. Again, I'd be in favour of > > separation here, give them

Re: another problem with conversations db

farm going on? I didn't know that there could be a problem with cache and archivecache. At the time we decided on the configuration for cyrus 3.0 I looked at the imapd.conf man page and for metapartition_files decided that I want all meta files on the ssd storage. There was no indication in th

Re: another problem with conversations db

-autocreate CFLAGS="-fPIC -g") > >> in a murder configuration on a RHEL 7.5 System. As filesystem we use xfs. > > > > They should be fine. I'll have a read of the config when I'm at a > > real computer. > > > > did you find anything in the co

Re: another problem with conversations db

em we use xfs. They should be fine. I'll have a read of the config when I'm at a real computer. did you find anything in the config that would explain the problems? > Bron. > > On Fri, Jan 25, 2019, at 04:08, Michael Menge wrote: >> Hi, >> >> I have discovered an o

Re: another problem with conversations db

Yes, updating reconstruct is on our roadmap. The biggest problem is that there are multiple file types across mailboxes and conversations and the changes can't be atomic, so if reconstruct discovers something partially done, it can't tell if the conversations were correct. The longer term

Re: another problem with conversations db

der configuration on a RHEL 7.5 System. As filesystem we use xfs. They should be fine. I'll have a read of the config when I'm at a real computer. > Bron. > > On Fri, Jan 25, 2019, at 04:08, Michael Menge wrote: >> Hi, >> >> I have discovered an other problem

Re: another problem with conversations db

uot;-fPIC -g") > in a murder configuration on a RHEL 7.5 System. As filesystem we use xfs. They should be fine. I'll have a read of the config when I'm at a real computer. > > > Bron. > > > > On Fri, Jan 25, 2019, at 04:08, Michael Menge wrote: > >> Hi, > >

Re: another problem with conversations db

ri, Jan 25, 2019, at 04:08, Michael Menge wrote: Hi, I have discovered an other problem with the conversations db: Thousends of lines with "IOERROR: conversations_audit on load:" and "IOERROR: conversations_audit on store:" A look at the source code shows that these errors are logg

another problem with conversations db

Hi, I have discovered an other problem with the conversations db: Thousends of lines with "IOERROR: conversations_audit on load:" and "IOERROR: conversations_audit on store:" A look at the source code shows that these errors are logged after "_sanity_check_counts&

Re: Big problem with replication

Le 16/01/2019 à 17:10:30+0100, Egoitz Aurrekoetxea a écrit > Good afternoon, > > > I would try doing it user by user (with -u). This way you would have all > synced > except the problematic mailbox. Hi, thanks for the help. I got some progress in my problem : >

Re: Big problem with replication

Good afternoon, I would try doing it user by user (with -u). This way you would have all synced except the problematic mailbox. Cheers! --- EGOITZ AURREKOETXEA Departamento de sistemas 944 209 470 Parque Tecnológico. Edificio 103 48170 Zamudio (Bizkaia) ego...@sarenet.es www.sarenet.es

Big problem with replication

Hi everyone. I've got some big issue with replication. I've master --- replica ---> slave_1 --- replica ---> slave_2 The replication between master and slave_1 work nice. Between slave_1 and slave_2 I've got some issue (log to big after network failure and work nagios_supervision).

Re: Problem with sync

Le 08/10/2018 à 10:36:10+0200, Albert Shih a écrit Hi everyone, > I still got my problem : > I got two level of synchro: > > master --- sync --> imap-mirror-1 --- sync --> imap-mirror-2 > > The first level work fine, the second level (imap-mirror-1 --> imap-mir

Problem with sync

Hi everyone, I got two level of synchro: master --- sync --> imap-mirror-1 --- sync --> imap-mirror-2 The first level work fine, the second level (imap-mirror-1 --> imap-mirror-2) crash sometime ago. Now I try to restart the sync, and currently I'm not sure it's working, in the

Re: cyradm problem

st.localdomain (via SSH) on my remote server or get a '*can't > connect to server*' (cyradm) reply. Not sure what you mean with "with ssh". What I do is log into the machine with ssh, and then: cyradm -u cyrus localhost testsaslauthd -u paul -p xx -f /var/spool/postfix/var/run/sasl

Re: cyrus imap 3.0.8 build in Linux: problem with unit test, test "badservice" failed

On Monday 17 September 2018, ellie timoney wrote: > Does this patch help? > https://github.com/cyrusimap/cyrus-imapd/commit/1cd8e90305093970d5d5953138a2ef8a723ea96f > No, the error remains. -- Regards, Sergey Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info:

Re: cyrus imap 3.0.8 build in Linux: problem with unit test, test "badservice" failed

error (threads.c:342: krb5int_key_register > > > ...) > > > with krb5-1.13 (I use 1.13.1) in Google. I attempted to rollback to krb5 > > > 1.12 > > > and test was passed. That is probably it is the problem of krb5. > > > > The problem remains with Cyrus-IM

Re: cyrus imap 3.0.8 build in Linux: problem with unit test, test "badservice" failed

19 October 2015, Sergey wrote: > > > I found messages with similag error (threads.c:342: krb5int_key_register > > ...) > > with krb5-1.13 (I use 1.13.1) in Google. I attempted to rollback to krb5 > > 1.12 > > and test was passed. That is probably it is the probl

Re: cyrus imap 3.0.8 build in Linux: problem with unit test, test "badservice" failed

On Monday 19 October 2015, Sergey wrote: > I found messages with similag error (threads.c:342: krb5int_key_register ...) > with krb5-1.13 (I use 1.13.1) in Google. I attempted to rollback to krb5 1.12 > and test was passed. That is probably it is the problem of krb5. The proble

cyradm problem

problem or misunderstanding of the stack at all but I am stuck finding the needle in the haystack. It's probably a SSH problem but I am not sure. Inside SSH I use a certificate-based authentication too with root-logins not allowed ('without password') Any help is very appreciated. Greets Gee

Cyrus 2.4 and vacation problem (smtputf8)

emailu zminene vyse. Dekuji. My domain use SPF (www.openspf.org) and DomainKeys/DKIM (with ADSP) policy and implementation of the DMARC. If you've problem with sending emails to me, start using email origin methods mentioned above. Thank you. Cyrus Home Page: http://www.cyrusimap.org/ List Archive

Re: reconstruct problem

Hello >> >> reconstruct doesn't process submailboxes even when using the -r >> option. No cyrus.* files are created in subfolders. >> What can I do? >> >> Thanks I have the same problem with Cyrus 3.0.5 reconstruct running on a FreeBSd-11.1 host. Even with th

Re: reconstruct problem

reconstruct only works when the cyrus files exist. You can just touch them prior to running reconstruct. > Am 01.05.2018 um 20:18 schrieb Dr. Harry Knitter > : > > Hello > > reconstruct doesn't process submailboxes even when using the -r option. > No cyrus.*

reconstruct problem

Hello reconstruct doesn't process submailboxes even when using the -r option. No cyrus.* files are created in subfolders. What can I do? Thanks Harry using cyrus 2.4 signature.asc Description: This is a digitally signed message part. Cyrus Home Page: http://www.cyrusimap.org/ List

Re: Problem after upgrading debian wheezy to jessie

Solution: 1. cyrus was not enabled via systemctl 2. Some symbolic links were not set: ln -s /usr/sbin/cyrus /usr/sbin/ctl_cyrusdb ln -s /usr/sbin/cyrus /usr/sbin/cyr_expire ln -s /usr/sbin/cyrus /usr/sbin/tls_prune WTF caused this? Greetings Harry Cyrus Home Page:

Re: Problem after upgrading debian wheezy to jessie

Am Samstag, 28. April 2018, 14:51:07 CEST schrieb Dan White: > On 04/28/18 20:43 +0200, Dr. Harry Knitter wrote: > >after upgrading debian wheezy to jessie a socket has gone: > >/var/run/cyrus/socket/lmtp > > > >How to get out of this problem? > > The lmtp unix d

Re: Problem after upgrading debian wheezy to jessie

Am Samstag, 28. April 2018, 14:51:07 CEST schrieb Dan White: > On 04/28/18 20:43 +0200, Dr. Harry Knitter wrote: > >after upgrading debian wheezy to jessie a socket has gone: > > > > > >How to get out of this problem? > > The lmtp unix domain socket is started

Re: Problem after upgrading debian wheezy to jessie

On 04/28/18 20:43 +0200, Dr. Harry Knitter wrote: after upgrading debian wheezy to jessie a socket has gone: /var/run/cyrus/socket/lmtp How to get out of this problem? The lmtp unix domain socket is started by master via its /etc/cyrus.conf config file, commonly in an entry called 'lmtpunix

Problem after upgrading debian wheezy to jessie

Hello folks, after upgrading debian wheezy to jessie a socket has gone: /var/run/cyrus/socket/lmtp How to get out of this problem? Thanks Harry signature.asc Description: This is a digitally signed message part. Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http

rsync problem backing up cyrus-imap emails

Title: Untitled Document Hello list. I send the following some years ago and still facing same problem again: I use rsync to backup cyrus mail dirs using the following command: rsync -vaR --delete --log-file=/var/log/rsync /var/lib/imap /var/spool/imap/ /mnt/backup The destination

Problem after update (deliver not working anymore)

Hi, I updated our cyrus server (SuSE SLES 12) to the latest release. First tests did not show any problem. But now I noticed the following: Oct 24 11:48:44 mail postfix/local[3438]: 0F6604A6F0: to=<x...@bgc-jena.mpg.de>, relay=local, delay=0.03, delays=0.01/0/0/0.01, dsn=4.3.0,

Re: odd problem with cyradm

nd bin/quota with and without -f all report correct values for quota. Only thing that does not work is cyradm for reading qoutas, "set quota" works. I think I'm giving up on this one for now because it is not a problem really production-wise. Thanks, > > El 21/8/17 a las 8:42,

Re: odd problem with cyradm

: Hi all, Wonder if someone can offer help. Host is FreeBSD 11.0-STABLE #0 r316644M and cyrus 2.5.11 in a jail. If I run cyradm as user cyrus (admin) and issue the lq command, usually there is a proper response at first, but subsequent commands fail. This could very well be a FreeBSD problem but I

Re: odd problem with cyradm

command, usually there is a proper response at first, but subsequent commands fail. This could very well be a FreeBSD problem but I thought I'll ask here first. 1st: read(0,"lq user/\n",8192) = 15 (0xf) write(3,"8 GETQUOTA user/\r\n",24) = 24 (0x18) select

odd problem with cyradm

Hi all, Wonder if someone can offer help. Host is FreeBSD 11.0-STABLE #0 r316644M and cyrus 2.5.11 in a jail. If I run cyradm as user cyrus (admin) and issue the lq command, usually there is a proper response at first, but subsequent commands fail. This could very well be a FreeBSD problem but I

Re: Asterisk problem in Sieve Script

Hello, with the, there is not any match ... '.*' would be a regular expression matching anything, but sieve filter language doesn't support regular expressions, or does it? I did a workaround on the other side, I did a reverse DNS lookup, and most times there is a DNS name instead of an IP

Re: Asterisk problem in Sieve Script

Try: elsif header :matches "subject" "[proxy] File-URL (.*) detected" On 5/16/2017 9:53 AM, Walter H. via Info-cyrus wrote: > Hello, > > I've got the following in the sieve script > > elsif header :matches "subject" "[proxy] File-URL (*) detected" > { > fileinto "INBOX._Info.ftpFileURLs";

Asterisk problem in Sieve Script

Hello, I've got the following in the sieve script elsif header :matches "subject" "[proxy] File-URL (*) detected" { fileinto "INBOX._Info.ftpFileURLs"; } else { fileinto "INBOX._Info"; } when the subject is e.g. [proxy] File-URL (Media-PC) detected then the if is true, this correct

Problem moving mailboxes

Hello, I need to move some mailboxes to a new partition. I'm following procedure given here https://lists.andrew.cmu.edu/pipermail/info-cyrus/2006-October/024096.html But when I issue the renamemailbox command i cyradm I get the following error: "renamemailbox: Server(s) unavailable to complete

Re: strange sieve problem

Hello, Oh, didn't change waldinet.local to my.local I found out why I had problems, the 2nd worked, the first not ... in /var/lib/imap/sieve there I had 2 folders: global and w/walter and both contained a sieve script, the one under w/walter was older and didn't handle the 2nd mail, and I

Re: strange sieve problem

Is it the second email sample that does not work? If so the To: on that one is walter@waldinet.local and I don't see any rules for walter@waldinet.local. Also, where does the mail that doesn't work end up? On 04/04/2017 03:00 AM, Walter H. via Info-cyrus wrote: Hello, I've found a Sieve

Re: strange sieve problem

On Tue, April 4, 2017 08:42, ellie timoney wrote: >> 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

Re: strange sieve problem

> 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

strange sieve problem

Hello, I've found a Sieve Tester, where everything works as I expect https://www.fastmail.com/cgi-bin/sievetest.pl but Cyrus Sieve doesn't here the Sieve-Script # Sieve filter require ["fileinto", "relational"]; if not exists ["from"] { discard; } elsif allof (address :all :is

Re: mailboxes.db locking problem after updating from 2.4 to 2.5.9

On 18/11/16 01:07, Bron Gondwana via Info-cyrus wrote: > On Fri, 18 Nov 2016, at 10:51, Wolfgang Breyha via Info-cyrus wrote: >> I already filed a bug https://github.com/cyrusimap/cyrus-imapd/issues/43 >> but no response so far. I directly asked Bron, but no response as well. > > Sorry, I really

Re: mailboxes.db locking problem after updating from 2.4 to 2.5.9

On Fri, 18 Nov 2016, at 10:51, Wolfgang Breyha via Info-cyrus wrote: > On 17/11/16 14:00, Deniss via Info-cyrus wrote: > > Any ideas or suggestion for investigation ? > > I already filed a bug > https://github.com/cyrusimap/cyrus-imapd/issues/43 > but no response so far. I directly asked Bron,

Re: mailboxes.db locking problem after updating from 2.4 to 2.5.9

On 17/11/16 14:00, Deniss via Info-cyrus wrote: > Hello, > > I trying to migrate one big cyrus imap server from 2.4 to 2.5.9. > > I updated binaries, fix db backend in imapd.conf and converted > mailboxes.db with ctl_mboxlist -d & -u to twoskip. > > cyrus ran fine until morning when a count of

Re: mailboxes.db locking problem after updating from 2.4 to 2.5.9

Did you run reconstruct like the upgrade documentation recommends? When I did my upgrade, from 2.4.x to 2.5 that's about all I had to do. I don't recall having to run ctl_mboxlist -du https://www.cyrusimap.org/docs/cyrus-imapd/2.5.0/install-upgrade.php

mailboxes.db locking problem after updating from 2.4 to 2.5.9

Hello, I trying to migrate one big cyrus imap server from 2.4 to 2.5.9. I updated binaries, fix db backend in imapd.conf and converted mailboxes.db with ctl_mboxlist -d & -u to twoskip. cyrus ran fine until morning when a count of simultanious sessions started to rise. then imapd processes

Re: Performance problem

On Fri, Aug 05, 2016 at 11:11:33AM -0400, Eric W. Bates via Info-cyrus wrote: > We are migrating our cyrus from a venerable computer to a new one. > > We've been gradually moving individuals over to the new machine and are > quite surprised at the poor performance characteristics we're seeing on

Performance problem

We are migrating our cyrus from a venerable computer to a new one. We've been gradually moving individuals over to the new machine and are quite surprised at the poor performance characteristics we're seeing on the new machine. The new machine: 2 @ 6 core Xeon E5-2640 256 Gb memory zfs built

Re: Problem moving between folders during 2.3.16 -> 2.5.9 upgrade

n reads it straight > > back in to ensure freshness -- and then having done so, appears to do an > > unconditional check against record->cache_crc (dodgy?) > > > > Actually that seems like all the spots this check happens -- so the fix > > might be as simple a

Re: Problem moving between folders during 2.3.16 -> 2.5.9 upgrade

t seems like all the spots this check happens -- so the fix > might be as simple as the attached patch? > > Kenneth, are you able to try this out? > > Cheers, > > ellie > Hi Ellie, That fixes the problem. Thank you so much for the quick response. Regards, Ken Cyr

Re: Problem moving between folders during 2.3.16 -> 2.5.9 upgrade

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 > > >1469384362>a0080 NO Mailbox format corruption detected > >

Re: Problem moving between folders during 2.3.16 -> 2.5.9 upgrade

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

Re: Problem moving between folders during 2.3.16 -> 2.5.9 upgrade

Thanks for reporting this. Ellie, if you get a chance can you look at it? I'm in the middle of the the FastMail security rollout right now, so I can't do anything today. Bron. On Mon, Jul 25, 2016, at 11:45, Kenneth Marshall wrote: > Hi, > > I accidentally hijacked another thread. So here

Problem moving between folders during 2.3.16 -> 2.5.9 upgrade

Hi, I accidentally hijacked another thread. So here is a new message. I am testing a Cyrus IMAP 2.3.16 to 2.5.9 upgrade and I am having problems moving messages between folders before the 'reconstruct -V max' has been run on the mailboxes. Here is the error from the IMAP client:

Problem setting up cyrus imapd server

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi, I am trying to setup a cyrus on CentOS 7 systems with a cyrus murder backend. Unfortunately I fail quite early while setting up the cyrus. The Problem ist that a cyrus murder setup with an cyrus-imapd newer than 2.4.17 seems to have

Re: 2.4.18, problem with reconstruct

h" subdirectory without any files (manualy created from backup). Reconstruct works if I put any of files cyrus.* to this subdirectory. At the same time there was the opposite problem: I can not delete existing directory, reconstruct restores it. Is this is a bug or require any other setting

2.4.18, problem with reconstruct

created from backup). Reconstruct works if I put any of files cyrus.* to this subdirectory. At the same time there was the opposite problem: I can not delete existing directory, reconstruct restores it. Is this is a bug or require any other settings to run reconstruct ? -- Regards, Sergey C

Re: 2.4.18, problem with reconstruct

On Friday 05 February 2016, Andrew Morgan wrote: > > Is this is a bug or require any other settings to run reconstruct ? > > I usually use these steps to add a new folder using reconstruct: > >touch cyrus.header >chown cyrus:mail cyrus.header >reconstruct -f -r user. > > So, I

Re: Seen problem after xfer command

Hi everybody, SERPRO (It's an IT services corporation of Brazilian Federal Government) has discovered what was going on about my xfer problem, they had the same situation in their environment. We've suppressed the Server Information turning the serverinfo parameter off and this was causing

Re: Replication problem do_folders(): failed to rename

Am Montag, den 14.12.2015, 07:31 -0400 schrieb Patrick Boutilier via Info-cyrus: > On 12/14/2015 06:25 AM, Marcus Schopen via Info-cyrus wrote: > > Am Freitag, den 11.12.2015, 19:10 +0100 schrieb Marcus Schopen via > > Info-cyrus: > >> Hi, > >> > >&

Re: Replication problem do_folders(): failed to rename

Hi, Quoting Patrick Boutilier via Info-cyrus <info-cyrus@lists.andrew.cmu.edu>: On 12/14/2015 06:25 AM, Marcus Schopen via Info-cyrus wrote: Am Freitag, den 11.12.2015, 19:10 +0100 schrieb Marcus Schopen via Info-cyrus: Hi, I have a problem with a single mailbox. The user's Outlook c

Re: Replication problem do_folders(): failed to rename

den 11.12.2015, 19:10 +0100 schrieb Marcus Schopen via > >> Info-cyrus: > >>> Hi, > >>> > >>> I have a problem with a single mailbox. The user's Outlook crashed and > >>> since then the sync_client is running wild on this user account and >

Re: Replication problem do_folders(): failed to rename

On 12/14/2015 06:25 AM, Marcus Schopen via Info-cyrus wrote: Am Freitag, den 11.12.2015, 19:10 +0100 schrieb Marcus Schopen via Info-cyrus: Hi, I have a problem with a single mailbox. The user's Outlook crashed and since then the sync_client is running wild on this user account and produces

Re: Replication problem do_folders(): failed to rename

Am Freitag, den 11.12.2015, 19:10 +0100 schrieb Marcus Schopen via Info-cyrus: > Hi, > > I have a problem with a single mailbox. The user's Outlook crashed and > since then the sync_client is running wild on this user account and > produces high load on the master. I stopped sync_c

Re: Replication problem do_folders(): failed to rename

Hi, forgot the cyrus version: 2.4.12 on Ubuntu 12.04 LTS Ciao! 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

Replication problem do_folders(): failed to rename

Hi, I have a problem with a single mailbox. The user's Outlook crashed and since then the sync_client is running wild on this user account and produces high load on the master. I stopped sync_client on master side for the moment. When I try to sync the user by hand /bin/su - cyrus -c "/us

2.5.x startup problem with mupadatepush enabled

d on 2.4.x for more than a decade, we are planning to migrate our mail system to 2.5.x. Frontends and Muder itself don't have this problem, the cyrus service starts and works properly after system reboots. Is anyone else facing such issues? Backend cyrus.conf: START { auth cmd="/u

Re: cyrus imap 2.5.5 build in Linux: problem with pcre

On Monday 19 October 2015, ellie timoney wrote: > Do you have pkg-config installed on your system? $ pkg-config --version 0.25 > Does your pcre library support utf8? I think yes: configure call in pcre.spec contains "--enable-pcre8 --enable-pcre16 --enable-utf" options. > Do you have a

Re: cyrus imap 2.5.5 build in Linux: problem with unit test, test "badservice" failed

t was passed. That is probably it is the problem of krb5. -- Regards, Sergey 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

Re: cyrus imap 2.5.5 build in Linux: problem with pcre

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

Re: cyrus imap 2.5.5 build in Linux: problem with unit test, test "badservice" failed

> 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

cyrus imap 2.5.5 build in Linux: problem with pcre

Hello. I built and run version 2.5.5 but I have some questions about build process. I will ask this in some different messages. I wanted to build Cyrus-IMAP with libpcre but it did not success. System libpcre-devel package install headers to /usr/include/pcre. I tried to replace pcreposix.h in

cyrus imap 2.5.5 build in Linux: problem with unit test, test "badservice" failed

Hello. I found what Cyrus IMAP contains unit tests now. I try it but test failed: Test: setentryatt ...passed Test: clearentryatt ...passed Suite: backend Test: badhost ...passed Test: badservice ...lt-unit: threads.c:342: krb5int_key_register: Assertion `destructors_set[keynum] == 0'

Seen problem after transfering a mailbox

Hello everybody, I have a weird trouble in my cyrus murder environment. After I move a mailbox between backend servers, for each non empty folder which has all email as read, it put the most recent email as unread. It seems a seen problem but I wasn't able to find out the reason

Sieve, a problem with if/elsif/else

Hello. I have a strange problem. I use a filter if address :contains ["To"] ["bounceerror@"] { ifaddress :contains ["From"] ["MAILER-DAEMON@srv1.domain"] { fileinto "INBOX/BounceError/srv1"; } elsif address :contains [&quo

Re: Sieve, a problem with if/elsif/else

On Mon, August 31, 2015 9:22 am, Sergey wrote: > Hello. > > > I have a strange problem. I use a filter > > > if address :contains ["To"] ["bounceerror@"] { ifaddress :contains > ["From"] ["MAILER-DAEMON@srv1.domain"] { > fi

Re: Sieve, a problem with if/elsif/else

On Monday 31 August 2015, Eric Luyten wrote: > > else { fileinto "INBOX/BounceError"; } > > } > > Why "else fileinto" doesn't work ? Discovered in 2.4.17, > > reproduced in 2.4.18. > Did you define "INBOX/BounceError" as a mailbox ? > This is not implied by the fact that it is a hierarchy. >

Seen problem after xfer command

Hi everybody, I've had a weird trouble in my cyrus murder environment. After I move a mailbox between the backend servers, for each non empty folder which has all email as read, it put the most recent email as unread. It seems a seen problem but I wasn't able to find out the reason. Have anyone

Re: Murder frontend problem

On 06/05/2015 07:42 PM, Andrew Morgan wrote: On Fri, 5 Jun 2015, Major Csaba wrote: There is one more small question: why the proxied LMTP needs to have admins permission on the backend? I thought the proxyservers setting is for this, but LMTP doesn't work without adding my proxy user in

Murder frontend problem

Hi, I'm rying to build a cyrus server with murder frontend/backend. The topology is quiet simple at the moment: there is one frontend + mupdate master, and there is one backend server. (Cyrus version: 2.4.17) Almost everything is working fine: * The backend populates the folder changes to

Re: Murder frontend problem

a bug. Although the following options may affect the problem: altnamespace unixhierarchysep defaultdomain defaultserver hashimapspool improved_mboxlist_sort proxyd_disable_mailbox_referrals sharedprefix virtdomains I don't recommend changing any of these on a production system however. See

Re: Murder frontend problem

On Fri, 5 Jun 2015, Major Csaba wrote: There is one more small question: why the proxied LMTP needs to have admins permission on the backend? I thought the proxyservers setting is for this, but LMTP doesn't work without adding my proxy user in the admins... Play around with lmtp_admins in

Re: Murder frontend problem

On 06/05/15 16:44 +0200, Major Csaba wrote: Hi, Thanks for the quick answer. I managed to get further as I realized I missed a small piece from the documentation. My fronted server and master update server is on the same machine and I didn't configure the mupdate_* parameter. But as I can see,

Re: single instance message store problem.

On Saturday 30 May 2015 9:34:44 AM Michael Neumann wrote: Am 30.05.2015 um 13:43 schrieb John McMonagle: Michael Thanks that works. Now maps in /etc/aliases are not working. I have aliases in ldap that are working. Read http://www.postfix.org/LOCAL_RECIPIENT_README.html

Re: single instance message store problem.

transaction (MAIL FROM, RCPT TO, DATA sequence). If the recipients are sent one at a time with duplicate DATA commands, there are treated as distinct messages. That is the problem, postfix default local transport does only one at a time, that breaks single instance storage. We had

Re: single instance message store problem.

Am 30.05.2015 um 13:43 schrieb John McMonagle: Michael Thanks that works. Now maps in /etc/aliases are not working. I have aliases in ldap that are working. Read http://www.postfix.org/LOCAL_RECIPIENT_README.html Sounds like need local_recipient_maps. It already existed and has

Re: single instance message store problem.

(MAIL FROM, RCPT TO, DATA sequence). If the recipients are sent one at a time with duplicate DATA commands, there are treated as distinct messages. That is the problem, postfix default local transport does only one at a time, that breaks single instance storage. We had to redefine

Re: single instance message store problem.

, -nic No problem Yes I checked. -rw--- 1 cyrus mail 3919 May 29 10:35 145026. -rw--- 1 cyrus mail 87189663 May 29 12:34 cyrus.squat drwx-- 2 cyrus mail 204800 May 29 13:15 Sent -rw--- 1 cyrus mail 2116 May 29 13:15 145027. The 2 mails should

Re: single instance message store problem.

-07-09 14:53 17204. -rw--- 3 cyrus cyrus 44942 2013-07-09 14:56 17205. -rw--- 1 cyrus cyrus 1395 2013-07-09 15:00 17206. The 2nd, 4th 5th messages have multiple hard-links (second column), which is how singleinstancestore does its thing. Cheers, -nic No problem Yes I

  1   2   3   4   5   6   7   8   9   10   >