There is a script available called "rc.dedup.list" to sort the dist-list and to remove duplicate e-mail addresses. Following the information I have, this script must be saved in the same directory as where the dist-list is stored.
My question is: what must I do to activate this script? I have added the line "RC_LOCAL_SUBMIT_00 =rc.dedup.list" at the end of the file "rc.custom", but it is not working. I am not familar with calling scripts, so please advise.
I need to know what to do to de link the hard link from dist file to the
accept file. I wish to have subscribers put in the dist file, and not the
access file. I wish to have the access file for only those I want to be
able to post to the list.
Thanks Jim Glaze
Or how can I do the same as this list and approve postings!!
like this!
X-Mailman-Version: 1.1
Precedence: bulk
List-Id: Discussion of the SmartList Software <smartlist.lists.RWTH-Aachen.DE>
Your mail to 'Smartlist' with the subject:
Help
Is being held until the list moderator can review it for approval.
The reason it is being held:
possible administrivia to list
Either the message will get posted to the list, or you will receive
notification of the moderator's decision.
I need to know what to do to de link the hard link from dist file to the
accept file. I wish to have subscribers put in the dist file, and not the
access file. I wish to have the access file for only those I want to be
able to post to the list.
Thanks Jim Glaze
I just read this on another list and was wondering if it is true:
>I spoke too soon about smartlist - it lets anyone post to it regardless of
>if they are a subscriber or not and regardless of what the 'access' is set.
>There is another hole that a person can send messages to a smartlist list by
>adding -dist to the end of a listname (Ie: testlist-dist(a)lists.mzaus.com) so
>I decided not to use SmartList.
... is that the case? I need a lightweight list program
but would like to have only people who are subscribed
to the list be able to post.
TIA,
--
Mark
In the context of CGI programming Perl is like duct tape
whereas C is like 2 part quick hardening epoxy.
--smithj(a)ulv.edu on the oclug list
I have a list that often will go a day or so without any posts, which
unhinges the next 2pm digest delivery. I have cronlist running daily, but
have not figured out how to work .digest.force into the daily schedule.
I've created it manually a few times and found that this helps the digest
delivery. But how do I automatically create this file on a daily basis?
Is it something that can be added to the cronlist or flush_digest scripts?
Or should it be a separate cron job? How do I do this?
TIA
linda
When I send a message to a maillist, I receive a copy of my own message, because I am listed in the dist-list as well. Is it possible to suppress this behaviour? So I will not receive a copy of my own message?
Frans Gouverne.
Hi,
I hope this list is still active. I have the following problem:
I'm using smartlist through the "control panel" of my webprovider, so with
some clicks, all was installed. After that, I changed a lot to get it
working the way I wanted it. Everything works fine except for
bounce-detection.
When I put some non-existing mail-adress in the dist list and send some
mails through the list, there is no sign of any bounce detection whatsoever.
There is not even a "bounces" directory. I am doing something wrong,
expecting something that is not there, or am I looking at the wrong place or
something?
Thanks allready,
Regards,
Jelmer
-----------------------------------------------------------
Drs. Jelmer Jellema - Spin in het Web
www.spininhetweb.com
Spin in het Web geeft internet inhoud
-------------------------------------------------------------
Spin in het Web is de producent van:
www.visinhetnet.nl: Grote Partij Kinderpostzegels Onderschept
www.irritantman.nl: Irritant Man! - Reden tot Klagen
Dear Smartlist subscribers,
> I retrieved your name/e-mail address from the SmartList FAQ web page with
> the hope you can provide an answer or direction to a problem I'm having.
> I've read the FAQ's and the SmartList manual regarding the insertion of a
> header/footer into an e-mail. I've followed the appropriate steps but it
> doesn't work completely.When I send an e-mail from Microsoft Outlook to my
> list the body contains only the message not the header and footer to the
> addresses that use Exchange. However, when the e-mail is delivered to the
> UNIX machines both the header and footer are present.
>
> I edited the rc.custom file and uncommented the
> RC_LOCAL_SUBMIT_20=rc.local.s20 line.
> I created the rc.local.s20 file and included the appropriate lines:
> :0 fhw
> | cat - header.txt
>
> :0fbw
> | cat - footer.txt
> I created the header.txt footer.txt file with the appropriate lines.
>
> It does work but only for accounts on the UNIX (hpux 10.20) machines.
> Currently running version 3.10 of smartlist.
>
> Here is the output of the mail using elm:
> <<email.txt>>
>
> Thanks,
> Tom O'Rourke
>
>
> I've set it (correctly I think) on our server, to collect
> email addresses for a company newsletter. I've downloaded
> the manual and read it over and over, but when I send
> X-Commands and try to distribute a newsletter, absolutely
> nothing happens.
>
> I've spent hours trying to figure out what it is I'm doing
> wrong [...]
One thing to check for: The X-Command has to be in the _header_ of
e-mail message sent to list-request(a)domain.com. Some mail clients
won't let you add your own custom header lines, or they make it
difficult.
I modified the way X-Command works, to support list admin commands
in the _body_ of the message. The logic checks to see if the from
address matches the list maintainer address, and if it does,
it allows the list commands. I didn't add a password check, but
that would have been straightforward as well. The list maintainer
check can be easily generalized to allow more than one maintainer.
The mod is in rc.request, just ahead of the recipe that already
handles X-Command. Here's the logic:
#
# Or is it a special remote "admin" command from the maintainer?
#
:0 H wf:dist.lock
* $^From:.*$maintainer
* ^Subject:.*admin
* $!^X-Loop: $listaddr
* $!^X-Loop-Admin: $listaddr
| do_admin
which is inserted just ahead of this part of the recipe:
#
# Or is it a remote X-Command from our maintainer?
#
:0 H wf:dist.lock
* $^$X_COMMAND:.*$maintainer[ ]*$X_COMMAND_PASSWORD
* $!^X-Loop: $listaddr
| x_command
The extra logic looking for X-Loop-Admin checks for the cases where
mail to the maintainer is looping. This can happen sometimes, and
when it does, bad things happen.
The "do_admin" script is in in the .bin directory, and is a slight
variation on "x_command":
#! /bin/sh
:
echo=echo # /bin/echo
test=test # /bin/test
cat=cat # /bin/cat
rm=rm # /bin/rm
formail=formail # /usr/local/bin/formail
subscribe=subscribe # ../.bin/subscribe
unsubscribe=unsubscribe # ../.bin/unsubscribe
multigram=multigram # ../.bin/multigram
tmprequest=tmp.request
tmpfrom=tmp.from
dist=dist
log=log
$test -z "$listaddr" &&
$echo "Don't start this script directly, it is used in rc.request" && exit 64
X_ENVELOPE_TO=$list-request # to convince (un)subscribe we used the right
export X_ENVELOPE_TO # address
$cat >$tmprequest
$formail -a X-Processed: <$tmprequest
set dummy `egrep '^(subscribe|unsubscribe|checkdist|showdist|showlog|help|info|wipelog|version)' < $tmprequest`
shift
while $test $# != 0
do
case "_$1" in
_subscribe|_unsubscribe|_checkdist)
if $test $# = 1
then
$echo "X-Diagnostic: Missing argument for $1"
set help
fi;;
esac
case "_$1" in
_subscribe)
$echo "From $2 " >$tmprequest
$echo "From: request ($listreq)" >>$tmprequest
$echo "Reply-To: $2" >>$tmprequest
$echo "To: $listreq" >>$tmprequest
$echo "Subject: subscribe $2" >>$tmprequest
$echo "$2" >$tmpfrom
$test -z "$subscribe_log" ||
$echo "x_command: subscribe" >>$subscribe_log
$subscribe <$tmprequest ||
$echo "X-Diagnostic: Unscreened, not subscribed"
shift ;;
_unsubscribe)
$echo "From $2 " >$tmprequest
$echo "From: $listreq" >>$tmprequest
$echo "Reply-To: $2" >>$tmprequest
$echo "To: $listreq" >>$tmprequest
$echo "Subject: unsubscribe $2" >>$tmprequest
$echo "$maintainer" "$2" >$tmpfrom
$test -z "$subscribe_log" ||
$echo "x_command: unsubscribe" >>$subscribe_log
$unsubscribe <$tmprequest | $SENDMAIL $sendmailOPT `cat $tmpfrom`
shift ;;
_checkdist)
$echo "Multigram checking the dist file for matches with"
$echo "$2:"
$echo ""
$echo "From $2" | $multigram -b8 -l-32767 dist
$echo ""
shift ;;
_showdist)
$echo "--- Current subscribers:"
$cat $dist
$echo "--- End of subscriber list" ;;
_showlog)
$echo "--- Current log:"
$cat $log
$echo "--- End of log" ;;
_wipelog)
$cat /dev/null >$log ;;
_version)
flist -v 2>&1
echo ""
procmail -v 2>&1 ;;
_help|_info)
$echo "Known $X_COMMAND keywords:"
$echo " subscribe mailaddress"
$echo " unsubscribe mailaddress"
$echo " checkdist mailaddress"
$echo " showdist"
$echo " showlog"
$echo " wipelog"
$echo " version"
$echo " help"
$echo " info" ;;
*) $echo "X-Diagnostic: Unknown command $1" ; set dummy help ;;
esac
shift
done
The key differences between "do_admin" and and "x_commend" are below.
The lines with exclamation points,
$cat >$tmprequest
! $formail -R$X_COMMAND: X-Processed: <$tmprequest
! set dummy `$formail -x$X_COMMAND: <$tmprequest`
! shift; shift
! test "_$X_COMMAND_PASSWORD" = "_$1" && shift
while $test $# != 0
do
case "_$1" in
are replaced with these:
$cat >$tmprequest
! $formail -a X-Processed: <$tmprequest
! set dummy `egrep '^(subscribe|unsubscribe|checkdist|showdist|showlog|help|info
|wipelog|version)' < $tmprequest`
! shift
Basically, instead of looking for X-Commmand in the header, and then
extracting the commands from those lines, the script looks for the
commands as the appearing in the first column, and then works through
those commands one-at-time as the previous script did. The password
handling was removed, but with a little work could be added back in.
For now, the check for the maintainer address is considered to
be sufficient, though this could be spoofed, and something more
robust is desirable for production use. The advantage of allowing
the commands in the body of the message is that the user who is
managing the list can use any mail client, and doesn't need to
figure out how to create custom header lines.
Here's an example of an admin message processed by the method
described above:
From: list_manager(a)domain.com
To: list-request(a)list_domain.com
Subject: admin
unsubscribe old_user_address(a)old.com
subscribe new_user_addr(a)new.com
showdist
Hi,
A lot of people (not all of them) who send us an
email, receive an error message and we do not receive
their mail. Our account is at Yahoo, but they don't
seem to respond to our cry for help.
Can you please HELP US !!!
Patricia and Edwin
patricia_edwin(a)yahoo.com
taaltotaal(a)email.com
__________________________________________________
Do You Yahoo!?
Yahoo! Photos - 35mm Quality Prints, Now Get 15 Free!
http://photos.yahoo.com/
