> [Jon Carnes replies] > > > Web over to the Admin pages and go to the Privacy Options page, field: > > "Alias names (regexps) which qualify as explicit to or cc destination > > names for this list." > > > > and put in the full name of list you are using. > > I don't *think* that's the right answer. It sounds like the problem is > that these automated emails don't have a "To" or "Cc" header at all, in > which case adding more addresses that are accepted as meaning "this > list" in To/Cc won't make a bit of difference. > > I think Matthew wants the option immediately before this one: "Must > posts have list named in destination (to, cc) field". Set it to "No". > > Don't do this on a public list, of course, as you'll get lots more spam > this way. You should probably restrict the list of allowed posters. > > Greg
[Jon Carnes replies again...] I agree that it sounds weird, but I'm not asking them to put in another username, I am asking them to put in a "Listname" that is equal to what they percieve their list to be named. This has worked quite well in the past. It seems that folks with multiple domain names for their server have a problem unless they use the default domain name with their lists. Adding the full list name (with the "@domain.com") solves the problem. It worked for two folks last week - both whom had identical sypmtoms as Matthew. Jon Carnes ------------------------------------------------------ Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users
