On Mon, Oct 11, 1999 at 05:25:33AM +0000, Franck PORCHER wrote:
>
> a) control/locals
> Let's say I'm trying to have my qmailhost server locally delivers mail
> for my top domain, eg "esoft.pf", and some of its sub domains as well,
> eg "sales.esoft.pf", "edu.esoft.pf" etc.. That means that qmail-smtp
> and qmail-send would have to accept mail adresses like [EMAIL PROTECTED],
> [EMAIL PROTECTED], [EMAIL PROTECTED]
> So far, I have had to put a separate line for each allowed subdomain in
> control/locals.
> My questions are :
> - Is that the only way to do it ? If not, which are the other ways?
> - Is that the best way ?
> - Is there a way we can use wildcards, like ".esoft.pf"
Putting a domain in "locals" makes it local, which means that EVERY USER on
the system gets the mail for <user>@<domain>.
If you have at least one user that should not get local domain mail this
way, it's most often better to make the domain "virtual" and thus putting it
in virtualdomains INSTEAD (never in both) of locals.
> b) control/rcpthosts
> For the mail to be received for those subdomains, I added a separate
> line in control/rcpthosts, and it works fine.
Good.
You could have wildcarded with
.esoft.pf
as well.
> Now, this server working inbound and outbound, it will have to accept
> ANY mail on port 25 (qmail-smtp) from internal employees using local
> clients like "outlook express" or "Netscape Messenger', and handle
> remote delivery for any external address. I understand that this means
> this server will have to be configured as a RELAYCLIENT.
>
> I have read how to set up the RELAYCLIENT environment variable, so
> that's one solution.
>
> Now, my question is about the use of wildcards within rcpthosts as
> another solution. It is said in the qmail-smtpd man page (8), that
> rcpthosts may include wildcards, in the form ".domain",
> meaning "accept any address belonging
> to <domain>". I tested it and it works. Now, in the sake of coherence,
> what is the reason why rcpthosts does not accept the record made of the
> dot itself ".", meaning "accept any address belonging to any topdomain",
> which would be another simple way to setup RELAYCLIENT='' ? I may be
> missing something...
This is a tcprules/tcpserver matter. You'll want to look into the
documentation and man pages for tcpserver and tcprules (found in the
ucspi-tcp-package). I would recommend filtering on IP-numbers instead of
domain names as they're much harder to fake/spoof.
You will definitively only relay for the hosts within your own net. All nets
(LAN/WAN:s) and ISP:s should include an SMTP host.
> c) For some reason, I have a employee, lets's say "jean", that works at
> home, and who gets his email thru a mailbox at our ISP : all email
> received by this ISP and matching the address "[EMAIL PROTECTED]"
> goes to his mailbox. So far, so good.
How is this mail fetched from the ISP? SMTP? POP?
> The problem I'm having here is that my qmailer being configured to
> locally deliver any mail to "esoft.pf" (see question a),
> it considers the address "[EMAIL PROTECTED]" to be local (cf point a) and
> does not deliver messages for jean thru my ISP. Here is my question :
> What would be the best way to configure qmail to have this specific
> address ([EMAIL PROTECTED]) remotely delivered to my ISP (say "mail.pf"), so
>
> any local mail to
> [EMAIL PROTECTED] would eventually end-up in his remote mailbox. ?
> I thought of putting
>
> [EMAIL PROTECTED]:alias-myisp
>
> in "control/virtualdomains",
> then setting up
>
> ~alias/.qmail-myisp-default ($DEFAULT holding "jean", and $HOST
> holding"esoft.pf")
>
> but I just do not seem to find out what to put in
> ~alias/.qmail-myisp-default so messages controlled by this file
> are actually sent to '"$DEFAULT"@"$HOST"' thru my remote isp (mail.pf).
Why do you want to forward this mail?
Where does jean pick up the mail? At the ISP or at your host?
If just the endpoint mail host is configured as a primary mail server, then
no forwarding has to be done.
--
magnus
-- MOST useless 1998 * http://x42.com/
