8 messages in net.sourceforge.lists.courier-usersRe: [courier-users] Postfix + maildro...
FromSent OnAttachments
Jorn ArgeloMar 27, 2007 6:06 am 
Enda CronnollyMar 27, 2007 6:12 am 
Jorn ArgeloMar 27, 2007 7:43 am 
Gordon MessmerMar 28, 2007 8:14 am 
Jorn ArgeloMar 28, 2007 12:34 pm 
Larry MooreMar 28, 2007 3:35 pm 
Larry MooreMar 29, 2007 2:04 am 
Gordon MessmerApr 1, 2007 9:38 pm 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:Re: [courier-users] Postfix + maildrop as mail relayActions...
From:Jorn Argelo (jo@wcborstel.com)
Date:Mar 27, 2007 7:43:07 am
List:net.sourceforge.lists.courier-users

Jorn Argelo wrote:

However, there is one problem. Since maildrop uses courier-authlib to authenticate, the best possiblity will be to use the postmap generated hash file. But now my question is ... is this possible? I was looking at auth_userdb, but I am not sure if this is able to do what I want. The best option would be that maildrop is not authenticating at all anymore, but I think maildrop always wants to authenticate. This because we only want to use the filtering capabilties of maildrop.

Both authlib and postfix can authenticate against ldap without any special hacks etc, and you get third party tools and a known interface for admin'ing that. Would have thought that was the best option.

-Enda.

Hi Enda,

Thanks for your reply. LDAP, however, is not really an option because of the amount of emails we get. You see, the postmap hash db is an extract of the email addresses defined in Active Directory. If we have to query AD for every email we get, we will probably slow things down / cause a lot of load on the domain controller (I think we're at around 65.000 emails / day ). This is why we made the choice to make an hash db based solution rather then an LDAP solution. This is faster and produces a lot less load.

I hope this makes more sense.

Thanks,

Jorn