--------
We may be talking at slightly cross purposes because I have not made myself
100% clear.
> Why mess with it at all? It all (normal sendmail + local named) works out
> of the box with a late 2.0 kernel when the line
>
> echo 5 > /proc/sys/net/ipv4/ip_dynaddr
>
> is placed somewhere in the startup scripts.
This is true, except when you through the following into the equation:
1. A standalone machine
2. Diald (hence the reason for the cc: to the other list)
3. An ISP who not only assigns dynamic IP addresses but dynamic hostnames as
well.
I want to use Diald to come up on demand and therefore some form of DNS is
required. This introduces the problem that every time I write an e-mail and
sent it to the queue, sendmail performs a DNS lookup which brings the link up.
The point I am trying to make is that whilst including nocanonify is a
reasonable option for sendmail, it causes a further potential problem of
sending non canonical addresses onto the net.
Consider the scenario of a small business network with a dial-on-demand
connection. Joe Bloggs, head of sales, sends a confirmatory mail to a customer
and copies it to Jack, the boss. If nocanonify is included in sendmail, then
depending on the setup, the copy to Jack is going to go onto the net where
Jack's e-mail address is unreasovable.
If your wondering about point 3 above; I cannot assign a suitable hostname
compatible with my ISP addresses to my machine, therefore I have to rewrite
the headers. This is a further minor annoyance but makes the need for
canonical addressing on my machine slightly more important because I cannot
use the smart host to determine my network e-mail addresses.
------------------------------------------------------------
Richard McMahon
Copenhagen
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
