Re: 2.4.17 --> 2.5.3
On 09/19/2015 09:00 AM, Patrick Goetz wrote: I recall Bron telling us that the upgrade from 2.4.x to 2.5.x would be completely painless. That was mostly, but not completely true. A bunch of variable names in /etc/cyrus/imapd.conf changed (OK, that was easy to fix), and the upgrade did mostly work out of the box. There was one issue, however, and there are some new and improved error messages in the logs that I'm sufficiently OCD to have questions about. One one of my installs, I had this line in /etc/cyrus.conf: squatter_a cmd="/usr/sbin/squatter" at=0517 This worked for 2.4.17, but caused cyrus-master to fail to start with this error message: Sep 19 05:27:58 www cyrus/master[29646]: configuration file /etc/cyrus/cyrus.conf: bad character '_' in name on line 57 Sep 19 05:27:58 www systemd[1]: cyrus-master.service: Main process exited, code=exited, status=78/n/a For the time being, I just commented out the squatter line. I'm unclear on how necessary it is to re-index the mailboxes every day. If necessary/useful, did the syntax for this command change? Looks like it doesn't like the underscore. Just try: squattera cmd="/usr/sbin/squatter" at=0517 Also, I'm now getting these warnings (maybe some were there for 2.4.17, I can't remember): --- Sep 19 05:44:54 toad systemd[1]: Starting Cyrus IMAP mail server... Sep 19 05:44:54 toad cyrus/master[22860]: setrlimit: Unable to set file descriptors limit to -1: Operation not permitted Sep 19 05:44:54 toad cyrus/master[22860]: retrying with 4096 (current max) Sep 19 05:44:54 toad systemd[1]: Started Cyrus IMAP mail server. Sep 19 05:44:54 toad cyrus/ctl_cyrusdb[22861]: skiplist: clean shutdown file missing, updating recovery stamp Sep 19 05:44:54 toad cyrus/ctl_cyrusdb[22861]: recovering cyrus databases Sep 19 05:44:54 toad cyrus/ctl_cyrusdb[22861]: done recovering cyrus databases Sep 19 05:44:54 toad cyrus/master[22860]: unable to open imap/ipv6 socket: Address family not supported by protocol Sep 19 05:44:54 toad cyrus/master[22860]: unable to open imaps/ipv6 socket: Address family not supported by protocol Sep 19 05:44:54 toad cyrus/master[22860]: unable to open sieve/ipv6 socket: Address family not supported by protocol Sep 19 05:44:54 toad cyrus/master[22860]: unable to setsocketopt(IP_TOS) service lmtpunix/unix: Operation not supported - We're not using ipv6 -- is there any way to let cyrus know so that it doesn't freak out? Second, where is this coming from? Sep 19 05:44:54 toad cyrus/master[22860]: setrlimit: Unable to set file descriptors limit to -1: Operation not permitted Finally, should I worry about this? setsocketopt(IP_TOS) service lmtpunix/unix: Operation not supported Thanks. 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 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: cyradm: perl: symbol lookup error?
Just a quick note: IMAP::Admin appears to be broken, at the moment, and
can't be compiled. The Debian people submitted a patch 3 months ago
with no activity, indicating that the Perl module is semi-abandoned.
On 9/17/2015 3:03 PM, Patrick Boutilier wrote:
> On 09/17/2015 04:07 PM, Patrick Goetz wrote:
>> Thanks. I'm just now getting around to looking at this script. This
>> creates a mailbox, but don't you also need to set access privileges for
>> the user associated with this mailbox?
>
> Only if you are going to change the default rights. User will have
> access by default.
>
>
>
>
>
>>
>>
>>
>> On 09/16/2015 12:00 PM, Patrick Boutilier wrote:
>>>
>>> We use this simple perl script to add users. Fill in appropriate
>>> username and password.
>>>
>>>
>>>
>>>
>>>
>>> #!/usr/bin/perl -w
>>> #
>>> use File::Basename;
>>> use IMAP::Admin;
>>>
>>> if ( 0 == scalar( @ARGV ) ) {
>>> die( "\n Usuage: $0 userid\n");
>>> }
>>>
>>>
>>> $mailbox = "user.$ARGV[0]";
>>> $username = "";
>>> $password = "";
>>>
>>> # Set this to the hostname of your IMAP server
>>> $IMAPSERVER = "localhost";
>>> #
>>>
>>> # Main Code
>>> #
>>> # Login to IMAP server
>>> $imap = IMAP::Admin->new('Server' => $IMAPSERVER,
>>>'Login' => $username,
>>>'Password' => $password,) || die "no go $!
>>> !";
>>>
>>> print "Login: " . $imap->error . "\n";
>>>
>>> # Add user
>>> $add = $imap->create("$mailbox");
>>>
>>> if ($add != 0) {
>>> print "Error: " . $imap->error . "\n";
>>> }
>>> else {
>>> print "$ARGV[0] added.\n";
>>> }
>>>
>>>
>>> # Close connection
>>> $imap->close;
>>> exit;
>>>
>>>
>>>
>>> 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 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 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 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
2.4.17 --> 2.5.3
I recall Bron telling us that the upgrade from 2.4.x to 2.5.x would be completely painless. That was mostly, but not completely true. A bunch of variable names in /etc/cyrus/imapd.conf changed (OK, that was easy to fix), and the upgrade did mostly work out of the box. There was one issue, however, and there are some new and improved error messages in the logs that I'm sufficiently OCD to have questions about. One one of my installs, I had this line in /etc/cyrus.conf: squatter_a cmd="/usr/sbin/squatter" at=0517 This worked for 2.4.17, but caused cyrus-master to fail to start with this error message: Sep 19 05:27:58 www cyrus/master[29646]: configuration file /etc/cyrus/cyrus.conf: bad character '_' in name on line 57 Sep 19 05:27:58 www systemd[1]: cyrus-master.service: Main process exited, code=exited, status=78/n/a For the time being, I just commented out the squatter line. I'm unclear on how necessary it is to re-index the mailboxes every day. If necessary/useful, did the syntax for this command change? Also, I'm now getting these warnings (maybe some were there for 2.4.17, I can't remember): --- Sep 19 05:44:54 toad systemd[1]: Starting Cyrus IMAP mail server... Sep 19 05:44:54 toad cyrus/master[22860]: setrlimit: Unable to set file descriptors limit to -1: Operation not permitted Sep 19 05:44:54 toad cyrus/master[22860]: retrying with 4096 (current max) Sep 19 05:44:54 toad systemd[1]: Started Cyrus IMAP mail server. Sep 19 05:44:54 toad cyrus/ctl_cyrusdb[22861]: skiplist: clean shutdown file missing, updating recovery stamp Sep 19 05:44:54 toad cyrus/ctl_cyrusdb[22861]: recovering cyrus databases Sep 19 05:44:54 toad cyrus/ctl_cyrusdb[22861]: done recovering cyrus databases Sep 19 05:44:54 toad cyrus/master[22860]: unable to open imap/ipv6 socket: Address family not supported by protocol Sep 19 05:44:54 toad cyrus/master[22860]: unable to open imaps/ipv6 socket: Address family not supported by protocol Sep 19 05:44:54 toad cyrus/master[22860]: unable to open sieve/ipv6 socket: Address family not supported by protocol Sep 19 05:44:54 toad cyrus/master[22860]: unable to setsocketopt(IP_TOS) service lmtpunix/unix: Operation not supported - We're not using ipv6 -- is there any way to let cyrus know so that it doesn't freak out? Second, where is this coming from? Sep 19 05:44:54 toad cyrus/master[22860]: setrlimit: Unable to set file descriptors limit to -1: Operation not permitted Finally, should I worry about this? setsocketopt(IP_TOS) service lmtpunix/unix: Operation not supported Thanks. 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: 2.4.17 --> 2.5.3 Delayed expunge?
(I tried sending this message directly to Patrick B., and it was rejected because utexas.edu apparently has a high spam score? Anyway...) You have been extremely helpful: thank you very much! In particular, I was looking at the documentation here: http://www.cyrusimap.org/docs/cyrus-imapd/2.5.3/man.php which is the same old incomplete stuff that we were dealing with before, and was just about to sift through the mailing list archive to find out where the real documentation is being developed these days. To avoid confusion for armchair cyrus admins like myself, would it be possible to include a note at http://www.cyrusimap.org/docs pointing people to the new and improved documentation at https://docs.cyrus.foundation/imap ? On 9/19/2015 9:50 AM, Patrick Boutilier wrote: > On 09/19/2015 11:41 AM, Patrick Goetz wrote: >> Upgrading from 2.4.17 to 2.5.3 I kept the same configuration files, save >> for changing the names of some deprecated variables in >> /etc/cyrus/imapd.conf. >> >> >> Now I am noticing some unexpected behavior; namely when messages are >> deleted (in Thunderbird, Trash emptied and folders compacted) the >> messages seem to persist in ~/cyrus/user/my_username >> >> Was this the behavior before, and I just didn't notice it because I'm >> only ever looking in the mail folders when debugging, or is this a new >> feature of 2.5.x? >> >> In particular, I notice that the /etc/cyrus/cyrus.conf file appears to >> have these new fields which I didn't have before: >> >> # Expire data older than 28 days. >> # deleteprune cmd="cyr_expire -E 4 -D 28" at=0430 >> # expungeprune cmd="cyr_expire -E 4 -X 28" at=0445 >> >> >> I commented them out, thinking these were for removing old mail no >> matter what; i.e. deleted or not. Am I suddenly getting a delayed >> expunge feature that I didn't have in 2.4.17, hence need to uncomment >> the pruning lines above? >> >> Thanks. > > > https://docs.cyrus.foundation/imap/release-notes/2.5/x/2.5.0.html > > > Looks for Default Change: delete_mode and Default Change: expunge_mode > . Also, Underscores in cmd Names in cyrus.conf :-) > > > > > > > >> >> >> 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 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 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: 2.4.17 --> 2.5.3
I'm uncertain why the _a was there in the first place. Why can't I just do this? squatter cmd="/usr/sbin/squatter" at=0517 I guess the subscript was so there so that you can have multiple squatter processes firing at different time/frequencies? On 9/19/2015 7:05 AM, Patrick Boutilier wrote: > On 09/19/2015 09:00 AM, Patrick Goetz wrote: >> I recall Bron telling us that the upgrade from 2.4.x to 2.5.x would be >> completely painless. That was mostly, but not completely true. >> >> A bunch of variable names in /etc/cyrus/imapd.conf changed (OK, that was >> easy to fix), and the upgrade did mostly work out of the box. There was >> one issue, however, and there are some new and improved error messages >> in the logs that I'm sufficiently OCD to have questions about. >> >> >> One one of my installs, I had this line in /etc/cyrus.conf: >> >> squatter_a cmd="/usr/sbin/squatter" at=0517 >> >> >> This worked for 2.4.17, but caused cyrus-master to fail to start with >> this error message: >> >> Sep 19 05:27:58 www cyrus/master[29646]: configuration file >> /etc/cyrus/cyrus.conf: bad character '_' in name on line 57 >> Sep 19 05:27:58 www systemd[1]: cyrus-master.service: Main process >> exited, code=exited, status=78/n/a >> >> For the time being, I just commented out the squatter line. I'm unclear >> on how necessary it is to re-index the mailboxes every day. If >> necessary/useful, did the syntax for this command change? > > > Looks like it doesn't like the underscore. Just try: > > > squattera cmd="/usr/sbin/squatter" at=0517 > > > > > > >> >> Also, I'm now getting these warnings (maybe some were there for 2.4.17, >> I can't remember): >> >> --- >> Sep 19 05:44:54 toad systemd[1]: Starting Cyrus IMAP mail server... >> Sep 19 05:44:54 toad cyrus/master[22860]: setrlimit: Unable to set file >> descriptors limit to -1: Operation not permitted >> Sep 19 05:44:54 toad cyrus/master[22860]: retrying with 4096 (current >> max) >> Sep 19 05:44:54 toad systemd[1]: Started Cyrus IMAP mail server. >> Sep 19 05:44:54 toad cyrus/ctl_cyrusdb[22861]: skiplist: clean shutdown >> file missing, updating recovery stamp >> Sep 19 05:44:54 toad cyrus/ctl_cyrusdb[22861]: recovering cyrus databases >> Sep 19 05:44:54 toad cyrus/ctl_cyrusdb[22861]: done recovering cyrus >> databases >> Sep 19 05:44:54 toad cyrus/master[22860]: unable to open imap/ipv6 >> socket: Address family not supported by protocol >> Sep 19 05:44:54 toad cyrus/master[22860]: unable to open imaps/ipv6 >> socket: Address family not supported by protocol >> Sep 19 05:44:54 toad cyrus/master[22860]: unable to open sieve/ipv6 >> socket: Address family not supported by protocol >> Sep 19 05:44:54 toad cyrus/master[22860]: unable to setsocketopt(IP_TOS) >> service lmtpunix/unix: Operation not supported >> - >> >> We're not using ipv6 -- is there any way to let cyrus know so that it >> doesn't freak out? >> >> >> Second, where is this coming from? >> >> Sep 19 05:44:54 toad cyrus/master[22860]: setrlimit: Unable to set >> file descriptors limit to -1: Operation not permitted >> >> >> Finally, should I worry about this? >> >> setsocketopt(IP_TOS) service lmtpunix/unix: Operation not supported >> >> >> Thanks. >> >> >> 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 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 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: 2.4.17 --> 2.5.3
On 09/19/2015 10:16 AM, Patrick Goetz wrote: I'm uncertain why the _a was there in the first place. Why can't I just do this? squatter cmd="/usr/sbin/squatter" at=0517 You can do that. I guess the subscript was so there so that you can have multiple squatter processes firing at different time/frequencies? Correct. On 9/19/2015 7:05 AM, Patrick Boutilier wrote: On 09/19/2015 09:00 AM, Patrick Goetz wrote: I recall Bron telling us that the upgrade from 2.4.x to 2.5.x would be completely painless. That was mostly, but not completely true. A bunch of variable names in /etc/cyrus/imapd.conf changed (OK, that was easy to fix), and the upgrade did mostly work out of the box. There was one issue, however, and there are some new and improved error messages in the logs that I'm sufficiently OCD to have questions about. One one of my installs, I had this line in /etc/cyrus.conf: squatter_a cmd="/usr/sbin/squatter" at=0517 This worked for 2.4.17, but caused cyrus-master to fail to start with this error message: Sep 19 05:27:58 www cyrus/master[29646]: configuration file /etc/cyrus/cyrus.conf: bad character '_' in name on line 57 Sep 19 05:27:58 www systemd[1]: cyrus-master.service: Main process exited, code=exited, status=78/n/a For the time being, I just commented out the squatter line. I'm unclear on how necessary it is to re-index the mailboxes every day. If necessary/useful, did the syntax for this command change? Looks like it doesn't like the underscore. Just try: squattera cmd="/usr/sbin/squatter" at=0517 Also, I'm now getting these warnings (maybe some were there for 2.4.17, I can't remember): --- Sep 19 05:44:54 toad systemd[1]: Starting Cyrus IMAP mail server... Sep 19 05:44:54 toad cyrus/master[22860]: setrlimit: Unable to set file descriptors limit to -1: Operation not permitted Sep 19 05:44:54 toad cyrus/master[22860]: retrying with 4096 (current max) Sep 19 05:44:54 toad systemd[1]: Started Cyrus IMAP mail server. Sep 19 05:44:54 toad cyrus/ctl_cyrusdb[22861]: skiplist: clean shutdown file missing, updating recovery stamp Sep 19 05:44:54 toad cyrus/ctl_cyrusdb[22861]: recovering cyrus databases Sep 19 05:44:54 toad cyrus/ctl_cyrusdb[22861]: done recovering cyrus databases Sep 19 05:44:54 toad cyrus/master[22860]: unable to open imap/ipv6 socket: Address family not supported by protocol Sep 19 05:44:54 toad cyrus/master[22860]: unable to open imaps/ipv6 socket: Address family not supported by protocol Sep 19 05:44:54 toad cyrus/master[22860]: unable to open sieve/ipv6 socket: Address family not supported by protocol Sep 19 05:44:54 toad cyrus/master[22860]: unable to setsocketopt(IP_TOS) service lmtpunix/unix: Operation not supported - We're not using ipv6 -- is there any way to let cyrus know so that it doesn't freak out? Second, where is this coming from? Sep 19 05:44:54 toad cyrus/master[22860]: setrlimit: Unable to set file descriptors limit to -1: Operation not permitted Finally, should I worry about this? setsocketopt(IP_TOS) service lmtpunix/unix: Operation not supported Thanks. 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 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 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 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
2.4.17 --> 2.5.3 Delayed expunge?
Upgrading from 2.4.17 to 2.5.3 I kept the same configuration files, save for changing the names of some deprecated variables in /etc/cyrus/imapd.conf. Now I am noticing some unexpected behavior; namely when messages are deleted (in Thunderbird, Trash emptied and folders compacted) the messages seem to persist in ~/cyrus/user/my_username Was this the behavior before, and I just didn't notice it because I'm only ever looking in the mail folders when debugging, or is this a new feature of 2.5.x? In particular, I notice that the /etc/cyrus/cyrus.conf file appears to have these new fields which I didn't have before: # Expire data older than 28 days. # deleteprune cmd="cyr_expire -E 4 -D 28" at=0430 # expungeprune cmd="cyr_expire -E 4 -X 28" at=0445 I commented them out, thinking these were for removing old mail no matter what; i.e. deleted or not. Am I suddenly getting a delayed expunge feature that I didn't have in 2.4.17, hence need to uncomment the pruning lines above? Thanks. 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: 2.4.17 --> 2.5.3 Delayed expunge?
On 09/19/2015 11:41 AM, Patrick Goetz wrote: Upgrading from 2.4.17 to 2.5.3 I kept the same configuration files, save for changing the names of some deprecated variables in /etc/cyrus/imapd.conf. Now I am noticing some unexpected behavior; namely when messages are deleted (in Thunderbird, Trash emptied and folders compacted) the messages seem to persist in ~/cyrus/user/my_username Was this the behavior before, and I just didn't notice it because I'm only ever looking in the mail folders when debugging, or is this a new feature of 2.5.x? In particular, I notice that the /etc/cyrus/cyrus.conf file appears to have these new fields which I didn't have before: # Expire data older than 28 days. # deleteprune cmd="cyr_expire -E 4 -D 28" at=0430 # expungeprune cmd="cyr_expire -E 4 -X 28" at=0445 I commented them out, thinking these were for removing old mail no matter what; i.e. deleted or not. Am I suddenly getting a delayed expunge feature that I didn't have in 2.4.17, hence need to uncomment the pruning lines above? Thanks. https://docs.cyrus.foundation/imap/release-notes/2.5/x/2.5.0.html Looks for Default Change: delete_mode and Default Change: expunge_mode . Also, Underscores in cmd Names in cyrus.conf :-) 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 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
