Chris Johnson wrote:
> 
> FAQ 4.6

Er, please excuse my idiocy but what FAQ are you refering to? Dan's FAQ
does not have section numbering ... http://cr.yp.to/qmail/faq.html.

Nonetheless, I did check Dan's FAQ when setting this up. That is why I
am stumped. The FAQ says, 

--BEGIN QUOTE--
How do I set up a virtual domain? I'd like any mail for nowhere.mil,
including [EMAIL PROTECTED] and [EMAIL PROTECTED] and so on, to be
delivered to Bob. I've set up the MX already. 

Answer: Add nowhere.mil:bob to /var/qmail/control/virtualdomains, and
tell qmail to read virtualdomains. Add nowhere.mil to
/var/qmail/control/rcpthosts. 

Now mail for [EMAIL PROTECTED] will be delivered locally to
bob-whatever. Bob can set up ~bob/.qmail-default to catch all the
possible addresses, ~bob/.qmail-info to catch [EMAIL PROTECTED], etc.
--END QUOTE--

Now, I added nowhere.mil (well, a real domain of course but let's stick
with the example) to control/virtualdomains
(nowhere.mil:alias-nowhere.mil). I "told" qmail to read virtualdomains.
I added nowhere.mil to control/rcpthosts. The MX records were changed
accordingly. I created ~alias/.qmail-nowhere.mil-default with
[EMAIL PROTECTED] as it's contents. Ergo, mail to *@nowhere.mil should go to
[EMAIL PROTECTED]

That is not happening. The mail is bouncing with the error quoted in my
first message. If I then create ~alias/.qmail-default with any email
address in it ([EMAIL PROTECTED]) then _all_ email  is forwarded to that
address, including all mail for nowhere.mil. Delete
~alias/.qmail-default and mail start bouncing again.

I expect, perhaps incorrectly, that the correct behaviour would be, in
the face of a message to say [EMAIL PROTECTED], to look for these files,
in this order:

        ~alias/.qmail-nowhere.mil-info
        ~alias/.qmail-nowhere.mil-default
        ~alias/.qmail-nowhere.mil
        ~alias/.qmail-default
        ~alias/.qmail

Now, maybe it does not check all of those but that is irrelevant.
Obviously, assuming the setup I stated above, all mail to *@nowhere.mil
should be going to [EMAIL PROTECTED] It is not and that is what I was hoping
someone could help me out with.

Claimer: I've read the docs, the HOWTO, LWQ, the FAQ. What I need is
some extra eyes to locate what I am doing wrong, not scripture.

-- 
Mark Drummond|ICQ#19153754|mailto:[EMAIL PROTECTED]
UNIX System Administrator|Royal Military College of Canada
The Kingston Linux Users Group|http://signals.rmc.ca/klug/
Saving the World ... One CPU at a Time

Reply via email to