Transfer existing quotas to new cyrus imap service

We are transferring an existing cyrus-imapd 3.0.11 mailstore to another host also running cyrus-imapd 3.0.11. I cannot find any documentation on how one transfers user quotas. Can someone provide me with the link to the documentation or explain how it is done? Thanks, -- *** e-Mail

Cyrus-3.0 getting rid of old message files

What does one do to permanently remove from the file system old messages. In cyrus.conf I have this: postmastercmd="ipurge -X -f -d 8 user/postmaster/delivery" at=0420 delprune cmd="cyr_expire -D 180d -E 3d -X 180d" at=0400 cyradm info shows this: info {Server Wide} private:

Re: Purging old email files from Cyrus-IMAPD v.3.0.9 on FreeBSD-12.0

On Thu, May 16, 2019 11:00, Savvas Karagiannidis wrote: > Hi James, > the command that performs the actual removal of the files from the > file system is cyr_expire > > According to your cyrus.conf and the manual

ipurge seg fault and core dump

Cyrus Imapd 3.0.8 on FreeBSD-12.0p3 We are obtaining these error messages on a regular basis: Mar 25 04:20:00 inet17 kernel: pid 39793 (ipurge), uid 60: exited on signal 11 (core dumped) Mar 25 04:20:00 inet17 CYRUS/master[56223]: process type:EVENT name:postmaster

Re: Upgrade to cyrus-imapd and connection drops when searching mailboxes

On Fri, January 11, 2019 17:51, Michael Menge wrote: Thank you for your assistance. > > have you configured a search engine? and have you enabled the > conversation db. > Xapian and Squatter seam to require enabled conversation db to use the > search index. At least for squatter there is even a

Upgrade to cyrus-imapd and connection drops when searching mailboxes

cyrus-imapd30-3.0.8_2 Name : cyrus-imapd30 Version: 3.0.8_2 Installed on : Tue Jan 8 11:07:34 2019 EST Origin : mail/cyrus-imapd30 Architecture : FreeBSD:11:amd64 Prefix : /usr/local Categories : ipv6 mail Licenses : BSD4CLAUSE Maintainer :

Re: IMAPD-3.0.8 on FreeBSD-11.2 unindexed messages in inbox

On Fri, November 30, 2018 12:35, Patrick Boutilier wrote: > > > Most likely delayed expunge. Does this show 209? > > unexpunge -l user.realuserid |grep UID|wc -l > Yes it does. Thanks. -- *** e-Mail is NOT a SECURE channel *** Do NOT transmit sensitive data via

IMAPD-3.0.8 on FreeBSD-11.2 unindexed messages in inbox

While investigating a problem I encountered a(nother) situation that I do not understand. I entered a user's root mailbox using cd and did 'ls -l *\.'. There are 245 files with names like '999\.' in this directory. My understanding is that this would up as 245 messages in the user's INBOX

Re: tls-1.0 and cyrus-imaps-3.0.8

On Mon, November 26, 2018 10:28, Ken Murchison wrote: > I can't reproduce your issue and I don't see where the sslscan output > states that TLS1.0 is being advertised.  Can you actually connect > using TLS1.0 protocol? > No, we cannot. I will pass the results of our test to the powers thast

tls-1.0 and cyrus-imaps-3.0.8

We have this setting in imapd.conf: tls_versions: tls1_1 tls1_2 tls1_3 tls_prefer_server_ciphers: 1 tls_ciphers:HIGH:!aNULL:!MD5:!RC4 We have received notice that port 993 on our IMAP service supports TLS-1.0. When we run sslscan we get this result: # sslscan

TLSv1.0

We have been informed that our mail server may no longer employ TLSv1.0. Only TLSv1.1 and higher are now approved. I attempted to implement this with the following change to imapd.conf: tls_versions: tls1_2 tls1_3 However restarting imapd does not seem to eliminate TLSv1.0. #

IMAP-3.0.8 and Diffie-Hellman

I would like someone to explain to me how the diffie-hellman parameters are adjusted for cyrus-imap. Unlike Postfix, there does not seem to be a separate setting in imapd.conf for a DH parameter file. At least, I cannot find documentation respecting such a thing. The only information I have

Re: [SOLVED] Re: ipurge difficulties

On Wed, November 21, 2018 09:33, Javier Angulo wrote: > > > On 11/21/18 2:38 PM, James B. Byrne via Info-cyrus wrote: >> >> >> On Wed, November 21, 2018 03:25, Javier Angulo wrote: >>> >>> Probably you have to use a '.' instead of '^' >>&

[SOLVED] Re: ipurge difficulties

