I'm using MD 1.93 with perl 5.0001m and linux 1.2.13 (ELF) with slackware
3.0.0. we are seeing a problem with subscribers addresses being concidered
different when in fact they are all from the same domain, and the munge
domain is set.
userid@host1.domain.name subscribes as userid@domain.name.
sie then send a post from userid@host2.domain.name. as we understood
munge domain, it should have accepted this as being the same address
as userid@domain.name. we *are* using restricted post option with the
list pointing at the list:list-digest, (both can post to the regular list).
# mungedomain [bool] (no) <majordomo>
# If set to yes, a different method is used to determine a matching
# address. When set to yes, addresses of the form user@dom.ain.com
# are considered equivalent to addresses of the form user@ain.com.
# This allows a user to subscribe to a list using the domain address
# rather than the address assigned to a particular machine in the
# domain. This keyword affects the interpretation of addresses for
# subscribe, unsubscribe, and all private options.
mungedomain = yes
# restrict_post [restrict_post] (undef) <resend>
# If defined only address listed in one of the files (colon or space
# separated) can post to the mailing list. This is less useful than it
# seems it should be since there is no way to create these files if
# you do not have access to the machine running resend. This mechanism
# will be replaced in a future version of majordomo/resend.
restrict_post = /hda6/lists/sanctuary:/hda6/lists/sanctuary-digest
what are we doing wrong?
we got a non-member BOUNCE error at owner-sanctuary for a subscribed address
posting from the form userid@host.domain.name and subscribed as
userid@domain.name. this is what mungedomain is supposed to address.
*sigh*
Fuz
|
|
