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
Ages ago when the server that I use was upgraded the X-Commands by
email stopped working As there was also webtools available, I played
and had general looks around and never got around to finding the
cause.
Anyway, I have finally tracked it down to ver 3.22 of procmail being
the culprit (I stuck in symlink to an earlier version and it worked).
I was wondering whether anyone else had the same problem (otherwise
it may just be the local build of procmail). Or if anyone does have
email X-Commands working with a procmail build of 3.22.
Thanks.
Regards, Andrew
I've been dealing with this for a few months on a number of lists I manage,
as the Bagle virus picks up from lines from received emails on infected
computers. From the pattern, it doesn't seem to be an intentional attack
against listserves, it's just another #*!&^ virus.
My lists are newsletter-type (with a few approved posters on each). Outlook
and Outlook Express, in use by most folks, can't add custom headers. The
"Organization" field is now rarely used by folks. Therefore, if I can get
smartlist to look at this header field AND have the approved posters use,
e.g. the organization "1234", I can have only approved posts get thru my
lists.
But I'm not a programmer. I simply bludgeon smartlist into submission, which
is preety easy due to the many easy-to-change parameters.
Here's what I came up with:
Filename: rc.local.20
-------- cut here ---------
HEAD=`formail -zx Organization:` # extract the header information
:0fw
* ^Organization:.*\[1234]\
-------- cut here ---------
Alas... it doesn't work. All posts go thru regardless of the contents of the
Organization field.
Any ideas?
-- Phil
> On Tue, Jun 15, 2004 at 02:42:32PM -0500, rgball wrote:
>
> >1) go through all the list's archives and match information in the
> bottom-most Received: line to
> >the subscriber's address. Keep all of this in a database (not the dist
> file).
>
> Can't rely on that. Received: lines can be faked, as long as they're
> below the point of injection into the system.
>
> If there's spoofing going on, the spoofers are presumably motivated to
> keep it happening.
>
> You could just rely on a valid PGP signature before passing on the
> message. But there are very few lists that do this, in large part
> because most people find PGP too hard to use.
>
> >It's still not going to be proof against a determined spoofer but should
> eliminate the casual
> >spammers.
>
> I first saw spam with fake Received: header lines some time around 1997.
>
> Roger
>
I am having trouble with a SmartList being used to send SPAM to list
recipients.
I have the rc.custom file set up to reject foreign submissions. A single,
authorized address in the accept file (ex: webmaster(a)mylist.com). My entire
60,000 member list just received a mailing from someone who apparently set
up the authorized address, webmaster(a)mylist.com, on their own machine, then
used it to send an email with attached virus.
Would it be possible to avoid this problem in the future by sending a
message to the list, then immediately removing the authorized "send" address
from the accept file?
>From the "request" record, it appears that the accept list is only read when
the message is sent (not at each iteration of the call to flist.) Is this
correct? If so, it seems that I could prevent spoofing by de-authorizing all
senders immediately after sending a legitimate message.
Thanks for your help, or any other advice you may have.
Kim R
You might try putting the new subscriber's address in the subject of the email
message:
Subject: subscriber newperson(a)new.host
and see if that suffices.
--
Rick DeMattia <rad(a)nshore.org>
The secret of the universe is|^&*||x|NO CARRIER
Hello,
I'm having a problem using SmartList with FormMail. I have a web form
that prompts for an email address, then generates a message to the
newsletter subscribe address, with subject "subscribe", from the
address that the user entered. The problem is that it doesn't work.
No user visible error is generated, but in the message mailed to the
list admin there are header lines
X-Diagnostic: Already on the subscriber list
X-Diagnostic: 752 listadmin(a)ourdomain.com 32744
listadmin(a)ourdomain.com
In the SmartList log I see
From listadmin(a)ourdomain.com Tue Aug 31 19:29:47 2004
Subject: subscribe
Folder: formail -R"From X-From_:" -iDate: -iReturn-Receipt-To: -iRe
1190
It looks like SmartList thinks that the message is sent from the
admin's address, and discards it since that address is already on the
list, even though the "from" header is set to the new address. Sending
a subscribe message from a mail client works, so the list software
seems to be set up correctly. The web form is configured correctly as
far as I can tell, and does put the email into the "from" header.
I'm at a loss to understand why SmartList thinks these message are
coming from the admin address. Any ideas? Thanks
--
Parker Abercrombie <parkera AT cs.ucsb.edu>