RA> My *understanding* is that virtual domains don't rewrite the envelope
RA> recipient, so if you get mail addressed to firstname.lastname@example.org and
RA> lists.example.com is a virtual domain pointing to the lists user, you get
RA> "majordomo" in LOCAL, not "lists-majordomo" which is the user that things
RA> are actually getting delivered to. So I *believe* that mjdispatch should
RA> do the right thing in that environment.
RA> I'm therefore somewhat confused as to the problem being fixed by using
RA> DEFAULT instead and could use some clarification.
My assumption is that one would use the virtualdomains control file,
perhaps in conjunction with the qmail-users(5) mechanism.
For example, for my experimental environment, I use this line in
and this line in users/assign:
which makes email@example.com get delivered to
the local address majordomo-softhome-majordomo
via ~majordomo/.qmail-softhome-default, which contains:
|/home/majordomo/bin/mj_email -Q -d list.softhome.net
That's with my DEFAULT hack. I have no idea how to implement more than a
single domain with just LOCAL. How do you do it?
In other words, I figure there should be one .qmail file per
majordomo-hosted domain: .qmail-domain-default.
And FWIW, my proposed DEFAULT patch falls back to LOCAL if DEFAULT is not set.
JL> DEFAULT is better, but was only introduced in qmail 1.03 which a few
JL> people still don't run. Use the code that's there, but put in a comment
JL> noting that they may have to twiddle it if they're not running 1.03 and
JL> have multi-component addresses before the default part.
I didn't realize it was a 1.03 thing. Is the fallback to LOCAL sufficient
to solve that concern?