Tere.
Your PAM modules are getting stuck. Probably has nothing to do with
Dovecot itself.
But I haven't change/install/upgrade anything, but the Dovecot. And
version 1.0.3 gives errors like crazy, 1.0.2 from time to time and older
versions none? Seems something in new Dovecot versions
On 9.9.2007, at 11.00, Mart Pirita wrote:
Your PAM modules are getting stuck. Probably has nothing to do with
Dovecot itself.
But I haven't change/install/upgrade anything, but the Dovecot. And
version 1.0.3 gives errors like crazy, 1.0.2 from time to time and
older versions none? Seems
Tere.
The only changes to dovecot-auth between 1.0.2 and 1.0.3 were for LDAP
code, which you aren't using. So I think the problem has more to do
with the binary getting compiled a bit differently, causing random
problems in a buggy PAM module.
Ok.
So where do PAM and passwd do the lookups
Timo Sirainen wrote:
On Fri, 2007-09-07 at 15:20 +0100, Ed W wrote:
Hi
Is it legal/sensible to use the following in the conf file
# default namespace
namespace private {
separator = /
prefix =
inbox = yes
}
# for backwards compatibility:
namespace private {
separator = .
prefix
On Vas, Szeptember 9, 2007 06:01, Timo Sirainen wrote:
On Sat, 2007-09-08 at 15:04 +0200, Farkas Levente wrote:
Timo Sirainen wrote:
But since there's still a chance that index files could break
(although
v1.1 tries harder than v1.0 to fix problems), it would be nice if the
Hi,
Monday, September 3, 2007, 23:16:07, you wrote:
One more piece of info that might (?) be interesting -- I have just
run a grep on historical logs and it seems the bug never occured on
previous versions of Dovecot I had been running in the past (first
it was stock Suse 9.3 Dovecot
Hi,
Saturday, September 8, 2007, 2:29:45, you wrote:
0x0806049d in imap_sync_more (ctx=0x80d9770) at imap-sync.c:104
104 if (ctx-seq == 0) {
A short follow-up on this, looks like an infinite loop to me, unless
some threading magic is supposed to happen here:
Fixed:
On Sep 9, 2007, at 12:21 AM, Timo Sirainen wrote:
http://dovecot.org/releases/1.0/dovecot-1.0.5.tar.gz
http://dovecot.org/releases/1.0/dovecot-1.0.5.tar.gz.sig
Just a reminder:
http://www.dovecot.org/download.html needs updating to reflect the
availability of the new version.
B. Bodger
On 9.9.2007, at 13.54, Bruce Bodger wrote:
On Sep 9, 2007, at 12:21 AM, Timo Sirainen wrote:
http://dovecot.org/releases/1.0/dovecot-1.0.5.tar.gz
http://dovecot.org/releases/1.0/dovecot-1.0.5.tar.gz.sig
Just a reminder:
http://www.dovecot.org/download.html needs updating to reflect the
Thanks, I updated in the meantime to 1.02, which is currently the newest
in OpenBSD 4.0 packages. The problem has vanished completely.
Performance has gone up in general a lot, too.
This is a wonderful programme, thanks Timo, for your hard work and for
responding to a newbie's question
Peter
Hi, Quick feature request for the proxy function:
I have a couple of machines which are all customer facing and customer
mailbox lives on any one of them. Customer can login to any machine and
the proxy feature then forwards them to the correct machine (often the
machine they are already
I guess it depends on what your Sieve code looks like? Or does it give
the same error even if your script is only keep;?
It doesn't depend on the script. Even the simplest script stop; gives
this error. I added two debug strings to cmusieve_deliver_mail in
cmusieve-plugin.c:
if (getenv(DEBUG)
Hello,
I'm using postfix(2.4.5) and dovecot(1.0.5), and till now I have been
using postfix deliver agent. Now I have tried to reconfigure postfix to
use the dovecot LDA, but I'm getting some strange error:
Sep 9 18:07:57 hostname deliver([EMAIL PROTECTED]): BUG: Unexpected
input from auth
* Timo Sirainen [EMAIL PROTECTED]:
On Sat, 2007-08-18 at 10:31 +0200, Ralf Hildebrandt wrote:
* Ralf Hildebrandt [EMAIL PROTECTED]:
Maybe it worked, since I see that particular User NOT getting the
errors anymore.
Seems to be a particular folder he's accessing:
Aug 18
14 matches
Mail list logo
