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
is there a way to keep the real name w/ the e-mail address upon
subscription? has anybody patched or knows of some patches that will allow
this?
tia,
Bill
I'm trying to set up a web presence for a client, and just tried setting up
an HTML form using post to subscribe people to a Smartlist mailing list.
(I didn't see it mentioned as working, but I thought I'd try. It does get
emailed.) It almost worked perfectly: it uses the address posted in the
form, but the form puts a '=' in front of the address. Can anyone point me
to a good way to strip that out? (Sorry, don't know shell code yet.)
Daniel T. Staal
p.s. Here's a copy of what gets sent to Smartlist, in case you need it:
Return-Path: <countrynews-request(a)strictly-country.com>
Delivered-To: daniel(a)gandolf.magehandbook.net
Received: by gandolf.magehandbook.net (Postfix, from userid 1004)
id DDEC616D; Wed, 31 Jul 2002 14:26:24 -0500 (CDT)
X-From_:DStaal@usa.net Wed Jul 31 14:26:18 2002
Delivered-To: countrynews-request(a)gandolf.magehandbook.net
Received: from [192.168.1.10] (mac.magehandbook.net [192.168.1.10])
by gandolf.magehandbook.net (Postfix) with ESMTP id AAFFD161
for <countrynews-request(a)strictly-country.com>; Wed, 31 Jul 2002 14:26:10
-0500 (CDT)
To: countrynews-request(a)strictly-country.com
subject:subscribe
X-Mailer: Mozilla/4.0 (compatible; MSIE 5.15; Mac_PowerPC)
MIME-Version: 1.0
Content-type: text/plain
Message-Id: <20020731192611.AAFFD161(a)gandolf.magehandbook.net>
Old-Date: Wed, 31 Jul 2002 14:26:11 -0500 (CDT)
From: DStaal(a)usa.net
X-Diagnostic: Sent confirmation instructions
X-Envelope-To: countrynews-request
Date: Wed, 31 Jul 2002 14:26:24 -0500 (CDT)
E-mail Address:=DStaal@usa.net
How can I customise the welcome message when people subscribe to the list, for each individual list I have on my server, i.e. having a different welcome message for each list. The subscribe.txt file is common to all lists, and when I change it, it sends the same message whatever the list is.
>I've wondered, if the addresses are properly formatted with RFC822
>comments, will they be handled correctly at distribution time?
>Seems like a reasonable assumption, and it would be very nice
>indeed to have those real names handy. But it's never gotten to
>the top of my priorities to poke through the code, or try a
>test case on my list.
>
>Maybe one of the experts can say for sure one way or the other.
Using my own web-based front end to manage the subscriptions to my lists,
I keep real names in my dist files, using the format
user(a)domain.com (real name)
It doesn't cause any problems at all. I don't remember if I ever tried
real name <user(a)domain.com>
but, knowing how choplist works, I think this format would work fine as
well.
The changes needed to the subscribe script and the multigram source
didn't look trivial, so I've never tried to get SmartList itself to put
real names in the dist file.
-cary
At 11:10 PM -0400 7/30/02, Gyan Penrose-Kafka is rumored to have typed:
> I looked at the log and I kept seeing: "formail: Duplicate key found: ..."
That implies your message is returning to the mailing list for a second
go-round. Sounds (on a guess, based on insufficient information) that the
address you subscribed is somehow externally being redirected back to the
list address. This would imply a problem outside SmartList, maybe in your
.procmailrc file.
Simple way to see if the message was "delivered" my SmartList is to check
for its existance in the listdir/archive/latest directory (assuming it isn't
a digested list, of course, although it'll be there in the digest.body file
if it is).
You're on a hosting service; is it fair to assume you are using a
.procmailrc file to direct mail to the list on a virtual account? Or are you
using some "control panel" supplied by your provider to direct the mail?
(This is a seperate thing from a control panel that _controls_
SmartList...I'm trying to get a handle on how you're getting the mail
delivered to the list, since your previous posts imply you aren't rooting the
box and so need to use some other method than the alias file.)
Ah...crap.
I'm almost certain I know _exactly_ why you're getting this problem, and
it's partially my fault. Nothing like spending a minute or two to go back
over the last month's postings and catch up on the thread, which I should
have done before I started typing.
A while back, I explained that you could use a .procmailrc file to direct
mail to your list on a virtual domain, like:
:0
* ^TOlistname(a)yourdomain.tld
|/full/path/to/SmartList/.bin/flist testing
...and that's absolutely correct. But let's use the hypothetical domain
mydomain.tld and the hypothetical list mylist and examine what's happening.
You have:
:0
* ^TO mylist(a)mydomain.tld
|/full/path/to/SmartList/.bin/flist mylist
...in your .procmnailrc file. Ok, so far, so good. Now I subscribe as
charlie(a)lofcom.com. I post, SmartLIst accepts the mail, and sends it off to
subscribers, including me. Cool.
Now you subscribe the address gyan(a)mydomain.tld to the list, and send a
message (or _I_ send a message, doesn't matter). The message comes in, is
seen to be to the list address, and is piped to flist. SmartList distributes
it to the subscribers, including gyan(a)mydomain.tld; that copy of the
distribution comes into your .procmailrc file, is seen to be to the LIST
ADDRESS, and is piped to flist...which recognizes that it's a duplicate.
Blame the fact that it's been a whole lot of years since I had to run
SmartList as a virtual user on a shared machine, and not anticipating that
you'd not realize subscribing an address on the same account was a Bad Idea.
If you're going to subscribe an email address on the same virtual domain (or
a parked domain that uses the same real unix account, for that matter),
you'll need to trap out for that condition using something like:
:0:
* ^X-Loop:.*mylist@mydomain.tld
* ^TO mylist(a)mydomain.tld
/full/path/to/system/mailbox
:0
* ^TO mylist(a)mydomain.tld
|/full/path/to/SmartList/.bin/flist mylist
What you _should_ do is subscribe an external address to the mailing list;
if you have an account somewhere else, like maybe your access provider
(cox.net?), use it instead of an address on the same virtual server - that
will eliminate the problem entirely without having to trap out the mail
coming to you (different server, no harm no foul). You could also use other
header fields in the trap recipe (X-Envelope-To: if your provider adds it, or
maybe a Received:.*unixusername, or something else), anything that will ONLY
occur in mail to you, not to the list. Finally, instead of subscribing
yourself, you could add as the last recipe in the rc.local.s20 file:
:0 c
/full/path/to/system/mailbox
Note this problem will happen on _any_ address delivered to the same unix
account, and so running the same .procmailrc file. This also likely accounts
for the repeting subscribe.txt file loop...I'd almost bet there were
X-Diagnostic: headers in those things (ALWAYS check messages from the
-request side for X-Diagnostic: header fields...they are your friends).
You're also going to have to anticipate -request mails as well, especially if
you use an account on mydomain.tld as the admin account for X-Commands and
the like. I wouldn't; I'd use an address on an external machine to avoid all
the possible pitfalls.
If you don't understand what I'm saying here, let me know and I'll try to
explain it better; it's a simple problem, with a simple solution, regardless
of my verbosity.
Charlie (who should have figured this out long before now)