John..
>I have been having problems sending mail to a verizon.net address for
>about a week. Is it just me
no idea ... do you have a message of any kind ?
>of is anyone else having this problem. My
>exchange server reports only that it failed to connect.
to which IP address ?
--
richard writing to inform and not as company policy
"Assembly of Japanese bicycle require great peace of mind" quoted in ZAMM
Sorry no.
>
>
>>of is anyone else having this problem. My
>>exchange server reports only that it failed to connect.
>
>
> to which IP address ?
relay.verizon.net (206.46.170.12)
John..
There's been a thread on this in uk.net.providers.aaisp over the last few
days. It looks like a configuration problem (or configurer problem) at
Verizon.
--
Thomas Sandford | ${thomas/03$}@paradisegreen.co.uk
Paradise Green Technical Services: S'ware/Hw design and Theatre Tech. Services
Email to this address from commercial mailing lists constitutes unauthorised
computer access, and appropriate action will be taken against offenders.
Thomas Sandford wrote:
| John de Mattos <jne...@appscintech.com> wrote:
|
|>I have been having problems sending mail to a verizon.net address for
|>about a week. Is it just me of is anyone else having this problem. My
|>exchange server reports only that it failed to connect. I have tried
|>sending via the demon smart host but this does not work either. Could
|>this be a Demon problem or is it more likely a problem with
verizon.net?
|
|
| There's been a thread on this in uk.net.providers.aaisp over the
last few
| days. It looks like a configuration problem (or configurer problem) at
| Verizon.
And Nanog and elsewhere. Perhaps Demon might check their mail logs
and let us know if they see it as well.
Symptom is can ping relay.verizon.net, but port 25 goes unanswered
(Sendmail "connection timed out"). So in general people won't have
messages to report till 3 or 5 days depending on the time allowed in
the queue.
So far only reports from the UK, US users seem to have no trouble,
but I can't believe it is UK specific, the Internet IP address
allocation and routing is not that focused (is it?).
Certainly not Demon specific, my SDU behaves just like out servers
hosted at two other UK ISPs. I have reports from 5 UK ISPs now of
the same issue. I assume it is either a spam block gone badly wrong,
or possibly a load balancing issue of some kind.
I've been trying to reach clue at Verizon since Friday, if they are
aware (and I'm told they are), they haven't asked for any assistance
in understanding the scope or nature of the problem.
-----BEGIN PGP SIGNATURE-----
Comment: Using GnuPG with Debian - http://enigmail.mozdev.org
iD8DBQFBv4BJGFXfHI9FVgYRAlaYAJ95Rr9IdZUc5WX1G6+hXBqm80ZOJQCgk8DN
hspbRPy2IsARRZfag+/XlWI=
=Czk7
-----END PGP SIGNATURE-----
>Perhaps Demon might check their mail logs
>and let us know if they see it as well.
Verizon were not accepting connections from the post machines on Monday.
I have not checked for all of today... but they weren't accepting
connections from at least one AS2529 machine this PM
>So far only reports from the UK, US users seem to have no trouble,
I found it was possible to connect from 18.0.0.0/8 ... but possibly not
from a machine that normally talks to them -- which may be relevant (or
may not, depends what their issue is)
>but I can't believe it is UK specific
Verizon may not like the UK -- there's no obligation on them to accept
email from anywhere really :(
>I've been trying to reach clue at Verizon since Friday, if they are
>aware (and I'm told they are), they haven't asked for any assistance
>in understanding the scope or nature of the problem.
perhaps they already do :(
Is there anything Demon can do?
John..
I've pondered routing around the problem, which I guess Demon could do
as well, but generally it is a bad idea to try and hack around other
peoples failings, as it complicates the systems, which are quite
complex <sophisticated?> enough already.
Generally only customers get anywhere with these big organisations. We
couldn't even get to speak to clueless people at Verizon without an
ADSL customers account details. But the story I hear is different for
each customer. Some get a story saying they know there is a problem,
some are told it is the remote end.
One of our clients was told we should email secu...@verizon.net to
describe the problem further <doh - I bet that support guy has had
better days>.
Thanks for checking the logs Richard.
One of our customers has started having this problem over the last week.
I tried connecting to relay.verizon.net from a few different "open relay"
checkers, including one in Japan, and couldn't connect. So it's not just a
UK-specific problem.
The customer got in touch with Verizon and said...:
"I've spoken to Verizon and apparently they've just noted the issue and are
working it as a "whiteboard" item (which means it's a major problem that
they freely admit to when you call them but they don't want to scare their
users by actually advertising it ;)"
Nice...
Mike
>In article <cpnv90$jh5$1$8302...@news.demon.co.uk>, Simon Waters
><si...@wretched.demon.co.uk> writes
>
>>Perhaps Demon might check their mail logs
>>and let us know if they see it as well.
>
>Verizon were not accepting connections from the post machines on Monday.
>I have not checked for all of today... but they weren't accepting
>connections from at least one AS2529 machine this PM
Any update on this? I started using post yesterday to clear the
backlog of messages in our queue (around 200 from a mailing list), as
I was able to connect from my shell account hosted in the US, but it
appears these may all come back from post as undeliverable in a few
days?
Andrew.
--
Andrew Hodgson in Bromyard, Herefordshire, UK.
My Email: use <andrew at hodgsonfamily dot org>.
>On Wed, 15 Dec 2004 00:28:04 +0000, Richard Clayton
><ric...@highwayman.com> wrote:
>
>>In article <cpnv90$jh5$1$8302...@news.demon.co.uk>, Simon Waters
>><si...@wretched.demon.co.uk> writes
>>
>>>Perhaps Demon might check their mail logs
>>>and let us know if they see it as well.
>>
>>Verizon were not accepting connections from the post machines on Monday.
>>I have not checked for all of today... but they weren't accepting
>>connections from at least one AS2529 machine this PM
>
>Any update on this?
I've looked at some 29 Dec logs, and can see email being accepted; and
also quite a lot of junk being rejected :(
>I started using post yesterday to clear the
>backlog of messages in our queue (around 200 from a mailing list), as
>I was able to connect from my shell account hosted in the US, but it
>appears these may all come back from post as undeliverable in a few
>days?
as always, it is almost entirely impossible to comment upon email
problems without sight of the messages and bounces involved
>In article <v2f6t0hmffr8sfb75...@4ax.com>, Andrew Hodgson
><m...@privacy.net> writes
>
>>On Wed, 15 Dec 2004 00:28:04 +0000, Richard Clayton
>><ric...@highwayman.com> wrote:
>>
>>>Verizon were not accepting connections from the post machines on Monday.
>>>I have not checked for all of today... but they weren't accepting
>>>connections from at least one AS2529 machine this PM
>>
>>Any update on this?
>
>I've looked at some 29 Dec logs, and can see email being accepted; and
>also quite a lot of junk being rejected :(
more evidence that this is a verizon.support issue (and not especially
relevant to d.s)
<URL:http://www.broadbandreports.com/forum/remark,12116645~mode=flat~day
s=9999>
Richard Clayton wrote:
|
| more evidence that this is a verizon.support issue (and not especially
| relevant to d.s)
I didn't think there was any doubt, Verizon seemed to blacklist all
major foreign ISPs without telling anyone, do we have an award for
the most stupid ISP cock-up of the year? I'm just amazed it didn't
get more press coverage, guess it didn't have the humour value of
the Harvard/AOL cock-up.
Still handy for people to know why they couldn't email Verizon.
-----BEGIN PGP SIGNATURE-----
Comment: Using GnuPG with Debian - http://enigmail.mozdev.org
iD8DBQFB1ZYXGFXfHI9FVgYRAhVVAJ97+72Xm2f17lUHaOG7NInDQ2SwqgCgtm9R
9l0BUcajYBOO4CbPIYXR6kY=
=H/J0
-----END PGP SIGNATURE-----