A multi-homed interface and qmail et al creates quite a nice framework for
making a truly virtual email domain. First there is tcpserv which allows you
to bind smtp and pop services to a particular interface. Second there
is virtualdomains which allows domain-based rules to deal with inbound mails.
However the one thing that appears to missing is an easy way to manage
separate qmail-user databases for separate virtual domains.
Does it make sense to have some sort of self contained qmail-lspawn-like
program that is fed a path to a /var/qmail/users directory? That way a
virtual domain could deliver to an alias which in turn feeds the mail into a
program which looks up the virtual domains user database and feeds the
result to qmail-alias.
ALternatively, is there an obvious way of doing this already? A brief look at
qmail-lspawn suggests that it only uses the local component to look up the
qmail-users data base thus precluding disambiguation by domain.
I don't pretend to have looked at qsmac, is that a serious contender for this
sort of thing or is in really only intended as a sendmail alias transition
package?
From an ISP perspective, re-compiling qmail to have a unique home for each
virtual domain is not a scalable option - though it does appear that
that would achieve the desired result.
Regards.
making a truly virtual email domain. First there is tcpserv which allows you
to bind smtp and pop services to a particular interface. Second there
is virtualdomains which allows domain-based rules to deal with inbound mails.
However the one thing that appears to missing is an easy way to manage
separate qmail-user databases for separate virtual domains.
Does it make sense to have some sort of self contained qmail-lspawn-like
program that is fed a path to a /var/qmail/users directory? That way a
virtual domain could deliver to an alias which in turn feeds the mail into a
program which looks up the virtual domains user database and feeds the
result to qmail-alias.
ALternatively, is there an obvious way of doing this already? A brief look at
qmail-lspawn suggests that it only uses the local component to look up the
qmail-users data base thus precluding disambiguation by domain.
I don't pretend to have looked at qsmac, is that a serious contender for this
sort of thing or is in really only intended as a sendmail alias transition
package?
From an ISP perspective, re-compiling qmail to have a unique home for each
virtual domain is not a scalable option - though it does appear that
that would achieve the desired result.
Regards.