Great Circle Associates Majordomo-Users
(April 2000)
 

Indexed By Date: [Previous] [Next] Indexed By Thread: [Previous] [Next]

Subject: Re: restricting post by domain(Year 2000)
From: Dan Liston <dliston @ netscape . com>
Organization: iPlanet E-Commerce Solutions, A Sun Netscape Alliance
Date: Fri, 28 Apr 2000 02:10:01 -0500
To: NA NA <kkohml @ yahoo . com>
Cc: majordomo-users @ greatcircle . com
References: <20000426184217.22215.qmail@web4303.mail.yahoo.com>

You have quite a dilema.

Lets narrow this down to a single list out of 400 and
work from there.  All employees are subscribed?  Or just
allowed to post to, say... abc-list@a.com?

If you are saying any employee, subscribed or not, can
post to a list, it becomes even more difficult.

Have you considered putting procmail filtering in front of
your lists?  I have procmail delivery enabled in sendmail.cf.

aliases file clip;
test:   "|/usr/local/bin/procmail -f- /home/mj1945/filters/test"
owner-test:     postmaster,
test-000428:  :include:/home/mj1945/lists/test,
owner-test-outgoing:    owner-test

here is the entire procmail filter (modified to fit your need)
I am not great at this, so just consider it food for thought;

# check that the message is to: or cc: our list
:0fhw
* !^TO_test@(a|b|c)\.com
| formail -I  "X-ApprovalRequired: true"

# check that message is from within our domain
# not sure if you can anchor the EOL with $ sign
:0fhw
* !^From[ :] .*@(a|b|c)\.com$
| formail -I "X-ApprovalRequired: true"

# we passed all tests, send it to majordomo
:0
| /home/mj1945/wrapper resend -l test test-000428,nobody


Now, to make all this work, you need to add to taboo_headers
in majordomo.cf or in each individual (internal) list that
you use procmail with.

taboo_headers       <<  END
/X-ApprovalRequired: true/
END

This will create a BOUNCE message for either procmail test
that fails.  You could also use /dev/null instead of formail.

Dan Liston

NA NA wrote:
> 
> Hi folks,
> 
> Problem trying to solve:
> ########################################
> SPAM PREVENTION AND MAILING LIST PRIVACY
> restricting post by domain
> ########################################
> I work for Company A(a.com).  Company A bought out
> company B(b.com).  Company B had bought out Company
> C(c.com) earlier.
> So there are 3 domains still in usage in daily
> operations.  That is b.com is still using b.com in its
> domain and likewise for c.com.
> A mix of mailservers in use, POP, Notes and Exchange.
> a.com has one mailing list server, lists.a.com
> servicing both internal(staff only) and
> external(staff+customers) needs.
> I need to configure 400 out of 500 mailing lists on
> server lists.a.com to be usable only internally.  Only
> internal users can send to this lists.  Most are
> unmoderated.
> All internal lists have email addresses ending in
> a.com which includes the employees previously from
> b.com and c.com.
> But b.com and c.com users are still appearing as FROM
> their respective domains in the email message headers.
> See the dilemma here?
> In .config,
> I cannot restrict a list such that only subscribers
> can send mail to the list using "restrict-post =
> listname"
> Lists have been hidden from the "lists" command.
> "who" command is taken care of as appropriate.
> BUT I still cannot restrict in such a way that only
> posters from a.com, b.com and c.com can post to this
> lists.
> 
> Reseach about taboo_headers.  Anyone has experience
> with this potential saver? Is this to be used in
> list.config or majordomo.cf.  If majordomo.cf, I
> cannot use it as it applies to the external lists too.
> 
> Folks, kindly comment please with regard to how I can
> configure Majordomo to restrict posting by certain
> domains instead of subscribers email addresses
> 
> Quote by Jason L. Tibbitts III:
> "It might be nice to have something like, say,
> allowed_addresses which would be an array of regexps,
> like taboo_headers, at least one of which must match.
> If none of these matches, restrict_post is consulted.
> Hmmm."
> See it at
> http://www.hpc.uh.edu/majordomo-users/9607/msg00496.html
> 
> That would be very cool, looks like majordomo can be
> hacked that way to improve its usefulness.  Need to
> brush up on my perl skills. Has this feature been
> implemented in the general latest release?  Anyone? I
> cannot find anything about it from my reading.
> 
> Would love to hear other possible solutions from y'all
> about restricting post by domain rather than
> subscribers' email addresses(using restrict-post).
> 
> Merger Madness in the MIS!!!!!!!!
> 
> __________________________________________________
> Do You Yahoo!?
> Send online invitations with Yahoo! Invites.
> http://invites.yahoo.com

--
--  Dan Liston --------------------- dliston@netscape.com  --
--  Netscape Consultant ------------------ (605) 232-3170  --
--  iPlanet E-Commerce Solutions, A Sun Netscape Alliance  --


References:
Indexed By Date Previous: Re: patches for listname-(un)zubscribe address?
From: Dan Liston <dliston@netscape.com>
Next: Performance...
From: Norman Walsh <ndw@nwalsh.com>
Indexed By Thread Previous: restricting post by domain(Year 2000)
From: NA NA <kkohml@yahoo.com>
Next: Re: patches for listname-unzubscribe address?
From: Dan Liston <dliston@netscape.com>

Google
 
Search Internet Search www.greatcircle.com