Barry Finkel wrote: >On 01/12/11 19:08, Mark Sapiro wrote: >> >> You could do a few different things in your config_list input. One such >> would be >> >> if mlist.acceptable_aliases: >> mlist.acceptable_aliases += '\[email protected]' >> else: >> mlist.acceptable_aliases = '[email protected]' >> > > >I revised my script, and I ran some tests. On a list where I had not >previously specified an acceptable_aliases string, what was placed in >that item was > > \[email protected]
Are you certain the fourth line was as above without the '\n'. That code says if acceptable_aliases is not the null string, append '\[email protected]' to it, otherwise set it equal to '[email protected]' (without a '\n'). So I don't see how the result could be '\[email protected]' unless acceptable aliases initially contained white space and the result in fact was '<whitespace>\[email protected]' >Is the leading "\n" going to cause problems? No. It will just result in an additional alias which is empty or all white space and such aliases are ignored by the code that checks acceptable_aliases. >When I ran it again on the same list using a different e-mail address, >the resulting item had > > \[email protected]\[email protected] Which is exactly what's expected, i.e. the string '\[email protected]' was added to the end of the existing string. -- Mark Sapiro <[email protected]> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan ------------------------------------------------------ Mailman-Users mailing list [email protected] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