On Wed, November 21, 2018 03:25, Javier Angulo wrote: > > On 11/20/18 3:29 PM, James B. Byrne via Info-cyrus wrote: >> # sudo -u cyrus /usr/local/cyrus/sbin/ipurge -v -f -d 35 >> 'user/x/INBOX^Trash' >> # echo $? >> 0 >> >> What is happening here?

ipurge difficulties

Having recently switched our mail service over to IMAPv3 I have a nagging doubt that the ipurge commands in our cyrus.conf file are not working as I anticipate. For example, my Trash folder does not seem to have been emptied since the conversion: find '/var/spool/imap/x/user/x/INBOX^Trash' -mtime

Quotas

Cyrus-IMAPD-3.0.7 on FreeBSD-11.2p4 We have users who, having deleted email, evidently do not recover the quota allocated to those messages. We do not believe that we have enabled delayed deletion. All the user mailboxes previous had been upgraded using: sudo -u cyrus

[SOLVED] Cyrus IMAP-3.0.7 - listmailbox user/* does not report all mailboxes

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 > imapd.conf? > > If you logged into cyradm as a regular user, you would only see > mailboxes that your user had

Cyrus IMAP-3.0.7 - listmailbox user/* does not report all mailboxes

I We recently moved our imap service from CentOS and IMAP-2.11 to FreeBSD and IMAP 3.0.7. At the time we followed the upgrade path and at the same time updated our mailboxes to the latest version: sudo -u cyrus /usr/local/cyrus/sbin/reconstruct -f -r -G -V max user/* # Reconstruct and upgrade the

Re: IMAPD Missing quota root

On Wed, May 23, 2018 03:18, Michael Menge wrote: > Hi, > > > Quoting "James B. Byrne via Info-cyrus" > <info-cyrus@lists.andrew.cmu.edu>: > >> We have a problem with quota settings on a new v3.0.5 service. The >> mailboxes were transferred via rsync f

IMAPD Missing quota root

We have a problem with quota settings on a new v3.0.5 service. The mailboxes were transferred via rsync from oldserver:/var/spool/imap/ to newserver:/var/spool/imap The mailboxes.db was unloaded on the old server using mboxelist, transferred to the new server, and then loaded into an empty

Re: Moving from cIMAP-2.3.16 to 3.0.5

I have managed to move the 2.3.16 mailstore and mailboxes.db to the 3.0.5 host and reconstructed the mailboxes using 'reconstruct -f -r -G -V max user/*' Connections between squirrelmail and the new service appear to be working fine. However, I have a couple of glitches and I would like to know

Re: Moving from cIMAP-2.3.16 to 3.0.5

On Mon, May 14, 2018 10:18, Savvas Karagiannidis wrote: > Hi James, > note that you will probably fall into this bug on the new system: > https://github.com/cyrusimap/cyrus-imapd/issues/2208 > Try running "reconstruct -G -V max" on the new system before switching > to > it. This will upgrade the

Re: Moving from cIMAP-2.3.16 to 3.0.5

On Sat, May 12, 2018 19:47, Nic Bernstein wrote: > James, > Patrick is entirely correct.  As explained in the man page for > ctl_mboxlist(8) the "-f" flag is to specify an alternative input file > (mailbox database) not an output file.  Output is via standard out, > and > can redirected into

Moving from cIMAP-2.3.16 to 3.0.5

I have used rsync to move our entire maill store from the old server to the new. I now I wish to move the contents of mailboxes.db from the old to the new. I have tried: sudo -u cyrus /usr/lib/cyrus-imapd/ctl_mboxlist -d -f /var/spool/imap/mailboxes.db.txt on the old followed by a transfer of

Re: reconstruct problem

On Tue, May 1, 2018 14:44, Sebastian Hagedorn wrote: > 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

[SOLVED] Re: Cannot LOGIN using openssl s_client

On Fri, April 27, 2018 09:56, James B. Byrne wrote: > > openssl s_client \ > -connect imap.hamilton.harte-lyne.ca:993 \ > -CApath /usr/local/etc/pki/tls/certs > > Resulting in: > . . . > Start Time: 1524836386 > Timeout : 300 (sec) > Verify return code: 19 (self signed

Cannot LOGIN using openssl s_client

OS : CentOS-6.9 Name: cyrus-imapd Arch: x86_64 Version : 2.3.16 Release : 15.el6 We have a working Apache-2.2 /Squirrelmail-1.42 (SM) / Cyrus-IMAP-2.3 (CI) setup. SM and CI reside on different hosts. We use TLS over port 993 to communicate. The login mechanism

IMAP-3.0.4

Using imapsync we are attempting to move our mail store from an Cyrus-IMAPd-2.3.16 running under CentOS-6.9 to a Cyrus-IMAPD-3.0.4 running under FreeBSD-11.1p6. In all instances we are using software as packaged by the respective distribution. On our existing system our user mailboxes are