On Thu, 2009-01-15 at 17:50 +0100, Martin Sengstschmid wrote:
> dovecot: Jan 15 17:38:55 Info: IMAP(b...@abcshop.at): maildir++:
> root=/usr/local/mail/abcshop.at/bamm/Maildir, index=, control=,
> inbox=/usr/local/mail/abcshop.at/bamm/Maildir
> dovecot: Jan 15 17:39:00 Info: IMAP(b...@abcshop.at)
dovecot.conf
auth_verbose = yes
auth_debug = yes
auth_debug_passwords = yes
mail_debug = yes
log_path=/var/log/dovecot.log
info_log_path=/var/log/dovecot-info.log
.
after dovecot restart
I got following LOG-files
Martin
dovecot-info.log:
dovecot: Jan 15 17:38:55 Info: auth(default):
On Thu, 2009-01-15 at 16:53 +0100, Martin Sengstschmid wrote:
> Although imap-Login seems to work dovecot doesn't write
> /usr/local/mail/abcshop.at/bamm
> /usr/local/mail/abcshop.at/bamm/Maildir
>
> The directory /usr/local/mail/ is owned by virtual:virtual (2000:2000)
>
> dovecot.conf
> .
Hallo,
Although imap-Login seems to work dovecot doesn't write
/usr/local/mail/abcshop.at/bamm
/usr/local/mail/abcshop.at/bamm/Maildir
The directory /usr/local/mail/ is owned by virtual:virtual (2000:2000)
dovecot.conf
.
auth_verbose = yes
auth_debug = yes
auth_debug_passwords = yes
log_p
Although "LOGIN" worked
in dovecot-info.log is written
dovecot: Jan 13 19:32:12 Info: imap-login: Aborted login (auth failed, 1
attempts): user=, method=PLAIN, rip=127.0.0.1,
lip=127.0.0.1, secured
Martin
Patrick Ben Koetter schrieb:
* Martin Sengstschmid :
Hallo,
thank you for trying
* Martin Sengstschmid :
> Hallo,
>
> thank you for trying to help me:
Welcome.
What does the Dovecot Log say?
p...@rick
>
> the bamm.ldif file is
> ldapsearch -x -LLL -b
> "uniqueidentifier=b...@abcshop.at,ou=it,ou=people,dc=abcshop,dc=at"
> "(objectclass=*)"
>
> dn: uniqueidentifier=b...
Hallo,
thank you for trying to help me:
the bamm.ldif file is
ldapsearch -x -LLL -b
"uniqueidentifier=b...@abcshop.at,ou=it,ou=people,dc=abcshop,dc=at"
"(objectclass=*)"
dn: uniqueidentifier=b...@abcshop.at, ou=it,ou=people,dc=abcshop,dc=at
objectClass: organizationalPerson
objectClass: pers
* Martin Sengstschmid :
> Hallo,
> I want to run postfix - dovecot - openldap working together
>
> The first problem is, that dovecot doesn't create the directories
>
> /usr/local/mail/abcshop.at/bamm/Maildir
> cur
> new
> tmp
>
> although I can contact the Dovecot-Server
>
> telnet localhost 143
>
Hallo,
I want to run postfix - dovecot - openldap working together
The first problem is, that dovecot doesn't create the directories
/usr/local/mail/abcshop.at/bamm/Maildir
cur
new
tmp
although I can contact the Dovecot-Server
telnet localhost 143
OK
1 login b...@abcshop.at secret
OK Logg
On Thu, 2007-03-15 at 11:33 -0700, Troy Engel wrote:
> This would not block/stall in the pipelines, not cause memory leaks
> (since underlying code is released each cycle), avoid/fix nss_ldap
> issues with file descriptor reuse.
>
> Do I finally have a good understanding now? (thanks for taking
Timo Sirainen wrote:
blocking=yes doesn't break anything with nss_ldap, since without
blocking=yes it'll run in one process anyway. PAM works differently.
Thanks for clarifying that.
You're somehow mixing up these things. :) Probably because of the
"blocking" naming, which actually does the
On Thu, 2007-03-15 at 10:58 -0700, Troy Engel wrote:
> Timo Sirainen wrote:
> >
> > Yes, http://wiki.dovecot.org/PasswordDatabase/PAM explains what it does
> > and why it might not be a good idea. Although no-one has yet reported
> > any success/failure stories, those are all my own guesses..
>
>
Timo Sirainen wrote:
Yes, http://wiki.dovecot.org/PasswordDatabase/PAM explains what it does
and why it might not be a good idea. Although no-one has yet reported
any success/failure stories, those are all my own guesses..
I gotcha, makes sense having read it. Now I'm back on the fence, as I'l
On Wed, 2007-03-14 at 11:38 -0700, Troy Engel wrote:
> Timo Sirainen wrote:
> >
> > I accidentally added it to passdb instead of to userdb. It doesn't at
> > least currently work in passdb passwd (although it could, but does
> > anyone use it anyway?)
>
> OK thanks for that, but I'm still a bit c
Timo Sirainen wrote:
I accidentally added it to passdb instead of to userdb. It doesn't at
least currently work in passdb passwd (although it could, but does
anyone use it anyway?)
OK thanks for that, but I'm still a bit confused -- I'm after the second
part of the wiki entry in relation to n
On Wed, 2007-03-14 at 11:02 -0700, Troy Engel wrote:
> The example conf lists blocking=yes in the passdb {} blocks, but the
> Wiki specifically gives an example for a userdb{} block. Is blocking=yes
> applicable to both types of blocks? Should I be setting it both places?
I accidentally added it
Thanks Timo!
-Original Message-
From: Timo Sirainen [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 14, 2007 12:39 PM
To: Ejay Hire
Cc: 'Arto Saraniva'; dovecot@dovecot.org
Subject: Re: [Dovecot] Postfix+Dovecot+LDAP
On Wed, 2007-03-14 at 12:20 -0500, Ejay Hire wrote:
>
Timo Sirainen wrote:
On Wed, 2007-03-14 at 12:20 -0500, Ejay Hire wrote:
The general consensus was that nss_ldap has some emotional problems and
dovecot seems to annoy it Kind of like poking an angry snapping turtle
with a stick.
The problem has been found since and it can be worked around
On Wed, 2007-03-14 at 12:20 -0500, Ejay Hire wrote:
> The general consensus was that nss_ldap has some emotional problems and
> dovecot seems to annoy it Kind of like poking an angry snapping turtle
> with a stick.
The problem has been found since and it can be worked around:
http://wiki.dovec
>> 2. Do not use PAM and Ldap and then let dovecot talk to pam. It is bad.
>> Don't do it.
>> 2a. Unless you like users digging around in random mailboxes.
>> 2b. NSCD is broken and should not be trusted.
>
> Erm... since I'm running precisely this kind of setup, could you
> please add some
[EMAIL PROTECTED] wrote:
Quoting Ejay Hire <[EMAIL PROTECTED]>:
2. Do not use PAM and Ldap and then let dovecot talk to pam. It is bad.
Don't do it.
2a. Unless you like users digging around in random mailboxes.
2b. NSCD is broken and should not be trusted.
Erm... since I'm running precise
Quoting Ejay Hire <[EMAIL PROTECTED]>:
2. Do not use PAM and Ldap and then let dovecot talk to pam. It is bad.
Don't do it.
2a. Unless you like users digging around in random mailboxes.
2b. NSCD is broken and should not be trusted.
Erm... since I'm running precisely this kind of setup, cou
This message does not contain a bug report or any issues. It is a summary
of my experiences with Postfix, Dovecot, and Ldap.
1. Do not use Dovecot 0.99, even if it's what your vendor has packaged.
1a. ... When you upgrade past 0.99, you'll get some double mail because of
UIDL's.
2. Do not use
23 matches
Mail list logo
