LSTOWN-L Archives

LISTSERV List Owners' Forum

LSTOWN-L

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Topic: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Mon, 14 Feb 2000 20:50:29 -0500
text/plain (451 lines)
A list member is getting more and more "probe failed" messages.  Note:
they seem to have started on Feb 03 and are bouncing around in
cyberspace.
She is getting 18 of these a day.
HELP !
I can't figure out why they are still arriving.  I thought that even if
her ISP bounced the first probe message on 2/3 they would have stopped
by now.
Of interest is that she received NONE over the weekend, but 18 today.

any thoughts ??

--
- bill -
co-listown IRWOLF-L



-------- Original Message --------
Subject: Probe failure for IRWOLF-L
Date: Mon, 14 Feb 2000 15:11:44 -0500
From: "L-Soft list server at Apple (1.8d)"
<[log in to unmask]>
To: Martha Ryan <[log in to unmask]>

Mon, 14 Feb 2000 15:11:44

[log in to unmask]  has just  received  the enclosed
delivery
error as a  result of a probe sent to  your [log in to unmask]
account
for the  IRWOLF-L list. If  you are reading  this message, it  means
that
your mail system  is successfully delivering mail to  your mailbox,
while
at the same time reporting that an error has occurred (or,
alternatively,
the error  could be  due to a  system problem which  has since  then
been
fixed). At any rate,  LISTSERV has no way to know  that you have
actually
received the  present message,  and is operating  on the  assumption
that
your e-mail address is no longer valid. Typically, LISTSERV will send
you
one or  more additional probe  messages, on  a daily basis,  to
determine
whether the failure persists, and if so you will be removed from the
list
eventually.  Some lists  are  configured  to remove  users  on the
first
failure.

Assuming you have not  been removed from the list yet,  you can stop
this
process by sending the following command to
[log in to unmask]
as soon as possible:

                            CONFIRM IRWOLF-L

This will tell LISTSERV that your account actually does work and that
you
still want to receive mail from the IRWOLF-L list.

While the CONFIRM command will solve your immediate problem, it is only
a
matter  of time  until you  find yourself  in the  same situation
again.
Please take  a look  at the  enclosed error report  and try  to
determine
whether it is a genuine error,  or just an informational message. Bear
in
mind that this error report was  processed by a computer that cannot
tell
"User JAIME24  does not exist" from  "Please note that the  Department
of
Microbiology will be  closed from December 19 to January  2" or
"Attempts
to deliver your message have been unsuccessful for 300 seconds; will
keep
trying for  another 431700 seconds." These  informational messages,
while
possibly useful  to a  human reader, should  not be sent  in answer  to
a
message coming from a mailing list (it  is very easy for the mail
program
to determine  whether a message is  coming from a mailing  list).
Genuine
errors should be reported to  your computer/network support staff as
soon
as possible so that they can be corrected.

------------------------- Delivery error report
-------------------------
Received: from glacier.purplemtn.com by mango.ease.lsoft.com (LSMTP for
Windows NT v1.1b) with SMTP id <[log in to unmask]>; Mon,
14 Feb 2000 15:11:31 -0500
Received: from localhost (localhost)
        by glacier.purplemtn.com (Build 93 8.9.3/NT-8.9.3) with internal
id
MAA06004;
        Mon, 14 Feb 2000 12:58:22 -0700
Date: Mon, 14 Feb 2000 12:58:22 -0700
From: Mail Delivery Subsystem <[log in to unmask]>
Message-Id: <[log in to unmask]>
To: <owner-irwolf-l*elkhorn**PURPLEMTN*[log in to unmask]>
MIME-Version: 1.0
Content-Type: multipart/report; report-type=delivery-status;
        boundary="MAA06004.950558302/glacier.purplemtn.com"
Subject: Returned mail: Cannot send message within 5 days
Auto-Submitted: auto-generated (failure)

This is a MIME-encapsulated message

--MAA06004.950558302/glacier.purplemtn.com

The original message was received at Thu, 03 Feb 2000 10:17:37 -0700
from demo.lsoft.com [209.119.0.46]

   ----- The following addresses had permanent fatal errors -----
<[log in to unmask]>

   ----- Transcript of session follows -----
