Joe Ah posted a patch location to the list last week - here's his
message...
-----
Here's the patch for 1.94.4, but it should easily apply to 1.94.5 too:
ftp://ftp.ccsf.org/majordomo-patches/1.94.4/resend.7
Regards,
Joe
--
_/ _/_/_/ _/ ____________ __o
_/ _/ _/ _/ ______________ _-\<,_
_/ _/ _/_/_/ _/ _/ ......(_)/ (_)
_/_/ oe _/ _/. _/_/ ah jjah@cloud.ccsf.cc.ca.us
On Mon, 29 May 2000, Hallvard Tangeraas wrote:
> I've been running a Majordomo list for a couple of years now, but the
> provider is closing down its services and I've had to ask a friend if
> he could let me use his server for a new list.
>
> He knows a lot about UNIX, programming and that sort of stuff has set
> up a new list which is working fine.
> I've spent the past few days configuring the "config", "intro" and
> "info" files as well as testing it.
>
> As he doesn't know much about Majordomo, and I don't know much about
> the technical stuff we try to complement each other's knowledge, so
> basically I'm trying to find the information needed, and he does the
> installments/configurations at the server.....
> I've got a fair bit of knowledge about the stuff you do via email
> concerning the files mentioned above.
>
>
> The version of Majordomo I'm now using with the new server is 1.94.5
> which I understand is the latest one, right?
>
> Any patches or fixes I should have my friend install? Any extra
> features which could come in handy with additional patches?
>
> What I really want to know is about the "bounce" problem.
> Now and then members with multiple accounts forget that they can only
> post from the same account as they've subscribed from.
>
> I've already set up the following parameters to make it as secure as possible:
>
> get_access = list
> intro_access = list
> restrict_post = notator
> subscribe_policy = open+confirm
> unsubscribe_policy = open+confirm
> which_access = list
> who_access = list
>
> Now, as far as I can tell this should eliminate just about all
> problems, alerting the sender that he/she can't access those commands
> because they're non-members, and that if subscribing/unsubscribing, the
> person in question is contacted (in case the non-subscribed address is
> used when sending the command) and so on.
>
> The only exception is when a non-member (i.e. a member using another
> account) posts a message to the list.
> In this case, I, as the list-owner get a "bounce" message.
> What good does this do? It only causes me more work as I have to
> contact the sender about this.
> Why not alert the sender as with those commands which are only
> restricted to list members?
>
> I believe there is a patch or a solution for this, but I couldn't find
> any looking through older messages.
>
> Hallvard
> --
> Hyperlink Launchpad: <http://also.as/hall/>
> Atari Launchpad : <http://www.geocities.com/SiliconValley/Bay/8745/>
> Notator/Creator SL : <http://www.crosswinds.net/~notator/>
>
>
References:
|
|
