On [2005-Jan-10] Stan Goodman <sgood(a)hashkedim.com> wrote:
>
> > SPAMTRAP=mylistspam
>
> No "$" before the name of the variable here? Why?
A programming convention adopted by Stephen when he created procmail and
its scripting language. If you look in rc.init and rc.custom you'll see
that all variables are defined this way (no $ in the definition, $
preceeds the name for simple substitutions).
While in general I agree with Charlie that an email list is not the place
to learn basic programming technigues it's not as if the SmartList list is
overwhelmed with traffic :-)
> > It is written in "procmail" (use man procmail and man formail as a
> > starting point to understand the recipes/instructions in smartlist
> > (smartlist is 'written' in procmail and in sh)
>
> Very compact language. Very little intuitive baggage. Not for the faint of
> heart.
Lean and fast, the criteria needed when dealing with system-level email
and especially back when the program was created -- machines were not as
fast as they are now and you couldn't afford slowness when tens of
thousands of email messages were going through the processing.
> I don't have any files of the form rc.local.rxx (only rc.local.sxx); I
assume
> that I can put the snippet into an otherwise empty one. No header is
required?
Take a look in rc.custom near the bottom. This is where the connection is
made between the variables like RC_LOCAL_REQUEST_XX and the actual
filenames like rc.local.rxx. To actually have rc.submit or rc.request call
the rclocal.xxx modules you need to uncomment the appropriate variable in
rc.custom.
If you look in rc.request you'll see that, if defined, rc.local.r00 is
called right after rc.init and rc.custom are called to define all the
list's parameters. So everything that is defined in those two modules will
be "known" to rc.local.r00 when it executes.
Rich
On [2005-Jan-10] Stan Goodman <sgood(a)hashkedim.com> wrote:
>
> If I understand the above correctly, this is a snippet intended to
examine an
> incoming message, and determine if there is an address in any of the named
> headers that is identical to an address in the dist file, and, if not,
to throw
> it into a file called . SPAMTRAP (I think the "$" is not part of the
filename;
> is that correct?
Pretty much. The variable $SPAMTRAP is assigned a file name via an entry like
SPAMTRAP=mylistspam
which preceeds the recipe given and where mylistspam is the actual
filename that will be used when procmail writes if the recipe succeeds.
>
> I hope someone will correct me if I am wrong (I don't even know the name
of the
> language in which thise scripts are written, so anything is possible).
It is written in "procmail" (use man procmail and man formail as a
starting point to understand the recipes/instructions in smartlist
(smartlist is 'written' in procmail and in sh)
>
> I think there is more to its main paragraph that than, because I can't
account
> for all the terms.
>
> I am not clear what to do with the sentence "(define $SPAMTRAP to be a
file of
> your choice)". How define?
see above
>
> In what file is this piece of script intended to go? And does it matter
where
> in that file it is located?
That little recipe would go in rc.local.r00. It is, as Charlie pointed
out, quite draconian. Once in place then only messages purporting to come
from someone already subscribed to your list will get through so you might
want to at least examine what gets put into the $SPAMTRAP file every once
and awhile.
The rc.local.r00 file goes into the directory containing all of the other
list's files.
If all this makes very little sense thenI'd spend some time looking at the
existing rc.local.** files (along with rc.submit and rc.request) to start
getting a basic idea of what each does and why. You don't need to be an
'adept' to make small changes but some familiarity is a really good idea.
I assume you can also make up a test list in which to run your additions
before commiting them to a real list.
Rich
To simply divert messages to the request-address that don't come from
current subscribers you can use the same mechanism smartlist uses to
restrict postings, i.e. formail/multigram and the dist file
(define $SPAMTRAP to be a file of your choice)
:0:
* !? formail -X"From " -xFrom: -xReply-To: -xSender: -xResent-From: \
-xResent-Reply-To: -xResent-Sender: -xReturn-Path: | \
multigram -b1 -m -l$submit_threshold -L$domain \
-x$listaddr -x$listreq dist
$SPAMTRAP
if you want to be a little less restrictive you can use (as was mentioned
by Jim Osborn) an approach which uses SpamAssassin (SA) to check for the
spamishness of messages that aren't from subscribers:
WHITEU=dist
FROM = `formail -IReply- -rtzxTo:`
:0
* ! ? fgrep -i $FROM $WHITEU
{
INCLUDERC=spamcheck.rc
}
-- where spamcheck.rc is tuned to whatever spam-finding package you
prefer, for instance a simple-minded (and low-volume) SA approach could
be:
:0fw
| /usr/local/bin/spamassassin
:0:
* ^X-Spam-Status: Yes
$SPAMTRAP
Rich
On [2005-Jan-10] Charlie Summers <charlie(a)lofcom.com> wrote:
> At 1:57 PM -0500 1/10/05, rgball(a)ellerbach.com is rumored to have typed:
>
> > To simply divert messages to the request-address that don't come from
> > current subscribers you can use the same mechanism smartlist uses to
> > restrict postings
>
> Which begs a question...how does one subscribe to this hypothetical
> mailing list?
:-) By invitation only?
>
> Charlie (who deals with spam on the system level instead)
oui, when I have the system-level tools available -- when I don't I make do.
These days my smartlist-hosting duties are nil because I no longer have
access to a machine that is a) capable of running a list and b) has
procmail on it.
Rich
Hi All,
I'm trying to set up the confirm package for one of my mailing lists.
In the directions it says to uncomment rc.local.s10 and create a
matching file containing the confirm code.
However, I currently use rc.local.s10 to insert the list name into the
subject line of all messages distributed by the list. I am also using
rc.local.s00 to block attachments and rc.local.s20 to add a footer with
unsubscribe instructions to all list messages, so all the default
rc.local file calls are in use.
Is it possible to combine any of these functions? For example, if I
pasted the code from rc.local.s10 into the bottom of rc.local.s20 would
it be able to perform both functions (inserting the subject line and
the footer) within a single rc.local.s20 file?
As an alternative, can I just create another rc.local.sXX file
(rc.local.s30?) and add the call to rc.custom?
Thanks,
Irwin
** Forwarding message from Mailer-Daemon(a)massart.edu on Sat, 08 Jan 2005 06:33:48 -0500
> Sorry. Your message could not be delivered to:
>
> paonia,Mass College Art (The name was not found at the remote site. Check
> that the name has been entered correctly.)
If I put a copy of the above in a bottle and throw it into the sea, is there a chance that the administrator of this list will eventually receive it, and find a way to get bounce messages to HIS mailbox?
--
Stan Goodman
Qiryat Tiv'on
Israel
"When your enemy falls, do not rejoice." -- Proverbs 24:17
"It's okay to laugh in the bedroom, but don't point." -- Anonymous
Hi Folks,
I'd like to use the confirm package to add the ability to confirm
subscriptions and unsubscriptions to my list. The FAQ says that it is
available at ftp://ftp.pure.ch/smartlist but that link is now dead.
Is there a mirror somewhere else I could try?
Thanks,
irwin
Could the list administrator for the smartlist mailing list please
remove the below user - I get this message every time I post to the
list:
Begin forwarded message:
> From: Mailer-Daemon(a)massart.edu
> Date: January 3, 2005 3:51:29 PM EST
> To: "Irwin Lazar" <imlazar(a)comcast.net>
> Subject: NDN: Confirm?
>
> Sorry. Your message could not be delivered to:
>
> paonia,Mass College Art (The name was not found at the remote site.
> Check
> that the name has been entered correctly.)
>
I guess I wasn't clear in what I was looking to do, which is
essentially build an XML feed such that whenever a message was sent to
the list, it would be added to the XML page.
It looks like the best way to accomplish this is via Mhonarc, which
supports creation of an XML file. This would enable me to simply add
an RSS feed to my list archive.
Thanks for the responses.
Irwin
On Dec 28, 2004, at 3:16 PM, Charlie Summers wrote:
> At 2:15 PM -0500 12/28/04, Irwin Lazar is rumored to have typed:
>
>> Has anyone set up their mailing lists to be distributed via RSS?
>
> Then it wouldn't be a "mailing" list, now would it? Seems relatively
> simple, but if you're going to use XML containers to hold the data and
> HTTP
> to move the data, might as well call it what it is - a web-based
> discussion
> group.
>
> Charlie
>
>
