I'm implementing an umbrella list over three other lists.
When I send mail to the umbrella list, three events occur: (a) For each of the three lists, I (as owner) receive a request for approval with the message: Message has implicit destination (b) Duplicate receiving email addresses (on two or all three of the sublists) are not being eliminated. (c) I do NOT receive a request for approval from the umbrella list (yes!)
I would like for the approval to be automatic and I'd like for duplicate email addresses to be eliminated. I've probably missed the obvious, but I've invested several hours in troubleshooting ...
What I've done: (1) added the sender's email address to the privacy options / sender filter / non-member (even though the sender is a member and the sender's email moderate check-box is not checked). (2) done (1) above for each sublist and the umbrella list, although in the umbrella list, the sender is not a member. (3) added the <umbrellalistname>@listdomain.org as a sender not needing approval as in (1) above, but I didn't think I should have to do this, since it's not the original sender.
I've presumed that email addresses are not case sensitive, and routinely enter all addresses in lower case.
Solutions or next troubleshooting step suggestions are welcomed.
Thank you, Bruce (newbie to mailman, oldie to information technology, and embarrassed that I can't figure this out on my own)
Bruce E. Breeding wrote:
I'm implementing an umbrella list over three other lists.
When I send mail to the umbrella list, three events occur: (a) For each of the three lists, I (as owner) receive a request for approval with the message: Message has implicit destination
On Privacy options...->Recipient filters for each sub-list, add the posting address of the umbrella lis to acceptable_aliases or, if you prefer, set require_explicit_destination to No.
(b) Duplicate receiving email addresses (on two or all three of the sublists) are not being eliminated.
That is correct. The members nodups setting only stops sending a list post to the member if the member is an explicit addressee of the post. The original idea of nodups was to do more, but it wasn't implemented.
(c) I do NOT receive a request for approval from the umbrella list (yes!)
I would like for the approval to be automatic and I'd like for duplicate email addresses to be eliminated. I've probably missed the obvious, but I've invested several hours in troubleshooting ...
As indicated, you can do the former, but doing the latter requires code modification.
What I've done: (1) added the sender's email address to the privacy options / sender filter / non-member (even though the sender is a member and the sender's email moderate check-box is not checked).
Never checked if the sender is a member and not the hold reason. See comment under (a) above.
(2) done (1) above for each sublist and the umbrella list, although in the umbrella list, the sender is not a member.
This for the umbrella list is probably what allows the sender's post to pass through to the sub-lists.
(3) added the <umbrellalistname>@listdomain.org as a sender not needing approval as in (1) above, but I didn't think I should have to do this, since it's not the original sender.
Probably correct that you didn't need to do this.
Remark under (a) will fix (a).
(b) is the subject of Feature Request <http://sourceforge.net/tracker/index.php?func=detail&aid=230730&group_id=103&atid=350103>.
-- Mark Sapiro <msapiro@value.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Bruce's original question:
(a) For each of the three lists, I (as owner) receive a request for approval with the message: Message has implicit destination
Mark Sapiro's answer to question (a):
On Privacy options...->Recipient filters for each sub-list, add the posting address of the umbrella lis to acceptable_aliases or, if you prefer, set require_explicit_destination to No.
Thank you, Mark (and Stephen who gave the same answer). Yes, I did this [added the posting address for the umbrella list in the "recipient filter" under privacy options for each sub-list] and it worked.
-- Bruce
Greetings,
I'm still not clear on the umbrella list function. What I'm trying to do is have a number of sub-lists (different faculty status) to which email to the super-list (all-faculty comprising all of the sub-list names) will distribute. I'd like to allow all sub-list members to send to the super-list and, if possible, allow all domain addresses i.e. *@gse.upenn.edu to send to certain lists. Is this possible? I've tried using the following options without success.
On Privacy options...->Recipient filters for each sub-list, add the posting address of the umbrella lis to acceptable_aliases or, if you prefer, set require_explicit_destination to No.
--
Todd Seeleman, Systems Analyst Penn Graduate School of Education 3440 Market Street, Rm 477 email: seeleman@gse.upenn.edu Philadelphia, PA. 19104-3325 phone: 215-573-8378
This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email
On 11/10/06, Todd Seeleman <seeleman@gse.upenn.edu> wrote:
I'm still not clear on the umbrella list function. What I'm trying todo is have a number of sub-lists (different faculty status) to which email to the super-list (all-faculty comprising all of the sub-list names) will distribute. I'd like to allow all sub-list members to send to the super-list
There is a patch to facilitate this, which allows you to reference other lists' memberships in Privacy Options > Sender Filters > accept_these_nonmembers.
and, if possible, allow all domain addresses i.e. *@gse.upenn.edu to send to certain lists. Is this possible? I've tried using the following options without success. You want to add ^.*@gse\.upenn\.edu to accept_these_nonmembers, which should make it a regexp match.
As for the umbrella list configuration, not only do you need either acceptable_aliases or !require_explicit_destination, but the umbrella list address will also need to be in accept_these_nonmembers, or a member of the sub lists (but the latter, here, is almost certainly a bad idea. So, stick with accept_these_nonmembers.)
Hope this helps,
--
- Patrick Bogen
Bruce E. Breeding writes:
I'm implementing an umbrella list over three other lists.
When I send mail to the umbrella list, three events occur:
(a) For each of the three lists, I (as owner) receive a request for approval with the message: Message has implicit destination
Add "UMBRELLALISTNAME@listdomain.org" to acceptable_aliases in Privacy>Recipient Filters.
(b) Duplicate receiving email addresses (on two or all three of the sublists) are not being eliminated.
No way to win here, currently. Mailman could easily keep a database of delivered-msgid/subscriber/timestamp triples, but for large high-traffic lists this would be huge even with short expirations, and probably would impact performance severely (the database would need to be locked for every single delivery). More sophisticated algorithms specifically for umbrella lists could be designed, but that would require a centralized user database which Mailman doesn't have yet. (For the relatively rare "do this for all my lists" kind of user request, it just interates over all lists looking for the user in the list-specific databases.)
If you really want that badly and your lists are small, it would be easy to insert such a delivery database filter into the pipeline, plus a couple of lines of code in the actual delivery Handler to consult it. (I don't have one yet, not even a proof of concept. Sorry. But somebody should be able to pick up on the hint.)
(b) Duplicate receiving email addresses (on two or all three of the sublists) are not being eliminated.
No way to win here, currently.
Try this patch.
http://sourceforge.net/tracker/index.php?func=detail&aid=1347962&group_id=103&atid=300103
-- Tokio Kikuch, tkikuchi@is.kochi-u.ac.jp http://weather.is.kochi-u.ac.jp/
Greetings,
I've been happily converting text/aliases based lists to mailman (Tru64 Unix v5.1b, Apache Server version: Apache/2.0.54, Mailman version: 2.1.9) and everything has been working great. I have 150 lists with ~16,000 addresses distributed among them. Most of the lists are < 100 with a few > 2000. I find when I add another list things get goofy. I can get to a list's admin page fine but when I click on another link, even a documentation or logout link, I get a "web page not found" browser message. At this point I cannot even logout from the admin page. When I remove the additional list operation returns to normal. I've checked_perms, restarted apache & mailman, and searched the FAQ all with no luck. I seem to be on the boarder of some system limit. Any ideas?
--
Todd Seeleman, Systems Analyst Penn Graduate School of Education 3440 Market Street, Rm 477 email: seeleman@gse.upenn.edu Philadelphia, PA. 19104-3325 phone: 215-573-8378
This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email
participants (6)
-
Bruce E. Breeding -
Mark Sapiro -
Patrick Bogen -
stephen＠xemacs.org -
Todd Seeleman -
Tokio Kikuchi