🚀 go-pugleaf

[POSTED TO comp.dcom.modems.cable; PLEASE REPLY THERE]

In <3A6521D1.AC7C5526@spamcop.net>, Mike Blackford
<mblackford@spamcop.net> wrote:

>Jim Turner wrote:
> 
> Both barrels:
> 
> Subject:  @Home Email Still SUCKS
> 
> I loose email messages every day.  Messages I know for a fact that get sent
> to my @home account are never received.  This is not acceptable.  I'm
> convinced that @home has hired circus monkeys to operate their email
> servers.
> ...

>I agree wholeheartedly. This has been the case for nearly a year, possibly
>more.


In trying to figure out why my own mail system was suddenly having
problems trying to deliver mail to @Home, it became painfully obvious
that @Home doesn't understand how to configure MX records:

| $ nslookup -type=mx home.com
| 
| home.com        preference = 100, mail exchanger = mx-b-rwc.mail.home.com
| home.com        preference = 100, mail exchanger = mx-a-rwc.mail.home.com
| home.com        preference = 125, mail exchanger = mx-d-rwc.mail.home.com
| home.com        preference = 50, mail exchanger = mx-rr.home.com
| home.com        nameserver = ns1.home.net
| home.com        nameserver = ns2.home.net
| mx-b-rwc.mail.home.com  internet address = 24.0.95.21
| mx-a-rwc.mail.home.com  internet address = 24.0.95.20
| mx-d-rwc.mail.home.com  internet address = 24.0.95.23
| mx-rr.home.com  internet address = 24.0.95.20
| mx-rr.home.com  internet address = 24.0.95.21
| mx-rr.home.com  internet address = 24.0.95.22
| mx-rr.home.com  internet address = 24.0.95.23
| mx-rr.home.com  internet address = 24.0.95.25
| ns1.home.net    internet address = 24.0.0.27
| ns2.home.net    internet address = 24.2.0.27

Since mx-rr.home.com is aliased to all 5 servers, there is no need or
purpose for mx-a-rwc.mail.home.com, mx-b-rwc.mail.home.com, and
mx-d-rwc.mail.home.com.  Worse, a mail loop might be possible depending
on how the servers are configured, since the same servers appear at
different preference levels.

RFC 974 / STD 0014:

   The first major principle is derived from the definition of the
   preference field in MX records, and is intended to prevent mail
   looping.  If the mailer is on a host which is listed as an MX for the
   destination host, the mailer may only deliver to an MX which has a
   lower preference count than its own host.

-- 
Best regards,
John Navas     <http://navasgrp.home.att.net/>
     CABLE MODEM/DSL GUIDE:  <http://Cable-DSL.home.att.net/>