Caveat: I've never used qmailadmin, so apologies if this is a dumb question ;-)
Can qmailadmin be made to work w/ the new webapp.eclass at all?
I guess this bug should also cover vqadmin too?
nope, they need a lot of information at compile-time.
vqadmin in itself deals with all of the virtual mail domains properly anyway.
they would have to be statically installed in a web instance somewhere. it doesn't even like being moved around after you have installed it.
couldn't we export to our environment a variable for example like:
and the ebuild would check if this var was set, and use it instead of the
default to localhost?
Closing this as CANTFIX, then...