Score:0

Handling all subdomains as the domain itself

cn flag

I'm forwarding all e-mails for a domain owned by a friend to his real e-mail address. This works fine for his example.com itself (with the @example.com virtusertable entry):

% sendmail -C new.cf -bv [email protected]
[email protected]... deliverable: mailer relay, host [myrelay], user [email protected]

We'd like to expand the functionality to work for anything.example.com too, and are facing unexpected difficulties...

The DNS record * IN MX 5 myserver.mydomain exists for his domain and works -- the Internet is trying to give e-mails intended for foo.example.com to my server.

But sendmail on my server does not know, that those subdomains should be handled the same as the domain itself -- how do I teach it?

The rule suggested here seems to be just, what I need -- but it does not help -- the address is not rewritten...

LOCAL_NET_CONFIG
R $+ < @ $+ .example.com. > $*    $: $1 < @ example.com > $3

If I insert the rule into LOCAL_RULE_0 instead of the LOCAL_NET_CONFIG, I get the address modified, but the virtuserable entry for the domain ([email protected]) is ignored:

% sendmail -C new.cf -bv [email protected]
[email protected]... deliverable: mailer relay, host [myrelay], user [email protected]

Seems like something small -- and silly -- is missing, but what is it?

mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.