Re: [Courier-imap] Errata release of courier and courier-imap packages.
21.03.2021 17:56, Sam Varshavchik пишет: Eugene Suprun writes: « HTML content follows » Hi Sam. Installed courier-imap 5.1.1 at the production server (1500 mailboxes), users get alerts in their clients (e.g. Mozilla Thunderbird) when jumping from a folder to another: Filesystem notification initialization error -- contact your mail administrator (check for configuration errors with the FAM/Gamin library) In /var/log/mail: Mar 21 16:57:49 mail imapd-ssl[1994]: LOGIN, mailto:user=u...@domain.org>user=u...@domain.org, ip=[194.158.XXX.YYY], port=[61752], protocol=IMAP Mar 21 16:57:49 mail imapd-ssl[1994]: Failed to create cache file: maildirwatch (mailto:u...@domain.org>u...@domain.org) Mar 21 16:57:49 mail imapd-ssl[1994]: Error: Too many open files Mar 21 16:57:50 mail imapd-ssl[1994]: Failed to create cache file: maildirwatch (mailto:u...@domain.org>u...@domain.org) Mar 21 16:57:50 mail imapd-ssl[1994]: Error: Too many open files openSuSE 15.2. I believe 'FAM/Gamin' should be replaced by 'inotify' in the alerts. inotifywait -m works fine at the server. Reinstalled courier-imap 5.0.14 Some Googling around suggests that this might be on a per-userid limit of inotify file descriptors: https://stackoverflow.com/questions/0245/inotify-fd-why-is-the-limit-per-user-id-and-not-per-process I'm guessing that all your mailboxes are virtual and use the same system userid. That is true. Try increasing /proc/sys/fs/inotify/max_user_instances Increased its value from 128 to 4096, no problems in an hour. Thanks for the tip. I am going to check it tomorrow, when there will be much more mail users. In any case, I think enabling inotify notification facility should be configurable: inotify structures require non-negligible amount of memory to maintain (and it can't be swapped out to disk) As for alerting a user? It frustrates the user. May be also configurable setting? Rough metric: number of concurrent IMAP sessions multiplied by 4. It's worth adding this to the installation notes. ___ Courier-imap mailing list Courier-imap@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-imap ___ Courier-imap mailing list Courier-imap@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-imap
Re: [Courier-imap] Errata release of courier and courier-imap packages.
Hi Sam. Installed courier-imap 5.1.1 at the production server (1500 mailboxes), users get alerts in their clients (e.g. Mozilla Thunderbird) when jumping from a folder to another: Filesystem notification initialization error -- contact your mail administrator (check for configuration errors with the FAM/Gamin library) In /var/log/mail: Mar 21 16:57:49 mail imapd-ssl[1994]: LOGIN, user=u...@domain.org, ip=[194.158.XXX.YYY], port=[61752], protocol=IMAP Mar 21 16:57:49 mail imapd-ssl[1994]: Failed to create cache file: maildirwatch (u...@domain.org) Mar 21 16:57:49 mail imapd-ssl[1994]: Error: Too many open files Mar 21 16:57:50 mail imapd-ssl[1994]: Failed to create cache file: maildirwatch (u...@domain.org) Mar 21 16:57:50 mail imapd-ssl[1994]: Error: Too many open files openSuSE 15.2. I believe 'FAM/Gamin' should be replaced by 'inotify' in the alerts. inotifywait -m works fine at the server. Reinstalled courier-imap 5.0.14 Regards, Eugene 21.03.2021 01:58, Sam Varshavchik пишет: Download: https://www.courier-mta.org/download.html New versions released of courier (1.1.1), courier-imap (5.1.1) packages. Changes: - courier: fix the RPM build script to build either with OpenSSL or GnuTLS. - courier, courier-imap: fix swapped TLS_CACHEFILE settings in the IMAP and POP3 configuration files. ___ Courier-imap mailing list Courier-imap@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-imap ___ Courier-imap mailing list Courier-imap@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-imap
Re: [Courier-imap] Courier 1.0.16/courier-imap 5.0.13 released
Hi Sam. Courier-imap: ./configure --with-notice=unicode ends with error message: ERROR: The Courier Unicode Library 2.1 header files appear not to be installed. You may need to upgrade the library or install a separate development subpackage in addition to the main package Courier Unicode 2.1.2 is installed ok Previous courier-imap version (5.0.12) source configures OK. 01.03.2021 16:30, Sam Varshavchik пишет: Download: https://www.courier-mta.org/download.html New releases of courier and courier-imap. Changes: - Fixes a crash caused by a malformed DNS query/response. ___ Courier-imap mailing list Courier-imap@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-imap -- /Regards, Eugene Suprun / ___ Courier-imap mailing list Courier-imap@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-imap
[Courier-imap] Courier-imap 5.0.2, pop access unicode errors
Hi! I upgraded Courier IMAP from v. 4.18.2 to 5.0.2, with maildirmake --checkutf8 foreach users' maildir OK, then maildirmake --convutf8 ... OK, while mail services (postfix, courier-imap-ssl, courier-imap, courier-pop3-ssl, courier-pop3) where stopped. Now I get multiple claims from our pop3 clients that they fail to retrieve messages, e.g. Mozilla Thunderbird shows the following: Command RETR failed. Error getting message. Mail server «pop.bsuir.by» replied /(That was my translation from Russian of the Thunderbird message, - E.S.)/: Cannot open message 1 /(or another number, - E.S.)/ because it is a Unicode message and your E-mail reader did not enable Unicode support. Please use an E-mail reader that supports POP3 with UTF-8 (see https://tools.ietf.org/html/rfc6856.html) One can download the maildir containing only one message that leads to the error, from https://yadi.sk/d/oQEZZ_0LqPsFxQ . I believe there is nothing wrong with the message, and I am sure there is nothing wrong with Thunderbird (latest version BTW), for if I send the message into trash and then bring it back to inbox, by means of an imap client, the pop3 client retrieves the message ok. I "repaired" the inbox of a user that above mentioned way: by means of an imap client (roundcube webmail) deleted all his mails from inbox, then brought them back to inbox, but in a couple of days the user gets another message that disables again his pop3 client because of "Command RETR failed" error. Another bad thing that occured while corier-imap upgrade 4.18.2 -> 5.0.2: All (!) our pop3 clients retrieved the copies of messages that were at the server (many of them failed to retrieve all their messages, because of the above mentioned "Command RETR failed" error). We use Courier-imap 5.0.2, Courier-unicode 2.1, maildrop 3.0.0, Courier-authlib 0.69.0 at openSUSE Linux 15.0. -- /Regards,/ /Eugene Suprun. / ___ Courier-imap mailing list Courier-imap@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-imap
