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@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
On Thu, 27 Jun 2002, Seth Chaiklin wrote:
For now I have simply kludged the following (inadequate) solution (mostly because my recipe writing ability remains at "trial-and-error").
- In aliases file:
listname-subscribe: "|exec /home/list/.bin/flist listname-request"
- Activiate rc.local.r10 in rc.custom
- rc.local.r10 is called in rc.request and contains a preemptory
:0: | subscribe
Couldn't you have a .forward file for the user listname-subscribe that forwards the email to listname-request, or perhaps even just "|exec /home/list/.bin/flist listname-request" stuck in the .forward file would be OK. I've forgotten what little I learned about sendmail.
On Thu, 27 Jun 2002, Greg Matheson wrote:
On Thu, 27 Jun 2002, Seth Chaiklin wrote:
For now I have simply kludged the following (inadequate) solution (mostly because my recipe writing ability remains at "trial-and-error").
- In aliases file:
listname-subscribe: "|exec /home/list/.bin/flist listname-request"
- Activiate rc.local.r10 in rc.custom
- rc.local.r10 is called in rc.request and contains a preemptory
:0: | subscribe
Couldn't you have a .forward file for the user listname-subscribe that forwards the email to listname-request, or perhaps even just "|exec /home/list/.bin/flist listname-request" stuck in the .forward file would be OK. I've forgotten what little I learned about sendmail.
Ok.....in the sendmail aliases file:
listname-subscribe: "|exec /home/list/listname/forward"
(i.e., this simply pipes the message through a file called "forward")
The script in the file "forward" is:
FORMAIL=/usr/bin/formail # define location of formail from=`$FORMAIL -xFrom: ` # use formail to extract sender
# send the appropriate command echo "Subject: subscribe" | /usr/sbin/sendmail -f "$from" testing-request
This seems to work just fine.
I suspect this "forward" script could be incorporated into the rc.request script -- so back to some trial-and-error.
Cheers, Seth Chaiklin
On Thu, 27 Jun 2002, Greg Matheson wrote:
Couldn't you have a .forward file for the user listname-subscribe
Sorry I don't think that is an improvement over your first method. You don't have any user called listname-subscribe, so you don't use a .forward file. My apologies.
On Thu, 27 Jun 2002, Seth Chaiklin wrote:
- In aliases file:
listname-subscribe: "|exec /home/list/.bin/flist listname-request"
- Activiate rc.local.r10 in rc.custom
- rc.local.r10 is called in rc.request and contains a preemptory
:0: | subscribe
Are steps 2 and 3 necessary? When I want to pipe a mail through flist again, I just run "| /home/list/.bin/flist listname-request" on it. No exec. I don't know when that is necessary and unnecessary. This however is for mail with To: listname-request, not To: listname-subscribe
smartlist@lists.rwth-aachen.de
-
Greg Matheson -
Seth Chaiklin