Here's my configs...
# This rc.custom file is customized for the confirm v.1.2 package.
# The variables set in the confirm chapter are triggering the confirmation
# of subscribe and/or unsubscribe requests. Subscriptions could be also
# forwarded to the maintainer(s) for confirmation.
#
# Assign the fully qualified mail address of the maintainer of this list
# to "maintainer". If empty, request-mail will not be mailed to any
# maintainer and will be stored in the "request" file for this list.
#
# If you want to define more than one maintainer you have to seperate
# the email addresses with commas. Don't leave blanks around the commas.
maintainer = baloo@ursine.dyndns.org,greddy@bright.net
LOGABSTRACT=yes # uncomment in case of emergency
VERBOSE=yes # uncomment in case of real emergency
size_limit = 524288 # sanity cutoff value for submissions
idcache_size = 81920 # duplicate-msgid cache size in bytes
archive_hist = 20 # number of messages left archived
# or "all" to keep them all
archive_dir = latest # subdirectory of archive to which
# the messages are saved in an
# MH-style folder
archive_log = $LOGFILE # log file for archive retrievals
subscribe_log = $LOGFILE # log file for administrivia
maxhist = 32 # bounce history limit
minbounce = 10 # no. of bounces before removal
cutoff_bounce = 256 # lines to keep in bounce processing
match_threshold= 30730 # for close matches to the list
medium_threshold= 28672 # for not so close matches to the list
loose_threshold= 24476 # for loosely finding your name
auto_off_threshold= $medium_threshold # for auto-unsubscribing bouncers
off_threshold = $loose_threshold # for unsubscribing
reject_threshold= $match_threshold # for rejecting subscriptions
submit_threshold= $medium_threshold # for permitting submissions
unsub_assist
##unsub_assist = 8 # uncomment (and change perhaps) this
# line to enable unsubscription
# assistance; it specifies the no. of
# multigram matches an unsuccessful
# unsubscriber will receive back
#foreign_submit = yes
foreign_submit # uncomment this line if you
# want to restrict submitting to
# people on the accept list
restrict_archive
##restrict_archive= yes # uncomment this line if you
# want to restrict archive retrievals
# to people on the accept list
force_subscribe
##force_subscribe= yes # uncomment to cause people to
# be autosubscribed upon first
# submission to the list
#
# Variables to control and activate the confirm mechanism
#
maxcookies = 500 # cookies held in cookies directory
require_confirm = yes # send confirmation message before
#require_confirm # subscribing
confirm_unsubscribe = yes
#confirm_unsubscribe
confirm_subscribe = yes
#confirm_subscribe
#confirm_maintainer = yes # This forwards all subscription requests to
confirm_maintainer # the maintainer(s) who have to confirm or
# ignore the messages.
auto_unsubscribe= yes
##auto_unsubscribe # uncomment to disable unattended
# unsubscription handling
auto_subscribe = yes
##auto_subscribe # uncomment to disable unattended
# subscription handling
#auto_help
auto_help = yes # uncomment to enable default help
# responses to all undecipherable
# requests
moderated_flag
##moderated_flag= yes # uncomment this to make the list
# moderated (you must create a
# `moderators' file for this to work)
# set moderator_PASSWORD to get
# stricter checking
cc_requests
##cc_requests = yes # uncomment if you want subscribe
# and help requests to be Cc'd to
# the maintainer
cc_unsubrequests
##cc_unsubrequests= yes # uncomment if you want unsubscribe
# requests to be Cc'd to the maintainer
divertcheck = yes
##divertcheck # uncomment to disable the check for
# misfiled administrative requests
pass_diverts
##pass_diverts = yes # uncomment to pass on administrative
# requests diverted from the normal
# list to the maintainer unprocessed
# (instead of trying to handle them)
reply_to
reply_to = "Reply-To: gc(a)ursine.dyndns.org" # uncomment to force replies to
# go to the list (discouraged)
# why discouraged? see:
# http://garcon.unicom.com/FAQ/reply-to-harmful.html
#digest_flag
##digest_flag = yes # uncomment this if you want digests
#digest_age = 262144 # maximum age of a digest in seconds
#digest_size = 32768 # maximum size of a digest in bytes
#undigested_list = $list@$domain # Reply-To: address for digests
#moderator_PASSWORD = # put the optional password for
# moderators here, this definition
# can contain regular expression magic
# characters (to support multiple
# passwords)
X_COMMAND = X-Command
X_COMMAND_PASSWORD = rj013442 # put the literal password for
# X-Command mails here
#daemon_bias='100^0 ^From:.*daemon@ok' # You could set "daemon_bias" to
# positively discriminate some
# mail address not to be from a daemon. Either with a regexp as demonstrated
# or with more complicated recipes that simply set it to '100^0' or nothing.
RC_LOCAL_SUBMIT_00 = rc.local.s00.mhonarc
#RC_LOCAL_SUBMIT_10 = rc.local.s10
#RC_LOCAL_SUBMIT_20 = rc.local.s20
#RC_LOCAL_REQUEST_00 = rc.local.r00
#RC_LOCAL_REQUEST_10 = rc.local.r10
#RC_LOCAL_REQUEST_20 = rc.local.r20
#RC_LOCAL_REQUEST_30 = rc.local.r30
#RC_CUSTOM # clear this one from the environment
# so that we include this file only
# once
And for the digest version...
# This rc.custom file is customized for the confirm v.1.2 package.
# The variables set in the confirm chapter are triggering the confirmation
# of subscribe and/or unsubscribe requests. Subscriptions could be also
# forwarded to the maintainer(s) for confirmation.
#
# Assign the fully qualified mail address of the maintainer of this list
# to "maintainer". If empty, request-mail will not be mailed to any
# maintainer and will be stored in the "request" file for this list.
#
# If you want to define more than one maintainer you have to seperate
# the email addresses with commas. Don't leave blanks around the commas.
maintainer = baloo@ursine.dyndns.org,greddy@bright.net
LOGABSTRACT=yes # uncomment in case of emergency
VERBOSE=yes # uncomment in case of real emergency
#size_limit = 524288 # sanity cutoff value for submissions
#idcache_size = 8192 # duplicate-msgid cache size in bytes
#archive_hist = 2 # number of messages left archived
# or "all" to keep them all
#archive_dir = latest # subdirectory of archive to which
# the messages are saved in an
# MH-style folder
archive_log = $LOGFILE # log file for archive retrievals
subscribe_log = $LOGFILE # log file for administrivia
#maxhist = 32 # bounce history limit
minbounce = 10 # no. of bounces before removal
#cutoff_bounce = 256 # lines to keep in bounce processing
match_threshold= 30730 # for close matches to the list
medium_threshold= 28672 # for not so close matches to the list
loose_threshold= 24476 # for loosely finding your name
auto_off_threshold= $medium_threshold # for auto-unsubscribing bouncers
off_threshold = $loose_threshold # for unsubscribing
reject_threshold= $match_threshold # for rejecting subscriptions
submit_threshold= $medium_threshold # for permitting submissions
unsub_assist
##unsub_assist = 8 # uncomment (and change perhaps) this
# line to enable unsubscription
# assistance; it specifies the no. of
# multigram matches an unsuccessful
# unsubscriber will receive back
#foreign_submit = yes
foreign_submit # uncomment this line if you
# want to restrict submitting to
# people on the accept list
restrict_archive
##restrict_archive= yes # uncomment this line if you
# want to restrict archive retrievals
# to people on the accept list
force_subscribe
##force_subscribe= yes # uncomment to cause people to
# be autosubscribed upon first
# submission to the list
#
# Variables to control and activate the confirm mechanism
#
maxcookies = 500 # cookies held in cookies directory
require_confirm = yes # send confirmation message before
#require_confirm # subscribing
confirm_unsubscribe = yes
#confirm_unsubscribe
confirm_subscribe = yes
#confirm_subscribe
#confirm_maintainer = yes # This forwards all subscription requests to
confirm_maintainer # the maintainer(s) who have to confirm or
# ignore the messages.
auto_unsubscribe= yes
##auto_unsubscribe # uncomment to disable unattended
# unsubscription handling
auto_subscribe = yes
##auto_subscribe # uncomment to disable unattended
# subscription handling
#auto_help
auto_help = yes # uncomment to enable default help
# responses to all undecipherable
# requests
moderated_flag
##moderated_flag= yes # uncomment this to make the list
# moderated (you must create a
# `moderators' file for this to work)
# set moderator_PASSWORD to get
# stricter checking
cc_requests
##cc_requests = yes # uncomment if you want subscribe
# and help requests to be Cc'd to
# the maintainer
cc_unsubrequests
##cc_unsubrequests= yes # uncomment if you want unsubscribe
# requests to be Cc'd to the maintainer
divertcheck = yes
##divertcheck # uncomment to disable the check for
# misfiled administrative requests
pass_diverts
##pass_diverts = yes # uncomment to pass on administrative
# requests diverted from the normal
# list to the maintainer unprocessed
# (instead of trying to handle them)
reply_to
##reply_to = "Reply-To: $listaddr" # uncomment to force replies to
# go to the list (discouraged)
# why discouraged? see:
# http://garcon.unicom.com/FAQ/reply-to-harmful.html
#digest_flag
digest_flag = yes # uncomment this if you want digests
digest_age = 262144 # maximum age of a digest in seconds
digest_size = 32768 # maximum size of a digest in bytes
undigested_list = gc(a)ursine.dyndns.org # Reply-To: address for digests
#moderator_PASSWORD = # put the optional password for
# moderators here, this definition
# can contain regular expression magic
# characters (to support multiple
# passwords)
X_COMMAND = X-Command
X_COMMAND_PASSWORD = rj013442 # put the literal password for
# X-Command mails here
#daemon_bias='100^0 ^From:.*daemon@ok' # You could set "daemon_bias" to
# positively discriminate some
# mail address not to be from a daemon. Either with a regexp as demonstrated
# or with more complicated recipes that simply set it to '100^0' or nothing.
#RC_LOCAL_SUBMIT_00 = rc.local.s00.mhonarc
#RC_LOCAL_SUBMIT_10 = rc.local.s10
#RC_LOCAL_SUBMIT_20 = rc.local.s20
#RC_LOCAL_REQUEST_00 = rc.local.r00
#RC_LOCAL_REQUEST_10 = rc.local.r10
#RC_LOCAL_REQUEST_20 = rc.local.r20
#RC_LOCAL_REQUEST_30 = rc.local.r30
#RC_CUSTOM # clear this one from the environment
# so that we include this file only
# once
--
Baloo
Hi,
I have been using SmartList for almost five years now. The FAQ and the
manual have been invaluable in helping me figure out how to manage my
lists but I have run into two situations that the FAQ does not address.
1. I use the recipes in section 8.7 of the FAQ to keep HTML and other
attachments off the list. I also block excessively quoted messages.
Only messages that are sent directly to the list seem to be filtered.
Messages that are CC'ed to the list do not seem to be sent through
these filters.
Is this a Procmail bug or something I can fix with SmartList?
2. Some email programs do not use '> ' to mark quoted text. Instead
they include the original message as-is and used '--- Original message
--- ' or something similar as a separator. I would like to block such
messages too but the 'excessive quoting filter' lets them through since
there is '> ' in the message. Each of the messages on the list has a
footer with information on unsubscribing etc. How do I block the
message if this specific text is present in the message?
Thanks for your help.
Regards,
Harshal
=====
http://www.mumbai-central.com : Where Mumbaikars meet
__________________________________________________
Do You Yahoo!?
Yahoo! Sports - Coverage of the 2002 Olympic Games
http://sports.yahoo.com
On Wed, 20 Feb 2002, Joyce Miletic wrote:
> This should not have this effect. Removing this line from accept file
> will just stop the digest from posting to the list.
OK, but will new subscribers be added to both accept and dist?
> Are you having a problem with subscribers not being able to subscribe?
No.
--
Baloo
Hello,
The web host I'm using offers Smartlist. I set it up as a newsletter
according to the directions and am getting an unusual header such as
I've not seen on other lists through the years.... Host tech support
tells me this is the way it's supposed to be...I am asking you, is this
the way it's supposed to be? or have I done something incorrectly?
The unusual part of the header to which I refer is the Resent-Date and
Resent-From lines.
Subject: test
Resent-Date: Mon, 18 Feb 2002 13:04:36 -0500
Resent-From: ThunderwolfNews(a)thunderwolfrecords.com
Date: Mon, 18 Feb 2002 10:03:24 -0800
From: Kim Foley <kim(a)thunderwolfrecords.com>
Organization: Thunderwolf Records
To: thunderwolfnews(a)thunderwolfrecords.com
Thank you.
Kim
--
*****NEW BOOK*****
"The Big Pocket Guide to Using & Creating Virtual Field Trips"
Get details at www.field-trips.org/book/
Kim Foley, Field Trips Site
kim(a)field-trips.org
http://www.field-trips.org (Field Trips on Nature Topics for K-12)
http://www.tramline.com (Buy TourMaker Software here)
===
The principal goal of education is to create people who are capable of
doing new things, not simply repeating what other generations have done.
- Piaget
It is not a large change to let users do this themselves. When I first created my lists (about 5 years ago) I extended the "dist" file concept so Smartlist "knows" who is allowed to subscribe themselves to the list (all initial subscriptions have to be done by the listsowner). Then they can switch themselves back and forth from regular list to digest by simply sending a mail/nomail command to the respective server addresses. I never bothered to add the extra steps to interpret a single digest/nodigest message to either server but it wouldn't be hard to do.
Rich
> Hi,
>
> This is my first time with procmail/SmartList and 'am having trouble
> building procmail 3.22.
>
> Find below the contents of output to the console:
>
root@test:/maint/procmail-3.22-# make install-suid
/bin/sh ./initmake /bin/sh "/bin/sh" "/bin/rm -f" "mv -f" "ln" \
"-lm -ldir -lx -lsocket -lnet -linet -lnsl_s -lnsl_i -lnsl -lsun -lgen
-lsockd
"/lib /usr/lib /usr/local/lib /usr/share/lib" \
/dev/null "make" o \
"cc" "-O" "-s " "procmail lockfile formail mailstat" \
"procmail formail lockfile" \
"procmailrc procmailsc procmailex" "src man" \
"/usr/local/bin" \
"strip"
gcc seems to work fine, using that as the C-compiler
...scanning for 13 libraries...
Added LDFLAGS= -lm -lsocket -lnsl -lgen -ldl -lc
make make install-suid
cd src; make ../autoconf.h
/bin/sh ./autoconf /bin/sh "/bin/rm -f" "mv -f" /dev/null \
"fgrep" "make" o "__defaults__" \
"/usr/local/bin" ../autoconf.h
=======================================================================
In order for the kernel-locking tests to work as intended I have to be able
to test-lock files on as many semantically different filesystems as possible
(for more information about this, READ PARAGRAPH TWO in INSTALL). To
suppress this prompt you can set the LOCKINGTEST variable in the Makefile.
Please add writable directories to the list. You should only add
directories that reside on filesystems that have unique characteristics.
E.g. if you have several remote NFS partitions, pick some unique
client-server pairs, there is little use in picking the same server twice
from the same client-machine. An excellent candidate would be a remotely
mounted mail spool directory.
=======================================================================
I will temporarily use a testdirectory named _locktest in the following
directories:
/tmp .
If you would like to add any, please specify them below, press return to
continue:
Initiating fcntl()/kernel-locking-support tests
-- output edited as no error messages were displayed --
/* autoconf completed */
=======================================================================
gcc -c -O sublib.c
=======================================================================
If you are a system administrator you should consider integrating procmail
into the mail-delivery system -- for advanced functionality, speed AND
SECURITY --. For more information about this topic you should look in the
examples/advanced file.
Also, HIGHLY RECOMMENDED (type 'make install-suid' to execute it):
chown root /usr/local/SmartList/bin/procmail
chgrp mail /usr/local/SmartList/bin/procmail
/usr/local/SmartList/bin/lockfile
chmod 6755 /usr/local/SmartList/bin/procmail
chmod 2755 /usr/local/SmartList/bin/lockfile
=======================================================================
cd src; make ../new/procmail ../new/lockfile ../new/formail ../new/mailstat
gcc -c -O procmail.c
/usr/ccs/bin/as: "/var/tmp/ccvGjLaB.s", line 1487: error: unknown opcode
".subsection"
/usr/ccs/bin/as: "/var/tmp/ccvGjLaB.s", line 1487: error: statement syntax
/usr/ccs/bin/as: "/var/tmp/ccvGjLaB.s", line 1613: error: unknown opcode
".previous"
/usr/ccs/bin/as: "/var/tmp/ccvGjLaB.s", line 1613: error: statement syntax
*** Error code 1
make: Fatal error: Command failed for target `procmail.o'
Current working directory /usr/local/procmail-3.22/src
*** Error code 1
make: Fatal error: Command failed for target `bins'
> And the output of uname -a:
>
> SunOS test 5.8 Generic_108528-12 sun4u sparc SUNW,UltraAX-i2
>
> Would appreciate any help with the build.
>
> Regards,
>
>
> Sanil
>
>
Are there any webboard type frontends that do not depend on an extra
database, just read against the archives ala mhonarc and store
web users and thier passwords for web-only type subscriptions in an
/etc/passwd type file? Subscriptions and unsubscriptions will be
confirmed by smartlist, so this could also be a part of it.
What brings this up is about 27% of the readership of a mailing list I'm
migrating from Yahoo have no-delivery subscriptions and are hostilly
against moving from Yahoo unless they get that functionality. I don't
want to have to deal with the slowness and crashiness of postgresql or
mysql databases in the hands of someone who has no clue about them (me).
The webboard doesn't need to be a speed king as long as it doesn't
affect performance of smartlist itself.
Preference given to packages in .deb format or easy to compile, install
and maintain.
Any ideas?
--
Baloo
