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 is NOT a SECURE channel *** Do NOT transmit sensitive data via e-Mail Do NOT open attachments nor follow links sent by e-Mail James B. Byrnemailto:byrn...@harte-lyne.ca Harte & Lyne Limited http://www.harte-lyne.ca 9 Brockley Drive vox: +1 905 561 1241 Hamilton, Ontario fax: +1 905 561 0757 Canada L8E 3C3 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
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:
admin: NIL
comment: NIL
expire: NIL
squat: NIL
usercounters: 0 0 0 0 0 0 0 0 0 0 0
usermodseq: 0
shared:
admin: NIL
comment: NIL
motd: NIL
expire: NIL
freespace: 68182048
most: 68182048;192015872
total: 68182048;192015872
shutdown: NIL
squat: NIL
When I go to the user mailbox
(/var/spool/imap/p/user/postmaster/delivery) I see messages from
December 2018 and earlier.
When I check the maillog I see this:
# grep cyr_expire /var/log/maillog | grep postmaster
Oct 9 05:46:14 inet17 CYRUS/cyr_expire[21667]: mailbox: longlock
user.postmaster.investigate for 2.3 seconds
Oct 9 05:46:16 inet17 CYRUS/cyr_expire[21667]: mailbox: longlock
user.postmaster.mailinglists for 1.2 seconds
Oct 9 05:46:19 inet17 CYRUS/cyr_expire[21667]: mailbox: longlock
user.postmaster.spamno for 1.3 seconds
What I do not see is anything being expunged for the postmaster.
cyr_expire is running as I see this in the maillog:
inet17 CYRUS/cyr_expire[21667]: Expired 0 and expunged 2055 out of
744420 messages from 2500 mailboxes
I want messages that are deleted and that are older than 180 days gone
from the file system entirely. I would like to know why is this not
happening? And, I would like to know how do I make it happen? What
setting or settings am I missing?
--
*** e-Mail is NOT a SECURE channel ***
Do NOT transmit sensitive data via e-Mail
Do NOT open attachments nor follow links sent by e-Mail
James B. Byrnemailto:byrn...@harte-lyne.ca
Harte & Lyne Limited http://www.harte-lyne.ca
9 Brockley Drive vox: +1 905 561 1241
Hamilton, Ontario fax: +1 905 561 0757
Canada L8E 3C3
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: 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 > <https://www.cyrusimap.org/imap/reference/manpages/systemcommands/cyr_expire.html> > According to your cyrus.conf and the manual of cyr_expire, the > operation is performed daily at 04:00. The command is executed > by the main cyrus process, so you don't have to do anything > else manually... > The parameters -D 180d and -X 180d specify that only mailboxes and > messages that are at least 180 days old will be deleted. > > When cyr_expire is executed you should see a line in your log file > like these: > Thanks. I have a question though. If expunge == purge then why does the documentation distinguish between them? When is What ... Deleted, Expired, Expunged or Purged? https://www.cyrusimap.org/imap/reference/faqs/o-deleted-expired-expunged-purged.html Expunged The message (which has been flagged as \Deleted) is also expunged, meaning that the user can in no way retrieve the message autonomously. Purged The messages index record may still exist (until they are expired), but the message file is removed from the filesystem, or in the context of folders, the mail folder is removed from the filesystem. This is what has me confused. Regards, -- *** e-Mail is NOT a SECURE channel *** Do NOT transmit sensitive data via e-Mail Do NOT open attachments nor follow links sent by e-Mail James B. Byrnemailto:byrn...@harte-lyne.ca Harte & Lyne Limited http://www.harte-lyne.ca 9 Brockley Drive vox: +1 905 561 1241 Hamilton, Ontario fax: +1 905 561 0757 Canada L8E 3C3 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
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 path:/usr/local/cyrus/sbin/ipurge age:0.092s pid:39793 signaled to death by signal 11 (Segmentation fault, core dumped) Mar 25 04:20:01 inet17 kernel: pid 39724 (ipurge), uid 60: exited on signal 11 (core dumped) Mar 25 04:20:01 inet17 CYRUS/master[56223]: process type:EVENT name:sysadmin path:/usr/local/cyrus/sbin/ipurge age:1.091s pid:39724 signaled to death by signal 11 (Segmentation fault, core dumped) Mar 25 04:20:02 inet17 kernel: pid 39619 (ipurge), uid 60: exited on signal 11 (core dumped) Mar 25 04:20:02 inet17 CYRUS/master[56223]: process type:EVENT name:sysadminroot path:/usr/local/cyrus/sbin/ipurge age:2.135s pid:39619 signaled to death by signal 11 (Segmentation fault, core dumped) Does anyone know what would cause this behaviour? -- *** e-Mail is NOT a SECURE channel *** Do NOT transmit sensitive data via e-Mail Do NOT open attachments nor follow links sent by e-Mail James B. Byrnemailto:byrn...@harte-lyne.ca Harte & Lyne Limited http://www.harte-lyne.ca 9 Brockley Drive vox: +1 905 561 1241 Hamilton, Ontario fax: +1 905 561 0757 Canada L8E 3C3 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: 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 performance > regression for TEXT search even if conversation db is enabled > (https://github.com/cyrusimap/cyrus-imapd/issues/2598) I do not believe that I have configured a search engine. > > >> Are the longlock reports and the imap connection drop related? >> > An cyrus processes tires to gain access to the mailbox while an > other process is still accessing it. If this takes to long the client > might disconnect. You can try telemetry logging to discover what is > happening. >> If imap drops a connection is the reason for that event logged? Can >> it be logged? >> > The question is which side drops the connection the cyrus-imapd > process or the imap client (squirrelmail)? tcpdum and telemetry > logging might reveal the answer. Squirrelmail reports that the IMAP server dropped the connection as part of the error message. In any case, even if it is the squrrelmail client that is dropping the connection one would expect that imap service could report this event. So the question remains, how does one log the cause of cyrus_imapd dropping a connection? As to the cause of the problem. It was an excessive load on the imap daemon from a persistent brute force attack. A recent reconfiguration and change of server host resulted in port 993 being opened to unrestricted public access. This attracted the usual assortment of script kiddies, security 'researchers' of various ilk, and so forth. Closing that port down immediately resolved the issue. Thanks for the suggestions. I will look into these now that the crisis has passed. Regards, -- *** e-Mail is NOT a SECURE channel *** Do NOT transmit sensitive data via e-Mail Do NOT open attachments nor follow links sent by e-Mail James B. Byrnemailto:byrn...@harte-lyne.ca Harte & Lyne Limited http://www.harte-lyne.ca 9 Brockley Drive vox: +1 905 561 1241 Hamilton, Ontario fax: +1 905 561 0757 Canada L8E 3C3 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
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 : u...@freebsd.org Since upgrading to this version from 3.0.8_1 on January 8 we have seen a considerable increase of messages in the maillog that look similar to this: CYRUS/lmtpunix[79768]: mailbox: longlock user.name.delivery for 1.4 seconds Where the number of seconds varies between 1.x and 11.x. When I say considerably I mean from between 10 and 30 per log rollover to over 800 today and it is not yet noon. Perhaps coincidently, users are reporting imap connections dropping when they are performing text searches on their mailboxes. The user mail client being squirrelmail. Are the longlock reports and the imap connection drop related? If imap drops a connection is the reason for that event logged? Can it be logged? -- *** e-Mail is NOT a SECURE channel *** Do NOT transmit sensitive data via e-Mail Do NOT open attachments nor follow links sent by e-Mail James B. Byrnemailto:byrn...@harte-lyne.ca Harte & Lyne Limited http://www.harte-lyne.ca 9 Brockley Drive vox: +1 905 561 1241 Hamilton, Ontario fax: +1 905 561 0757 Canada L8E 3C3 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: upgrade to cyrus_imap or saslauth or both gon horribly wrong
> FreeBSD-11.2p7 > cyrus-imapd30-3.0.8_2 > cyrus-sasl-saslauthd-2.1.27 > cyrus-sasl-2.1.27 > > This morning we upgraded our cyrus_imap server using the FreeBSD pkg package > manager. Following this we are unable to authenticate with imap. The error > we receive is this: > > Jan 8 14:05:37 inet17 CYRUS/imaps[40533]: SASL cannot connect to saslauthd > server: Permission denied > Jan 8 14:05:37 inet17 CYRUS/imaps[40533]: badlogin: servername [server > address] plaintext username SASL(-1): generic failure: checkpass failed > > imapd.conf was not changed. it contains this: > > sasl_mech_list: PLAIN > sasl_pwcheck_method:saslauthd > > > I am posting this from a temporary email because, duhh, I cannot access my > regular mailbox. > > I am open to any reasonable suggestions as to how to fix this, quickly. However, if I do this then I get a success. read -ers -p 'prompt: ' PASSWD ; echo -e '\n' prompt: read -ers -p 'prompt: ' USERNAME ; echo -e '\n' prompt: testsaslauthd -u $USERNAME -p $PASSWD 0: OK "Success." Does anyone here know what is going on or how to fix it? 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
upgrade to cyrus_imap or saslauth or both gon horribly wrong
FreeBSD-11.2p7 cyrus-imapd30-3.0.8_2 cyrus-sasl-saslauthd-2.1.27 cyrus-sasl-2.1.27 This morning we upgraded our cyrus_imap server using the FreeBSD pkg package manager. Following this we are unable to authenticate with imap. The error we receive is this: Jan 8 14:05:37 inet17 CYRUS/imaps[40533]: SASL cannot connect to saslauthd server: Permission denied Jan 8 14:05:37 inet17 CYRUS/imaps[40533]: badlogin: servername [server address] plaintext username SASL(-1): generic failure: checkpass failed imapd.conf was not changed. it contains this: sasl_mech_list: PLAIN sasl_pwcheck_method:saslauthd I am posting this from a temporary email because, duhh, I cannot access my regular mailbox. I am open to any reasonable suggestions as to how to fix this, quickly. 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: 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 e-Mail Do NOT open attachments nor follow links sent by e-Mail James B. Byrnemailto:byrn...@harte-lyne.ca Harte & Lyne Limited http://www.harte-lyne.ca 9 Brockley Drive vox: +1 905 561 1241 Hamilton, Ontario fax: +1 905 561 0757 Canada L8E 3C3 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
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 display. However, the user's INBOX only shows 36. There is is also a subfolder named 'INBOX^Trash' that is shown to contain 246 messages but which actually contains 14820. I am not familiar with IMAP3 and have only recently converted to it from imap2 running on a different host. It was during the conversion process that the existing .Trash/.Sent/.Drafts were replaced by INBOX^Trash/INBOX^Sent/INBOX^Drafts. So there may be something obvious that I do not know about. I speculate that this has something to do with the difference between delete and expunge but I would like to know for certain what is happening if someone would explain it to me. Thanks -- *** e-Mail is NOT a SECURE channel *** Do NOT transmit sensitive data via e-Mail Do NOT open attachments nor follow links sent by e-Mail James B. Byrnemailto:byrn...@harte-lyne.ca Harte & Lyne Limited http://www.harte-lyne.ca 9 Brockley Drive vox: +1 905 561 1241 Hamilton, Ontario fax: +1 905 561 0757 Canada L8E 3C3 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: 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 be and see what their reply is. Thank you, that was most helpful advice. -- *** e-Mail is NOT a SECURE channel *** Do NOT transmit sensitive data via e-Mail Do NOT open attachments nor follow links sent by e-Mail James B. Byrnemailto:byrn...@harte-lyne.ca Harte & Lyne Limited http://www.harte-lyne.ca 9 Brockley Drive vox: +1 905 561 1241 Hamilton, Ontario fax: +1 905 561 0757 Canada L8E 3C3 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
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 216.185.71.17:993 Version: 1.11.11 OpenSSL 1.0.2-chacha (1.0.2k-dev) Connected to 216.185.71.17 Testing SSL server 216.185.71.17 on port 993 using SNI name 216.185.71.17 TLS Fallback SCSV: Server supports TLS Fallback SCSV TLS renegotiation: Session renegotiation not supported TLS Compression: Compression disabled Heartbleed: TLS 1.2 not vulnerable to heartbleed TLS 1.1 not vulnerable to heartbleed TLS 1.0 not vulnerable to heartbleed Supported Server Cipher(s): Preferred TLSv1.2 256 bits ECDHE-RSA-AES256-GCM-SHA384 Curve P-256 DHE 256 Accepted TLSv1.2 256 bits ECDHE-RSA-AES256-SHA384 Curve P-256 DHE 256 Accepted TLSv1.2 256 bits ECDHE-RSA-AES256-SHA Curve P-256 DHE 256 Accepted TLSv1.2 256 bits DHE-RSA-AES256-GCM-SHA384 DHE 2048 bits Accepted TLSv1.2 256 bits DHE-RSA-AES256-SHA256 DHE 2048 bits Accepted TLSv1.2 256 bits DHE-RSA-AES256-SHADHE 2048 bits Accepted TLSv1.2 256 bits DHE-RSA-CAMELLIA256-SHA DHE 2048 bits Accepted TLSv1.2 256 bits AES256-GCM-SHA384 Accepted TLSv1.2 256 bits AES256-SHA256 Accepted TLSv1.2 256 bits AES256-SHA Accepted TLSv1.2 256 bits CAMELLIA256-SHA Accepted TLSv1.2 128 bits ECDHE-RSA-AES128-GCM-SHA256 Curve P-256 DHE 256 Accepted TLSv1.2 128 bits ECDHE-RSA-AES128-SHA256 Curve P-256 DHE 256 Accepted TLSv1.2 128 bits ECDHE-RSA-AES128-SHA Curve P-256 DHE 256 Accepted TLSv1.2 128 bits DHE-RSA-AES128-GCM-SHA256 DHE 2048 bits Accepted TLSv1.2 128 bits DHE-RSA-AES128-SHA256 DHE 2048 bits Accepted TLSv1.2 128 bits DHE-RSA-AES128-SHADHE 2048 bits Accepted TLSv1.2 128 bits DHE-RSA-CAMELLIA128-SHA DHE 2048 bits Accepted TLSv1.2 128 bits AES128-GCM-SHA256 Accepted TLSv1.2 128 bits AES128-SHA256 Accepted TLSv1.2 128 bits AES128-SHA Accepted TLSv1.2 128 bits CAMELLIA128-SHA Preferred TLSv1.1 256 bits ECDHE-RSA-AES256-SHA Curve P-256 DHE 256 Accepted TLSv1.1 256 bits DHE-RSA-AES256-SHADHE 2048 bits Accepted TLSv1.1 256 bits DHE-RSA-CAMELLIA256-SHA DHE 2048 bits Accepted TLSv1.1 256 bits AES256-SHA Accepted TLSv1.1 256 bits CAMELLIA256-SHA Accepted TLSv1.1 128 bits ECDHE-RSA-AES128-SHA Curve P-256 DHE 256 Accepted TLSv1.1 128 bits DHE-RSA-AES128-SHADHE 2048 bits Accepted TLSv1.1 128 bits DHE-RSA-CAMELLIA128-SHA DHE 2048 bits Accepted TLSv1.1 128 bits AES128-SHA Accepted TLSv1.1 128 bits CAMELLIA128-SHA SSL Certificate: Signature Algorithm: sha512WithRSAEncryption RSA Key Strength:4096 Subject: imap.harte-lyne.ca Yes, I realise that the ciphers we use are all TLS-1.1 and above. Nonetheless cyrus-imapd seems to be telling connections that TLS-1.0 is available and this is causing us a headache with PCI. How do we turn off tls-1.0 in cyrus-imapd-3.0.8? -- *** e-Mail is NOT a SECURE channel *** Do NOT transmit sensitive data via e-Mail Do NOT open attachments nor follow links sent by e-Mail James B. Byrnemailto:byrn...@harte-lyne.ca Harte & Lyne Limited http://www.harte-lyne.ca 9 Brockley Drive vox: +1 905 561 1241 Hamilton, Ontario fax: +1 905 561 0757 Canada L8E 3C3 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
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. # sslscan 216.185.71.17:993 Version: 1.11.11 OpenSSL 1.0.2-chacha (1.0.2k-dev) Connected to 216.185.71.17 Testing SSL server 216.185.71.17 on port 993 using SNI name 216.185.71.17 TLS Fallback SCSV: Server supports TLS Fallback SCSV TLS renegotiation: Session renegotiation not supported TLS Compression: Compression disabled Heartbleed: TLS 1.2 not vulnerable to heartbleed TLS 1.1 not vulnerable to heartbleed TLS 1.0 not vulnerable to heartbleed <<=== Supported Server Cipher(s): How do I eliminate TLSv1.0? -- *** e-Mail is NOT a SECURE channel *** Do NOT transmit sensitive data via e-Mail Do NOT open attachments nor follow links sent by e-Mail James B. Byrnemailto:byrn...@harte-lyne.ca Harte & Lyne Limited http://www.harte-lyne.ca 9 Brockley Drive vox: +1 905 561 1241 Hamilton, Ontario fax: +1 905 561 0757 Canada L8E 3C3 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
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 gleaned is that it may be necessary to append the DHParm file to the private key of the imap server. That seems to be a rather inelegant way of doings but, if that is the only way to do so then I need that confirmed. If not, then I would very much appreciate being told how else to accomplish it. -- *** e-Mail is NOT a SECURE channel *** Do NOT transmit sensitive data via e-Mail Do NOT open attachments nor follow links sent by e-Mail James B. Byrnemailto:byrn...@harte-lyne.ca Harte & Lyne Limited http://www.harte-lyne.ca 9 Brockley Drive vox: +1 905 561 1241 Hamilton, Ontario fax: +1 905 561 0757 Canada L8E 3C3 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: [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 '^' >>> >>> try: >>> # sudo -u cyrus /usr/local/cyrus/sbin/ipurge -v -f -d 35 >>> 'user/*/INBOX.Trash' >>> >> >> Thank you. That was it exactly. >> >> My next question is: Why did the conversion to imap3 ignore users' >> existing Trash folder and create a new folder named INBOX^Trash for >> everyone; and likewise with Drafts and Sent? >> > > > mmm we have upgraded quite a few mailboxes and never had that thing. > Just speculating but could be related to new defaults > > unixhierarchysep: on > altnamespace: on > > We had both on before upgrading. > We had previously used the '.' as the separator. Our current settings are: /usr/local/etc/imapd.conf:unixhierarchysep: true /usr/local/etc/imapd.conf:altnamespace: true Before the purge this mailbox folder was displayed in my webmail application (Squirrelmail) as INBOX^Trash, which is why I choose that construction for the ipurge command. However, following the successful purge run of ipurge INBOX.Trash the mailbox now displays as INBOX.Trash. What is equally curious is that there exists a folder simply named Trash, which was used as the trash folder by the previous version of IMAP and which was replaced by INBOX^Trash by some part of the upgrade process. It is certain that these changes (Trash -> INBOX^Trash, Sent -> INBOX^Sent, Drafts -> INBOX^Drafts) were not consciously made and they affected all users. And, yes, I did follow the published upgrade procedures to the best of my understanding. -- *** e-Mail is NOT a SECURE channel *** Do NOT transmit sensitive data via e-Mail Do NOT open attachments nor follow links sent by e-Mail James B. Byrnemailto:byrn...@harte-lyne.ca Harte & Lyne Limited http://www.harte-lyne.ca 9 Brockley Drive vox: +1 905 561 1241 Hamilton, Ontario fax: +1 905 561 0757 Canada L8E 3C3 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
[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? > > Probably you have to use a '.' instead of '^' > > try: > # sudo -u cyrus /usr/local/cyrus/sbin/ipurge -v -f -d 35 > 'user/*/INBOX.Trash' > Thank you. That was it exactly. My next question is: Why did the conversion to imap3 ignore users' existing Trash folder and create a new folder named INBOX^Trash for everyone; and likewise with Drafts and Sent? -- *** e-Mail is NOT a SECURE channel *** Do NOT transmit sensitive data via e-Mail Do NOT open attachments nor follow links sent by e-Mail James B. Byrnemailto:byrn...@harte-lyne.ca Harte & Lyne Limited http://www.harte-lyne.ca 9 Brockley Drive vox: +1 905 561 1241 Hamilton, Ontario fax: +1 905 561 0757 Canada L8E 3C3 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
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 +36d | wc -l 11367 # sudo -u cyrus /usr/local/cyrus/sbin/ipurge -v -f -d 35 'user/*/INBOX^Trash' # echo $? 0 # sudo -u cyrus /usr/local/cyrus/sbin/ipurge -v -f -d 35 'user/x/INBOX^Trash' # echo $? 0 What is happening here? -- *** e-Mail is NOT a SECURE channel *** Do NOT transmit sensitive data via e-Mail Do NOT open attachments nor follow links sent by e-Mail James B. Byrnemailto:byrn...@harte-lyne.ca Harte & Lyne Limited http://www.harte-lyne.ca 9 Brockley Drive vox: +1 905 561 1241 Hamilton, Ontario fax: +1 905 561 0757 Canada L8E 3C3 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
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 /usr/local/cyrus/sbin/reconstruct -f -r -G -V max user We have also run reconstruct. None-the-less some users show that they have exceeded their quota even when most of their email has been deleted. Why? -- *** e-Mail is NOT a SECURE channel *** Do NOT transmit sensitive data via e-Mail Do NOT open attachments nor follow links sent by e-Mail James B. Byrnemailto:byrn...@harte-lyne.ca Harte & Lyne Limited http://www.harte-lyne.ca 9 Brockley Drive vox: +1 905 561 1241 Hamilton, Ontario fax: +1 905 561 0757 Canada L8E 3C3 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
[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 been granted access to... ;) > I was logged on as the cyrus administrator via sudo. However, I discovered that the problem does not really exist. What happened is that the terminal manager I was using (tmux) was helpfully only showing the first few lines returned and the last few, leaving out the vast majority of the report. I had run into tmux's extraordinary behaviour previously with output from the cat utility. But I was not expecting it to be encountered in this case. Anyway, everything WRT IMAP is as it should be and my heart rate has returned to its normally elevated state. -- *** e-Mail is NOT a SECURE channel *** Do NOT transmit sensitive data via e-Mail Do NOT open attachments nor follow links sent by e-Mail James B. Byrnemailto:byrn...@harte-lyne.ca Harte & Lyne Limited http://www.harte-lyne.ca 9 Brockley Drive vox: +1 905 561 1241 Hamilton, Ontario fax: +1 905 561 0757 Canada L8E 3C3 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
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 mailbox folders Since the conversion everything has been running fine and we have no reported problems with mailbox administration, message receipt, or anything else having to do with IMAP. However, this morning I had cause to check for the existence of a particular mailbox folder. When I logged into cyradm and ran 'listmmailbox' I only received listings for three of our users, none of which showed the entire mailbox folder tree for any of those reported. This anomaly gives me great concern. Are there any known issues with cyrus-imapd that might cause this problem? Is it necessary to run reconstruct on a regular basis? -- *** e-Mail is NOT a SECURE channel *** Do NOT transmit sensitive data via e-Mail Do NOT open attachments nor follow links sent by e-Mail James B. Byrnemailto:byrn...@harte-lyne.ca Harte & Lyne Limited http://www.harte-lyne.ca 9 Brockley Drive vox: +1 905 561 1241 Hamilton, Ontario fax: +1 905 561 0757 Canada L8E 3C3 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: 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 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 >> mailboxes.db. >> > > Did you also rsync the config dir (see man imapd.conf > configdirectory:)? > It is often set to /var/lib/imap > Yes I did: rsync \ --chown=cyrus:cyrus \ --delete-after \ --group \ --hard-links \ --links \ --owner \ --perms \ --progress \ --recursive \ --specials \ --times \ --verbose \ --rsh="ssh " \ --exclude="delivery.db" \ --exclude="ptscache.db" \ --exclude="socket" \ --exclude="statuscache.db" \ --exclude="tls_sessions.db" \ remotehost:/var/lib/imap \ localhost:/var/imap -- *** e-Mail is NOT a SECURE channel *** Do NOT transmit sensitive data via e-Mail Do NOT open attachments nor follow links sent by e-Mail James B. Byrnemailto:byrn...@harte-lyne.ca Harte & Lyne Limited http://www.harte-lyne.ca 9 Brockley Drive vox: +1 905 561 1241 Hamilton, Ontario fax: +1 905 561 0757 Canada L8E 3C3 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
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 mailboxes.db. We ran 'reconstruct -f -r -G -V max user/*'. All this when well. However, we cannot re-establish a quota root for the transferred mailboxes. When we try to run quota from the command line then we see this: sudo -u cyrus /usr/local/cyrus/sbin/quota -f user/* Quota % Used Used Resource Root If we just run it to get a list of the user quotas then we the same thing: sudo -u cyrus /usr/local/cyrus/sbin/quota Quota % Used Used Resource Root And if we run it to rebuild the quotas for a specific user then we first see this: # sudo -u cyrus /usr/local/cyrus/sbin/quota -f user.x user.x: quota root user.x --> (none) user.x.Bayshore_Hobbies: quota root user.x --> (none) user.x.Drafts: quota root user.x --> (none) user.x.HLL: quota root user.x --> (none) . . . But if we rerun the same command after seeing the above then we this instead: # sudo -u cyrus /usr/local/cyrus/sbin/quota -f user.x Quota % Used Used Resource Root In maillog we see things like this: May 22 12:03:43 inet17 CYRUS/lmtpunix[85335]: LOSTQUOTA: unable to record change of 1639 bytes and 1 messages in quota user.x: Quota root does not exist May 22 12:03:43 inet17 CYRUS/lmtpunix[85335]: Delivered: <20180522120340.067...@imap.internal.harte-lyne.ca> to mailbox: user.x.delivery May 22 12:03:43 inet17 CYRUS/lmtpunix[85335]: USAGE x user: 0.010593 sys: 0.010593 and this: May 22 04:14:00 inet17 CYRUS/ipurge[68591]: Expunged 33 messages from user.y.Sent May 22 04:14:00 inet17 CYRUS/ipurge[68591]: LOSTQUOTA: unable to record change of -1634898 bytes and -33 messages in quota user.y: Quota root does not exist. May 22 04:10:00 inet17 CYRUS/ipurge[63950]: Expunged 252 messages from user.x.Trash May 22 04:10:00 inet17 CYRUS/ipurge[63950]: LOSTQUOTA: unable to record change of -22899753 bytes and -252 messages in quota user.x: Quota root does not exist On the old (v2.3) service we have no such problems. How do I transfer quotas? How do I create the missing quota roots? -- *** e-Mail is NOT a SECURE channel *** Do NOT transmit sensitive data via e-Mail Do NOT open attachments nor follow links sent by e-Mail James B. Byrnemailto:byrn...@harte-lyne.ca Harte & Lyne Limited http://www.harte-lyne.ca 9 Brockley Drive vox: +1 905 561 1241 Hamilton, Ontario fax: +1 905 561 0757 Canada L8E 3C3 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: 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 if there is anything I can do to eliminate them before thae actual switchover, scheduled for this Saturday. 1. All of the use folders are unsubscribed following the reconstruct. 2. All of the messages show as unread following the reconstruct. Is there any way to avoid these consequences of transfer and reconstruct? -- *** e-Mail is NOT a SECURE channel *** Do NOT transmit sensitive data via e-Mail Do NOT open attachments nor follow links sent by e-Mail James B. Byrnemailto:byrn...@harte-lyne.ca Harte & Lyne Limited http://www.harte-lyne.ca 9 Brockley Drive vox: +1 905 561 1241 Hamilton, Ontario fax: +1 905 561 0757 Canada L8E 3C3 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: 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 mailboxes avoiding the issue. > Thank you very much for the heads-up. I have had so many niggling issues respecting this conversion that one more would have a traumatic effect on me far beyond its material implications. Regards. -- *** e-Mail is NOT a SECURE channel *** Do NOT transmit sensitive data via e-Mail Do NOT open attachments nor follow links sent by e-Mail James B. Byrnemailto:byrn...@harte-lyne.ca Harte & Lyne Limited http://www.harte-lyne.ca 9 Brockley Drive vox: +1 905 561 1241 Hamilton, Ontario fax: +1 905 561 0757 Canada L8E 3C3 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: 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 the file of your choice, or piped to the new host, > like so: > Thank you both. I will try this approach and report if I somehow manage to get it wrong again. Regards, -- *** e-Mail is NOT a SECURE channel *** Do NOT transmit sensitive data via e-Mail Do NOT open attachments nor follow links sent by e-Mail James B. Byrnemailto:byrn...@harte-lyne.ca Harte & Lyne Limited http://www.harte-lyne.ca 9 Brockley Drive vox: +1 905 561 1241 Hamilton, Ontario fax: +1 905 561 0757 Canada L8E 3C3 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
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 /var/spool/imap/mailboxes.db.txt to the new followed by: sudo -u cyrus /usr/local/cyrus/sbin/ctl_mboxlist -u -f /var/spool/imap/mailboxes.db.txt on the new and all I get is a blank line and no indication in ps that the task is consuming any cpu. If I press I see this: line 1: no partition found line 2: no partition found line 3: no partition found . . . There is only one partition on both systems and it is '/var/spool/imap' on both. I have also tried the method suggested on the 3.0.6 documentation respecting upgrading and use rsync to move over mailboxes.db. In each case I cannot get reconstruct to run and upgrade or rebuild the mail store on the new service. # sudo -u cyrus /usr/local/cyrus/sbin/reconstruct -r -f -V * # I get an immediate empty return. I know that there exist physical mailboxes on the server that cyradm does not report. I know that these mailboxes exist on the old server and therefore I infer are present in mailboxess.db. How do I get the contents of the old mailboxes.db file into the new so that reconstruct will run? -- *** e-Mail is NOT a SECURE channel *** Do NOT transmit sensitive data via e-Mail Do NOT open attachments nor follow links sent by e-Mail James B. Byrnemailto:byrn...@harte-lyne.ca Harte & Lyne Limited http://www.harte-lyne.ca 9 Brockley Drive vox: +1 905 561 1241 Hamilton, Ontario fax: +1 905 561 0757 Canada L8E 3C3 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: 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 >> <ha...@knitter-edv-beratung.de>: >> >> 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 the -f option it still does not recurse. sudo -u cyrus /usr/local/cyrus/sbin/reconstruct -r -f user.testuser ll /var/spool/imap/t/user/testuser_hll/delivery/imports/cyrus.index-rw--- 1 cyrus cyrus 96 Apr 27 09:13 /var/spool/imap/t/user/testuser_hll/delivery/imports/cyrus.index rm /var/spool/imap/t/user/testuser_hll/delivery/imports/cyrus.index remove /var/spool/imap/t/user/testuser_hll/delivery/imports/cyrus.index? y sudo -u cyrus /usr/local/cyrus/sbin/reconstruct -r -f user.testuser_hll ll /var/spool/imap/t/user/testuser_hll/delivery/imports/cyrus.index ls: /var/spool/imap/t/user/testuser_hll/delivery/imports/cyrus.index: No such file or directory sudo -u cyrus /usr/local/cyrus/sbin/reconstruct -r -f user.testuser_hll/delivery/imports/cyrus.index ll /var/spool/imap/t/user/testuser_hll/delivery/imports/cyrus.index ls: /var/spool/imap/t/user/testuser_hll/delivery/imports/cyrus.index: No such file or directory Clearly either I am not using reconstruct correctly or it is not working as it did formerly. I expected that the missing index file would be recreated by reconstruct and it was not. In fact on other mailboxes in the same maildir tree I can see absolutely no evidence that reconstruct does anything at all. -- *** e-Mail is NOT a SECURE channel *** Do NOT transmit sensitive data via e-Mail Do NOT open attachments nor follow links sent by e-Mail James B. Byrnemailto:byrn...@harte-lyne.ca Harte & Lyne Limited http://www.harte-lyne.ca 9 Brockley Drive vox: +1 905 561 1241 Hamilton, Ontario fax: +1 905 561 0757 Canada L8E 3C3 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
[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 certificate in certificate > chain) > --- > * OK [CAPABILITY IMAP4 IMAP4rev1 LITERAL+ ID AUTH=PLAIN SASL-IR > COMPRESS=DEFLATE] inet07.hamilton.harte-lyne.ca Cyrus IMAP > v2.3.16-Fedora-RPM-2.3.16-15.el6 server ready > > LOGIN testusermb testuserpw > LOGIN BAD Please login first > > According to the documentation the message LOGIN BAD means that the > arguments to the LOGIN command are not understood. But, as far as I > can discover, the LOGIN command only takes two arguments: user name > and password. > > I get the same results on both the new SM host and the old so the > issue is with my employment of s_client. How does one connect to a > mailbox using s_client? > > I discovered that one must first preface IMAP commands with an arbitrary string. So this works: str LOGIN testusermb testuserpw str OK [CAPABILITY IMAP4 IMAP4rev1 LITERAL+ ID LOGINDISABLED AUTH=PLAIN COMPRESS=DEFLATE ACL RIGHTS=kxte QUOTA MAILBOX-REFERRALS NAMESPACE UIDPLUS NO_ATOMIC_RENAME UNSELECT CHILDREN MULTIAPPEND BINARY SORT SORT=MODSEQ THREAD=ORDEREDSUBJECT THREAD=REFERENCES ANNOTATEMORE CATENATE CONDSTORE SCAN IDLE LISTEXT LIST-SUBSCRIBED X-NETSCAPE URLAUTH] User logged in -- *** e-Mail is NOT a SECURE channel *** Do NOT transmit sensitive data via e-Mail Do NOT open attachments nor follow links sent by e-Mail James B. Byrnemailto:byrn...@harte-lyne.ca Harte & Lyne Limited http://www.harte-lyne.ca 9 Brockley Drive vox: +1 905 561 1241 Hamilton, Ontario fax: +1 905 561 0757 Canada L8E 3C3 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
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 is plaintext authenticating against /etc/passwd. We are in the process of transitioning from this setup to one hosted on FreeBSD and I am having problems getting SM on the new host to connect to the existing CI service. To debug this I am using openssl s_client as follows: 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 certificate in certificate chain) --- * OK [CAPABILITY IMAP4 IMAP4rev1 LITERAL+ ID AUTH=PLAIN SASL-IR COMPRESS=DEFLATE] inet07.hamilton.harte-lyne.ca Cyrus IMAP v2.3.16-Fedora-RPM-2.3.16-15.el6 server ready LOGIN testusermb testuserpw LOGIN BAD Please login first According to the documentation the message LOGIN BAD means that the arguments to the LOGIN command are not understood. But, as far as I can discover, the LOGIN command only takes two arguments: user name and password. I get the same results on both the new SM host and the old so the issue is with my employment of s_client. How does one connect to a mailbox using s_client? -- *** e-Mail is NOT a SECURE channel *** Do NOT transmit sensitive data via e-Mail Do NOT open attachments nor follow links sent by e-Mail James B. Byrnemailto:byrn...@harte-lyne.ca Harte & Lyne Limited http://www.harte-lyne.ca 9 Brockley Drive vox: +1 905 561 1241 Hamilton, Ontario fax: +1 905 561 0757 Canada L8E 3C3 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
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 referenced using user.mailbox. On the new system we can create mailboxes with the same nomenclature (user.mailbox). However, when we try to transfer an existing mailbox to the new server via imapsync it does not use the existing mailbox given by user.mailbox. Instead, it seems to create on the target host a new mailbox called user/mailbox distinct from user.mailbox. My question is: What configuration issue is causing this discrepancy between expected (user.mailbox --> user.mailbox) and observed behaviour (user.mailbox --> user/mailbox)? The the non-default settings in imapd.conf on the target system are: syslog_prefix: CYRUS syslog_facility:MAIL admins: cyrus admin configdirectory:/var/imap partition-default: /var/spool/imap sieveusehomedir:false sievedir: /var/imap/sieve allowplaintext: true anyoneuseracl: true autocreate_inbox_folders: delivery|\ delivery.forwarding|\ delivery.imports|\ delivery.private|\ Drafts|\ Intray|\ Sent|\ Spamyes|\ Spamno|\ Trash autocreate_quota: 102400 autocreatequota_units: 1048576 autocreate_subscribe_folders: delivery|\ delivery.forwarding|\ delivery.imports|\ delivery.private|\ Drafts|\ Intray|\ Sent|\ Spamyes|\ Spamno|\ Trash client_timeout: 10 hashimapspool: 1 lmtp_downcase_rcpt: true lmtp_fuzzy_mailbox_match: true quotawarn: 5 sasl_mech_list: PLAIN sasl_pwcheck_method:saslauthd sendmail: /usr/sbin/sendmail tls_client_ca_file: /usr/local/etc/pki/tls/certs/ca-bundle.crt tls_server_cert: /usr/local/etc/pki/imapd/20160039.pem tls_server_key: /usr/local/etc/pki/imapd/20160039.key -- *** e-Mail is NOT a SECURE channel *** Do NOT transmit sensitive data via e-Mail Do NOT open attachments nor follow links sent by e-Mail James B. Byrnemailto:byrn...@harte-lyne.ca Harte & Lyne Limited http://www.harte-lyne.ca 9 Brockley Drive vox: +1 905 561 1241 Hamilton, Ontario fax: +1 905 561 0757 Canada L8E 3C3 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
setting acl on autocreate folders
centOS-6.2 cyrus-imapd-2.3.16-6.el6_2.5 My question is: Is there a mechanism to automatically assign a default acl to a specific mailbox upon creation? I found the configuration option defaultacl but, this states that it is specifically used by mailboxes OTHER than users. The reason this feature is desired is that presently there seems no way to stop cyrus-master from directory recursion when this command is executed: cleanup_delivery cmd=ipurge -X -d 183 -f * at=0414 Because of this we adopted the convention of delivering messages to user/mailbox/delivery using the smtp mailbox+delivery scheme. This allows us to prune what are effectively INBOX messages over a certain age without trashing the contents of our users' archives folders. cleanup_delivery cmd=ipurge -X -d 183 -f *.delivery at=0414 To handle this setup we have these lines in /etc/imapd.conf autocreateinboxfolders: delivery|Drafts|Intray|Sent|Spamyes|Spamno|Trash autosubscribeinboxfolders: delivery|Drafts|Intray|Sent|Spamyes|Spamno|Trash Our difficulty arises from the requirement that the mailbox.delivery folder must have the acl anyone:p in order to permit direct delivery of addresses using the plus + addressing scheme. This requires manually setting that acl on every new users' delivery folder, which effectively eliminates the labour efficiency gained through the folder auto create commands. Ideally, we would like to be able to set the acl anyone:p on a specific folder: user/mailbox/delivery. -- *** E-Mail is NOT a SECURE channel *** James B. Byrnemailto:byrn...@harte-lyne.ca Harte Lyne Limited http://www.harte-lyne.ca 9 Brockley Drive vox: +1 905 561 1241 Hamilton, Ontario fax: +1 905 561 0757 Canada L8E 3C3 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: Differences in imap quota reporting between v2.2.13 and v2.3.16]
On Tue, May 15, 2012 17:08, Dan White wrote: What you describe sounds like what would happen if there were a quotaroot defined at each sub-hierarchy level, rather than at just the user's INBOX level. This is indeed the case. What does the output of quota/cyrquota look like? Do you see any quota roots defined other than for top level user mailboxes? If so, then you may need to manually remove them: http://cyrusimap.org/docs/cyrus-imapd/2.4.16/overview.php#recoveryquotasrm Which quota database format are you using (imapd.conf option quota_db)? This option is not specified in imapd.conf so I infer that the default value is used. In any case, irrespective of format, I deleted all the files in /var/lib/imap/quota/?/ pertaining to quotas set on sub folders. Then ran sudo -u cyrus /usr/lib/cyrus-imapd/quota -f. I discovered that I needed to run the quota -f command twice before the % usage would calculate correctly. I will now transfer the new meta data to the new server and see what happens. Thank you. -- *** E-Mail is NOT a SECURE channel *** James B. Byrnemailto:byrn...@harte-lyne.ca Harte Lyne Limited http://www.harte-lyne.ca 9 Brockley Drive vox: +1 905 561 1241 Hamilton, Ontario fax: +1 905 561 0757 Canada L8E 3C3 -- *** E-Mail is NOT a SECURE channel *** James B. Byrnemailto:byrn...@harte-lyne.ca Harte Lyne Limited http://www.harte-lyne.ca 9 Brockley Drive vox: +1 905 561 1241 Hamilton, Ontario fax: +1 905 561 0757 Canada L8E 3C3 Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
Differences in imap quota reporting between v2.2.13 and v2.3.16
OS CentOS-6.2 HW i86_64 KVM guest We are migrating from cyrus-imapd-2.2.13 running on CentOS-4.9 to v2.3.16 running on CentOS-6.2; being is the most recent version distributed by the packager. To the best of my ability to determine I have followed the upgrade instructions at http://cyrusimap.web.cmu.edu/docs/cyrus-imapd/2.3.16/install-upgrade.php. The data transfer and SELinux considerations completed successfully as did the mailbox reconstruction and quota updates. The new service is running and I can administer user mailboxes. However, the quota usage reported for user accounts under 2.3.16 differs dramatically from that reported under 2.2.13. It appears on the surface that the usage reported is for each individual mailbox and not for the accumulated usage under the user's INBOX. For example, I have the situation under 2.3.16 where a user with 500mb quota and 375mb usage is reported at the highest level as 3% usage because there is very little mail in their INBOX but a great deal of archived mail in subordinate folders. On the 2.2.13 server this identical user mailbox is reported as 75% utilization. I see in the change logs that there were numerous changes to quotas. But it seems odd to me that usage would no longer report cumulative totals. Can somebody give me the short form explanation of how quota is assigned to folders and usage is reported under 2.3.16? -- *** E-Mail is NOT a SECURE channel *** James B. Byrnemailto:byrn...@harte-lyne.ca Harte Lyne Limited http://www.harte-lyne.ca 9 Brockley Drive vox: +1 905 561 1241 Hamilton, Ontario fax: +1 905 561 0757 Canada L8E 3C3 Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
Re: How to get plus formatted addresses delivered to sub-folders
On Fri, June 18, 2010 17:54, Dan White wrote: On 18/06/10 15:14 -0400, James B. Byrne wrote: and a message with this email address: bylmbx001+delivery+t...@domain.tld . . . I'm attaching a perl script I use (I don't recall which website I grabbed it from) which will allow you to interact with your lmtp socket directly, to isolate your Cyrus configuration. For multi level plus addressing, you'll need to use your mailbox hierarchy separator, like: bylmbx001+delivery.t...@domain.tld Ahh. This is the bit that I did not grasp. I did not understand what the instruction For both methods, if 'mailfolder' is more than one level deep, you will need to conform to the hierarchy separator appropriate to your site was telling me. Your example makes it clear what my error was. Perhaps providing a similar example in the FAQ would help to make this clearer to others as well. Thank you, -- *** E-Mail is NOT a SECURE channel *** James B. Byrnemailto:byrn...@harte-lyne.ca Harte Lyne Limited http://www.harte-lyne.ca 9 Brockley Drive vox: +1 905 561 1241 Hamilton, Ontario fax: +1 905 561 0757 Canada L8E 3C3 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/mailing-list.html
How to get plus formatted addresses delivered to sub-folders
OS = CentOS-5.5 MTA = sendmail-8.13.1-3.3 IMAPD = cyrus-imapd-2.2.12-10 I have checked the archives of this list and followed threads on several related venues trying to understand how to get this to work. I have not succeeded. I have small, but somewhat complex, sendmail setup that involves two public MX hosts and an internal and private sendmail server that only accepts smtp connections from the public MX hosts. Final delivery through Cyrus-IMAPd takes place on the private host. We support multiple domains using virtusertable. We do not, currently, assign domain specific user mailbox ids but just have unique mailbox ids for everyone on that host. What I would like to have happen, given this entry in virtusertable: @.domain.tld %...@other_domain.tld and this entry in the IMAP directory tree: /var/spool/imap/b/user/bylmbx001/delivery/test and a message with this email address: bylmbx001+delivery+t...@domain.tld is to have the message placed directly in /var/spool/imap/b/user/bylmbx001/delivery/test The 'test' directory has the 'p' attribute set for the user 'anyone'. The sendmail delivery setting are: define(`CYRUSV2_MAILER_ARGS', `FILE /var/lib/imap/socket/lmtp')dnl define(`confLOCAL_MAILER',`cyrusv2')dnl MAILER(`cyrusv2')dnl I am not sure what imapd.conf settings, if any, apply. The cyrus.conf setting for delivery are: # at least one LMTP is required for delivery lmtpunix cmd=lmtpd listen=/var/lib/imap/socket/lmtp prefork=1 I have been picking at this problem for years and have never been able to get anywhere with it. I would really like to nail this down once and for all this time. I would greatly appreciate any help in discovering how this is accomplished. -- *** E-Mail is NOT a SECURE channel *** James B. Byrnemailto:byrn...@harte-lyne.ca Harte Lyne Limited http://www.harte-lyne.ca 9 Brockley Drive vox: +1 905 561 1241 Hamilton, Ontario fax: +1 905 561 0757 Canada L8E 3C3 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/mailing-list.html
Re: cyrus-imapd-2.2.12-10 -- ipurge and -f recursion --
On Mon, January 18, 2010 04:28, ram wrote: I think you mean ipurge (not impurge) Yes, ipurge is the actual name. Even I had exactly the same issue .. I modified ipurge.c a bit so that it will expect a -r switch to recurse through subfolders along with -f else -f works only on the inbox I have a workaroud patch to ipurge.c I can share .. but *absolutely no guarantee* that it will work for you Thank you very much. From what I have read this problem is raised quite frequently. I would think that simply providing an -F option that acted as -f without recursion would suffice. This would preserve the present -f behaviour so that existing scripts are not affected. Is there any design reason why the ability to simply purge only the INBOX is not provided? -- *** E-Mail is NOT a SECURE channel *** James B. Byrnemailto:byrn...@harte-lyne.ca Harte Lyne Limited http://www.harte-lyne.ca 9 Brockley Drive vox: +1 905 561 1241 Hamilton, Ontario fax: +1 905 561 0757 Canada L8E 3C3 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/mailing-list.html
cyrus-imapd-2.2.12-10 -- impurge and -f recursion --
I run cyrus-imapd under CentOS-4.8 (a RedHat el4 clone). I am trying to discover if there is any way to purge a user's INBOX of old and over-sized messages without affecting the contents of any subfolders thereof. I have looked at impurge as the mechanism. However,my reading of the man page, and of online discussions relating to this matter, indicate that in order for impurge to remove any mail from the INBOX then the -f switch has to be passed. But, I also gather that whenever the -f switch is used then ALL subfolders of the target directory are purged recursively as well. This strikes me as a rather odd combination of attributes but I cannot see any way to prevent recursion if the -f switch is used. What is the recommended way to purge mail from a user's INBOX only using criteria such as age and size? Sincerely, -- *** E-Mail is NOT a SECURE channel *** James B. Byrnemailto:byrn...@harte-lyne.ca Harte Lyne Limited http://www.harte-lyne.ca 9 Brockley Drive vox: +1 905 561 1241 Hamilton, Ontario fax: +1 905 561 0757 Canada L8E 3C3 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/mailing-list.html
