Re: Email POP relay

From: Dave {Reply Address in.sig} (noone$$_at_llondel.org)
Date: 01/05/05


Date: Wed, 05 Jan 2005 22:48:05 +0000

In message <71268e09.0501051257.63d9616e@posting.google.com>, Lee Hanken
wrote:

> My family currently access all our email from a machine in the living
> room. It is sorted into folders according to who it is to by Outlook
> Express. I thought it would be nice if we could access our mail from
> our own computers (without all switching to new separate email
> accounts).
>
> I am considering setting up a linux box on my home network to collect
> email from 2 or more external POP accounts on request and then serve
> it to POP or IMAP clients on the network.
>
> The machines on the network I am envisaging will have local IP
> addresses assigned by the DHCP serving wired+wireless router (attached
> to my broadband cable modem), such as 192.168.0.x and will be running
> various operating systems.
>
> My first question is what combination of software can accomplish the
> task of immediately getting mail from various sources and serving it,
> whenever a client email program makes a connection.
>
> My second, more troublesome, question is how can I specify an internet
> address to the mail clients that will resolve to whatever dynamically
> assigned IP address my 'mail-hub' happens to have.
>
Do you have to the mailhub get a dynamic IP? Just reduce the range allocated
by the router by one and assign that one statically to the mailhub. Then
you can put an entry in the hosts file on each of the other machines so
they'll always know what it is.

Also, some more modern router boxes will do some form of dynamic DNS on the
addresses served but it depends on whether yours is one of them. You could
always set up the Linux box to do the DHCP for you and also run a local
DNS, that's what I have here and it updates nicely from one to the other.
It's quite easy to do from the relevant HOWTOs.

> Please let me know if I am thinking in entirely the wrong direction,
> or if what I am suggesting is possible.

-- 
Dave
mail da ve@llondel.org (without the space)
http://www.llondel.org/
So many gadgets, so little time...


Relevant Pages

  • Re: Windows 2000 Server - Problems getting internet to clients
    ... There is really no reason to use your DC as a router when you have a device specially built to do that for you. ... Switch off the DHCP function on the Netgear and run DHCP on the server (or just configure the clients manually, as you will for the server). ... All machines, including the DC, use the router as their default gateway but use the DC for DNS. ... Briefly you will have a single network with machines all in the same subnet using the Netgear as the gateway. ...
    (microsoft.public.windows.server.networking)
  • Re: Windows Server 2003 R2 x64 RRAS seems to be limiting connectio
    ... the 192.168.17.0 network is a mixture of wired ... The route on the ADSL modem (router) is to ensure that the default gateway ... There is no WiFi on LAN2 but wired connections on the 192.168.11.0 subnet ... assgned to the WiFi Clients? ...
    (microsoft.public.win2000.ras_routing)
  • Re: Connect 2 LANs via 2 NICs - Windows2000 Server
    ... The clients on LAN1 and LAN2 need a way to route to each other. ... correct default gateway to the clients: ... Router on LAN2 will need a router to the 10.1.1.x subnet using 10.22.64.2 ... > The Windows 2000 server can access and ping all computers> on each network. ...
    (microsoft.public.win2000.ras_routing)
  • Re: Wireless Network in Public Places Options
    ... the clients can be trusted. ... DHCP server on a wireless laptop that will deliver a creative IP ... wireless access point and router going to the internet. ... In a common shared network, broadcasts go to every machine on the ...
    (microsoft.public.win2000.networking)
  • Re: Remote Desktop problems
    ... dynamic dns client and a dns server that supports dynamic dns updates. ... >> router doesn't "know" what that ip is and for what computer. ... The computers on your network will now get their ip from ... >>>> forwarding is for TCP port not udp. ...
    (microsoft.public.windowsxp.hardware)