similar to: Dovecot still failing with RC10...

Displaying 20 results from an estimated 300 matches similar to: "Dovecot still failing with RC10..."

2006 Jun 09
1
Can't run POP3 and IMAP simultaneously from xinetd...
Hello all, I'm hoping you can help out with an issue I'm having running dovecot-beta8 on Solaris 9 (SPARC). The reason I need to run them from xinetd is that we require the filtering ability that tcp_wrappers provide. My issue is that, when running both from xinetd, IMAP runs fine, but then, when you try to POP in to check mail on the same box, it seems that the login section is
2006 Oct 10
1
RC8 failing...
I just tried upgrading from RC7 to RC8 this morning, and I'm seeing an issue I've never seen before. On my first POP3 login, all is fine, but any subsequent logins seem to fail with the message: dovecot: Oct 10 11:04:31 Error: Maximum number of mail processes exceeded In the dovecot log file. I'm also oddly seeing the message: Oct 10 11:01:05 popbkup pop3-login: [ID 799321
2015 Oct 14
2
[PATCH 1/2] lib: info: Move common code for setting child rlimits.
This is almost just refactoring, but I also set the memory limit to really 1 GB, and not 1×10⁹. --- src/info.c | 27 +++++++++++++++------------ 1 file changed, 15 insertions(+), 12 deletions(-) diff --git a/src/info.c b/src/info.c index d7f45f0..616ef50 100644 --- a/src/info.c +++ b/src/info.c @@ -56,6 +56,7 @@ static yajl_val get_json_output (guestfs_h *g, const char *filename); static char
2008 Jun 13
5
v1.1.rc10 released
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
2008 Jun 13
5
v1.1.rc10 released
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
2006 Oct 24
1
RC10 errors
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
2006 Nov 20
1
Problem with rc10, perhaps 11-15
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 --
2006 Oct 30
2
Upgrade from RC7 to RC10 didn't go too well...
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
2006 Oct 19
2
performance problems with rc10 and solaris 10
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
2015 May 26
0
[PATCH] lib: Limit space and time used by 'qemu-img info' subprocess.
After fuzzing 'qemu-img info' I found that certain files can cause the command to use lots of memory and time. Modify the command mini-library to allow us to place resource limits on subprocesses, and use these to limit the amount of space and time used by 'qemu-img info'. --- configure.ac | 3 +++ src/command.c | 53
2024 Jan 24
0
NHW v0.3.0-rc10 new version
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:
2006 Oct 15
2
1.0.rc10 released
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
2006 Oct 15
2
1.0.rc10 released
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
2006 Oct 18
1
1.0.rc10 in inetd mode
Hey.. I'm finding that I can force dovecot (setup in inetd mode) into a wedged state by spamming it with carrage returns. As I've not had enough time to familiarize myself with the code.. I thought I'd ping the list before 1.0 is christened. -Phil.
2006 Oct 28
2
BUG in RC10 deliver using mbox format
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 ***************
2006 Oct 17
4
Problem with rc10
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 =
2006 Oct 20
4
1.0.rc10 status report
(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
2001 Feb 08
0
openssh2.3.0p1 and /etc/limits
Hi! I wrote a small patch to enable /etc/limits support in openssh. nice thing when you don't have PAM installed.. It is based on Ultor's openssh 1.x patch (http://marc.theaimsgroup.com/?l=secure-shell&m=96427677022741&w=2) Works fine on slackware7.1. define USE_ETC_LIMITS in config.h , and compile as usual. Sagi -------------- next part -------------- diff -N -u
2008 Jul 10
2
A couple of dovecot issues I've noted recently...
Timo et al., I haven't been reading the list in a while, but wanted to report back that we've transitioned to dovecot 1.0.15 and things look to be working very nicely. The platform is Solaris "Nevada" running on x86. I have been saving up a couple of issues to bring to your attention. On our server, we gather all core files, and so we get a good taste of the different things
2016 May 09
2
R process killed when allocating too large matrix (Mac OS X)
On 05/05/2016 10:11, Uwe Ligges wrote: > Actually this also happens under Linux and I had my R processes killed > more than once (and much worse also other processes so that we had to > reboot a server, essentially). I found that setting RLIMIT_AS [1] works very well on Linux. But this requires that you cap memory to some fixed value. > library(RAppArmor) > rlimit_as(1e9) >