On Wed, 16 Jun 2004 11:14:12 +1200 "Craig Box"
wrote:
| While we're on the subject of mail rejections, I look after a couple
| of sites on a TelstraClear Tempest connections, both with IP addresses
| on 203.97.48.0/21. Unfortunately, spam DNS blacklist SORBS list them
| as being on Dynamic IP space:
|
| 203.97.48.x found in Dynamic IP Space (Cable, DSL & Dial Ups)
| Address or Block: 203.97.48.0 / 21
| Information: Dynamic IP address, use your ISPs mail server
|
| ..and as such a number of sites (a number growing by about one a day,
| just the ones I get told about) are blocking mail based on the SORBS
| listing.
The point being that the inbound mail administrators have the right to
decide whether to accept connections from hosts in dynamic-IP ranges.
| Some months ago I got in touch with TC's faults desk and they
| claim to have emailled off to SORBS to have this reclassified.
|
| Nothing changed, so I got in touch with our local tech contact at TC;
| he said he'd fire it off to the ISP guys but I've not heard back from
| him either.
All true. On Jan 30 The Telstra Abuse Desk wrote to SORBS about the
block being labelled as "dynamic" and asked for "a copy of the headers
of the spam". SORBS replied, explaining that the DUHL list identified
their IP's DHCP status, not that any spam had been sent.
Telstra Abuse Desk didn't respond to that reply.
On March 11 Mark Seward wrote in again from Telstra, asking for the
block status to be changed: SORBS replied, explaining that for security
reasons such a request would need to come from the designated APNIC
PoC for the IP block (which currently would be netobjs(a)clear.net.nz)
However that reply got an auto-response saying that Mark Seward was
no longer with Telstra, and mail should now go to Peter Ambrose and/or
Sid Jones, so SORBS dutifully forwarded the previous correspondence to
those two people, hoping they'd get the appropriate person to write in
to authorise the change. But nothing further was heard until April 7
when Jason, as "isp.duty(a)team.telstraclear.co.nz" wrote in asking how
to get the block's status changed, and he was sent a similar answer to
that which had gone to Mark Seward, Peter Ambrose, and Sid Jones: but
still nothing was heard from the designated PoC.
| I've asked around about this and the best suggestions are "you're an
| ISP customer, you should be smarthosting through an ISP mail server."
| Problems with this include the fact that we no longer have any control
| over retry/routing/any of the niceties of controlling your own outbound
| SMTP; the fact that clear.net.nz mailservers are currently being eaten
| by Zafi and mail delivery will probably slow down; and the fact that
| we "just plain shouldn't have to."
If you're on static IP, then as you say, you shouldn't have to.
TelstraClear should have been able to follow the simple instructions
to get this changed, normally a very straightforward process!
| I'm not sure where to go from here. It's possible that if I ask TC
| to set the PTR for each affected customer to smtp.$CLIENT and then
| manually request that it's removed from SORBS, it may be done.
If an IP is to send mail, that is a good suggestion in its own right.
DNS should also have a sensible TTL - at least 12 hours is reasonable.
--
Richard Cox
