Verizon Postmaster contact?

Hi,

I see VZ was not kind enough to put any contact info in Jared's NOC list.
They are currently blocking all mail from an ISP customer of mine (based
on the envelope From, not IP), and I need to get someone on the phone to
clear this up.

Sorry for the OT.

Charles

My understanding is that they started breaking the RFC by refusing mail
with null <> senders last week.

Based on past experience, I wasn't too surprised.

-bob

My understanding is that they started breaking the RFC by refusing mail
with null <> senders last week.

Based on past experience, I wasn't too surprised.

Heh.

Doesn't seem to be that:

spork@green[~]$ telnet relay.verizon.net 25
Trying 206.46.170.12...
Connected to relay.verizon.net.
Escape character is '^]'.
220 sc001.verizon.net MailPass SMTP server v1.0.6 - 103003062626JY ready
Mon, 3 Nov 2003 14:00:11 -0600
mail from: spork@spork.us
250 Sender <spork@spork.us> OK
rset
250 Ok resetting state
mail from: spork@bway.net
550 You are not allowed to send mail:sc001.verizon.net
rset
250 Ok resetting state
mail from: <spork@bway.net> sporker
550 You are not allowed to send mail:sc001.verizon.net
quit
221 sc001.verizon.net closing connection
Connection closed by foreign host.

We receive very very few spam complaints, and spamcop has been silent on
us for at least a month. About the only spam I've been made aware of is
from trojaned dsl customers, but we cut that off when notified. So I'm at
a loss as to what this is all about...

Thanks,

Charles

Bob German writes on 11/3/2003 2:54 PM:

My understanding is that they started breaking the RFC by refusing mail
with null <> senders last week.

Based on past experience, I wasn't too surprised.

Doesn't look like they are doing this.

suresh@frodo 01:31:15 [~]$ dnsmx verizon.net
0 relay.verizon.net

suresh@frodo 01:31:23 [~]$ telnet relay.verizon.net 25
Trying 206.46.170.12...
Connected to relay.verizon.net.
Escape character is '^]'.
220 sc011.verizon.net MailPass SMTP server v1.0.6 - 103003062626JY ready Mon, 3 Nov 2003 14:01:28 -0600
ehlo frodo.hserus.net
250-sc011.verizon.net
250-8BITMIME
250 SIZE 20971520
mail from: <>
250 Sender <> OK
rcpt to: <postmaster@verizon.net>
250 Recipient <postmaster@verizon.net> Ok
rset
250 Ok resetting state
quit
221 sc011.verizon.net closing connection
Connection closed by foreign host.

Another thing - verizon is fairly responsive and does have some clued people in there. I have forwarded this thread to a friend in Verizon's postmaster desk.

  srs

I see VZ was not kind enough to put any contact info in Jared's NOC
list. They are currently blocking all mail from an ISP customer of
mine (based on the envelope From, not IP), and I need to get someone
on the phone to clear this up.

Verizon is listed in EDDB; I think that I've made this offer here
before, but anybody who'd like to participate in EDDB, and who
otherwise qualifies, can have a healthy "Nanog Discount", or even be
listed only (no access) for free.

EDDB is at http://www.isipp.com/eddb.php

In the meantime, Charles, may I forward your note to the Verizon
contact?

Anne

Anne P. Mitchell, Esq.
President/CEO
Institute for Spam & Internet Public Policy
Professor of Law, Lincoln Law School of SJ

I am working on the issue(s) now.

I am working on the issue(s) now.

The only problem is, you're not getting my replies because you are also
now deferring mail from this ISP as well... It sounds like something is
either a bit overzealous, or more likely, broken.

Anyone else want to dig around for VZ deferrals?

Thanks,

Charles

Charles Sprickman writes on 11/3/2003 8:29 PM:

Anyone else want to dig around for VZ deferrals?

You mean their 4xx'ing all mail that you send them?

thenose.net is Dennis' personal domain btw - that's not hosted by Verizon.

No, I'm seeing your e-mail's at verizon.net. In fact, you just replied to
one of my inquires. I am researching the issue and will make a reply to you
as soon as I understand what is going on.

-Dennis

Getting 550's all day on MAIL FROM: <*@modwest.com> -- noticed it because we're running billing.