I'm getting the following error messages for the FEMINAMAIL list that sent
out the newsletter for what now turns out 8 times.  Could and invalid entry
be the cause of multiple mailings?  How can I fix an invalid entry in the
list?  I can't figure out where listserv is storing the lists email
addresses.

Also, I'm not really sure how target-soft.com & gerstl-haustechnik.de would
be able to actually post to the list because this is an announce only list.

ERROR MESSAGES
>>> LSWLSTGN: Invalid entry in FEMINAMAIL list, line 790
>>> LSWLSTGN: data=
>>> LSWLSTGN: Invalid entry in FEMINAMAIL list, line 855
>>> LSWLSTGN: data=
>>> LSWLSTGN: Invalid entry in FEMINAMAIL list, line 1067
>>> LSWLSTGN: data=
>>> LSWLSTGN: Invalid entry in FEMINAMAIL list, line 1068
>>> LSWLSTGN: data=
>>> LSWLSTGN: Invalid entry in FEMINAMAIL list, line 1077
>>> LSWLSTGN: data=
>>> LSWLSTGN: Invalid entry in FEMINAMAIL list, line 1078
>>> LSWLSTGN: data=
>>> LSWLSTGN: Invalid entry in FEMINAMAIL list, line 1079
>>> LSWLSTGN: data=
>>> LSWLSTGN: Invalid entry in FEMINAMAIL list, line 1080
>>> LSWLSTGN: data=
>>> LSWLSTGN: Invalid entry in FEMINAMAIL list, line 1081
>>> LSWLSTGN: data=
>>> LSWLSTGN: Invalid entry in FEMINAMAIL list, line 1082
>>> LSWLSTGN: data=
>>> LSWLSTGN: Invalid entry in FEMINAMAIL list, line 1083
>>> LSWLSTGN: data=
>>> LSWLSTGN: Invalid entry in FEMINAMAIL list, line 1084
>>> LSWLSTGN: data=
>>> LSWLSTGN: Invalid entry in FEMINAMAIL list, line 1085
>>> LSWLSTGN: data=
>>> LSWLSTGN: Invalid entry in FEMINAMAIL list, line 1086

-----Original Message-----
From: LISTSERV give-and-take forum
[mailto:[log in to unmask]]On Behalf Of Valdis Kletnieks
Sent: Friday, November 07, 2003 2:29 AM
To: [log in to unmask]
Subject: Re: Same email going out 4 times


On Fri, 07 Nov 2003 00:01:00 EST, Nelly Yusupova <[log in to unmask]>  said:
> Hmmm...this is the header for one of the messages.  Why are there so many
> Received lines?  Can someone explain how this header could be the reason
the
> newsletter went out multiple times?

> Received: from mailout03.sul.t-online.com (mailout03.sul.t-online.com
>           [194.25.134.81]) by echo.cgim.com (8.11.6/8.11.6) with ESMTP id
>           hA6A0Jh06799 for <[log in to unmask]>; Thu, 6 Nov 2003
>           05:00:19 -0500 (EST)
> Received: from fwd07.aul.t-online.de by mailout03.sul.t-online.com with
smtp
> id
>           1AHheJ-00065k-0M; Thu, 06 Nov 2003 11:45:59 +0100
> Received: from target01.target-soft.com
> (JT5fvBZ6gekbuVfexZx3ZJSpLV7mpWdRvK7BdqXZhnL4+O+Uvo9nYq@[80.131.155.14])
by
> fmrl07.sul.t-online.com with
>           esmtp id 1AHheA-2Bomgq0; Thu, 6 Nov 2003 11:45:50 +0100

It's looping.  Do you have the loop detector disabled, it SHOULD usually
catch these.

> Delivered-To: [log in to unmask]
> Received: (qmail 15588 invoked by uid 110); 6 Nov 2003 10:35:49 -0000
> Delivered-To: [log in to unmask]
> Received: (qmail 15584 invoked from network); 6 Nov 2003 10:35:49 -0000

Apparently, somebody at target-soft.com is doing something evil/stupid with
the mail
and reposting it.  But wait....


> Received: from mailout04.sul.t-online.com (mailout04.sul.t-online.com
>           [194.25.134.18]) by echo.cgim.com (8.11.6/8.11.6) with ESMTP id
>           hA63gvh18595 for <[log in to unmask]>; Wed, 5 Nov 2003
>           22:42:57 -0500 (EST)
> Received: from fwd09.aul.t-online.de by mailout04.sul.t-online.com with
smtp
> id
>           1AHbl5-0001Cw-00; Thu, 06 Nov 2003 05:28:35 +0100
> Received: from gerstl1.gerstl-haustechnik.de
>
> (E2I-F6ZGgeAd9qt9MMdlm51uz7kEjPKSszL5PCAPVXFBBJAarKg96M@[217.228.219.48])
by
> fmrl09.sul.t-online.com with
>           esmtp id 1AHbl3-1L32n20; Thu, 6 Nov 2003 05:28:33 +0100
> thread-index: AcOkHm9XTGi2FHQ1QI61LfeHht3O0g==
> Received: from mail pickup service by gerstl1.gerstl-haustechnik.de with
>           Microsoft SMTPSVC; Thu, 6 Nov 2003 05:28:31 +0100

Here's another loop - but THIS one was a gerstl-haustechnik.de recipient,
but
it ended up at a fwd*.auk.t-online.de machine again...

If I didn't know better, I'd say you have 2 subscribers who are forwarding
their mail, and t-online.de is intercepting the forwarding and then botching
it.  The odd part is that in that failure mode, it *should* have gone
into Sorceror's Apprentice mode (both subscriber's forwarding should have
been trapped and sent back, causing 2 reposts, then both of those should
have
generated 2 more, an those 4 should have....).   I'm really confused
why t-online.de did it 2 different times for 2 different subscribers.

This is just too bizarre for me to decypher at 2:30AM (and that's saying
a lot.. ;)