I'm managing a majordomo list, but have access only to my list's config
file. I hope it's OK to ask a question here.
I have a bunch of long-term subscribers with addresses like
xxx@foo.bar.com whose ISPs no longer use the foo subdomain. I have set
restrict-post to the listname. When one of these subscribers tries
to post, his post bounces. When this happens I can solve the problem by
changing his address to xxx@bar.com . I was thinking that setting
mungedomain to "yes" would be a general and preventative solution, but
found when I did so that subscribers with addresses of the form xxx
then could not post (i.e., subscribers using the same ISP as my list).
So I immediately changed mungedomain back to "no". I've spent some
time on the phone with a majordomo support person at the ISP in
question, who is as puzzled as I am about this.
So a couple of questions:
1. Is my interpretation (really a guess) of mungedomain correct?
Will setting mungedomain = yes mean that a post from xxx@bar..com,
who is on the list as xxx@foo.bar.com, won't bounce? It seems to cover
only the reverse case form mine, but it does use the word "equivalent".
(I've quoted below from the config file.)
# 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 = no
2. With mungedomain = yes set, should posts from xxx@isp.com (but who
are on the list as xxx) bounce? (isp.com is the ISP the list is on.)
I'd appreciate any comments or suggestions, including ones that I can
pass on to the ISP majordomo support person.
Dick Moores rdm@netcom.com
Follow-Ups:
|
|
