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
PMI Support - Dave Mills <[log in to unmask]>
Fri, 18 Feb 2000 09:34:51 -0700
text/plain (560 lines)
I believe the problem has been resolved.  Please let me know it the message repeats again.
Dave

william wrote:

> Lynda and others,
> I sure could use some help.  The ISP is saying that the message is
> "stuck"
>  in the lsoft queue - lsoft says that the message keeps bouncing back
> from the isp: PURPLMTN.com.  The ex-list member says she is being
> treated badly, I say HELP !!!!!!!!!
>
> Apparently the whole problem started on 2/2/00 when the following
> message arrived, minus the IRWOLF-L footer.  It then kept repeating -
> and still is being received by her.  I have deleted the message body,
> there is not a strange header, just the same message, still minus the
> IRWOLF-L footer.
>
> -------------------------------------------------------------------------------------------------------------------------first
> message----------------------------
> Subject: [IW-L] genetic tongue dropsy versus the "just stopped by for
> apitty pat"
> Date: Wed, 2 Feb 2000 20:17:31 -0800
> From: Chris Drew <[log in to unmask]>
> Reply-To: Irish Wolfhound discussion list
> <[log in to unmask]>
> To: [log in to unmask]
> References:
> <[log in to unmask]><[log in to unmask]>
>
>  ...
> footer missing
>
> thhe same message arrived multiple times, with the same id and sending
> date.   as of yesterday it still arrives even though she is off the
> list.
> Header: from repeating message
> -----------------------------------------------------------------------------------------------------------------------------
>
> Subject: [IW-L] genetic tongue dropsy versus the "just stopped by for
> apitty pat"
> Date: Wed, 2 Feb 2000 20:17:31 -0800
> From: Chris Drew <[log in to unmask]>
> Reply-To: Irish Wolfhound discussion list
> <[log in to unmask]>
> To: [log in to unmask]
> References:
> <[log in to unmask]><[log in to unmask]>
>
> bill said:
> ...
> footer missing
>
> NOTE: the list member did not send the compete header she received so I
> can't verify the date she received it, but she is a nice and truthful
> lady so I presume that she really is getting more and more of this same
> message, two weeks later.
>
> NOW on to the probe failed
> messages-----------------------------------------------------------------------------------------------------------------------------------
>
> Up to 18 a day of these messages arrive.  At the bottom I have put a
> complete message showing the i/o error messages, the top one are just
> the header and the "delivery error report" parts of the message.  I cut
> out the lsoft probe failed boilerplate, indicated by ...
> 1st probe failed
> message:------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Subject: Probe failure for IRWOLF-L
> Date: Fri, 11 Feb 2000 12:12:19 -0500
> From: "L-Soft list server at Apple
> (1.8d)"<[log in to unmask]>
> To: Martha Ryan <[log in to unmask]>
> ...
> Fri, 11 Feb 2000 12:12:19
>
> ------------------------- 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]>; Fri,
> 11 Feb 2000 12:12:19 -0500
> Received: from localhost (localhost)
>         by glacier.purplemtn.com (Build 93 8.9.3/NT-8.9.3) with internal
> id
> JAB00002;
>         Fri, 11 Feb 2000 09:58:58 -0700
> Date: Fri, 11 Feb 2000 09:58:58 -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="JAB00002.950288338/glacier.purplemtn.com"
> Subject: Returned mail: Cannot send message within 5 days
> Auto-Submitted: auto-generated (failure)
>
> This is a MIME-encapsulated message
>
> --JAB00002.950288338/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]>
>
> another probe failed
> message------------------------------------------------------------------------------------------------------------------
>
> Subject: Probe failure for IRWOLF-L
> Date: Tue, 8 Feb 2000 16:41:21 -0500
> From: "L-Soft list server at Apple (1.8d)"
> <[log in to unmask]>
> To:
>
> Tue, 8 Feb 2000 16:41:21
> ...
> ------------------------- 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]>; Tue, 8
>
> Feb 2000 16:41:21 -0500
> Received: from localhost (localhost)
>         by glacier.purplemtn.com (Build 93 8.9.3/NT-8.9.3) with internal
> id
> OAA27049;
>         Tue, 08 Feb 2000 14:22:51 -0700
> Date: Tue, 08 Feb 2000 14:22:51 -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="OAA27049.950044971/glacier.purplemtn.com"
> Subject: Returned mail: Cannot send message within 5 days
> Auto-Submitted: auto-generated (failure)
>
> This is a MIME-encapsulated message
>
> --OAA27049.950044971/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]>
>
> another------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Subject: Probe failure for IRWOLF-L
> Date: Tue, 8 Feb 2000 12:21:43 -0500
> From: "L-Soft list server at Apple (1.8d)"
> <[log in to unmask]>
> To: Martha Ryan <[log in to unmask]>
>
> Tue, 8 Feb 2000 12:21:43
>
> [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
> ...
> ------------------------- 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]>; Tue, 8
>
> Feb 2000 12:21:31 -0500
> Received: from localhost (localhost)
>         by glacier.purplemtn.com (Build 93 8.9.3/NT-8.9.3) with internal
> id
> JAA26297;
>         Tue, 08 Feb 2000 09:59:01 -0700
> Date: Tue, 08 Feb 2000 09:59:01 -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="JAA26297.950029141/glacier.purplemtn.com"
> Subject: Warning: could not send message for past 4 hours
> Auto-Submitted: auto-generated (warning-timeout)
>
> This is a MIME-encapsulated message
>
> --JAA26297.950029141/glacier.purplemtn.com
>
>     **********************************************
>     **      THIS IS A WARNING MESSAGE ONLY      **
>     **  YOU DO NOT NEED TO RESEND YOUR MESSAGE  **
>     **********************************************
>
> 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 transient non-fatal errors -----
> <[log in to unmask]>
>
> another: This time I included the whole message, note the multiple ISP
> error
> messages:----------------------------------------------------------------------
>
> 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:32 -0500
> Received: from localhost (localhost)
>         by glacier.purplemtn.com (Build 93 8.9.3/NT-8.9.3) with internal
> id
> MAA06005;
>         Mon, 14 Feb 2000 12:58:27 -0700
> Date: Mon, 14 Feb 2000 12:58:27 -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="MAA06005.950558307/glacier.purplemtn.com"
> Subject: Returned mail: Cannot send message within 5 days
> Auto-Submitted: auto-generated (failure)
>
> This is a MIME-encapsulated message
>
> --MAA06005.950558307/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
> 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
>
> --MAA06005.950558307/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:27 -0700
>
> --MAA06005.950558307/glacier.purplemtn.com
> Content-Type: message/rfc822
>
> --
> - bill -
>
> and Deborah,
> and the Hounds of Heaven: Fionna, Tulia, Carina (aka "the Monster"), and
> Becka
> visit us at: http://www.HoundsOfHeaven.com

ATOM RSS1 RSS2