I'm setting up SmartList on my in-house mail server. The server is
running Debian 2.2 and using exim 3.12 as my MTA, procmail 3.13.1, and
SmartList 3.13.1. The aliases for the list test ok when I run:
exim -bt <listname(a)domain.org>
But when I submit a test subscription, the exim log produces a correct
piping to flist as seen in the log excerpt:
2000-09-20 11:41:56 13bmwV-0003ER-00 <= dnewman(a)chickenusa.org
H=(chickenusa.org) [209.8.37.151]
P=esmtp S=1531 id=39C8D94B.1F367604(a)chickenusa.org
2000-09-20 11:41:56 13bmwV-0003ER-00 => |/var/list/.bin/flist
WashingtonReport-request
<WashingtonReport-request(a)chickenusa.org> D=system_aliases
T=address_pipe
2000-09-20 11:41:56 13bmwV-0003ER-00 Completed
But nothing happens. The address is not added to dist. I have
"LOGABSTRACT = yes" and "VERBOSE = yes" in the list's rc.custom, but I
get no log file.
How do I test that flist is operating?
Thank you for your assistance.
--
Wade Parker
National Chicken Council
I'm in the process of setting up mailing lists for a very large
organization. I need to find a set of web based utilities to allow the list
maintainers to point and click their way through list administration
(subs/unsubs/digesting/etc). Any suggestions??
--
Sarah Miller
List Administrator
Digitaleve.org
It is in .bin/subscribe
> Subject: subscribe.txt questions
>
> 1) When someone subscribes to one of my lists they get this "header" which
> appears above the text contained in subscribe.txt:
>
> You have added to the subscriber list of:
> mylist(a)mydomain.com
> the following mail address:
> subscriber(a)somedomain.com
>
> How can I get rid of this, along with the transcript of the original
> subscription, so that I can include only a simple url (to an html based
> subsciption/unsubscription page) and some other basic instructions?
>
> Many thanks,
>
> Simon Troup
I want to stop bounces from foreign senders from being sent to my list
maintainers. I want foreign senders to receive a copy of the accept.txt file
and I want their original message to go into the bit bucket, without being
sent to the list maintainer. How do I do this?
--
Sarah Miller
List Administrator
Digitaleve.org
1) When someone subscribes to one of my lists they get this "header" which
appears above the text contained in subscribe.txt:
You have added to the subscriber list of:
mylist(a)mydomain.com
the following mail address:
subscriber(a)somedomain.com
How can I get rid of this, along with the transcript of the original
subscription, so that I can include only a simple url (to an html based
subsciption/unsubscription page) and some other basic instructions?
Many thanks,
Simon Troup
does smart list allow you to have seprate distribution (who gets mail) and
accept lists (who can send mail) if not do people know of other software
that does?
thanks
Paonia
Are there any kind souls out there who would like to answer some
questions I have as a new user of smart list?
I don't want to bore the whole list with my basic questions.
-charlene
--
--------------------------
Charlene Reese - S r T e U e D s I e O
Digital Graphic Design for Print, Multimedia and the Web
c(a)reesestudio.net http://www.reesestudio.net
949.766.7822
I am tryign to figure out how to set my list to only allow subscribed users
to post to the list. Is it possible to do this without setting the list as
moderated?
TIA.
Hi.
I want to setup a mailing list that will be administered by one of my clients but i want him to be able to add users just up to a certain predefined number of mailing list users. For instance, i want to allow him to add users to a certain mailing list up to a maximum of 20 users. Of course, i don't want to have to check everyday if he's over the limit. Does Smartlist provide a way to do this ?
Thank you,
Carlos.
----------------------------------------------------
CARLOS SANTOS
(Cell/Mobile: +351 966456574, ICQ: 21537583)
----------------------------------------------------
NETOSFERA, INTERNET & MULTIMEDIA, LDA.
http://www.netosfera.pt / geral(a)netosfera.pt
Tel(Phone): (+351 253276998) / Fax: (+351 253274255)
Lrg. Sr. Aflitos, n8, 1And., Escr4
4710-261 Braga - Portugal
----------------------------------------------------
I'm pleased to announce the release of SmartList version 3.15.
This version includes support for the List-* headers (rfc2369),
corrects some problems in the support for having a digested and an
undigested list tied together, and fixes some other minor problems.
Items changed in version 3.14, which was only available as a
prerelease, included better handling of bounce messages (including
DSNs), a solution to the infamous "@yahoo" problems (incorrect address
extractions by multigram), as well as several other issues.
For the complete list of changes, please see the HISTORY file items
included below.
As with previous versions, you can find this package at the URLs:
http://www.procmail.org/SmartList-3.15.tar.gzftp://ftp.procmail.org/pub/procmail/SmartList-3.15.tar.gz
The procmail homepage, http://www.procmail.org, includes a list of
mirror sites at which this package should be obtainable within a few
days. It also has links to PGP signatures for the above.
Many thanks to the members of the smartlist-dev mailing list for their
ideas and testing, and special thanks to Santiago Vila for his last
minute testing.
Philip Guenther
Procmail & SmartList Maintainer
bug(a)procmail.org
1999/12/17: v3.14 (never really released, was only available as prerelease)
If no Message-ID could be recovered from a bounced message,
procbounce always picked the same hashkey (this time I mean it)
Strip List-* header fields from incoming messages and add
List-Subscribe: and List-Unsubscribe: with mailto: URLs for
the request address
Automatic cross-posting of messages sent to a digested list over
to the undigested list only worked if the latter contained
the letter 'y'
Recognize still more queue warning messages
Ignore "Data format", 8-bit conversion, and size errors -- the
address is fine, the particular message is presumably at fault
Use four digit digest volume numbers starting in the year 2000
Setting archive_hist to "all" causes the archive to never be
truncated
Changes to multigram:
- ignore words that start with an '@' unless they look like
a route address
Reject attempts to subscribe someone twice with an X-Command mail
Recognize DSNs and enable some primitive parsing of them
Mention online FAQ in SmartList Manual
2000/09/03: v3.15
Let the location of the "latest" archive be set from rc.custom
Add List-Help: and List-Post: header fields with mailto: URLs for
the request address and correct format of other List-* header
fields
"Wrong address" archive retrieval warnings could end up in the
header
Send submitted messages to maintainer if moderators file is
needed but missing
Only add List-Subscribe: and List-Unsubscribe: header fields if
auto_subscibe and auto_unsubscribe, respectively, are enabled
Clarify the error message when a list cannot be created
When forwarding a message from a digest list to its corresponding
undigested list, remove any Delivered-To: header field
containing the name of the digested list, thus allowing the
message forwarded back to go out.
Changes to multigram:
- prevent attempts to exercise a Linux kernel security hole
