To allow also email addresses with characters like "? * +" in the user part
of an email address (thats permitted by RFC822) I released a new version
of the confirm package (v. 1.2.5).
It's available from
ftp.pure.ch/pub/smartlist/
Werner
On Mon, 27 Jun 2002, Greg Matheson wrote:
> What modifications do you have in mind? With qmail, it is easy
> for ordinary users to set up alternatives like
> listname-subscribe(a)host.tld, but more difficult with other MTAs.
For now I have simply kludged the following (inadequate) solution (mostly
because my recipe writing ability remains at "trial-and-error").
1. In aliases file:
listname-subscribe: "|exec /home/list/.bin/flist listname-request"
2. Activiate rc.local.r10 in rc.custom
3. rc.local.r10 is called in rc.request and contains a preemptory
:0:
| subscribe
(Yes, I know, this is a catastrophe ... but in my case, I have just
started the list, and while I am waiting for a week or two for people to
sign up, I am hoping I can find a better solution!)
----------------------------------
What would be better is that there is a recipe in rc.request that
would check the "To" field. If it was "listname-subscribe" or
"listname-unsubscribe", then it would do the appropriate actions.
I am sure it is trivial. But even if I have been using Smartlist for 5
years, I am not very smart about it, and my trial-and-error attempts to
make recipes here did not give good results, hence my query to this list.
Cheers,
Seth Chaiklin
I could not figure out (nor find in the FAQ)
how to allow persons to subscribe with:
listname-subscribe(a)host.tld
This is much easier to explain to novices.
There must be a variety of solutions, but some are
probably more elegant (and secure) than those that
I could create.
Thanks for any advice.
Sincerely,
Seth Chaiklin
Well, we have a huge list (more than 50,000 subscribers). Of course, with
so many subscribers, we have a large number of request actions (sub,
unsub, bounces, etc).
And some time, multigram gone in the nirvhana ;~{
The load average grow up, and all things are locked.
~>top
8:25am up 4 days, 9:41, 2 users, load average: 10.24, 9.74, 8.33
....
PID USER PRI NI SIZE RSS SHARE STAT LIB %CPU %MEM TIME COMMAND
15792 list 10 0 396 396 324 R 0 26.8 0.1 156:54 multigram
13949 root 10 0 2040 2040 1048 R 0 3.1 0.7 0:00 sendmail
Any idea welcome.
Thanks,
Francois.
--
"Quelle Connerie la guerre" (J. Prevert)
Francois Sauterey
Tel: +33 01 40 33 68 46 mailto:Francois@sauterey.org-nospam
Mon seul hébergeur : le RAS (.eu.org) ;~}
Hi,
A few of my members are asking for daily per-person message limits. I
am pretty sure that doing this is quite difficult so I am not even
going to try it.
However, I am interested in figuring out if I can limit the total
number of messages per day on the list. I have a general idea of how to
do this (increment a file-based counter for each message; check the
value against the limit; if less, pass the message to the next stage;
if threshold exceeded, replace the accept file with a file with only my
address in it) but am not sure how feasible this is.
Has anyone tried something like this?
Thanks,
Harshal
=====
http://www.mumbai-central.com : Where Mumbaikars meet
__________________________________________________
Do You Yahoo!?
Yahoo! - Official partner of 2002 FIFA World Cup
http://fifaworldcup.yahoo.com
I just moved mail delivery for my domain from from server A to server B, and
now messages sent to the lists on server B aren't being delivered.
Un/Subscriptions (with confirmations) and digests work, but when a message
is sent to the list itself it just goes *poof* and disappears. No
dead.letter files (that I can find), LOGABSTRACT is set to yes, but logging
stops after the message is added to the digest folder.
Any ideas? Is this a known problem that's been seen before? I'm on RH 7.2
(kernel 2.4.9-31), procmail 3.21-1 (rpm) and smartlist 3.15. I installed
smartlist using the procmail 3.15 source tree. Could the problem be with
using a newer version of the procmail binary?
TIA,
Steve
Hi,
is there anywhere in docs explained what id the meaning of these
scripts? I cannot find it anywhere! :(
I always hoped rc.local.s* means possibly "send" but rc.local.r* means
"receive" or maybe "resend"?
I had to put in form of each rc.* script line like:
LOG="rc.local.XX begin:
"
XXXXXX
LOG="rc.local.XX end
"
to trace them.
So, I figured out they are executed in order
rc.init
rc.custom
rc.local.r00 ???
rc.local.s10
rc.local.s20
BUT!!! My calls to html-trap got bypassed today, as it seems rc.local.r00
is executed only when the senders address is not on the accept list ....
:( So it the rc.local.r* means "reject", right? Arrgh.
Could someone clearly state the naming convention, order seems from lowest
to highest number.
Which scripts are always executed and which only in some tricky
conditions?
Attached you can find diff of the early beginning of procmail's processing
a message. The one was catched from from address not on the list, the
second which bypassed checks and got accidentally through was sent from
address on the list.
Maybe I'm totally wrong with my guesses, could then someone tell me why
execution diverged in those 2 cases?
TIA
--
Martin Mokrejs <mmokrejs(a)natur.cuni.cz>
PGP5.0i key is at http://www.natur.cuni.cz/~mmokrejs
MIPS / Institute for Bioinformatics <http://mips.gsf.de>
GSF - National Research Center for Environment and Health
Ingolstaedter Landstrasse 1, D-85764 Neuherberg, Germany
tel.: +49-89-3187 3683 , fax: +49-89-3187 3585
Can you help me troubleshoot this SmartList problem? I searched the smartlist archives but couldn't find reference to this...
Problem:
Text in the header.txt file is -not- included in an email if a file is attached to the email.
Additional information:
* The problem does not happen if the email does not include any attachments.
* The proper SmartList files are set up (header.txt, rc.custom and rc.local.s20) correctly because the header text does display in emails without attachments.
I don't know where to start troubleshooting this. I just started using the basic features of SmartList for 'announcement-only' emails to a mailing list. Can you point me to where the cause might be?
Thanks in advance.
Abbo
