On Sat, Sep 12, 2020 at 11:52:51AM -0700, PGNet Dev wrote:
> I'm exploring an all flat-file virtual-address-only postfix setup.
> well, using lmdb -- NOT sql or ldap, to be accurate.
This feels like an instance of an XY problem. Your approach to problem
X leads you to approach Y, which runs into an issue, and so now you're
asking about Y, but really you should start by asking about X.
What is the actual goal here? What sort of virtual alias management
problem are you trying to solve by partitioning virtual aliases across
multiple source files. Why are you loathe to consider a database, ...
Are you experiencing Qmail nostalgia? :-)
In Qmail you get an alias file *per-domain*, with domains owned by some
user, and then an alias for each domain managed by the owning user.
Pushing the model to alias file per user, without first scoping the
aliases to a domain owned by the user is likely ill-defined, who gets to
claim which aliases?
Questions about how to assemble virtual aliases are premature absent
a clear data model.
On Sat, Sep 12, 2020 at 04:52:43PM -0700, PGNet Dev wrote:
> On 9/12/20 3:26 PM, Viktor Dukhovni wrote:
> > What is the actual goal here?
> having recently migrated a few boxes from my own, DIY'd app & prereq builds to distro pkg'ing reminded of the 'joys' of pulling in bloated dependencies, etc.
> i'm simply exploring an as-thin-as-possible/lightweight deployment. minimal external dependencies, etc. -- ideally _just_ requiring a postfix install, and flatfiles.
If this is just your own way to organise data managed by a single
authority (you), then organise it any way you like, then run "make"
to create a single virtual(5) aliases file that you "postmap" in
the usual way.