In article <v03130311b8e9ecdc17ce(a)[192.168.123.10]>,
Charlie Summers <charlie(a)lofcom.com> writes:
> At 12:20 PM -0400 4/22/02, Kapoor, Nishikant X is rumored to have typed:
>
>> Is there a way to restrict postings from a particular email address ? I
>>have a poster who just would not stop posting junk stuff ?
>
> This is something of a FAQ, too; or at least is covered in the Manual file
> (see section 3b) that comes with the SmartList distribution. Short answer:
> add the address to the linked reject file.
The reject file is unfortunately only applied to subscribe requests;
if someone is subscribed to your list, adding their e-mail address to
the reject file won't prohibit them from posting.
This patch to rc.submit should make SmartList use the reject file to
screen list postings.
diff -u -r1.5 -r1.6
--- rc.submit 1999/06/07 15:31:40 1.5
+++ rc.submit 1999/06/23 17:57:17 1.6
@@ -109,6 +109,20 @@
multigram -b1 -m -l$submit_threshold -L$domain \
-x$listaddr -x$listreq $accept_files
{
+ # Check to see if the poster is on the reject list. The reject
+ # list overrides the accept list.
+
+ :0
+ * ? formail -X"From " -xFrom: -xReply-To: -xSender: -xResent-From: \
+ -xResent-Reply-To: -xResent-Sender: -xReturn-Path: | \
+ multigram -b1 -l$reject_threshold reject rejectx
+ {
+ :0 wfh
+ | formail -A "X-Diagnostic: Found on the reject list" \
+ -A "X-Diagnostic: `multigram -b1 -l$reject_threshold reject rejectx`"
+
+ HOST=continue_with_rc_request
+ }
INCLUDERC=$RC_LOCAL_SUBMIT_10
Hi,
I wanted to make our list subscriber only, so I uncommented the
foreign_submit line per the FAQ. However, I soon realized that nobody except
the one address that was in the accept file was able to post to the list.
Evidently, the accept list was never linked to the dist list, or somehow
became unlinked.
Anyway, I'm a Linux rookie, but I did figure out how to SSH into my site
through my web provider, then I used the following shell commands:
rm accept
ln dist accept
This seemed to do the trick, but did I do it right? Any ideas how the file
may have become unlinked in the first place?
--
Bruce Vander Werf
brucev(a)cyberlink.com
Is there anyway to configure smartlist to reject attachments?
Thanks
Jerry Sloan
--
"Let us take care that age does not make more wrinkles on our spirit
than on our face."
Michel de Montaigne
To extend another tool for xcommands with encryption capability I modified
my xcommand cgi and named it xcommsec. It is available at
ftp://ftp.pure.ch/smartlist/
For the usage of xcommsec it is required to install xc_sec, available at
the same URL and to use something like TLS/SSL to have a secure connection
to the script.
BTW: Anyone on the list knows of other MLM with mechanismn like xcommand.
If there are some, how do they handle the authentification. Do they
also send cleartext passwords?
Werner
Just put a new version of xc_sec on my ftp server. xc_sec is an addon
to SmartList for the secure transmission of xcommand passwords. By
default xcommand passwords are send in cleartext over the wire.
I released a new version because the usage of sequence numbers is
cumbersome, especially if you use different machines for sending xcommands.
The new version uses a combination of time stamps and unique ID's to ensure
that the encrypted password isn't reusable.
You can get xc_sec at
ftp://ftp.pure.ch/smartlist/xc_sec-0.4.tar.gz
Werner
Good day.
I have been receiving these messages all day on this one individual. I have not
seen one of these with this wording and since Yahoo does not support their
service, I had hoped I could find an answer on this list.
Thank you.
The original message was received at Tue, 16 Apr 2002 18:56:05 -0400
from intrepid@localhost
----- The following addresses had permanent fatal errors -----
wwood_38478(a)yahoo.com
(reason: 552 Put ,E=\r\n at the end of Mether, Mtcp, or Msmtp in sendmail.cf
if you are using Solaris 2.5 (fi... cannot accept messages with stray newlines.
Many SMTP servers will time out waiting for \r\n.\r\n.)
----- Transcript of session follows -----
procmail: Couldn't read ".rc.local.init"
procmail: Couldn't read ".rc.local.init"
... while talking to mx1.mail.yahoo.com.:
>>> DATA
<<< 552 Put ,E=\r\n at the end of Mether, Mtcp, or Msmtp in sendmail.cf if you are
using Solaris 2.5 (fixed in 2.5.1). I cannot accept messages with stray newlines.
Many SMTP servers will time out waiting for \r\n.\r\n.
554 5.0.0 wwood_38478(a)yahoo.com... Service unavailable
Jeff
Jeff Dougherty
Intrepid Video & Electronics God answers
501 Luther Rd Knee-mail.
The 0.3 version of xc_sec is now offering truly unique one time ciphers.
Should somebody have already installed xc_sec 0.1 or 0.2 an upgrade only
requires to customize the scripts mkfish.pl and decrpwd, copy decrpwd
to the .bin directory of your Smartlist installation and create sequence
files as described in the INSTALL file.
xc_sec is available at
ftp://ftp.pure.ch/smartlist/xc_sec-0.3.tar.gz
Werner
Since the maintainer password is send in cleartext with the x_command
interface of SmartList I made some scripts and patches to enable SmartList
to process x_commands with encrypted passwords. The encryption mechanismn
is Twofish. Encryption can be enabled/disabled with a variable in
rc.custom. Two small patches for rc.request and the x_command script are
necessary.
Grab it at
ftp://ftp.pure.ch/smartlist/
It's called xc_sec-0.1.tar.gz.
Werner
The first version of xc_sec isn't very helpful because it lacks the
capability to create unique ciphers. The new version
ftp://ftp.pure.ch/smartlist/xc_sec-0.2.tar.gz
has also a customized doxcommand script which you can use to send
your xcommand's on the command line with safely encrypted passwords.
Werner
