All,
I am trying to use rc.local.s10.mhonarc from
http://www.ha-schneider.de/software/smartlist/
to set up an archive for a mailing list.
I have renamed rc.local.s10.mhonarc to rc.local.s30 and added following line to rc.custom
RC_LOCAL_SUBMIT_30 = rc.local.s30
rc.local.s10 and rc.local.s20 are already in use and since I do not know how to merge the recipe in rc.local.s10.mhonarc with either of the two, I renamed it to rc.local.s30 and added a new line in rc.custom.
Could someone please help me understand as to how it all works.
Thanks
Nishi
The following is a sample of the results of a search that I receive by email.
This there a way to hide the line number?
ARCHIVE egrep august latest/*
BEGIN---------------cut here------------------
latest/10:16:Monday, August 27, 2001
latest/11:16:Tuesday, August 21, 2001
latest/12:16:Wednesday, August 29, 2001
END-----------------cut here------------------
Thanks for your help!
Alan,
hi!
how can i modyfiy the text for the automatic subscribe/unsubscribe-mail?
The possibilities of a *subscribe.txt*-file in my folder are not enough for
me. I want suppress the information about the transmited data and translate
the rest of the mail to german.
TIA, martin
--
"Who needs horror movies when we have Microsoft?"
- Christine Comaford, PC Week
Hello:
Does SmartList have an archiving and (hopefully user friendly) search capability?
[I'm not interested in the archives of this Disc List, but of the list I run for my
'users'].
Thanks,
Mitch Darer
--
Mitchell Darer, WebMaster, mitch(a)focusing.org
The Focusing Institute, 34 East Lane, Spring Valley, NY 10977
http://www.focusing.org (845) 362-5222 (phone/fax)
At 11:41 AM -0400 7/28/00, Werner Reisberger is rumored to have typed:
> I never saw any
> admin reply to the numerous complains about spam messages.
Actually, that's not _strictly_ true, since I remember when Stephen was
actually maintaining the list (and probably anally have archives of the list
from that time somewhere on some floppy or MO cart from a long time ago and
far far away). But you're right, it's been _years_ since he's been around.
However, the list belongs to the maintainer (or at least the machine's
admin), not the members. You'll get no argument from me that the list should
be moved (I believe I said exactly that a couple of times), but to suggest
the admins need to take a poll to ask what they may or may not do with the
existing list is silly, to say the least. They are certainly able to move
this list to mailman without the list subscriber's permission - indeed, they
_have_ done so, which makes my point for me.
Whether we should move this list to a SmartList server is a completely
seperate issue...one which Philip should probably weigh in on, since he is
now maintaining the procmail/SmartList source and as such the de facto head
of our band of merry wanderers...
Charlie
This comes directly from SmartList/etc/rc.request (i.e., it is an
unmodified installation file).
Consider this recipe:
#
# Is it an archive retrieval command?
#
:0 HB w
* 9876543210^0 ^^(.+$)*Subject:[ ]*(([(<]no(ne| subject\
( (\(file transmission|given))?)[>)])?\
$(.+$)*(^[ ]*)+)?(archives?:?([ ]|$)|\
((send|get)(me)?|gimme|retrieve|mail|ls|dir(ectory)?|list|show|\
search|[fe]?grep|find|maxfiles|version)([ ]+[^ ]*)?$)
* 1^0 B ?? ^^([ ]|$)*\
((archives?:?($|[ ]+)|\
((send|get)(me)?|gimme|retrieve|mail|ls|dir(ectory)?|\
list|show|search|[fe]?grep|find|maxfiles|version|help|info)\
([ ].*)?$)([ ]|$)*)+\
([^ a-z].*$(.*$(.*$(.*$(.*$)?)?)?)?)?^^
{
:0 W
* 9876543210^0 !restrict_archive ?? y
* 2^0 ? formail -rt -R To: "From " -X "From " | \
multigram -b1 -m -l$submit_threshold -L$domain \
-x$listaddr -x$listreq accept accept2
| arch_retrieve
:0 E fhw
| formail -A "X-Diagnostic: Not on the accept list"
}
As I remember, this is supposed to be a complete recipe; so where is
the closing parenthesis for
9876543210^0 ^^(.+$)*Subject:[ ]*____(____([(<]no(ne| subject\
the marked left paren supposed to go?
Ditto for
#
# Is it an unsubscription request?
#
:0 EHB
* 9876543210^0 ^^(.+$)*Subject:[ ]*____(____[(<]no(ne| subject\
and
#
# Is it a subscription request?
#
:0 EHB
* 9876543210^0 ^^(.+$)*Subject:[ ]*____(____[(<]no(ne| subject\
and
#
# Is it an info or help request? Send back the help.txt and the
# optional info.txt file.
# We do the same on a complete empty mail (except for perhaps a signature).
#
:0 EHB
* 3^0 ^^(.+$)*Subject:[ ]*\
____(____([(<]no(ne| subject( (\(file
transmission|given))?)[>)])?$\
(.+$)*(^[ ]*)+)?[a-z,. ]*(help|info(rmation)?)\>
* 1^0 ^^(.+$)*Subject:[ ]*\
____(____[(<]no(ne| subject( (\(file
transmission|given))?)[>)])?$
Thanks; that was helpful. It reminded me that I had modified SmartList
a decade ago so that it did work that way, and that I needed to go
find a copy of my changes. I did and now things are working the way
they are supposed to be working for my site.
It had been so long since I had really studied Smartlist recipes that
I had forgotten all about it.
Thanks again for taking the time to dissect the messages.
--
Greg
On Mon, Nov 3, 2008 at 8:57 PM, Cary Coutant <ccoutant(a)gmail.com> wrote:
>> procmail: Executing "multigram,-b1,-l30730,reject"
>>
>> procmail: Non-zero exitcode (1) from "multigram"
>>
>> procmail: No match on "multigram -b1 -l30730 reject"
>
> This just means that the address you were trying to subscribe was not
> on the "reject" list. No problem here.
>
>> procmail: Executing " formail -IReceived: -IX-Envelope-To:
>> -IIn-Reply-To: -ICc: | \
>> multigram -b1 -x$listreq -x$listaddr -l$reject_threshold dist"
>>
>> procmail: Non-zero exitcode (1) from " formail -IReceived:
>> -IX-Envelope-To: -IIn-Reply-To: -ICc: | \
>> multigram -b1 -x$listreq -x$listaddr -l$reject_threshold dist"
>> procmail: No match on " formail -IReceived: -IX-Envelope-To:
>> -IIn-Reply-To: -ICc: | \
>> multigram -b1 -x$listreq -x$listaddr -l$reject_threshold dist"
>
> And this means that the address isn't already on the mailing list. No
> problem here either.
>
>> procmail: No match on "y"
>
> This means that you haven't enabled auto_subscribe. This is probably
> your problem.
>
> This isn't going to do what you expect anyway. Sending a message to
> the -request address with "subscribe" in the subject will add you, the
> *sender*, to the list -- not the address you give after the
> "subscribe" command.
>
> If you as the list maintainer are trying to repopulate all your lists,
> you should be using X-Commands. In rc.custom, set X_COMMAND_PASSWORD
> to a password of your choice, then you can send a message to the
> -request address with an X-Command header like this:
>
> X-Command: you(a)example.com PASSWORD subscribe someone(a)example.com
>
> Where you(a)example.com is the maintainer and someone(a)example.com is the
> address you want to subscribe. You can even send multiple commands in
> one message:
>
> X-Command: you(a)example.com PASSWORD subscribe someone(a)example.com
> subscribe someoneelse(a)example.com
>
> See section 2 of .etc/Manual for more details.
>
> -cary
>
[Sorry if this is a duplicate. I sent it earlier from the wrong email account.]
> procmail: Executing "multigram,-b1,-l30730,reject"
>
> procmail: Non-zero exitcode (1) from "multigram"
>
> procmail: No match on "multigram -b1 -l30730 reject"
This just means that the address you were trying to subscribe was not
on the "reject" list. No problem here.
> procmail: Executing " formail -IReceived: -IX-Envelope-To:
> -IIn-Reply-To: -ICc: | \
> multigram -b1 -x$listreq -x$listaddr -l$reject_threshold dist"
>
> procmail: Non-zero exitcode (1) from " formail -IReceived:
> -IX-Envelope-To: -IIn-Reply-To: -ICc: | \
> multigram -b1 -x$listreq -x$listaddr -l$reject_threshold dist"
> procmail: No match on " formail -IReceived: -IX-Envelope-To:
> -IIn-Reply-To: -ICc: | \
> multigram -b1 -x$listreq -x$listaddr -l$reject_threshold dist"
And this means that the address isn't already on the mailing list. No
problem here either.
> procmail: No match on "y"
This means that you haven't enabled auto_subscribe. This is probably
your problem.
This isn't going to do what you expect anyway. Sending a message to
the -request address with "subscribe" in the subject will add you, the
*sender*, to the list -- not the address you give after the
"subscribe" command.
If you as the list maintainer are trying to repopulate all your lists,
you should be using X-Commands. In rc.custom, set X_COMMAND_PASSWORD
to a password of your choice, then you can send a message to the
-request address with an X-Command header like this:
X-Command: you(a)example.com PASSWORD subscribe someone(a)example.com
Where you(a)example.com is the maintainer and someone(a)example.com is the
address you want to subscribe. You can even send multiple commands in
one message:
X-Command: you(a)example.com PASSWORD subscribe someone(a)example.com
subscribe someoneelse(a)example.com
See section 2 of .etc/Manual for more details.
-cary