🚀 go-pugleaf

I have been on the phone with their 1st and 2nd
level support for hours.  They don't acnowledge
this problem.  They will not let me speak with
their postmaster, and messages to
postmaster@demon.net are ignored.

I have now started to email all the messages we
get back this way to them.

I have analysed the problem to be 100% verified
demon.net at fault.

I have suggested to them where they might look
for the fault, but they insist that it can't be
at their end.  They have a policy not to take any
queries regarding their mail servers if it is not
accompanied with a mail header generated at their
system.  As the mail header is never generated
they are ignoring the problem altogether.

The log of the connection is VERY CLEAR:
01:29 00:04 SMTP-(00000227) Trying
cheshirecircuits.co.uk (0)
01:29 00:04 SMTP-(00000227) Connect
cheshirecircuits.co.uk [194.217.242.35:25] (1)
01:29 00:04 SMTP-(00000227) 220 punt-
10.mail.demon.net Server SMTP (Complaints/bugs
to:  postmaster@demon.net)
01:29 00:04 SMTP-(00000227) >EHLO
mail.kookiejar.net
01:29 00:04 SMTP-(00000227) 500 Unknown or
unimplemented command
01:29 00:04 SMTP-(00000227) >HELO
mail.kookiejar.net
01:29 00:04 SMTP-(00000227) 250 Good morning,
pleased to meet you
01:29 00:04 SMTP-(00000227) >MAIL
FROM:<Nigel@prestim.co.uk>
01:29 00:04 SMTP-(00000227) 451 Nameserver
timeout during parsing
01:29 00:04 SMTP-(00000227) SMTP_DELIV_FAILED
01:29 00:04 SMTP-(00000227) >QUIT
01:29 00:04 SMTP-(00000227) 221 punt-
10.mail.demon.net says goodbye to
ns10.kookiejar.net at Sat Jan 29 00:01:33.

DEMON FIX THIS THING.  Don't look stupid by
ignoring it, FIX IT !

The problem lies most likely in the fact that
their ns0.demon.net and/or ns1.demon.net are not
reachable via their internal LAN for address
resolution.

>>> By the way. I have noticed a SHARP increase
in business with as reason: Demon won't deliver
my mail anymore....

Anthony Santen
NetSolution.co.uk


In article <85djud$394$1@gxsn.com>,
  "Nuera" <the1@globalnospamnet.co.uk> wrote:
> Is anyone else having problems sending emails
to a Demon user, or if your a
> Demon user are you having problems receiving
emails ?
>
> For more than two months almost every email
I've tried to send to a Demon
> user has been retruned or delayed, generally
due to parsing on the punt 1 &
> punt 2 mailservers.
>
> Its beginning to really piss me off.
>
> At first we though Globalnet was to blame, but
I'm getting the same
> problems when sending from other SMTP servers,
and it ONLY happens when the
> recipient has a Demon account.
>
> see below for a common transcript:
> ------------------------------------------------
------
>
> The original message was received at Fri, 10
Dec 1999 11:57:10 -0500 (EST)
> from opal.virtual-domain.com [209.67.8.180]
>
>    ----- The following addresses had permanent
fatal errors -----
> website@homeblown.demon.co.uk
>
>    ----- Transcript of session follows -----
> .. while talking to punt-1.mail.demon.net.:
> >>> MAIL From:<neut@neutralize.com>
> <<< 451 Nameserver timeout during parsing
> .. while talking to punt-2.mail.demon.net.:
> >>> MAIL From:<neut@neutralize.com>
> <<< 451 Nameserver timeout during parsing
> website@homeblown.demon.co.uk... Deferred: 451
Nameserver timeout during
> parsing
> Message could not be delivered for 5 days
> Message will be deleted from queue
>
>



Sent via Deja.com http://www.deja.com/
Before you buy.

On Sat, 29 Jan 2000 18:03:05 GMT, asanten@my-deja.com <asanten@my-deja.com> wrote:
>I have been on the phone with their 1st and 2nd
>level support for hours.  They don't acnowledge
>this problem.  They will not let me speak with
>their postmaster, and messages to
>postmaster@demon.net are ignored.
>
>I have now started to email all the messages we
>get back this way to them.

This runs a risk that a complaint will be raised with your provider :(

>I have analysed the problem to be 100% verified
>demon.net at fault.

Our experts disagree with your analysis.

>I have suggested to them where they might look
>for the fault, but they insist that it can't be
>at their end.  They have a policy not to take any
>queries regarding their mail servers if it is not
>accompanied with a mail header generated at their
>system.  As the mail header is never generated
>they are ignoring the problem altogether.
>
>The log of the connection is VERY CLEAR:

Indeed.

>01:29 00:04 SMTP-(00000227) Trying
>cheshirecircuits.co.uk (0)
>01:29 00:04 SMTP-(00000227) Connect
>cheshirecircuits.co.uk [194.217.242.35:25] (1)
>01:29 00:04 SMTP-(00000227) 220 punt-
>10.mail.demon.net Server SMTP (Complaints/bugs
>to:  postmaster@demon.net)
>01:29 00:04 SMTP-(00000227) >EHLO
>mail.kookiejar.net
>01:29 00:04 SMTP-(00000227) 500 Unknown or
>unimplemented command
>01:29 00:04 SMTP-(00000227) >HELO
>mail.kookiejar.net
>01:29 00:04 SMTP-(00000227) 250 Good morning,
>pleased to meet you
>01:29 00:04 SMTP-(00000227) >MAIL
>FROM:<Nigel@prestim.co.uk>

A user at prestim.co.uk claimed to be sending mail to our MX relay.

>01:29 00:04 SMTP-(00000227) 451 Nameserver
>timeout during parsing

A nameserver timed out. At the time our mail relay was checking
prestim.co.uk to see if it has a valid DNS entry.

Now which nameserver would it be using to check prestim.co.uk ?

>01:29 00:04 SMTP-(00000227) SMTP_DELIV_FAILED
>01:29 00:04 SMTP-(00000227) >QUIT
>01:29 00:04 SMTP-(00000227) 221 punt-
>10.mail.demon.net says goodbye to
>ns10.kookiejar.net at Sat Jan 29 00:01:33.

Hmmm - there appears to be a hint here ... ns10.kookiejar.net is one
of the nameservers for prestim.co.uk.

>DEMON FIX THIS THING.  Don't look stupid by
>ignoring it, FIX IT !

I am afraid the problem lies with the people that host prestim.co.uk -
their nameserver is timing out requests :(

>The problem lies most likely in the fact that
>their ns0.demon.net and/or ns1.demon.net are not
>reachable via their internal LAN for address
>resolution.

Nope - wrong nameserver. I suspect the other message in this thread
has a similar answer.

Our experts also point out that the two nameservers for prestim.co.uk
have adjacent IP addresses (209.205.25.141 and 209.205.25.140) which
suggests they are on the same network segment at the same location
sharing connectivity to the Internet. This is considered unwise and
could account for some of the difficulty reaching them.

As an example we have three name servers in defferent buildings, on
different networks, in two countries.

-- 
Malcolm S. Muir                               Demon Internet
Sunderland                                    322 Regents Park Road
England                                       London N3 2QQ