Re: ISP Mail Hosts on Black Lists (was "Re: Input on identities")

Philip Miller wrote:
> > > I guess to prove this point, Greg, nekodojo.org's MX rejects based on 
> > > SORBS listings. Conveniently, one of comcast.net's servers is listed 
> > > this month, and apparently is not eligible for automatic removal. 
> > > Have a look at
> > > <http://www.dnsbl.us.sorbs.net/cgi-bin/lookup?IP=216.148.227.85>.
> > >
> > > My ultimate goal here is to be able to send mail directly from my 
> > > private MTA, using my domain name, for which I am fully responsible, 
> > > rather than relying on Comcast to keep things straight.
> >
> > If this data is stored in rDNS, then gaining access over the rDNS 
> > space would give you an ability to run your own MTA. If it is a DUL 
> > list, than you will have no access to it.
>
> No, this is data about the IP of comcast.net's outgoing host. If you 
> look at the link I sent, it shows that someone sent a message to a SORBS 
> spamtrap address.
> Because of the above discrimination, I am forced to send through 
> Comcast's MTA. This MTA got blocked for sending 'spam'. Thus, my mail 
> being blocked is collateral damage.
> Any proposal that would give my MTA more legitimacy, specifically at the 
> domain level, would be a good thing, because I might be able to send 
> directly rather than through Comcast.
Allow me to explain myself. If instead of DUL lists, ISPs would use MTA 
MARK-style in-addr.arpa entries in rDNS for marking dialup accounts (not 
the regular rDNS IP check), then you gaining access over your rDNS space 
would let you "opt-out" your machine from the list. But if the DUL list 
is not accessable to you, then you are forced to route email over their 
smarthost or an external MTA.
Yakov