Re: [Dovecot] LDA questions

2008-12-08 Thread Romer Ventura
Well I got it working.. I had a typo on my LDAP config for postfix so that's
why the user info wasn't found.

Now we in order to activate an Active Directory account all we have to do is
assign an email address to the mail field on the users properties tab and
works with no problems.

The only thing is that it does 2 lookups every time a user checks for
emails, but since we only have about 120 users and the number not likely to
get any bigger any time soon it should be ok for the next few years.

Thanks for the help..


On 12/7/08 11:57 AM, Timo Sirainen [EMAIL PROTECTED] wrote:

 On Sun, 2008-12-07 at 20:21 +0300, Dmitri V. Ivanov wrote:
 On Fri, Dec 05, 2008 at 09:17:58PM +0200, Timo Sirainen wrote:
 
 Like Matt said, this is a Postfix configuration issue. You'll have to
 configure Postfix to figure out what users exist.
 
 One question. Postfix has TCP lookup table type with a very simple
 protocol: (get|put) space key newline.
 
 Also I think there was some user lookup protocol that originated from
 Sendmail. Dovecot should support that some day..
 
 But there is a question: how would act dovecot with much lookups with
 nonexistant users (there is no big problem to write some stupid
 connector)?
 
 Shouldn't be a problem.
 

-- 
Romer Ventura
Network Administrator
Houston-Sigma Technologies, L.P.
1333 Industrial Blvd. Sugar Land Tx. 77478
Voice 281-295-5017
[EMAIL PROTECTED]




Re: [Dovecot] LDA questions

2008-12-08 Thread Thomas Siebert
 
 The only thing is that it does 2 lookups every time a user checks for
 emails, but since we only have about 120 users and the number not
 likely to
 get any bigger any time soon it should be ok for the next few years.
 
 Thanks for the help..
 

You have to use userdb prefetch before userdb ldap to get rid of that extra
lookup. POP3 and IMAP use the extra fields from passdb ldap (those starting
with userdb_) while deliver uses userdb ldap (as there was no passdb-query
to prefetch).

http://wiki.dovecot.org/UserDatabase/Prefetch



Re: [Dovecot] LDA questions

2008-12-07 Thread Timo Sirainen
On Sun, 2008-12-07 at 20:21 +0300, Dmitri V. Ivanov wrote:
 On Fri, Dec 05, 2008 at 09:17:58PM +0200, Timo Sirainen wrote:
 
  Like Matt said, this is a Postfix configuration issue. You'll have to
  configure Postfix to figure out what users exist.
 
 One question. Postfix has TCP lookup table type with a very simple
 protocol: (get|put) space key newline.

Also I think there was some user lookup protocol that originated from
Sendmail. Dovecot should support that some day..

 But there is a question: how would act dovecot with much lookups with
 nonexistant users (there is no big problem to write some stupid
 connector)?

Shouldn't be a problem.



signature.asc
Description: This is a digitally signed message part


Re: [Dovecot] LDA questions

2008-12-05 Thread Matt Rude

On Thu, December 4, 2008 1:24 pm, Romer Ventura wrote:
 Hello,


 I am looking at the docs and I see this:
 Problems with deliver
 Namespaces are supported with v1.1 and later. With v1.0 and older
 versions mails can be delivered only to mailboxes specified by the
 mail_location setting.

 But in the dovecot.conf I see:
 # NOTE: Namespaces currently work ONLY with IMAP! POP3 and LDA currently
 ignore # namespaces completely, they use only the mail_location setting.


 I am running 1.1.7 so is that a typo in the dovecot.conf or the wiki
 page..?


 Also, I got postfix+dovecot configure to authenticate to Active Directory
  using pam_krb5 and I am able to login and send emails with pop3 or imap,
 but unable to receive emails since postfix complaints about the user not
 being found in the local recipient table.

 Now I have made a few changes, but I cant get to see deliver complaint,
 all I see is:
 postfix/smtpd[19924]: NOQUEUE: reject: RCPT from : 550 5.1.1
 [EMAIL PROTECTED]: Recipient address rejected: User unknown in local
 recipient table;

 So I think that it is not being passed to deliver...


 Master.cf has:
 dovecot unix-   n   n   -   -   pipe flags=DR
 user=vmail:vmail argv=/usr/lib/dovecot/deliver -f ${sender} -d
 ${recipient}


 Main.cf has:
 virtual_mailbox_domains = your.domain.here virtual_transport = dovecot

 Any ideas..?
 Thanks


Talk to the postfix list, it looks like you may have a problem with your
aliases.


-- 
Matt Rude
website: www.mattrude.com  -  wiki: wiki.mattrude.com
PGP Fingerprint: 0E94 70DA 89F8 5102 0862  5EA2 CB10 759E E65F 2C46


Re: [Dovecot] LDA questions

