Good Morning,
I run a list for our tech support department that sends an auto-reply to the original sender. My problem is this e-mail address gets a boatload of spam. But when the messages come through smartlist has stripped the original message headers. Is there any way to keep the original message headers so that I can use them to block spam?
Thanks in advance for any help
Jerry Sloan Network/System Admin fP Technologies, Inc
Jerry Sloan wrote:
Good Morning,
I run a list for our tech support department that sends an auto-reply to the original sender. My problem is this e-mail address gets a boatload of spam. But when the messages come through smartlist has stripped the original message headers. Is there any way to keep the original message headers so that I can use them to block spam?
Thanks in advance for any help
Jerry Sloan Network/System Admin fP Technologies, Inc -- "Let us take care that age does not make more wrinkles on our spirit than on our face."
Michel de Montaigne
Smartlist mailing list Smartlist@lists.RWTH-Aachen.DE http://MailMan.RWTH-Aachen.DE/mailman/listinfo/smartlist
Asking the same question for the third time..May I please get some help with this?
Jerry Sloan
At 10:55 AM -0500 1/18/02, Jerry Sloan is rumored to have typed:
Asking the same question for the third time..May I please get some help with this?
Not really, no. SmartList isn't a great choice for a tech support system IMHO (if you're not going to use a dedicated support system, why not just use a sendmail alias for your support staff which would avoid the resent-header problem completely?), and the problem you're experiencing isn't one common to "real" mailing lists (that is, the function for which SmartList was originally designed, since most mailing lists limit postings to those subscribed, something you obviously cannot do), and archiving a message to a text file is covered in the most basic of place - the procmail man pages - _anyway,_ so unless someone here uses it for the same function you do _and_ experiences the same problem _and_ is patient enough to gently suggest you at least read the procmail man pages even if you aren't willing to learn procmail itself, the odds are you won't get an answer.
Since you've already asked the question twice, and haven't received a response, it looks like that is the case. Sorry.
Charlie
"Jerry" == Jerry Sloan jerry@fptech.net writes:
Jerry> Asking the same question for the third time..May I Jerry> please get some help with this?
Oops, sorry, in the name of the whole list. :-)
Jerry> Jerry Sloan wrote: >> Good Morning, >> >> I run a list for our tech support department that sends an >> auto-reply to the original sender. My problem is this >> e-mail address gets a boatload of spam. But when the >> messages come through smartlist has stripped the original >> message headers. Is there any way to keep the original >> message headers so that I can use them to block spam?
The original headers are in the archived mails (in the subdirectory named "archive/latest" in the list directory). However, if you get a lot of messages, and you have not done anything to archive more than the last few of them (as is the default), the interesting ones may well have disappeared from the archive.
There is a rc.local.s20 file at http://www.ha-schneider.de/software/smartlist/ that stores the mails in a directory per month (i.e., you get files "archive/Jan02/NNN" etc. where NNN is the mail's number). Look for "rc.local.s20.mmmyy", towards the end of that page. You can change the date command to anything you like and your "date" gives you, including per-day or per-week directories (see the short intro to the UNIX command "date" at the end of the web page, and invoke "man date" on your UNIX command line).
To activate this file, store it as "rc.local.s20" in your list directory, then edit rc.custom and remove the # sign in front of RC_LOCAL_SUBMIT_20.
Hmm, as you are doing an auto-ack, you probably already have some rc.local.* file(s). If you already have an rc.local.s20 file, either add the contents of rc.local.s20.mmmyy to it, or replace it by something saying
INCLUDERC=first.rc.local.s20 INCLUDERC=second.rc.local.s20
To decide on which rc.local.s* file is best suited for your spam filtering, this is the flow of rc.submit:
include rc.init (global initializations) include rc.custom (per-list initializations) ## At this point, the mail is still unchanged. include rc.local.s00 if it looks like a regular submission (no bounces, no X-Xommand, size looks OK, etc.): if the sender is allowed to submit: include rc.local.s10 if the list is moderated and the mail is not approved, send it to the moderator(s) drop if "Message-Id:" has already been handled (avoid duplicate sending) auto-subscribe if $force_subscribe=yes forward to digested list, if appropriate store in archive/latest, and truncate that directory ## The mail is still unchanged unless you ## modified it in rc.local.s00 or rc.local.s10 fiddle with the headers include rc.local.s20 send it else (if the sender is not allowed to submit): add "X-Diagnostic: Not on the accept list" if present, send file accept.txt to the sender if the mail is still unprocessed: add "X-Diagnostic: Diverted & unprocessed" continue with rc.request
After storing the mail to archive/latest, the variable $ARCHIVE ist set to the resulting filename, and that variable is used in rc.local.s20.mmmyy. So you get the unmodified headers in archive/Jan02/NNN, in spite of the fact that they have already been modified when rc.local.s20 is included.
Hans-Albert
smartlist@lists.rwth-aachen.de
-
Charlie Summers -
Hans-Albert Schneider -
Jerry Sloan