451 <[log in to unmask]>... I/O error: Invalid argument
<[log in to unmask]>... I/O error: Invalid argument
Warning: message still undelivered after 4 hours
Will keep trying until message is 5 days old
451 <[log in to unmask]>... I/O error: Invalid argument
<[log in to unmask]>... I/O error: Invalid argument
Warning: message still undelivered after 4 hours
Will keep trying until message is 5 days old
451 <[log in to unmask]>... I/O error: Invalid argument
<[log in to unmask]>... I/O error: Invalid argument
Warning: message still undelivered after 4 hours
Will keep trying until message is 5 days old
451 <[log in to unmask]>... I/O error: Invalid argument
<[log in to unmask]>... I/O error: Invalid argument
Warning: message still undelivered after 4 hours
Will keep trying until message is 5 days old
451 <[log in to unmask]>... I/O error: Invalid argument
<[log in to unmask]>... I/O error: Invalid argument
Warning: message still undelivered after 4 hours
Will keep trying until message is 5 days old
451 <[log in to unmask]>... I/O error: Invalid argument
<[log in to unmask]>... I/O error: Invalid argument
Warning: message still undelivered after 4 hours
Will keep trying until message is 5 days old
451 <[log in to unmask]>... I/O error: Invalid argument
<[log in to unmask]>... I/O error: Invalid argument
Warning: message still undelivered after 4 hours
Will keep trying until message is 5 days old
451 <[log in to unmask]>... I/O error: Invalid argument
<[log in to unmask]>... I/O error: Invalid argument
Warning: message still undelivered after 4 hours
Will keep trying until message is 5 days old
451 <[log in to unmask]>... I/O error: Invalid argument
<[log in to unmask]>... I/O error: Invalid argument
Warning: message still undelivered after 4 hours
Will keep trying until message is 5 days old
451 <[log in to unmask]>... I/O error: Invalid argument
<[log in to unmask]>... I/O error: Invalid argument
Warning: message still undelivered after 4 hours
Will keep trying until message is 5 days old
451 <[log in to unmask]>... I/O error: Invalid argument
<[log in to unmask]>... I/O error: Invalid argument
451 <[log in to unmask]>... I/O error: Invalid argument
<[log in to unmask]>... I/O error: Invalid argument
Warning: message still undelivered after 4 hours
Will keep trying until message is 5 days old
451 <[log in to unmask]>... I/O error: Invalid argument
<[log in to unmask]>... I/O error: Invalid argument
451 <[log in to unmask]>... I/O error: Invalid argument
<[log in to unmask]>... I/O error: Invalid argument
Warning: message still undelivered after 4 hours
Will keep trying until message is 5 days old
451 <[log in to unmask]>... I/O error: Invalid argument
<[log in to unmask]>... I/O error: Invalid argument
Warning: message still undelivered after 4 hours
Will keep trying until message is 5 days old
451 <[log in to unmask]>... I/O error: Invalid argument
<[log in to unmask]>... I/O error: Invalid argument
451 <[log in to unmask]>... I/O error: Invalid argument
<[log in to unmask]>... I/O error: Invalid argument
Message could not be delivered for 5 days
Message will be deleted from queue
451 <[log in to unmask]>... I/O error: Invalid argument
<[log in to unmask]>... I/O error: Invalid argument
Message could not be delivered for 5 days
Message will be deleted from queue
451 <[log in to unmask]>... I/O error: Invalid argument
<[log in to unmask]>... I/O error: Invalid argument
Message could not be delivered for 5 days
Message will be deleted from queue
451 <[log in to unmask]>... I/O error: Invalid argument
<[log in to unmask]>... I/O error: Invalid argument
Message could not be delivered for 5 days
Message will be deleted from queue
451 <[log in to unmask]>... I/O error: Invalid argument
<[log in to unmask]>... I/O error: Invalid argument
Message could not be delivered for 5 days
Message will be deleted from queue
451 <[log in to unmask]>... I/O error: Invalid argument
<[log in to unmask]>... I/O error: Invalid argument
451 <[log in to unmask]>... I/O error: Invalid argument
<[log in to unmask]>... I/O error: Invalid argument
451 <[log in to unmask]>... I/O error: Invalid argument
<[log in to unmask]>... I/O error: Invalid argument
451 <[log in to unmask]>... I/O error: Invalid argument
<[log in to unmask]>... I/O error: Invalid argument
Message could not be delivered for 5 days
Message will be deleted from queue
451 <[log in to unmask]>... I/O error: Invalid argument
<[log in to unmask]>... I/O error: Invalid argument
Message could not be delivered for 5 days
Message will be deleted from queue
451 <[log in to unmask]>... I/O error: Invalid argument
<[log in to unmask]>... I/O error: Invalid argument
Message could not be delivered for 5 days
Message will be deleted from queue
451 <[log in to unmask]>... I/O error: Invalid argument
<[log in to unmask]>... I/O error: Invalid argument
Message could not be delivered for 5 days
Message will be deleted from queue
451 <[log in to unmask]>... I/O error: Invalid argument
<[log in to unmask]>... I/O error: Invalid argument
Message could not be delivered for 5 days
Message will be deleted from queue
451 <[log in to unmask]>... I/O error: Invalid argument
<[log in to unmask]>... I/O error: Invalid argument
451 <[log in to unmask]>... I/O error: Invalid argument
<[log in to unmask]>... I/O error: Invalid argument
Message could not be delivered for 5 days
Message will be deleted from queue
451 <[log in to unmask]>... I/O error: Invalid argument
<[log in to unmask]>... I/O error: Invalid argument
Message could not be delivered for 5 days
Message will be deleted from queue
451 <[log in to unmask]>... I/O error: Invalid argument
<[log in to unmask]>... I/O error: Invalid argument
Message could not be delivered for 5 days
Message will be deleted from queue
451 <[log in to unmask]>... I/O error: Invalid argument
<[log in to unmask]>... I/O error: Invalid argument
Message could not be delivered for 5 days
Message will be deleted from queue
451 <[log in to unmask]>... I/O error: Invalid argument
<[log in to unmask]>... I/O error: Invalid argument
Message could not be delivered for 5 days
Message will be deleted from queue
451 <[log in to unmask]>... I/O error: Invalid argument
<[log in to unmask]>... I/O error: Invalid argument
Message could not be delivered for 5 days
Message will be deleted from queue
451 <[log in to unmask]>... I/O error: Invalid argument
<[log in to unmask]>... I/O error: Invalid argument
Message could not be delivered for 5 days
Message will be deleted from queue
451 <[log in to unmask]>... I/O error: Invalid argument
<[log in to unmask]>... I/O error: Invalid argument
Message could not be delivered for 5 days
Message will be deleted from queue
451 <[log in to unmask]>... I/O error: Invalid argument
<[log in to unmask]>... I/O error: Invalid argument
Message could not be delivered for 5 days
Message will be deleted from queue
451 <[log in to unmask]>... I/O error: Invalid argument
<[log in to unmask]>... I/O error: Invalid argument
451 <[log in to unmask]>... I/O error: Invalid argument
<[log in to unmask]>... I/O error: Invalid argument
Message could not be delivered for 5 days
Message will be deleted from queue
451 <[log in to unmask]>... I/O error: Invalid argument
<[log in to unmask]>... I/O error: Invalid argument
Message could not be delivered for 5 days
Message will be deleted from queue
451 <[log in to unmask]>... I/O error: Invalid argument
<[log in to unmask]>... I/O error: Invalid argument
Message could not be delivered for 5 days
Message will be deleted from queue
451 <[log in to unmask]>... I/O error: Invalid argument
<[log in to unmask]>... I/O error: Invalid argument
Message could not be delivered for 5 days
Message will be deleted from queue
451 <[log in to unmask]>... I/O error: Invalid argument
<[log in to unmask]>... I/O error: Invalid argument
Message could not be delivered for 5 days
Message will be deleted from queue
451 <[log in to unmask]>... I/O error: Invalid argument
<[log in to unmask]>... I/O error: Invalid argument
Message could not be delivered for 5 days
Message will be deleted from queue
451 <[log in to unmask]>... I/O error: Invalid argument
<[log in to unmask]>... I/O error: Invalid argument
Message could not be delivered for 5 days
Message will be deleted from queue
451 <[log in to unmask]>... I/O error: Invalid argument
<[log in to unmask]>... I/O error: Invalid argument
Message could not be delivered for 5 days
Message will be deleted from queue
451 <[log in to unmask]>... I/O error: Invalid argument
<[log in to unmask]>... I/O error: Invalid argument
Message could not be delivered for 5 days
Message will be deleted from queue
451 <[log in to unmask]>... I/O error: Invalid argument
<[log in to unmask]>... I/O error: Invalid argument
Message could not be delivered for 5 days
Message will be deleted from queue
451 <[log in to unmask]>... I/O error: Invalid argument
<[log in to unmask]>... I/O error: Invalid argument
Message could not be delivered for 5 days
Message will be deleted from queue
451 <[log in to unmask]>... I/O error: Invalid argument
<[log in to unmask]>... I/O error: Invalid argument
451 <[log in to unmask]>... I/O error: Invalid argument
<[log in to unmask]>... I/O error: Invalid argument
Message could not be delivered for 5 days
Message will be deleted from queue
451 <[log in to unmask]>... I/O error: Invalid argument
<[log in to unmask]>... I/O error: Invalid argument
Message could not be delivered for 5 days
Message will be deleted from queue
451 <[log in to unmask]>... I/O error: Invalid argument
<[log in to unmask]>... I/O error: Invalid argument
Message could not be delivered for 5 days
Message will be deleted from queue
451 <[log in to unmask]>... I/O error: Invalid argument
<[log in to unmask]>... I/O error: Invalid argument
Message could not be delivered for 5 days
Message will be deleted from queue
451 <[log in to unmask]>... I/O error: Invalid argument
<[log in to unmask]>... I/O error: Invalid argument
451 <[log in to unmask]>... I/O error: Invalid argument
<[log in to unmask]>... I/O error: Invalid argument
Message could not be delivered for 5 days
Message will be deleted from queue
451 <[log in to unmask]>... I/O error: Invalid argument
<[log in to unmask]>... I/O error: Invalid argument
Message could not be delivered for 5 days
Message will be deleted from queue
451 <[log in to unmask]>... I/O error: Invalid argument
<[log in to unmask]>... I/O error: Invalid argument
Message could not be delivered for 5 days
Message will be deleted from queue
451 <[log in to unmask]>... I/O error: Invalid argument
<[log in to unmask]>... I/O error: Invalid argument
Message could not be delivered for 5 days
Message will be deleted from queue

