search for: 2.0beta3

>Date: Tue, 8 Dec 1998 11:00:42 -0500 (EST) >From: Rob Naccarato <rob@sheridanc.on.ca> >To: samba@samba.org >Subject: Can't connect to shares w/2.0beta3 on OSF1 > > >I was running 1.9.18p10 on a test DEC Unix 4.0d box here and I decided to >give 2.0beta3 a try. For some reason, I cannot connect to any of the >server's >shares or even get a list of

Hi, apparently the following change in dovecot hg * New revision (10876:370ee9717a6c) in dovecot Mercurial repository: - config: Forgot to add header file. broke listen = 83.170.6.69, 2001:1b10:1000::110:1:1 mail.svr02.mucip.net:~# dovecot -F -c /etc/dovecot/dovecot.conf doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:29: listen=..:port has been replaced by service {

Hi, another LMTP problem. When a sieve userscript tries to fileinto a nonexisting mailbox the LMTP process hangs. Mar 12 12:55:28 mail dovecot: lmtp(1328, berni at vmail.mail.mucip.net): kPpuOKArmkswBQAA/GZUZg: sieve: msgid=<201003111751.o2BHpTbX069309 at squid-cache.org>: failed to store into mailbox 'squidbugs': Mailbox doesn't exist: squidbugs after that I cannot get a LMTP

Le 17 mars 2010 ? 21:25:38, Timo Sirainen a ?crit : > On Wed, 2010-03-17 at 21:21 +0100, Renaud Allard wrote: >>>> dovecot_delivery transport output: lda: Fatal: User lookup failed: >>>> net_connect_unix(/opt/dovecot/etc/dovecot/dovecot.conf) failed: No such >>>> file or directory >>> >>> Yeah, I broke this yesterday. Fixed it today.

Hi Timo, are the latest 'Auth-Changes' supposed to be complete? They break 'alias at domain.tld' logins for me. Regards Thomas

Hello, I tried to install dovecot 2.0 beta3 and deliver seems to look for its config file in unusual places. In my exim logs, I get: 010-03-17 13:39:24 [31257] 1NrsWt-0004T0-1K <email at example.com>: dovecot_delivery transport output: lda: Fatal: User lookup failed: net_connect_unix(/opt/dovecot/etc/dovecot/dovecot.conf) failed: No such file or directory 2010-03-17 13:39:24 [31257]

Hi, with 'changeset 10910' the Auth master process is running as 'default_internal_user' now (dovecot). This requires permissions tuning for 'passwd-files' at least, while other plugins would run in a different user context, 'vmail' in my setup. I see that this may be safer, just wondering how to streamline the config: [20:27] root spectre:/var/vmail/conf.d# l

I was running 1.9.18p10 on a test DEC Unix 4.0d box here and I decided to give 2.0beta3 a try. For some reason, I cannot connect to any of the server's shares or even get a list of it's services (via Start->Run->\\server) from Win95 clients. It asks for a password and no matter what I put in there I get "The password is not correct. Try again." I configured Beta3 a la:

Latest from Mercurial. Dovecot crashes with 'mail_log' and 'notify' plugins enabled when deleting a message: [08:22] root spectre:~# gdb /usr/lib/dovecot/imap /tmp/core GNU gdb 6.8-debian Copyright (C) 2008 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and

Hi, captured a crash on mdbox with latest mercurial: Mar 9 13:56:28 spectre dovecot: imap(tlx at leuxner.net): Corrupted dbox file /var/vmail/leuxner.net/tlx/mdbox/storage/m.59 (around offset=1438073): msg header has bad magic value Mar 9 13:56:28 spectre dovecot: imap(tlx at leuxner.net): Corrupted dbox file /var/vmail/leuxner.net/tlx/mdbox/storage/m.59 (around offset=1438073): uid=4831

I'm trying to kickstart 2.0b3 on my NetBSD system (where 1.2.x works great!), and keep hitting: Fatal: service(tcpwrap) access(/software/dovecot-2.0beta3/libexec/dovecot/tcpwrap) failed: No such file or directory Indeed, that file doesn't exist...but I don't have nor want libwrap. It appears that doveconf includes tcpwrap... service tcpwrap { chroot = client_limit = 1

Dear samba-list! I just upgraded our linux-file server from the last samba version (1.19.-something??) to the 2.0beta3 since the speed-up effect seemed worth a try. I did this over the weekend to keep our network functional workdays... But now I've seen that only me can write and read properly from the different shares. The other users (I set up user level security as before) have some