Discussion of spam-fighting and prevention techniques, discussion of ongoing legislation and the pros/cons of same, and other spam-related discussion.
Posting spam you receive is OK, as long as you follow these guidelines:
Here's a few other guidelines for posting to SPAM-L:
There is a limit of 8 postings per day per subscriber, and each post may be up to 200 lines long.
If you find this limit to be too low, then it would be helpful to consolidate multiple messages into one, especially if they are on the same topic and/or read the list more frequently.
On at least one occasion, a spammer has shown up in SPAM-L and caused considerable disruption by posting messages like "why not hit delete" (he obviously was too good to read this FAQ before posting), calling us all sorts of names, and just causing general disruption.
The best way to deal with such an individual is to ignore them, and they will usually get mad, and leave the list on their own. Of course, if they are creating excessive disruption, feel free to e-mail your friendly list owner and the matter will be looked into, and the troll be unsubbed from the list if absolutely necessary.
In order for a troll to show up in SPAM-L, he has to first find out about it. Therefore, logic dictates that if he does not know about this mailing list, he won't get on it and cause trouble. Therefore, I strongly recommend that you do not mention the SPAM-L mailing list when initially contacting a spammer or their ISP. If the ISP turns out to be anti-spam however, feel free to refer them to the list as we could always use another list member.
Actually, contacting a spammer directly isn't recommended either, the full reasons for which are explained in another section
Since a large number of the members of SPAM-L are sysadmins and UNIX gurus, it's safe to say that this mailing list can be considered a professional resource with all the rights and responsibilities thereof. An important part of acting in a professional manner is using profanity very sparingly. There are many, many ways to communicate your message without having to resort to vulgarity, no matter how upset you may be at the spammer who crashed your mailserver and caused you hours of downtime.
Also, since people are using search facilities on the web more and more (employers, potential customers, etc.), and SPAM-L is archived, using excessive profanity could come back to haunt you someday.
For those who aren't too familiar with messaging forums on the Internet, signal is referred to on-topic posts which contribute to the value of a list whereas noise is anything off-topic, such as personal remarks and flames.
As for why one should bother staying on-topic, while it might be a little satisfying to flame some unresponsive ISP (I speak this from experience :-), it just adds noise as opposed to signal, and the only effect it will have is to convince people new to the list, such as ISP Abuse people, that the list is unprofessional and not worth reading, and the list loses a potential ally.
If you really need to chat with someone or flame them, please take it to private e-mail for the sake of the list.
There is a list of topics which one should place at the beginning of the SUBJECT: line of messages to SPAM-L. This helps people determine more easily what the message is about, plus it facilitates LISTSERV's topic-sorting mechanism. However, topics do not apply in the digest or index form of distribution.
Be sure to have have a colon and a space ": " following the topic so that the LISTSERV will recognise that posting as belonging to that topic. Also, a message can have multiple topics like:
Subject: ABUSE,ABUSE-RE: My correspondence with AGISand the message will then belong to both topics.
There are "implicit" topics too: ALL, NONE, and OTHER. If a message is posted without a topic, or with an undefined topic, it will automatically fall into OTHER.
You should also be aware that unlike on other lists, on the spam-l list, the "other" topic is, essentially, the bit-bucket. By default, a new subscriber's topics options are set to "-other", and many existing subscribers have removed "other" from their list of subscribed topics.The only people who see "other" messages are those who read the list in digest and those who have explicitly subscribed to "other". If you have a message that doesn't seem to fit in any other topic, use "misc". That topic was explicitly created as a replacement for "other", because so many subscribers were complaining about untagged messages in the "other" topic. There were a number of long and sometimes acrimonious discussions about the problems with "other" until "misc" was created several months ago. The complaints could be under any topic; the announcement of the creation of "misc" and the rationale behind it are almost certainly tagged "meta".
To arrange to receive messages that are only in specific topics, send the following command(s) to the listserv:
set SPAM-L topics: all|(+|-)topic Examples: SET SPAM-L TOPICS: ALL (To get all the topics) SET SPAM-L TOPICS: -FAQ (To stop getting postings of the FAQ) SET SPAM-L TOPICS: +NUKE (To start getting NUKE if you didn't previously)Oh yes, if you are replying to a post, please re-topic if it is necessary to prevent from perpetuating the mis-topiced thread.
Having read the rest of section 2, you are now ready to post to SPAM-L. To make a post to the list, send e-mail to SPAM-L@peach.ease.lsoft.com.
By default, new subscribers to SPAM-L will see their own postings to SPAM-L. To change this default, e-mail firstname.lastname@example.org the single line of text:
SET SPAM-L NOREPROwhich will not send you copies of your own posts.
Since you may get large amounts of e-mail from other mailing lists, you may wish to have some way to tell messages from SPAM-L apart from other e-mail. If you are using a UNIX system with Procmail installed, the following recipe will store e-mail from SPAM-L in a separate folder:
:0 : * ^Sender:.*SPAM-L@PEACH.EASE.LSOFT.COM $MAILDIR/spam-lOr, you can send the command SET SPAM-L SUBJECTHDR to email@example.com which will prepend the Subject: headers of all postings to the list with the text [SPAM-L]. For example, a subject line of:
Subject: MEDIA: Cnet article on spambecomes:
Subject: [SPAM-L] MEDIA: Cnet article on spamBack to Top
No. See the section titled What should be posted for posting guidelines.
Well, if it was from someone other than a list member, it's a good bet that
Recently, a limit of 200 lines per message has been imposed on SPAM-L. This took place because of a few very large files which were posted to the list over the last few months.
There hasn't ever been much advertising of anti-spam products/services in SPAM-L so here are a few pointers that it is suggested you follow. This section will be revised as necessary. I'm also open to comments regarding this section.
It seems that the LISTSERV software munges postings made to the list in some way. Since verifying a PGP signed message involves computing a hash and comparing it to a signed hash, any change in the message will cause the verification to fail. Since I use PGP whenever I send out e-mail, my postings will always fail to verify.
Greg Sabino Mullane reports that part of the problem has to do with the LISTSERV software converting tabs in messages to a series of 8 spaces, which will in turn produce a different checksum for the message.
SPAM-L is not any sort of a political action group. The list exists for informational purposes and discussion only. The reason why we say this is so that a list member doesn't complain about a spammer and CC the list, to try and imply some sort of a threat if the site being e-mailed doesn't comply and deal with their spammer.
Not only does CCing SPAM-L on complaints go against the fact that we're not any sort of an "action" group, but it also opens the door to possible other problems as well. For example, if the person you complain to is a kook, we could end up with a kook on this list, which has already happened at least once. Another problem is that if the admin replies to you to defend himself (maybe the spam was forged or he already nuked the spammer), and gets a bounce from the LISTSERV, it's only going to annoy/confuse them, and that certainly won't help things.