--MAA06004.950558302/glacier.purplemtn.com
Content-Type: message/delivery-status

Reporting-MTA: dns; glacier.purplemtn.com
Arrival-Date: Thu, 03 Feb 2000 10:17:37 -0700

Final-Recipient: RFC822; <[log in to unmask]>
Action: failed
Status: 4.4.7
Remote-MTA: DNS; local
Last-Attempt-Date: Mon, 14 Feb 2000 12:58:22 -0700

--MAA06004.950558302/glacier.purplemtn.com
Content-Type: message/rfc822

Return-Path:
<owner-irwolf-l*elkhorn**PURPLEMTN*[log in to unmask]>
Received: from mango.ease.lsoft.com (demo.lsoft.com [209.119.0.46])
        by glacier.purplemtn.com (Build 93 8.9.3/NT-8.9.3) with ESMTP id

KAA15536
        for <[log in to unmask]>; Thu, 03 Feb 2000 10:17:37 -0700
Received: from mango (demo.lsoft.com) by mango.ease.lsoft.com (LSMTP for

Windows NT v1.1b) with SMTP id <[log in to unmask]>; Thu, 3

Feb 2000 12:15:37 -0500
Received: from APPLE.EASE.LSOFT.COM by APPLE.EASE.LSOFT.COM
(LISTSERV-TCP/IP
          release 1.8d) with spool id 20292115 for
          [log in to unmask]; Thu, 3 Feb 2000 12:13:30 -0500
