similar to: 0.99.10-test12

http://dovecot.procontrol.fi/test/ - Hopefully OpenSSL is fixed :) - We sometimes produced invalid ENVELOPE with 8bit headers. That could really have broken things (broke it in test12). So, what's left is to make PAM work well..

http://dovecot.org/test/ - "Maildir sync: UID < next_uid (446 < 447, file = .." errors should be fixed - fixes for detecting changes in uidvalidity and external uidnext changes - several fixes and cleanups in index file handling. less code than before and now changes to index header also go through transaction log. that should mean that soon I can get mmap_disable = yes

I've been seeing the Dovecot/SSL/Fedora 1 problem. I have a dovecot server which tends to die at least once a day, with messages like these :- May 24 13:44:44 mail pop3-login: RAND_bytes() failed: error:24064064:random number generator:SSLEAY_RAND_BYTES:PRNG not seeded May 24 13:44:44 mail dovecot: Login process died too early - shutting down I noticed Timo's email about this at:

What I want to do is pop my email off of a Pop3 server and give it to dovecot for imap serving. Does anyone know of a utility that will allow me to do this? I looked at fetchmail but it seems to want to talk to an SMTP server. Thanks, Brad -- Brad Figg - brad at tpi.com 503.601.0235 ext. 105 TriplePoint, Inc. - http://www.tpi.com

Hi Reuben, I hope you don't mind me copying the dovecot list again. > dovecot: Aug 21 04:08:22 Error: IMAP(reuben): inotify_rm_watch() failed: > Invalid argument Odd. > This is with a 2.6.13-rc6-mm1 release. I've posted to LKML because there is > also a kernel stack produced at one point which looks inotify related (but the > messages above are contant). > See

Hi, with current test releases SSL doesn't work anymore for me on AIX 4.3 with dovecot-0.99.10-test14. It worked with 0.99.9.1. dovecot: Jun 23 19:42:23 Info: Dovecot starting up imap-login: Jun 23 19:42:25 Fatal: RAND_bytes() failed: error:24064064:random number generator:SSLEAY_RAND_BYTES:PRNG not seeded imap-login: Jun 23 19:42:25 Fatal: RAND_bytes() failed: error:24064064:random number

Helo List, Sorry I missed the rest of my email in my previous post. Please see below. I'm having an issue using the AND (&) operator evaluation in the code of my dialplan. The dial plan is coded to detect inbound DTMF digits from callers. key "1" is equivalent to "yes" and key "2" is equivalent to "no" in two diferent contexts in the dial plan.

(Sorry, just joined the list, can't reply in the original message from Feb 4.) > Hi, > Dovecot (pre-compiled version of Fedora Core 1, configured for Maildir) > is running fine for me since a few days. It happened now twice to me > that dovecot died with the following error message in /var/log/maillog: > > Feb 4 11:18:27 hundehuette imap-login: RAND_bytes() failed: >

Hi, Yesterday I tried to replace the system openssl in a gentoo system with libressl. With openssh an interesting issue popped up: * RAND_bytes in libressl calls arc4random * arc4random is a compat function both in openssh and libressl * arc4random from openssh uses RAND_bytes So what's happening is a recursion. arc4random wants to use RAND_bytes and RAND_bytes wants to use arc4random. The

Hello All, I'm new to the list and I don't have much of experience with samba. I have a test setup on CentOS 7.8 with samba-4.10.4 and samba-vfs-glusterfs . When my client mounts the samba share via vers=1.0 , the user sees the share properly (uid,gid,mode are just like on gluster). When the share is mounted with vers=2.0 or not specified (anything higher) the files are owned by

Hello, I have been doing some looking at openssl 0.9.7 and openssh3.5p1 and found a minor descrepancy. RAND_bytes() is called around line 69 of openbsd-compat/bsd-arc4random.c. It checks to see if the return is not zero. The RAND_bytes function can also return -1, too. All the code in openssl uses <=0 for the test rather than !. Best Regards, Steve Grubb

First let me thank you for my initial newby question about poping from a pop3 server and delivering into my Dovecot maildir folders. Now I'm getting an assertion in imap-bodystructure.c and one of my imap folders is now inaccessable. I think the two are related. Whenever I select the folder from my email client (kmail) I get two log entries in the dovecot log of the format:

Hi, I am happy to (re)send a set of patches for compiling OpenSSH 4.7p1 with FIPS 140-2 OpenSSL. These are based on previously reported patches by Steve Marquess <marquess at ieee.org> and Ben Laurie <ben at algroup.co.uk>, for ver. OpenSSH 3.8. Note that these patches are NOT OFFICIAL, and MAY be used freely by anyone. Issues [partially] handled: SSL FIPS Self test. RC4,

Although the specific behaviour that was reported has been fixed, bugs remain in Sweave's processing of comment lines when keep.source=TRUE This is in some senses a follow-up from earlier bugs. Hence the query -- what is the preferred procedure, to submit a new bug report? (Another option might be to add a comment to the web page for bug 14459.) Is there now a preference to submit via

Hello! This is my first time trying to run dovecot so maybe I've overlooked something, but I'm having a hard time running dovecot. First of all, it's worth noting that I'm trying to run dovecot on an embedded platform: the target architecture is mipsel; I have patches for the 2.4.18 kernel with special support for the board so I'm still using the 2.4.18 kernel. My C library

Hi, I have a Samba4 domain controller installed on Debian Wheezy (Domain = CHEZMOI.PRIV). I try to installed an another Samba4 server which is just a member of the CHEZMOI.PRIV domain. But I don't succeed. I have followed this page : https://wiki.samba.org/index.php/Samba4/Domain_Member But I have : ~# net ads join -U administrator Enter administrator's password: kinit succeeded but

Hello all llvm-link merges together the metadata from the IR files being linked together. This means that when linking different libraries together (i.e. multiple source files that have been compiled into a single LLVM IR file) it can be hard or impossible to identify the library boundaries. We're using LLVM to do static analysis of applications (together with their dependent libraries) and

I woke up this morning and my dovecot server had died with the following in the dovecot.log file: pop3-login: Jan 23 10:23:08 Fatal: RAND_bytes() failed: error:24064064:random number generator:SSLEAY_RAND_BYTES:PRNG not seeded dovecot: Jan 23 10:23:08 Error: Login process died too early - shutting down dovecot: Jan 23 10:23:08 Error: child 16321 (login) returned error 89 How can I find out

Aloha, again, Timo. Concerning the problem of copying within one folder... I'm still not sure it's not a problem I created myself, but I think it's caused by the use of the buffered IO routines in ostream-file.c ... you use io_add() to schedule write operations for later while simultanously reading new chunks from the very same file. This seems to confuse dovecot and make it write

I hacked some command line options into imaptest. I dont think I broke it.. Place into dovecot-source root as usual and compile with: gcc imaptest.c -o imaptest -Wall -W -I. -Isrc/lib -DHAVE_CONFIG_H src/lib/liblib.a As per Timo's instructions. # imaptest -h imaptest [USER at IP:PORTNO] [pass=PASSWORD] [mbox=MBOX] [clients=CC] [msgs=NMSG] [use_authenticate] [PORTNO] USER = template for