>>>>> "BR" == Brock Rozen <brozen@torah.org> writes:
BR> Jason -- tell me, if I'm on a hidden list, how could I find out the
BR> exact address I'm zubscribed under?
echo "I need to find the exact address I\'m zubscribed as" | mail list-owner
Presumably the list owner has reasons for hiding the list and doesn't want
it exposed through trivial fudging of the which command. If you're
subscribed and address transforms and aliasing equate the address you're
posting as and the address you're zubscribed as, the show command will tell
you about it. See the aliasing/show example I sent a few days ago.
>> No matches are reported if more than M (list owner's choice; M=1 is
>> perfectly feasible) matches would result without password authorization.
BR> While M=1 might be valid, it might be one more than some people want,
BR> and M=0 means no restriction. Some other way of turning it off?
No, 0 is deny. (A zero return value from an access_check function is
always denial.) No way of turning it off, short of setting it to a large
value. I see no problem with this.
BR> How about only showing it in cases where a direct hit is scored? I'm
BR> subscribed as 'brozen@pop.torah.org' and I sent through a which on that
BR> exact address. A which on 'brozen@torah.org' should not show it.
There's no such thing as a direct hit; either the addresses compare
equivalently or they don't. Addresses that are equivalent through
transforms and aliasing are not somehow less equivalent because of this.
This is integral to the concepts of transformation and aliasing. To do
otherwise leads us back to the problems with mungedomain.
- J<
Follow-Ups:
References:
|
|
