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
I seem to have got smartlist up and running on my shell account now,
I have successfully subscribed myself to a test list anyway. However
all my requests to the request list get the following warning:-
WARNING:
Please try to use 'uk-riders-request(a)isbd.co.uk'
the next time when issuing (un)subscribe requests.
As far as I can tell I *am* sending reqests to
'uk-riders-request(a)isbd.co.uk'.
--
Chris Green (chris(a)areti.co.uk)
Home: chris(a)isbd.demon.co.uk Work: cgreen(a)bcs.org.uk
WWW: http://www.isbd.co.uk/
Greetings.
I've set up the Maintainer email in rc.custom
and set cc_requests & cc_unsubscribe_requests to "yes".
Problem is that while _subscribe_ requests work as
they should, _unsubscribe_ requests generate an
*extra* Unsubscribe acknowledgment to the sender,
only with "possible loop" and "mail from daemon"
msgs in the header. Nothing is then CC'd to maintainer.
Any ideas on how to fix?
Thanks!
Scott Warstler
Hi!
I keep asking questions :-)
I've created a separate account within the same domain as my list is on
with the purpose of sending news items to my list. From that account,
however, I cannot post to the list. The address is both in the dist and
accept files.
The only one who receives mail from that address is the administrator
account. The header says: 'Mail coming from a daemon, ignored'
Can someone please tell me why?
Kind regards,
Anne-Marie Oualit
hi,
On Mon, 20 Nov 2000 19:57:46 you wrote:
>
> i have some problems with confirm (v 1.2.3) and Smartlist 3.15
> If the subscriber sends back his confirmation-mail, he is not
> subscribed and added into dist-file, but the message is
> forwarded to the maintainer with X-Diagnostic: Unprocessed
>
> #confirm_maintainer = yes # This forwards all subscription requests to
> confirm_maintainer # the maintainer(s) who have to confirm or
> # ignore the messages.
try commenting out the 2nd `confirm_maintainer' line. I seem to recall
someone explaining in this list that configuration options were set
depending on whether the line was commented out or not, and that
the `=yes' or `=no' at the end was there for cosmetic (readibility)
purposes. Thus, with the above uncommented line your are configuring
smartlist to do what you complain it does: forward all subscription
requests to the maintainer for confirmation.
Miquel
Miquel E Cabanas ------------------------------------------------------
e-mail: Miquel.Cabanas(a)uab.es
Servei d'Espectroscopia de RMN (SeRMN), Univ. Autonoma de Barcelona
Edifici Cs. Cerdanyola del Valles, 08193. Catalunya - Spain
------------------------------------------------------------------------
Hi all, from one month I'm running 10 mail list with Smartlist.
Untill today the server (Linux SUSE 6.4 - with last version of Exim in
replacement of the default sendmail) has worked very good, but today there
was a loop and the same e-mail was sent to the list about 30 times ...
In the mailer log I have these entries:
Mainlog:
2000-11-23 16:16:21 13yy5C-0006NW-00 Failed to get write lock for
/var/spool/exi
m/db/wait-remote_smtp.lockfile: timed out
2000-11-23 16:16:22 13yy5C-0006NW-00 Failed to open wait-remote_smtp
database: C
onnection timed out
Paniclog:
2000-11-23 16:19:19 13yy8r-0006Ul-00 failed to unlink
/var/spool/exim/input//13y
y8r-0006Ul-00-D
2000-11-23 16:19:19 13yy8q-0006UM-00 failed to unlink
/var/spool/exim/input//13y
y8q-0006UM-00-D
In the rc.local.S20 I have this line to strip from the header the e-mails of
the list subscribers:
:0 fhw
| formail -k -X From: -X Subject: -X Date: -X To: -X Reply-To:
Maybe I have stripped the loop flag (if it exists !) ?
Many thanks in advance
Giorgio
Occasionally procbounce detects an excessive number of bounces and proceeds
to unsubscribe the sender, not the bouncing address. Have looked at
procbounce and rc.request, but I can't find how this can happen. I am using
the default bounce parameters, using 3.13.1 in a Solaris environment with
the public (not Sun) sendmail. Any ideas?
Del
D. L. Kimbler, Ph.D., P.E.
Professor, Industrial Engineering
Clemson University
Voice: (864)656-5645
Fax: (864)656-0795