Digby Tarvin wrote:
It is easy enough to set it up and test it in parallel with your
current setup. Nothing important should be directed there till you
advertise it..
That's fine for outgoing mail, but unless an MX record exists for the
internal server on a domain/subdomain, it's difficult to 'direct'
traffic from the outside in.
The only other way I can think off is to test the server using either a
telnet port or a script from an off-site computer onto the new server.
I have been running a mail server on my home system ever since I got
my DSL connection at home. It is where I normally direct mailing
list traffic and other correspondence which is non critical,
because I can create dedicated aliases which all point the the
same ultimate mailbox, making it easy to identify where spammers
have been obtaining addresses from, and making it possible to just
invalidate the effected address...
For person mail that I want to be able to access when I am
travelling I use a mail forwarding address which can be
pointed at an ISP hosted POP3 mailbox (which is polled using
fetchmail when I am home) or when needed can be pointed direct
to my home server.
All me e-mail comes in on my home server and has been now for ~3 years,
along with my families for the last year or so now that multiple domains
has been setup. I've even used it as an emergency backup for another
server when that went down.
As for remote access, I use IMAP over SSL. Most new phones and PDA's
support SSL encryption over IMAP and SMTP, plus I have the advantage of
all my mail being handled from one location.
--
Jonathan Wright ~ mail at djnauk.co.uk
~ www.djnauk.co.uk
--
2.6.13-gentoo-r3-djnauk-b2 AMD Athlon(tm) XP 2100+
up 5:41, 2 users, load average: 1.22, 0.86, 0.83
--
"I can't help looking gay. I put on a dress and people say,
"Who's the dyke in the dress?""
~ Karen Ripley
--
[email protected] mailing list
