Chris Laif wrote:
On Tue, Jul 8, 2008 at 5:39 PM, Proskurin Kirill [EMAIL PROTECTED] wrote:
Error: auth(default): password([EMAIL PROTECTED],172.16.1.19): Invalid password
format for scheme CRAM-MD5
dovecot-ldap.conf:
default_pass_scheme = CRAM-MD5
Set default_pass_scheme to PLAIN as you
Hi,
I'm using dovecot v1.0.rc15 (from debian etch) and I have some performance
problems.
Every time I log in I see the following in the mail log:
Jul 8 21:05:31 myserver dovecot-auth: (pam_unix) check pass; user unknown
Jul 8 21:05:31 myserver dovecot-auth: (pam_unix) authentication
Hi all,
Sorry for the mail below, we have found the solution.
We had to comment out the passdb pam { line in dovecot.conf althoug this
section was empty. This
solved all the problems.
Bye,
zs-
Hi,
I'm using dovecot v1.0.rc15 (from debian etch) and I have some performance
problems.
Greetings,
I recently upgraded our server from Dovecot 1.0.14 to 1.1.1. I am building
using the FreeBSD ports system, so nothing is custom aside from the flags
set there.
dovecot fell down a few days after the update with:
pid 1823 (imap), uid 1000: exited on signal 11
the mail log shows:
Hi Friends,
I'm running postfix 2.2.10, dovecot-0.99.11 and openldap -2.2.13 in my
organization. Here, all my postfix, dovecot, saslauthd, depends on ldap
only. Means ldap is acting as a centralized database for user information.
In this picture everything is working fine except user login to
I'm looking for some help with an nfs error that is filling our logs. I
get a constant stream of these messages:
Jul 8 10:47:08 servername dovecot: [ID 107833 mail.error]
IMAP(username): nfs_flush_file_handle_cache_dir: rmdir(/var/mail)
failed: Device busy
I have two dovecot IMAP
Bill Cole wrote:
You might even be better off configuring your system to not use the
TSC as a clock source. There's a strong chance that you won't really
be sacrificing anything that you actually use.
Time to conclude on this.
Rather than going along with my Dovecot hack, I went and changed
Hi all,
With some help of this list, I've managed to set up some mailboxes keeping
\Seen flags as private. Thanks Timo for updating the documentation about
that.
But now, I've got another question: is it possible to keep those flags as
private and have shared keywords (Junk, NotJunk, etc.)? I
El Wednesday 09 July 2008 10:35:24 Imobach González Sosa escribió:
Hi all,
With some help of this list, I've managed to set up some mailboxes keeping
\Seen flags as private. Thanks Timo for updating the documentation about
that.
But now, I've got another question: is it possible to keep
Apparently it doesn't like that I try to fsync() a read-only
directory file descriptor.
I would argue that NetBSD is correct in this.
Posix says:
The fsync() function shall request that all data for the open file
descriptor named by fildes is to be transferred to the storage
device
On Jul 9, 2008, at 3:48 PM, Edgar Fuß wrote:
Apparently it doesn't like that I try to fsync() a read-only
directory file descriptor.
I would argue that NetBSD is correct in this.
Posix says:
The fsync() function shall request that all data for the open file
descriptor named by fildes is
On 7/8/2008, Hari ([EMAIL PROTECTED]) wrote:
Version Details:
Dovecot: dovecot-0.99.11
Postfix:postfix-2.2.10
Openldap: openldap-2.2.13
Thats far enough...
Time to upgrade. Every one of these is ancient.
--
Best regards,
Charles
On 7/8/2008, Michael B Allen ([EMAIL PROTECTED]) wrote:
dovcot 1.0.rc15.
Upgrade, this is very old...
--
Best regards,
Charles
Hans Wunsch wrote:
I'm looking for some help with an nfs error that is filling our logs. I
get a constant stream of these messages:
Jul 8 10:47:08 servername dovecot: [ID 107833 mail.error]
IMAP(username): nfs_flush_file_handle_cache_dir: rmdir(/var/mail)
failed: Device busy
What OS are
If there is no 3 and the server crashes just after 4, I don't think
the rename() was guaranteed to have reached the disk.
OK, I understand.
If NetBSD doesn't support this, what other way is there to do it?
I don't know of a way of doing this. The problem probably is that
metadata writes
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
Hi all.
Looking at previous weeks logs I discovered strange errors: file
mail-transaction-log-view.c: assertion failed
dovecot v 1.0.12
Server is hosting more than 500 virtual users. It is compleate dovecot error
log; only my own mailbox is affected ...and imap folder affected is dovecots
17 matches
Mail list logo