2008-12-05 Thread Timo Sirainen
On Thu, 2008-12-04 at 13:24 -0600, Romer Ventura wrote:
 Hello,
 
 I am looking at the docs and I see this:
 Problems with deliver
 Namespaces are supported with v1.1 and later. With v1.0 and older
 versions mails can be delivered only to mailboxes specified by the
 mail_location setting.
 
 But in the dovecot.conf I see:
 # NOTE: Namespaces currently work ONLY with IMAP! POP3 and LDA currently
 ignore
 # namespaces completely, they use only the mail_location setting.
 
 I am running 1.1.7 so is that a typo in the dovecot.conf or the wiki page..?

I forgot to remove that text in v1.1. Removed now.

 Now I have made a few changes, but I cant get to see deliver complaint, all
 I see is:
 postfix/smtpd[19924]: NOQUEUE: reject: RCPT from : 550 5.1.1
 [EMAIL PROTECTED]: Recipient address rejected: User unknown in local
 recipient table;

Like Matt said, this is a Postfix configuration issue. You'll have to
configure Postfix to figure out what users exist.


signature.asc
Description: This is a digitally signed message part


Re: [Dovecot] LDA questions

2008-12-05 Thread Thomas Siebert
Hi,

First, namespaces: Deliver runs perfectly with namespaces, so I suppose it's
a little glitch in the config file comments.


Regarding your delivery problem, read this from your config file (or
http://wiki.dovecot.org/UserDatabase/Static):
--- snip ---
Unless your MTA already verifies that the user exists before calling
deliver, you'll most likely want deliver itself to verify the user's
existence. Since deliver looks up the user only from the userdb, it of
course doesn't work with static userdb because there is no list of users.
Normally static userdb handles this by doing a passdb lookup instead. This
works with most passdbs, with PAM being the most notable exception. If you
want to avoid this user verification, you can add allow_all_users=yes to the
args in which case the passdb lookup is skipped.
--- snap ---

...which should explain why you don't get anything delivered. I think you
have three options: allow_all_users=yes (which would be cheesy), setup
another database or use postfixes virtual transport agent. Depends.



Regards,
Thomas



[Dovecot] LDA questions

2008-12-04 Thread Romer Ventura
Hello,

I am looking at the docs and I see this:
Problems with deliver
Namespaces are supported with v1.1 and later. With v1.0 and older
versions mails can be delivered only to mailboxes specified by the
mail_location setting.

But in the dovecot.conf I see:
# NOTE: Namespaces currently work ONLY with IMAP! POP3 and LDA currently
ignore
# namespaces completely, they use only the mail_location setting.

I am running 1.1.7 so is that a typo in the dovecot.conf or the wiki page..?


Also, I got postfix+dovecot configure to authenticate to Active Directory
using pam_krb5 and I am able to login and send emails with pop3 or imap, but
unable to receive emails since postfix complaints about the user not being
found in the local recipient table.

Now I have made a few changes, but I cant get to see deliver complaint, all
I see is:
postfix/smtpd[19924]: NOQUEUE: reject: RCPT from : 550 5.1.1
[EMAIL PROTECTED]: Recipient address rejected: User unknown in local
recipient table;

So I think that it is not being passed to deliver...

Master.cf has:
dovecot unix-   n   n   -   -   pipe
  flags=DR user=vmail:vmail argv=/usr/lib/dovecot/deliver -f ${sender} -d
${recipient}

Main.cf has:
virtual_mailbox_domains = your.domain.here
virtual_transport = dovecot

Any ideas..? 
Thanks

Dovecot ­n
# 1.1.7: /etc/dovecot/dovecot.conf
# OS: Linux 2.6.16.60-0.21-xenpae i686 SUSE Linux Enterprise Server 10
(i586) 
protocols: imap imaps pop3 pop3s
login_dir: /var/run/dovecot/login
login_executable(default): /usr/lib/dovecot/imap-login
login_executable(imap): /usr/lib/dovecot/imap-login
login_executable(pop3): /usr/lib/dovecot/pop3-login
mail_location: maildir:~/Maildir/
mail_executable(default): /usr/lib/dovecot/imap
mail_executable(imap): /usr/lib/dovecot/imap
mail_executable(pop3): /usr/lib/dovecot/pop3
mail_plugins(default): acl
mail_plugins(imap): acl
mail_plugins(pop3):
mail_plugin_dir(default): /usr/lib/dovecot/modules/imap
mail_plugin_dir(imap): /usr/lib/dovecot/modules/imap
mail_plugin_dir(pop3): /usr/lib/dovecot/modules/pop3
imap_client_workarounds(default): delay-newmail outlook-idle netscape-eoh
imap_client_workarounds(imap): delay-newmail outlook-idle netscape-eoh
imap_client_workarounds(pop3):
pop3_client_workarounds(default):
pop3_client_workarounds(imap):
pop3_client_workarounds(pop3): outlook-no-nuls oe-ns-eoh
auth default:
  mechanisms: plain login
  username_format: [EMAIL PROTECTED]
  passdb:
driver: pam
  userdb:
driver: static
args: uid=1001 gid=1000 home=/home/vmail/%Ud/%Ln
  socket:
type: listen
client:
  path: /var/spool/postfix/private/auth
  mode: 432
  user: postfix
  group: postfix