Cyrus IMAP 3.0.9 released
The Cyrus team is proud to announce the immediate availability of a new version of Cyrus IMAP: 3.0.9 I'm trialling hosting the release files using Github's releases feature. Please use the Github download links if possible, and advise if you have any problems! (It may even download faster due to Github's content delivery network.) Download URLs: https://github.com/cyrusimap/cyrus-imapd/releases/download/cyrus-imapd-3.0.9/cyrus-imapd-3.0.9.tar.gz https://github.com/cyrusimap/cyrus-imapd/releases/download/cyrus-imapd-3.0.9/cyrus-imapd-3.0.9.tar.gz.sig https://www.cyrusimap.org/releases/cyrus-imapd-3.0.9.tar.gz https://www.cyrusimap.org/releases/cyrus-imapd-3.0.9.tar.gz.sig Please consult the release notes and upgrade documentation before upgrading to 3.0.9: https://www.cyrusimap.org/imap/download/release-notes/3.0/x/3.0.9.html https://www.cyrusimap.org/imap/download/upgrade.html And join us on Github at https://github.com/cyrusimap/cyrus-imapd to report issues, join in the deliberations of new features for the next Cyrus IMAP release, and to contribute to the documentation. On behalf of the Cyrus team, Kind regards, ellie timoney Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/ To Unsubscribe: https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus
Re: Mailbox hierarchy determination?
> On 3/14/19 9:46 AM, Simon Matter wrote: >> I guess you're missing the fact that these options have possibly changed >> between releases. Another thing is that distribution packages can also >> alter the defaults and if they don't do it correct, they may "forget" to >> also change the docs accordingly. >> > > Thank you for your help with this. I think what you're saying is that > for my configuration I should have > >fulldirhash: 1 >hashimapspool: 1 > > > I'm not 100% certain how the defaults are set for my installation -- is > there any way to check this? Our RPMs create two files at build time: /usr/share/cyrus-imapd/rpm/imapd.conf.dist This is what the source distribution uses. /usr/share/cyrus-imapd/rpm/imapd.conf.default This is what the patched build uses. Unfortunately I don't know of a way to get the same info at run time. Regards, Simon 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: Mailbox hierarchy determination?
On 3/14/19 1:23 PM, Patrick Goetz wrote: On 3/14/19 9:46 AM, Simon Matter wrote: I guess you're missing the fact that these options have possibly changed between releases. Another thing is that distribution packages can also alter the defaults and if they don't do it correct, they may "forget" to also change the docs accordingly. Thank you for your help with this. I think what you're saying is that for my configuration I should have fulldirhash: 1 hashimapspool: 1 I'm not 100% certain how the defaults are set for my installation -- is there any way to check this? Check the directories such as /var/imap/quota/E and see if all the userids start with e. If not you are most likely using fulldirhash . Do the same for your mail partition to see if hashimapspool is enabled. 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: Mailbox hierarchy determination?
On 3/14/19 9:46 AM, Simon Matter wrote: I guess you're missing the fact that these options have possibly changed between releases. Another thing is that distribution packages can also alter the defaults and if they don't do it correct, they may "forget" to also change the docs accordingly. Thank you for your help with this. I think what you're saying is that for my configuration I should have fulldirhash: 1 hashimapspool: 1 I'm not 100% certain how the defaults are set for my installation -- is there any way to check this? 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: renaming INBOX
On 3/14/19 11:48 AM, Marco wrote: Il 13/03/2019 09:16, Marco ha scritto: Il 12/03/2019 13:30, Ken Murchison ha scritto: If I remember correctly, Cyrus only permits the owner of the INBOX to rename it. Proxy authenticate as n...@example.com and try again. Hello Ken, I tried with proxy authentication. It is the same. The operation is not allowed: Ops, sorry, I'm confusing myself. I confirm that with proxy authentication it works as described by the RFC. I can rename the INBOX :) RFC says: Renaming INBOX is permitted, and has special behavior. It moves all messages in INBOX to a new mailbox with the given name, leaving INBOX empty. So you still have an INBOX right? Just an empty one and new mail still gets delivered to INBOX? Thank you very much!! Bye Marco 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: renaming INBOX
Il 13/03/2019 09:16, Marco ha scritto: Il 12/03/2019 13:30, Ken Murchison ha scritto: If I remember correctly, Cyrus only permits the owner of the INBOX to rename it. Proxy authenticate as n...@example.com and try again. Hello Ken, I tried with proxy authentication. It is the same. The operation is not allowed: Ops, sorry, I'm confusing myself. I confirm that with proxy authentication it works as described by the RFC. I can rename the INBOX :) Thank you very much!! Bye Marco 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: Mailbox hierarchy determination?
> On 3/14/19 3:50 AM, Simon Matter wrote: >> >> Dirhashing is controlled by "fulldirhash" and "hashimapspool". >> > > > Right. This is what it says in imapd.conf: > > > fulldirhash: 0 >If enabled, uses an improved directory hashing scheme which hashes on > the entire username instead of using just the first letter as the hash. > This changes hash algorithm used for quota and user directories and if > hashimapspool is enabled, the entire mail spool. > > Note that this option CANNOT be changed on a live system. The server > must be quiesced and then the directories moved with the rehash utility. > > hashimapspool: 0 > If enabled, the partitions will also be hashed, in addition to the > hashing done on configuration directories. This is recommended if one > partition has a very bushy mailbox tree. > > > I don't have these options enabled, and my interpretation of this > description is that enabling them would facilitate my configuration, not > the other way around. This is what confused me in the first place. > > What am I missing? I guess you're missing the fact that these options have possibly changed between releases. Another thing is that distribution packages can also alter the defaults and if they don't do it correct, they may "forget" to also change the docs accordingly. Regards, Simon 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: Cyrmaster at 100% cpu, defunct processes, connection timeouts
On 14/03/2019 10:45, Vladislav Kurz wrote: > Hello everybody > > yesterday evening I have update a server with ubuntu 18.04 (just the routine > security update, libc, kernel, not cyrus), and after reboot cyrus fails in > quite strange way. > > It works fine for a few minutes, but then the cyrmaster spins up to 100% cpu > (1-core), and stops receiving new connections. Processes that exit stay in > defunct/zombie state, and eventually all of them end up like that. > > At first I suspected some SSL problems, so eptied the tls_sessions.db, even > set > tls_session_timeout: 0, tried to disable mailnotifier (I had it at log), > enabled debug, but still can't find the problem. > > Anybody has/had the same problem and perhaps a solution? replying to myself, changing to prefork=1 (instead of prefork=0) solved the issue. I vaguely remembered that I changed to prefork=0 to fix some previous problems... For completenetes: cyrus-imapd 2.5.10-3ubuntu1 libc6:amd64 2.27-3ubuntu1 linux-image-4.15.0-46-generic 4.15.0-46.49 -- Best regards Vladislav Kurz 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: Mailbox hierarchy determination?
On 3/14/19 3:50 AM, Simon Matter wrote: Dirhashing is controlled by "fulldirhash" and "hashimapspool". Right. This is what it says in imapd.conf: fulldirhash: 0 If enabled, uses an improved directory hashing scheme which hashes on the entire username instead of using just the first letter as the hash. This changes hash algorithm used for quota and user directories and if hashimapspool is enabled, the entire mail spool. Note that this option CANNOT be changed on a live system. The server must be quiesced and then the directories moved with the rehash utility. hashimapspool: 0 If enabled, the partitions will also be hashed, in addition to the hashing done on configuration directories. This is recommended if one partition has a very bushy mailbox tree. I don't have these options enabled, and my interpretation of this description is that enabling them would facilitate my configuration, not the other way around. This is what confused me in the first place. What am I missing? 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
Cyrmaster at 100% cpu, defunct processes, connection timeouts
Hello everybody yesterday evening I have update a server with ubuntu 18.04 (just the routine security update, libc, kernel, not cyrus), and after reboot cyrus fails in quite strange way. It works fine for a few minutes, but then the cyrmaster spins up to 100% cpu (1-core), and stops receiving new connections. Processes that exit stay in defunct/zombie state, and eventually all of them end up like that. At first I suspected some SSL problems, so eptied the tls_sessions.db, even set tls_session_timeout: 0, tried to disable mailnotifier (I had it at log), enabled debug, but still can't find the problem. Anybody has/had the same problem and perhaps a solution? Best regards Vladislav Kurz 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: Mailbox hierarchy determination?
> The first couple of times I set up cyrus-imapd I used Debian packages
> which separated mailboxes in the default partition into folders based on
> the starting letter of the mailbox; i.e. something like:
>
>/var/spool/cyrus/mail/{[A-Z,a-z,0-9]}/user
>
> Since I have fewer than 50 users and since I found myself frequently
> "going to the files" so to speak to definitely determine the presence or
> absence of some message a user was concerned about, this hierarchy was
> something of a annoyance, so during the last major upgrade I switched
> this to:
>
> /srv/imap/{user1,user2,...,userN}
>
> i.e. flattening the folder structure and moving the default partition to
> a large non-system disk unaffected by /var volatility.
>
> Now for the life of me I can't figure out what setting in imapd.conf (if
> any) facilitated this structure (not the location of the default
> partition, but rather not using the [A-Z,a-z,0-9] subfolders.
>
> Last time I left the sieve folders divided by letter; in the next
> iteration I'd like to flatten that folder structure to.
>
> Looking at the Arch package post_install script, it pre-creates a ton of
> folders:
>
> --
> # all kinds of directories needed for the IMAP spool
> for subdir in imap/{,db,log,msg,proc,socket,sieve}
> spool/imap/{,stage.}; do
> if [ ! -d /var/${subdir} ]; then
> mkdir -m 0750 -p "/var/${subdir}"
> fi
> done
> for subdir in imap/{user,quota,sieve} spool/imap; do
> for i in a b c d e f g h i j k l m n o p q r s t v u w x y z \
> A B C D E F G H I J K L M N O P Q R S T U V W X Y Z \
> 0 1 2 3 4 5 6 7 8 9; do
> if [ ! -d /var/${subdir}/${i} ]; then
> mkdir -m 0750 -p "/var/${subdir}/${i}"
> fi
> done
> --
>
> I'm wondering how much or if any of this is really necessary. Will cyrus
> autocreate the necessary folders if missing?
Dirhashing is controlled by "fulldirhash" and "hashimapspool".
IIRC creating the dirs like above is not needed, they are created on demand.
Regards,
Simon
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
Mailbox hierarchy determination?
The first couple of times I set up cyrus-imapd I used Debian packages
which separated mailboxes in the default partition into folders based on
the starting letter of the mailbox; i.e. something like:
/var/spool/cyrus/mail/{[A-Z,a-z,0-9]}/user
Since I have fewer than 50 users and since I found myself frequently
"going to the files" so to speak to definitely determine the presence or
absence of some message a user was concerned about, this hierarchy was
something of a annoyance, so during the last major upgrade I switched
this to:
/srv/imap/{user1,user2,...,userN}
i.e. flattening the folder structure and moving the default partition to
a large non-system disk unaffected by /var volatility.
Now for the life of me I can't figure out what setting in imapd.conf (if
any) facilitated this structure (not the location of the default
partition, but rather not using the [A-Z,a-z,0-9] subfolders.
Last time I left the sieve folders divided by letter; in the next
iteration I'd like to flatten that folder structure to.
Looking at the Arch package post_install script, it pre-creates a ton of
folders:
--
# all kinds of directories needed for the IMAP spool
for subdir in imap/{,db,log,msg,proc,socket,sieve}
spool/imap/{,stage.}; do
if [ ! -d /var/${subdir} ]; then
mkdir -m 0750 -p "/var/${subdir}"
fi
done
for subdir in imap/{user,quota,sieve} spool/imap; do
for i in a b c d e f g h i j k l m n o p q r s t v u w x y z \
A B C D E F G H I J K L M N O P Q R S T U V W X Y Z \
0 1 2 3 4 5 6 7 8 9; do
if [ ! -d /var/${subdir}/${i} ]; then
mkdir -m 0750 -p "/var/${subdir}/${i}"
fi
done
--
I'm wondering how much or if any of this is really necessary. Will cyrus
autocreate the necessary folders if missing?
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: renaming INBOX
Il 13/03/2019 11:56, Patrick Boutilier ha scritto: Pretty sure you can't rename INBOX for the same user. Thank you Patrick, I'm afraid so. I have to definitively think that renaming INBOX is not allowed on Cyrus IMAP... Cheers Marco 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
