You will really feel a sense of accomplishment when you get everything
done too. I secure my lists just a little further with,
which_access = closed
who_access = closed
These commands can still be used by anyone with the admin_passwd and
knowledge of how to use the approve command.
As far as your non-member bounces go, if you know for a fact that the
person posting is a member but under a different email address, add
the "wrong" address to another file and add that filename to the
restrict_post = notator:notator-post
There has been some discussion on this list lately that a standardized
filename for this purpose should be <yourlistname>-post. Basically,
this is a file of non-members that are allowed to post to your list.
What you do as the list owner, is subscribe the offending address to
the notator-post list/file the first time you receive this type of
bounce message, and send a message asking this offender to please use
the correct address. If this offender happens to be your boss, gently
inform them that you have added this new address to the list of names
allowed to post to the list (for his/her convenience) but please
unsubscribe this address from listname-post if they ever unsubscribe
their other address from listname. Setting listname-post.config to
strip = no
you can then use comments to remind yourself of why the name is in
this file, or what subscribed account this address is related to.
You may even want to consider sending out a monthly reminder to the
list-post membership, explaining why they are on that list, and the
why, when, and how to get off of it. (similar to the bounces list)
Right now, you as the list-owner have the ability to blackhole the
messages rather than support people who can't remember where they
are subscribed from. Or you could be nice enough to forward it back
to the original address. Really just another form of list moderation.
When they complain about their messages not getting in, kindly ask
them what address they are posting from, as only subscribed addresses
are allow to post to the mailing list. Or, you could even decide on
a policy that "to post, one MUST be subscribed", which means no
special hastle on the list-owner part, and if someone wants to post
from an address that they did not subscribe from, the message gets
blackholed. Period.
Dan Liston
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:
|
|
