Gerhard Fiedler wrote:

> I don't remember the exact command, but there is a command you can
> send to the list server which enables that your own messages get sent
> back to you (by default this is disabled).

  As others have said, SET PICLIST REPRO

  But this must be sent to the listserver, *not* the list.  What's the
bet we get half a dozen postings of this to the list?

> as long as this is going like it does, you might want to enable this
> option -- then you get a confirmation that your message got through
> despite the "rejected" messages.

  I see no reason whatsoever to do so.  As best I can see, *No-one* is
getting "rejected" messages, they are *already* getting *confirmatory*
replies.

  What is so absolutely, awfully infuriating about the problem is the
stubborn refusal of people to *read* the messages they get.  They look
at them briefly and presume, but don't actually read them.  That said,
it's understandable given the awful "block" (Justified) format of the
message, 8 or 9 solid lines of apparently conflicting information.

  You may actually receive either or *both* of two sorts of message,
*neither* of which makes any suggestion you should post again!

  The error-message from the list-server *DOES NOT SAY* that your
message wasn't transferred, or didn't "get through".  Those who actually
*read* it find what it actually says is that your posting was received
by the list-server *more than once* and was distributed the first time.

  Of course, you didn«t post it more than once to start with, so it was
obviously not your fault, but must have been an "echo" somewhere and of
course this matter is still under investigation.  The list is telling
you it has a *safety feature* to prevent messages being sent out more
than once.

  Therefore, as it *has* distributed it already, you shouldn«t post it
*again*.  This message goes on to say if you *really, really, really*
want to subject the list to *extra* copies of your posting, you have to
change it around to get past its protective function.  But you *don«t*
want to do this!

  The second sort of message says that a posting couldn«t be delivered
somewhere, *because the recipient no longer exists*.

  This message is *not* from the listserver, but from some long-forsaken
spot in the wilds of the Internet, not even remotely connected with the
listserver.  It's impossible your message would need to stop off at this
site to arrive at the listserver, so it's obviously been passed on and
*everyone else* on the list has received the posting, so you don«t need
to send it again.

  Not only that, but the message is telling you explicitly that no
matter *how many* times you send, it will *never* get to this particular
recipient because ... they no longer exist!  It«s not fair to spam the
rest of the list just to test that out.
-- 
  Cheers,
        Paul B.