Re: [Mailman-Users] Problem with 2.1.9 acceptable_aliases
Barry Finkel wrote: Barry Finkel wrote: There was a posting to a number of lists here yesterday To: [EMAIL PROTECTED] all of the lists are linked; some of the lists are subscribed to others. I took that address and added it to acceptable_aliases And Mark Sapiro replied: What did you add to acceptable_aliases? And for which list(s)? A post addressed to [EMAIL PROTECTED] will presumably be delivered to the comp_info list. In order for it not to be held by that list, you need either [EMAIL PROTECTED] As you discovered, the above is wrong. All entries in acceptable_aliases are interpreted as regexps, thus any regexp special characters must be escaped as you indicate below. I have not looked at the code, and I am not an expert in regular expressions. I surmise that Mailman is treating the address as a regular expression, which matches ab at anl.gov aab at anl.gov aaab at anl.gov b at anl.gov ... but does not match a+b at anl.gov I then changed the acceptable_aliases to a\+b at anl.gov and test mail was distributed. -- Mark Sapiro [EMAIL PROTECTED]The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Problem with 2.1.9 acceptable_aliases
Barry Finkel wrote: There was a posting to a number of lists here yesterday To: [EMAIL PROTECTED] all of the lists are linked; some of the lists are subscribed to others. I took that address and added it to acceptable_aliases And Mark Sapiro replied: What did you add to acceptable_aliases? And for which list(s)? A post addressed to [EMAIL PROTECTED] will presumably be delivered to the comp_info list. In order for it not to be held by that list, you need either [EMAIL PROTECTED] or a regexp like ^comp_info([EMAIL PROTECTED])[EMAIL PROTECTED] in the acceptable_aliases of the comp_info list. Then if other lists are members of the comp_info list, you need the same thing in acceptabale_aliases of those other lists to prevent the post from being held there. and I replied: For each of the five lists for which there was a posting held for moderation I entered [EMAIL PROTECTED] in the acceptable_aliases box on the admin web page via cut-and-paste. The mailling list that, I assume, is part of the distribution list for this comp_info_cats+noc list is [EMAIL PROTECTED] That address is an accceptable_alias for the Mailman list [EMAIL PROTECTED] and to that list is subscribed [EMAIL PROTECTED] [EMAIL PROTECTED] In addition [EMAIL PROTECTED] is an accceptable_alias for the Mailman list [EMAIL PROTECTED] and to that itad list is subscribed three other Mailman lists: [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] For each of these six lists (out, itad, opstr, ad, cs, us) I had added [EMAIL PROTECTED] to accceptable_aliases. The only thing strange about the string I added to acceptable_aliases is the two + characters. I did not know if the plus characters were causing problems. I ran another test: 1) I set up an e-mail alias [EMAIL PROTECTED] that points to an existing test list on my test Mailman 2.1.9 system. 2) Via that test list admin web page, I added [EMAIL PROTECTED] to the acceptable_aliases list. This address is the only entry in the list. 3) I sent test mail to [EMAIL PROTECTED] and the mail was sent to the moderator (i.e., me) due to implicit destination I have not looked at the code, and I am not an expert in regular expressions. I surmise that Mailman is treating the address as a regular expression, which matches [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] ... but does not match [EMAIL PROTECTED] I then changed the acceptable_aliases to [EMAIL PROTECTED] and test mail was distributed. -- Barry S. Finkel Computing and Information Systems Division Argonne National Laboratory Phone:+1 (630) 252-7277 9700 South Cass Avenue Facsimile:+1 (630) 252-4601 Building 222, Room D209 Internet: [EMAIL PROTECTED] Argonne, IL 60439-4828 IBMMAIL: I1004994 -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Problem with 2.1.9 acceptable_aliases
Barry Finkel wrote: There was a posting to a number of lists here yesterday To: [EMAIL PROTECTED] all of the lists are linked; some of the lists are subscribed to others. I took that address and added it to acceptable_aliases What did you add to acceptable_aliases? And for which list(s)? A post addressed to [EMAIL PROTECTED] will presumably be delivered to the comp_info list. In order for it not to be held by that list, you need either [EMAIL PROTECTED] or a regexp like ^comp_info([EMAIL PROTECTED])[EMAIL PROTECTED] in the acceptable_aliases of the comp_info list. Then if other lists are members of the comp_info list, you need the same thing in acceptabale_aliases of those other lists to prevent the post from being held there. -- Mark Sapiro [EMAIL PROTECTED]The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Problem with 2.1.9 acceptable_aliases
Barry Finkel wrote: There was a posting to a number of lists here yesterday To: [EMAIL PROTECTED] all of the lists are linked; some of the lists are subscribed to others. I took that address and added it to acceptable_aliases And Mark Sapiro replied: What did you add to acceptable_aliases? And for which list(s)? A post addressed to [EMAIL PROTECTED] will presumably be delivered to the comp_info list. In order for it not to be held by that list, you need either [EMAIL PROTECTED] or a regexp like ^comp_info([EMAIL PROTECTED])[EMAIL PROTECTED] in the acceptable_aliases of the comp_info list. Then if other lists are members of the comp_info list, you need the same thing in acceptabale_aliases of those other lists to prevent the post from being held there. For each of the five lists for which there was a posting held for moderation I entered [EMAIL PROTECTED] in the acceptable_aliases box on the admin web page via cut-and-paste. The mailling list that, I assume, is part of the distribution list for this comp_info_cats+noc list is [EMAIL PROTECTED] That address is an accceptable_alias for the Mailman list [EMAIL PROTECTED] and to that list is subscribed [EMAIL PROTECTED] [EMAIL PROTECTED] In addition [EMAIL PROTECTED] is an accceptable_alias for the Mailman list [EMAIL PROTECTED] and to that itad list is subscribed three other Mailman lists: [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] For each of these six lists (out, itad, opstr, ad, cs, us) I had added [EMAIL PROTECTED] to accceptable_aliases. The only thing strange about the string I added to acceptable_aliases is the two + characters. I did not know if the plus characters were causing problems. -- Barry S. Finkel Computing and Information Systems Division Argonne National Laboratory Phone:+1 (630) 252-7277 9700 South Cass Avenue Facsimile:+1 (630) 252-4601 Building 222, Room D209 Internet: [EMAIL PROTECTED] Argonne, IL 60439-4828 IBMMAIL: I1004994 -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
