OSEC

Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com
Postfix Archives: Re: Virtual local delivery agent

Re: Virtual local delivery agent

Subject: Re: Virtual local delivery agent
From: Andrew McNamara (andrewmconnect.com.au)
Date: Mon Jan 24 2000 - 00:52:39 CST

>> - I've called the agent "virtual", but I'm slightly concerned people
>> will confuse this with the virtual table. Other suggestions are
>> welcome.
>
>vlocal or virtlocal or vdeliver

I've been considering vlocal, although I'd prefer a single word, rather
than some abreviated concatenation.

>Both of these sound good. Another way is how ncFTPd does virtual FTP
>trees. Basically, your agent could get the uid and gid of the directory
>you are about to write into and then use these id's as the uid and gid for
>the running process. For example, if uid:gid pair for
>/var/mail/domain.com/ was vuser53:other, then the agent would change to
>vuser53:other when trying to write to /var/mail/domain.com/bob/Maildir/.

Yep - I had also considered this - this is how we currently operate,
although I'm not sure Wietse would accept this.

>> - Currently every recipient is looked up in the uid map and the gid map. If
>> a site is running with fixed uid and/or fix gid across all their dialup
>> users, then they could specify a fixed map that returned these values. Do
>> people consider it worthwhile having a config file option to specify
>> fixed uid/gid instead?
>
>Yes, a config file option would be nice to save a lookup.

A fixed regexp map would be fast enough that it's load would not be
noticed. I'm considering adding a sort of "immediate" map type that can
be included in the config files - this could be valuable where you have
a simple mail config and would like to only ship around main.cf and
master.cf - you could include basic "transport" maps right in the
main.cf.

>> - To perform a delivery, the agent has to look up the mailbox path map, the
>> uid map, and the gid map. Does this tie in with how people would like to
>> use the agent with LDAP, or is there a better way of doing this (maybe
> one map lookup that returns 3 delimited fields)?
>
>The fewer lookups the better. One map with three fields would be best.

The problem there is how it sits with existing databases - it raises
nasty issues of what should be used to delimit the fields (I'd chose
colon, but people will certainly bitch). I suspect the ldap people
would prefer separate maps. Can the LDAP protocol return multiple
fields with one query (I'd guess yes)? Does the postfix implementation
support this (I'd guess no)?

 ---
Andrew McNamara (System Architect)

connect.com.au Pty Ltd
Lvl 3, 213 Miller St, North Sydney, NSW 2060, Australia
Phone: +61 2 9409 2117, Fax: +61 2 9409 2111

This archive was generated by hypermail 2b27 : Mon Jan 24 2000 - 01:12:03 CST