Displaying 20 results from an estimated 1200 matches similar to: "Big problems after upgrade from beta8 (FC5) to rc21"
2007 Feb 02
4
1.0.rc21 released
http://dovecot.org/releases/dovecot-1.0.rc21.tar.gz
http://dovecot.org/releases/dovecot-1.0.rc21.tar.gz.sig
Just one fix. Maybe the one big thing in Dovecot v2.0.* will be a test
suite, which is run before any release. :)
- Cache file handling could have crashed rc20
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type:
2007 Feb 02
4
1.0.rc21 released
http://dovecot.org/releases/dovecot-1.0.rc21.tar.gz
http://dovecot.org/releases/dovecot-1.0.rc21.tar.gz.sig
Just one fix. Maybe the one big thing in Dovecot v2.0.* will be a test
suite, which is run before any release. :)
- Cache file handling could have crashed rc20
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type:
2007 Feb 05
2
Nitpicking: rc21 startup banner says rc19
> [jhg at helios RPMS]$ rpm -q dovecot
> dovecot-1.0-1_42.rc21.fc5.at
but:
> dovecot: Feb 05 10:49:21 Info: Dovecot v1.0.rc19 starting up
2007 Feb 05
1
LDAP auth_bind=yes in rc21 = goodness
Hi all,
I finally got a chance to try out the fix for the LDAP auth_bind=yes
issues in production (using rc21). It seems to be working just fine even
after 24 hours of severe abuse.
Incidentally, I had switched to bsdauth+login_ldap (on OpenBSD) which was
often OK, but occasionally I would see Postfix smtpd throttled with SASL
errors due to "connection refused" on the Dovecot
2024 Sep 13
0
NHW v0.3.0-rc21 new version
Hello,
For those interested, I have released the NHW v0.3.0-rc21 new version.
I continue to fine-tune the nhw_kernel weights.This new version has more
precision and a better visual quality.
If you don't agree with this new version, do let me know and I'll revert
the commit.
More at: https://nhwcodec.blogspot.com/
Cheers,
Raphael
-------------- next part --------------
An HTML
2007 Feb 05
2
--log-error and the mysterious "not starting" problem
I've finally upgraded to 1.0.rc21. If I run "dovecot --log-error", then
dovecot fails to start. The following appears in the log:
Feb 5 10:54:00 taurus1 dovecot: Dovecot v1.0.rc21 starting up
Feb 5 10:54:00 taurus1 dovecot: This is Dovecot's error log
Without --log-error, it will start up fine from command-line.
Dovecot still fails to start, as near as I can tell, in the
2012 Sep 07
0
Samba4 beta8: samba daemon doesn' t start nmbd daemon !
Hi anybody.
I use Samba4 beta8 as AD DC. But also I need fully working file server with
showing it at neighborhood.
In Samba4 beta6 I run samba as main daemon, then nmbd that server could be
showed at neighborhood.
But in beta8 doc is written: "When running an AD DC, you only need to run
'samba' (not nmbd/smbd/winbind), as the required services are co-coordinated
by this master
2007 Nov 11
3
v1.1.beta8 released
http://dovecot.org/releases/1.1/beta/dovecot-1.1.beta8.tar.gz
http://dovecot.org/releases/1.1/beta/dovecot-1.1.beta8.tar.gz.sig
Changes since beta7:
- Added a new "raw" mail storage backend which allows opening
files/streams as single mail mailboxes. deliver uses this now instead of
opening the incoming mail as a mbox. So deliver should be now faster and
it doesn't anymore remove
2008 Apr 22
1
Asterisk 1.2.28, 1.4.19.1, and 1.6.0-beta8 Released
The Asterisk development team has released versions 1.2.28, 1.4.19.1, and
1.6.0-beta8.
All of these releases contain a security patch for the vulnerability described
in the AST-2008-006 security advisory. 1.6.0-beta8 is also a regular update to
the 1.6.0 series with a number of bug fixes over the previous beta release.
Early last year, we made some modifications to the IAX2 channel driver to
2008 Apr 22
1
Asterisk 1.2.28, 1.4.19.1, and 1.6.0-beta8 Released
The Asterisk development team has released versions 1.2.28, 1.4.19.1, and
1.6.0-beta8.
All of these releases contain a security patch for the vulnerability described
in the AST-2008-006 security advisory. 1.6.0-beta8 is also a regular update to
the 1.6.0 series with a number of bug fixes over the previous beta release.
Early last year, we made some modifications to the IAX2 channel driver to
2006 May 14
2
beta8: complaint about tilde at startup
Timo,
After installing beta8 on Solaris 10 sparc and starting it for the
first time, I noticed this in my syslog:
May 14 19:35:45 emerald dovecot: [ID 475045 mail.info] Dovecot v1.0.beta8 starting up
May 14 19:35:47 emerald dovecot: [ID 536776 mail.error] stat(~) failed: No such file or directory
The only appearance of the tilde (~) in my dovecot.conf is here:
default_mail_env =
2012 Oct 06
1
Samba 4: character encoding issue (was: Samba-tool dbcheck shows "incorrect GUID" after update from alpha17 to beta8)
Hi
On 5 October 2012 21:25, <X-Dimension at gmx.net> wrote:
>
> -------- Original-Nachricht --------
>> Datum: Thu, 4 Oct 2012 12:22:54 +0200
>> Von: Michael Wood <esiotrot at gmail.com>
>> An: Julian Timm <X-Dimension at gmx.net>
>> CC: samba at lists.samba.org
>> Betreff: Re: [Samba] Samba-tool dbcheck shows "incorrect GUID" after
2006 Jun 19
2
beta8 + mbox + Thunderbird
Hi all,
I'm still using beta8 (on FreeBSD 5.4-RELEASE).
Recently I put a co-worker who's using Thunderbird (1.5.0.4) on it and
he seemed to have lost some messages (which were delivered on the
spool since seen on procmail logfile).
I switched him on another server to play safe and tried to test it
myself but failed to reproduce the issue. I myself use mutt on a daily
basis with no
2006 May 29
1
beta8 starts but no POP3 access
Hi
I just compiled stock beta8 on FC3 with
./configure
make
make install
all looked ok and i changed my dovecot.conf to suit.
start dovecot and i see it running
May 29 08:18:00 Info: Dovecot v1.0.beta8 starting up
POP3 to 1 account and
May 29 08:18:06 Info: auth(default): client in: AUTH 1 PLAIN service=POP3
lip=xx.xx.xx.xx rip=yy.yy.yy.yy resp=<hidden>
May 29 08:18:06 Info:
2006 Nov 20
1
cache_key assertion error 1.0.beta8
I just added auth caching with pam, and I'm getting this error:
dovecot: [ID 107833 mail.error] auth(default): file passdb.c: line 178
(passdb_init): assertion failed: (passdb->passdb->default_pass_scheme !=
NULL || passdb->passdb->cache_key == NULL)
A google search turns up
<http://www.dovecot.org/list/dovecot-cvs/2005-March/004117.html>
which looks approx like this
2006 May 12
1
beta8 compile error
Hello,
On FreeBSD 5.4-RELEASE dovecot-1.0.beta8 build cause the following
error :
---------------------------------------------
make all-recursive
Making all in src
Making all in lib
if gcc -DHAVE_CONFIG_H -I. -I. -I../.. -I /usr/local/include/db41 -I/usr/local/include -std=gnu99 -g -O2 -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2
2012 Oct 03
1
Samba-tool dbcheck shows "incorrect GUID" after update from alpha17 to beta8
After updating our Samba4 server from alpha17 to beta8 "samba-tool dbcheck" shows 24 "incorrect GUID" errors.
What does it mean and what should i do to fix this?
Thx
2007 Nov 20
1
1.1.beta8 crashes with segfault when SIGHUP
Hello,
dovecot crashes when it receives -HUP signal. It happens always if there was
some activity - for example, if I start dovecot, check any account through
POP3 and then send -HUP to dovecot process, it crashes with the following log
entry:
segfault at 00000008 eip 0804d3fb esp bfdd3860 error 4
If there were no activity at all since starting, it does not crash.
my dovecot -n output:
#
2006 May 19
4
beta8: core, signal 11
Timo,
The gdb analysis is attached. It looks like memory got seriously
stomped in this core dump. There was no assert or other useful
information in the syslog. My setup: Solaris 9, imap and imaps,
mbox format, INBOXes NFS mounted, index files on local ufs
filesystem, beta8 configured like so:
VERSION=1.0.beta8
CC=gcc CFLAGS="-g -O" CPPFLAGS=-I/opt/openssl/include
2012 Oct 03
1
Wrong menu language on Windows 7 clients after update to Samba4 beta8
After updating from Samba4 alpha 17 to beta8 most Windows start menu entries on our Windows 7 clients are in english now, instead of german.
Also the desktop.ini files are not hidden anymore like it was before.
What goes wrong here?
Do i need to set a new parameter in smb.conf or mount the filesystem with some attributes?
Thanks for help