Verizon FiOS: No SMTP Service

My neighbor is letting me connect to his Verizon FiOS wireless router while
he's away. Everything works OK, except outgoing mail.

Attempts to connect to port 25 of 'relay.verizon.net', which is the MX for
verizon.net, causes the mail server to close the connection with the
message:

"571 Email from 71.175.54.72 is currently blocked by Verizon Online's
anti-spam system. The email sender or Email Service Provider may visit
http://www.verizon.net/whitelist and request removal of the block."

That address is within Verizon Internet Services own CIDR block:
71.160.0.0/11, so why is it blocked? It belongs to a Verizon customer.

What's going on? Does the router assign a different IP address to each user
on the local network? That doesn't seem right.

Or am I all wet about that Verizon MX server?

HaroldWho
--
Powered by Slackware 12.0 Linux -- Kernel 2.6.21.5-hla
News Reader slrn 0.9.8.1

On Tue, 26 Feb 2008 19:38:24 -0000, HaroldWho wrote:
> My neighbor is letting me connect to his Verizon FiOS wireless router while
> he's away.

Bet he would just hate if Verizon cancels his service for violation of
his agreement by allowing you access.

> Everything works OK, except outgoing mail.
>
> What's going on? Or am I all wet about that Verizon MX server?

Outbound mail is to be sent to outgoing.verizon.net. To stop malware
from sending email, user id and password are required to send mail.

On Tue, 26 Feb 2008 19:38:24 +0000, HaroldWho wrote:

> Attempts to connect to port 25 of 'relay.verizon.net', which is the MX for
> verizon.net, causes the mail server to close the connection with the
> message:
>
> "571 Email from 71.175.54.72 is currently blocked by Verizon Online's
> anti-spam system. The email sender or Email Service Provider may visit
> http://www.verizon.net/whitelist and request removal of the block."

Those people have some real problems maintaining their SMTP services. I
have seen their servers go down for up to a week. But they didn't send
that message then.

Why not do as they suggest and see if the problem gets resolved?

On Tue, 26 Feb 2008 13:50:15 -0600, Dave Uhring wrote:
>
> Those people have some real problems maintaining their SMTP services. I
> have seen their servers go down for up to a week. But they didn't send
> that message then.

I have been a FiOS customer for about 8 months.
I have a humor/fyi email list which sends something almost every day.
I have had no problems with Verizon but have received a few messages
about hotmail and yahoo not accepting mail.

On Tue, 26 Feb 2008 20:03:51 +0000, Bit Twister wrote:
> On Tue, 26 Feb 2008 13:50:15 -0600, Dave Uhring wrote:
>>
>> Those people have some real problems maintaining their SMTP services. I
>> have seen their servers go down for up to a week. But they didn't send
>> that message then.
>
> I have been a FiOS customer for about 8 months.
> I have a humor/fyi email list which sends something almost every day.
> I have had no problems with Verizon but have received a few messages
> about hotmail and yahoo not accepting mail.

They may finally have fixed their problems in having SMTP servers which
actually accept messages from the Internet. I used to have queued
messages from our customers attempt retransmit every 1/2 hour for 5 days
and eventually bounce back to the senders because of Verizon's ineptness.

HaroldWho wrote:

> My neighbor is letting me connect to his Verizon FiOS wireless router while
> he's away. Everything works OK, except outgoing mail.
>
> Attempts to connect to port 25 of 'relay.verizon.net', which is the MX for
> verizon.net, causes the mail server to close the connection with the
> message:

What a surprise, you made up a procedure and it didn't work.

> "571 Email from 71.175.54.72 is currently blocked by Verizon Online's
> anti-spam system. The email sender or Email Service Provider may visit
> http://www.verizon.net/whitelist and request removal of the block."
>
> That address is within Verizon Internet Services own CIDR block:
> 71.160.0.0/11, so why is it blocked? It belongs to a Verizon customer.

It's blocked because that's not the correct method for sending mail
through Verizon. You did what a malware script would do rather than
what a sane person would do, so Verizon treated you like malware.

> What's going on? Does the router assign a different IP address to each user
> on the local network? That doesn't seem right.

How could the router not assign a different IP address to each machine
on the local network? What else could it do?

> Or am I all wet about that Verizon MX server?

Yeah, Verizon's instructions like a smart human being rather than
thrashing around randomly like a piece of malware.

DS

On Tue, 26 Feb 2008 15:44:39 -0800 (PST), David Schwartz wrote
in comp.os.linux.networking:
>
> What a surprise, you made up a procedure and it didn't work.
>
> It's blocked because that's not the correct method for sending mail
> through Verizon. You did what a malware script would do rather than
> what a sane person would do, so Verizon treated you like malware.
>
> Yeah, Verizon's instructions like a smart human being rather than
> thrashing around randomly like a piece of malware.
>
> DS

Wow, are you this helpful all the time? Try to stay on your meds.

HW
--
Powered by Slackware 12.0 Linux -- Kernel 2.6.21.5-hla
News Reader slrn 0.9.8.1

On Tue, 26 Feb 2008 19:45:16 +0000 (UTC), Bit Twister wrote
in comp.os.linux.networking:
> On Tue, 26 Feb 2008 19:38:24 -0000, HaroldWho wrote:
>> My neighbor is letting me connect to his Verizon FiOS wireless router while
>> he's away.
>
> Bet he would just hate if Verizon cancels his service for violation of
> his agreement by allowing you access.

Oops, I guess he didn't know that, nor did I.

> Outbound mail is to be sent to outgoing.verizon.net. To stop malware
> from sending email, user id and password are required to send mail.
>

Well, that would explain it. I wonder why an MX request with 'dig' returns
that 'relay.verizon.net' address.

Anyway, thanks for clearing that up.

HW
--
Powered by Slackware 12.0 Linux -- Kernel 2.6.21.5-hla
News Reader slrn 0.9.8.1

On Feb 27, 11:08 am, HaroldWho <r...@yahoo.com> wrote:

> Wow, are you this helpful all the time? Try to stay on your meds.

Sometimes the most helpful thing you can do is show a person that they
are approaching a problem completely the wrong way.

DS

On Wed, 27 Feb 2008 19:12:01 +0000, HaroldWho wrote:

> Well, that would explain it. I wonder why an MX request with 'dig'
> returns that 'relay.verizon.net' address.

Because that's the name used for inbound service, which is what one wants
to express with an MX record. There's no analog for expressing the
outbound server in DNS. Presumably, this is because "inside" users have
some other way of informing themselves of their outbound server(s) (ie.
the documentation at which clients are pointed).

[Though it occurs to me that this would be a useful field provided by
DHCP servers.]

- Andrew