In between the choice of accepting mail from *anybody* by default
which we have now and the choice of accepting mail from *nobody* by
default that explicit peering agreements represents there is another
solution; which is to accept mail only from IPs that have *some
relation* to the sender's From
On 18 Jun 2005, John Levine wrote:
In between the choice of accepting mail from *anybody* by default
which we have now and the choice of accepting mail from *nobody* by
default that explicit peering agreements represents there is another
solution; which is to accept mail only from IPs that
james edwards [EMAIL PROTECTED] writes:
I am looking for a seller of outdoor Telephone pedestals. I plan to install
a DSLAM, post splitters
and associated cross connect gear in this enclosure. Can anyone suggest a
dealer for this sort of gear ?
http://www.sprintnorthsupply.com/
This has the same problem as all of the other duct tape authorization
schemes -- it breaks a lot of valid e-mail, ...
In this particular case, the biggest issue is forwarders, ...
This gets into the discussion of what percentage of mail a user gets that
is like this. It varies widely.
w Date: Mon, 13 Jun 2005 10:39:54 -0700 (PDT)
w From: william(at)elan.net
w http://www.completewhois.com/statistics/data/ips-bycountry/rirstats/
See also:
.zz.countries.nerd.dk
IN A lookups return 127.0.x.x, where x.x is a two-octet representation
of the ISO 3166 numeric country
Folks,
DNSWL -- this is already being done. It is not widely viewed as being in
any way similar to a peering concept. What would be more similar would
be a consortium of large providers providing such a whitelist. That
would be something I would welcome.
To repeat what John Levine said,
[EMAIL PROTECTED] wrote:
Today, if Joe Business gets lots of spam, it is not his
ISP's responsibility. He has no-one to take responsibility
for this problem off his hands. But if he only accepts
incoming email through an operator who is part of the
email peering network, he knows that
Hello-
ARIN received the IPv4
address blocks 74.0.0.0 /8 and 75.0.0.0 /8 and 76.0.0.0 /8 from the IANA on June
17, 2005. In the near future, ARIN will begin making allocations from these
new blocks. This will include allocations of /20 and shorter prefixes,
according to ARIN's minimum
