Cyrus IMAP 3.6.0-rc1 released

2022-11-15 Thread ellie timoney
The Cyrus team is proud to announce the first release candidate from the new Cyrus IMAP 3.6 series: 3.6.0-rc1 This release is basically the same thing as 3.6.0-beta3 While 3.6 is still in pre-release, the main https://www.cyrusimap.org/ website will continue to be focused on the stable 3.4

Re: server not accessible - 3.6-beta3-1

2022-11-15 Thread cyrus
Hi, I was surprised too, but in a different way: I have the same values. I probably found the debian 9 standard in my archive, which was also a template for me: .../src/debian/cyrus-imapd/cyrus-imapd_2.5.10-3.debian/debian/cyrus.conf -->

Re: server not accessible - 3.6-beta3-1

2022-11-15 Thread Simon Matter
> Thank you Ivan, > > I just checked it and modified to  > > imapcmd="imapd -U 60" listen="imap" prefork=10 > maxchild=500 proto=tcp4 > imaps cmd="imapd -s -U 60" listen="imaps" prefork=10 > maxchild=500 proto=tcp4 > > We will see, soon. > > The old (default)

Re: server not accessible - 3.6-beta3-1 - seems solved

2022-11-15 Thread Pongrácz István
Thank you Ivan, You are the winner :) Users are happy in the last 1 hour, so, I assume the maxchild did the trick. The old server has no this kind of limit, so, never had this issue. Now we have 118 connections, 140 processes, which a little bit higher than the limit, so, that explains the

Re: server not accessible - 3.6-beta3-1

2022-11-15 Thread vladas via Info
That may also happen due to conflicting settings in Thunderbird. For verification, try to switch a place of sending message copy to some local folder. Also bear in mind the similar settings in Identities, where they may be different or pointing to non-existing folder.

Re: server not accessible - 3.6-beta3-1

2022-11-15 Thread Pongrácz István
Thank you Ivan, I just checked it and modified to  imapcmd="imapd -U 60" listen="imap" prefork=10 maxchild=500 proto=tcp4 imaps cmd="imapd -s -U 60" listen="imaps" prefork=10 maxchild=500 proto=tcp4 We will see, soon. The old (default) was: imap

Re: server not accessible - 3.6-beta3-1

2022-11-15 Thread Ivan Kuznetsov
Hello It can be a lack of available IMAP handlers. One TB makes more than one IMAP connection depending of a number of tabs opened. Some client connections can hit a limit of running imapd processes. Consult with cyrus.conf Regards, Ivan 15.11.2022 12:18, Pongrácz István пишет: Hi, Is

server not accessible - 3.6-beta3-1

2022-11-15 Thread Pongrácz István
Hi, Is that possible, the cyrus imap cannot be reached sometimes, due to some bugs? My users reported frequently (seems too frequent) when they send an email TB cannot save the copy of the sent email to the Sent folder, or when they just browse their account, TB reported: connecting to the