[anti-spam-wg@localhost] Verizon blocking all IP addresses delegated by RIPE?

  • From: "pna.lists" <
    >
  • Date: Fri, 21 Jan 2005 17:25:44 +0100

Is there any official RIPE statement available regarding Verizon seemingly
blocking incoming e-mail traffic from IP addresses delegated by RIPE?

There is only one MX record available for the Verizon.net domain (used for
the customers' mailboxes and for service addresses like support@localhost,
security@localhost):
relay.verizon.net (206.46.170.12)

If you attempt to send an e-mail to somebody @verizon.net from an address
delegated by RIPE, the SMTP connection to the port 25 of relay.verizon.net
is blocked. I tested this with a mailserver using an IP address whaich has
never been blacklisted on any major blacklist.

According to media reports, incoming e-mail traffic from Australia is
blocked by Verizon, too.

The Verizon employee addresses use another domain Verizon.com. That domain
uses single MX record, too:
ftwmail.bdi.gte.com (192.76.86.129)

Ironically, sending e-mail from Europe to the Verizon employee addresses is
allowed, so I was able to ask about the blockade. Unfortunately, Verizon
just denies this is happening, so the answer I received from Verizon
employee Sandy Arnette was not much usable.

I would like to ask if there is any official RIPE statement available
regarding Verizon seemingly blocking incoming e-mail traffic from IP
addresses delegated by RIPE. Or was any such statement published by any
major European ISP?

Will major European ISP's perform any special action against Verizon e-mail
blockade, like using US-based server for sending outgoing e-mail to the 3
milliond of the Verizon customers

Here are some links to recent media coverage of Verizon blocking scandal:

http://www.wired.com/news/ebiz/0,1272,66226,00.html

http://www.washingtonpost.com/wp-dyn/articles/A19567-2005Jan18.html

http://www.iht.com/articles/2005/01/14/business/ptend15.html

http://www.technewsworld.com/story/news/39722.html

http://www.theregister.co.uk/2005/01/14/verizon_email_block/