Post by thread:piclist digest

Hello to all who want to archive all the piclist traffic themselves: Here I quote a part of the mail, every new subscriber gets after successful subscription to the piclist: ------------------------------------------------------------------------------- ... Please save this message for future reference, especially if you are not familiar with LISTSERV. This might look like a waste of disk space now, but in 6 months you will be glad you saved this information when you realize that you cannot remember what are the lists you are subscribed to, or what is the command to leave the list to avoid filling up your mailbox while you are on vacations. ... Contributions sent to this list are automatically archived. You can get a list of the available archive files by sending an "INDEX PICLIST" command to spam_OUTLISTSERVTakeThisOuTMITVMA.BITNET (or .....LISTSERVKILLspam@spam@MITVMA.MIT.EDU). You can then order these files with a "GET PICLIST LOGxxxx" command, or using LISTSERV's database search facilities. Send an "INFO DATABASE" command for more information on the latter. ... More information on LISTSERV commands can be found in the LISTSERV reference card, which you can retrieve by sending an "INFO REFCARD" command to LISTSERVKILLspamMITVMA.BITNET (or .....LISTSERVKILLspam.....MITVMA.MIT.EDU). ------------------------------------------------------------------------------- to summarize: send GET PICLIST LOG9509 to EraseMELISTSERVspam_OUTTakeThisOuTMITVMA.MIT.EDU, wait some seconds and you have what you want. Siggi

> Mike DeMetz wrote: > > > Excuse the double posting. The PICLIST server was sending me an > > undeliverable mail message. > > I can't see a connection between an undeliverable mail message and > double posting? Is this an implementation of the engineer's dictum "If it > doesn't fit the hole, whack harder"? > It is a normal response to sending a message to a list server and having a error in delivery sent back > Today's lesson: The PIClist server does *not* send "undeliverable > mail" messages. How could it? Why would it? > The headers indicated that it went to PICLISTspam_OUTMITVMA.MIT.EDU then to 3rd party who rejected it back to me. Why would it? How could it?