Received: from rewrite1.san.cerf.net by mango.ease.lsoft.com (LSMTP for
Windows
          NT v1.1b) with SMTP id <[log in to unmask]>; Thu,

3 Feb
          2000 12:13:29 -0500
Received: from cerfnet.com (default42.isdn-sd1.cerfnet.com
[206.19.212.42]) by
          rewrite1.san.cerf.net (8.9.3/8.9.3) with ESMTP id RAA07430 for

          <[log in to unmask]>; Thu, 3 Feb 2000 17:14:19 GMT
X-Mailer: Mozilla 4.7 [en] (Win98; I)
X-Accept-Language: en
MIME-Version: 1.0
References: <[log in to unmask]>
            <[log in to unmask]>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID:  <[log in to unmask]>
Date:         Wed, 2 Feb 2000 20:17:31 -0800
Reply-To: Irish Wolfhound discussion list
<[log in to unmask]>
Sender: Irish Wolfhound discussion list <[log in to unmask]>
From: Chris Drew <[log in to unmask]>
Subject:      [IW-L] genetic tongue dropsy versus the "just stopped by
for a
              pitty pat"
To: [log in to unmask]

bill said:
> genetic condition and I have no control.......By the way, now that I
put
> my tongue on your plate can I have it ?"

Or my fave is to be peacefully reading a book, watching tv, listening to

music or whatever and you just happen to have a small but highly
desirable morsel you are idly conveying to your own lips, savoring the
peaceful moment when...out of nowhere a nose suddenly slips under your
elbow and with a swift move, the elbow is flipped up and the morsel
careens from your fingers to arc across the room.

And the hound is standing there looking so dumbfounded like "Now HOW did

that happen?   Have you got the jitters?  Gosh and Golly, I had no
idea.  Well, since it IS dirty and I am the crumb patrol...wouldn't want

it to be just left laying around, would we?"

Another dog story:

One of my favorite men of all times was talking to me on the phone and I

heard his IW start this caterwauling.  I mean making the most dreadful
racket.  He would hold the phone away and I could hear him yelling at
his girl KoDe who would simmer down and she wouldn't even pause in this
dreadful howling whine.

He had opened a bag of Tortilla Chips and she was not allowed in the
hallway where he was talking on the phone and she wanted her chips.  I
am surprised no one called the humane society because she definitely
sounded like she was being slowly tortured.  He was so mad at her he was

bound and determined she would NOT have a chip and he was going to
finish his conversation with me without being interrupted.  KoDe was
absolutely positive her man was just overlooking her presence and had
forgotten about her.  She started rolling around and crawling on her
belly down the hallway and I could hear this
OooooOooooOoowooowoowooOOoowoowoo <scrabble scrabble> *whimper whimper*
snivel snivel...oooowwwwwooooooooooooowooooo...

ATOM RSS1 RSS2