Re: a new sendmail question

Tim wrote:
On Mon, 2007-12-17 at 08:25 -0600, Aaron Konstam wrote:
I would claim that you do have a domain. The domain of the external
interface of your router.

Hmm, claiming your ISP's domain as if it were your own can be a problem.
All's fine and well if you simply use it with your e-mail addresses
provided by your ISP. But something like using root@ your ISP's domain
name would be a major no-no.

You'd have to be very careful about keeping internal mail internal.
That, pretty much, means you need to run your own DNS server, so that a
mailserver doesn't to a MX lookup on the domain, using the ISP's name
server, and send the message through the ISP's SMTP server.

There's another problem with most NAT routers. Unless you provide your own internal DNS service so that the name resolves internally to the private address of the host you want to accept email, you will try to deliver it to the outside interface of the router. Even if the router is configured to forward inbound connections from the external interface to the receiving host, most routers won't do this if the connection originates on the internal interface.

--
Les Mikesell
lesmikesell@xxxxxxxxx

--
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list

Relevant Pages

  • Re: static routing
    ... I am creating a deman dial interface on the corporate server and ... connects to the branch office server. ... problem is, I knew this was going to happen, the router that I use at the ... A static route has been added that matches the subnet of the ...
    (microsoft.public.windows.server.networking)
  • Re: static routing
    ... You can't do it manually because the interface doesn't exist until the ... static route for the subnet of the remote site and select the demand dial ... When you make a connction to the server you use the name of the ... The packet goes to the default router ...
    (microsoft.public.windows.server.networking)
  • Re: Please Help Site-To-Site without ISA
    ... You can configure more than one site to site VPN connection on the ... You set up a new demand-dial interface and configure a new site to ... public IP of the VPN server at the second site on the front. ... to router connection. ...
    (microsoft.public.windows.server.networking)
  • [Full-Disclosure] FW: Cisco Vulnerability forensic protocol analysis results.
    ... AMILABS CISCO IP PROTOCOL EXPLOIT TESTING RESULTS ... Cisco router interfaces using either all or one of the following IP ... of a remote Cisco interface uses all of them. ... output buffer failures, 0 output buffers swapped out Router4# ...
    (Full-Disclosure)
  • Re: 2003 server config for routing and remote access
    ... The router works fine. ... As I said the server sees the internet. ... everything other than that interface ...
    (microsoft.public.win2000.ras_routing)