similar to: 1.0.rc10 in inetd mode

http://dovecot.org/releases/1.1/rc/dovecot-1.1.rc10.tar.gz http://dovecot.org/releases/1.1/rc/dovecot-1.1.rc10.tar.gz.sig v1.1.0 will be released on next Friday if nothing horrible happens. * LIST X-STATUS renamed to LIST STATUS and fixed its behavior with LIST-EXTENDED options. It's now compatible with STATUS-IN-LIST draft 00. - Message parsing could have sometimes produced

http://dovecot.org/releases/1.1/rc/dovecot-1.1.rc10.tar.gz http://dovecot.org/releases/1.1/rc/dovecot-1.1.rc10.tar.gz.sig v1.1.0 will be released on next Friday if nothing horrible happens. * LIST X-STATUS renamed to LIST STATUS and fixed its behavior with LIST-EXTENDED options. It's now compatible with STATUS-IN-LIST draft 00. - Message parsing could have sometimes produced

I just installed a limited test of RC10 last night. So far, all is great except for errors being logged for one user (out of about 150 users total). This one user has not yet complained or anything, but the log file has repeated entries of the following format for him (host and username changed to protect the guilty/innocent): Oct 24 06:13:02 mail dovecot: IMAP(username): file

I don't recall if I mentioned this on the list, but when you are configured with mbox format, and a user has no Dovecot index files yet, and the config is such that mbox_min_index_size is set to non-zero, non-default (128 in my test case), dovecot deliver fails. Commenting out "mbox_min_index_size" fixed the problem, and the indexes then get created. This problems exists in RC10 --

Hi, On the weekend I tried to upgrade from RC7 to RC10. Clearly, I have to change some things before I can do this. What does it take to get to RC10? As is, my mail client got an error trying to list messages in /INBOX (via IMAP) and the mail.err log shows the following messages: Oct 29 10:27:32 siona dovecot: IMAP(archangel): open(/var/mail/archangel/inbox, O_CREAT) failed: Not a

Hi, i have 2 dovecot imap server running on solaris 10 The primary server with dovecot 1.0.alpha4 is running with best performance on Sun Sparc E4k5 with 8x 450MHz The secondary with rc10 has ugly performanceproblems on Sun E450 wth 4x 450MHz. Every new imap process takes permanent 25% cpu usage List the folder and fetch message are both slowy! Both servers are configred with ldap backend

Hello, For those interested (and yes, also to keep the topic warm), I have released the NHW v0.3.0-rc10 new version. I continue to fine-tune the nhw_kernel weights and pre_processing.This new version has then more precision and a better visual quality. More at: http://nhwcodec.blogspot.com/ Cheers, Raphael -------------- next part -------------- An HTML attachment was scrubbed... URL:

http://dovecot.org/releases/dovecot-1.0.rc10.tar.gz http://dovecot.org/releases/dovecot-1.0.rc10.tar.gz.sig I've finally read all the mails in the mailing list and in my INBOX. If I haven't replied to some of your mail, please resend it. Remember that since 1.0.rc9 release dovecot.index.cache files will get rebuilt in 64bit systems, and it's probably better to delete them manually so

http://dovecot.org/releases/dovecot-1.0.rc10.tar.gz http://dovecot.org/releases/dovecot-1.0.rc10.tar.gz.sig I've finally read all the mails in the mailing list and in my INBOX. If I haven't replied to some of your mail, please resend it. Remember that since 1.0.rc9 release dovecot.index.cache files will get rebuilt in 64bit systems, and it's probably better to delete them manually so

Are there anyone who has a machine on which the *current* version of SYSLINUX ends up with an inoperable USB keyboard, especially when using the menu system? I might have a workaround, but I don't have a system which exhibits the problem available to me at the moment, and I really don't want to put in a hack without knowing that it actually does anything... If you do have such a

After recently adding the -f parameter to the call to the deliver command which is called by Postfix, I found that e-mail with a null return path (MAIL FROM:<>) was causing Dovecot deliver to SEGFAULT. I verified this by making this patch to deliver.c (notice I fixed a typo here, too): *** deliver.c.orig Fri Oct 13 07:32:28 2006 --- deliver.c Fri Oct 27 21:26:08 2006 ***************

Hello, I mentioned back with version RC8 that dovecot was having an issue with the first login working, but all subsequent attempts failing with the error message: "Error: Maximum number of mail processes exceeded" in the dovecot log file. This is with an unchanged working conf file from RC7 (which, aside from comments, nothing has changed config-wise in the conf from version RC7).

I believe I have found the cause of the unexplained error (code ??) at main.c(line #). In the version I'm running 2.5.2 (obtained from the Free Software Foundation) the line number is 576. It appears the root cause is related to a race condition associated with the termination of child processes. If the signal handler for SIGCHILD is executed, as the result of a child termination, before the

I just upgraded our test server from rc6 to rc10... ISSUE #1 I noticed that we no longer are getting two "From_" lines. However, the one that was good (had the original sender e-mail address) is now gone. The one with "dovecot.deliver" remains. I attempted to add "-d test" to the mailbox_command line in main.cf as follows: mailbox_command =

(Background: Relatively new to dovecot; looking to do transparent replacement of long-established UW-IMAP on cluster of Linux boxes which NFS-mount a shared "/var/spool/mail".) With rc8, where I had already increased "login_max_processes_count" from default 128 to 1024, we had still hit the issue of too many logins crashing dovecot, so that trial had only lasted a couple of

Am 08.05.20 um 23:52 schrieb Bernd Petrovitsch: > I assume you are aware of https://en.wikipedia.org/wiki/CLOUD_Act > so using software from (heavily) US-based companies > implies that all data (controlled by said companies) will - > sooner or later - end up in the databases of > US-3-letter-organizations. > > So forget about GDPR compliance with such software > providers.

'--no-degraded' flag in the first mdadm call inhibits the startup of array unless all expected drives are present. This will prevent starting arrays in degraded state. Second mdadm call (after LVM is scanned) will scan unused yet devices and make an attempt to run all found arrays even they are in degraded state. Two new tests are added. This fixes rhbz1527852. Here is boot-benchmark

On Oct 14, 2011, at 9:04 PM, Hae-woo Park wrote: > I've met a problem that eliminates a live code in code generation phase. > > The initially generated code is shown as follows (as a pseudo code): > ( Before pseudo-code expansion. ) > > ---------- > loop: > : > : > set P0 <- xxx ( P0: a physical register for a parameter of function F ) > set P1

Timo, I finally made the time to backport a pam fix I created for proftpd over to dovecot, that allows FreeBSD's pam_group to work as expected. (the bug was escalated to me internally hehe.. ). I also noticed an issue while testing that will be confusing to users. If the docs stay as is, or the other half of this patch is applied, then when the dovecot.conf contains: passdb pam {

ok, so let's take stock of things on the first of august... fletcher penney has updated multimarkdown to 3.1... plus he's working on finalizing his editor-app, which it seems he has christened as "multimarkdown composer". brett terpstra is rewriting-from-scratch his "marked" app. ("better sooner than later", he says.) from my experience, i decide to