[BBLISA] Verizon help

[A Page in the Life of ...]

Hi ... this is from another list I'm on, I'm chainging the names of the
other folks, for privacy reasons ...

- -=> On Sun, 15 Feb 2004, A Page in the Life of ... wrote:
- -=> 
- -=> > Hi folks ...
- -=> >
- -=> > Does anyone know why I keep getting:
- -=> >
- -=> >   == postmaster at verizon.net T=remote_smtp defer (0): SMTP error from remote
- -=> > mailer after MAIL FROM:<dkap at opal.haven.org> SIZE=3065: host
- -=> > relay.verizon.net [206.46.170.12]: 450 Requested mail action not taken-Try
- -=> > later:sc003pub.verizon.net
- -=> >
- -=> > from any address I send to at Verizon.net?
- -=> >
- -=> > Thanks!
- -=> >
- -=> > -dkap

-=> From: NM
-=> 
-=> It could be that verizon is implementing that new system to check MX
-=> records for any domain (I just read about this a month ago, but I forgot
-=> what it is called already).  So when mail shows up at verizon coming from
-=> opal.haven.org, it looks to see if that host is a valid mail server for
-=> your domain, which it is not.
-=> 
-=> haven.org.              78719   IN      MX      30 crystalpalace.haven.org.
-=> haven.org.              78719   IN      MX      10 mailhost.haven.org.
-=> haven.org.              78719   IN      MX      20 sanctuary.haven.org.
-=> 
-=> Heck, might not even be the stuff I read about, it might be something
-=> else.  See if you can send a message and have it come from one of your
-=> servers that has an MX record to see if it goes through.

I just checked for that:

<abuse at verizon.net>... Connecting to relay.verizon.net. via esmtp...
220 sc024pub.verizon.net MailPass SMTP server v1.1.1 - 121803235448JY ready
Sun, 15 Feb 2004 12:21:30 -0600
>>> EHLO crystalpalace.haven.org
250-sc024pub.verizon.net
250-8BITMIME
250 SIZE 8388608
>>> MAIL From:<dkap at crystalpalace.haven.org> SIZE=670
450 Requested mail action not taken-Try later:sc024pub.verizon.net
<abuse at verizon.net>... Deferred: 450 Requested mail action not taken-Try
later:sc024pub.verizon.net
Closing connection to relay.verizon.net.
>>> QUIT
221 sc024pub.verizon.net closing connection

Still no go.

Anyone else having similar problems?

Is there an address at verizon that follows the RFC of allways accepting
mail that actually get's read that I can query?  Or does anyone have an in?

-dkap

P.S.  I just checked with DNS for verizon, so if they are putting this
policy in place, they should be following it, right?

> dig MX verizon.net
;; ANSWER SECTION:
verizon.net.            16865   IN      MX      0 relay.verizon.net.

> dig relay.verizon.net
;; ANSWER SECTION:
relay.verizon.net.      736     IN      A       206.46.170.12

> dig -x 206.46.170.12
;; ANSWER SECTION:
12.170.46.206.in-addr.arpa. 710 IN      PTR     relay.gte.net.

None of which are the machine that answered:
> dig sc024pub.verizon.net
;; ANSWER SECTION:
sc024pub.verizon.net.   3600    IN      A       206.46.170.25