Nevermind. I wasn’t thinking.

 

Andrew

 

 

From: LISTSERV Site Administrators' Forum [mailto:[log in to unmask]] On Behalf Of Andrew Bosch
Sent: Friday, October 10, 2014 6:33 PM
To: [log in to unmask]
Subject: Re: local= / service= local

 

Can the Send keyword use the grouping notation like Send = (SendersList-L)? If so, you can set up a second list for managing who can send to the first list and managing that is just an add or delete.

 

Andrew

 

 

From: LISTSERV Site Administrators' Forum [mailto:[log in to unmask]] On Behalf Of F J Kelley
Sent: Friday, October 10, 2014 3:12 PM
To: [log in to unmask]
Subject: Re: local= / service= local

 

Thanks, this is an interesting idea.  In my case, the "Local= " settings are in a keywords file.  I copied the file, used the editor to change all instances of "Local= " to "Send= ".  The addresses were specified as

Send= *@*.university.edu,*@university.edu

 

and so on.  "Send= Public" was removed.  I did add a "Send= Private" on the off chance that there would be a post from someone on the actual list (a vendor, for example).  The list includes many of the higher ed sites and they (and only they) should be able to post.  It was not practical to keep up with email addresses across these as we have seen them change (sometimes substantially) over the years.

 

  


From: LISTSERV Site Administrators' Forum <[log in to unmask]> on behalf of Mangione, John <[log in to unmask]>
Sent: Friday, October 10, 2014 2:01 PM
To: [log in to unmask]
Subject: Re: local= / service= local

 

Actually, the “Service=” parameter is used for restricting/allowing senders to a list in the following way.

 

We want people from our entire e-mail domain to be able to send to the list, and not just the list subscribers. Furthermore, we DON’T want the public to be able to send to some of our lists, so those lists are configured like this:

 

Send=Service

Service=*My.Domain.name

 

You can have several “Send” and “Service” parameters, and that will work. So I could say:

 

Send=service,[log in to unmask]

Service=*My.domain.name,*my.domain.net

 

This would allow the people in those two domains to send, as well as John Doe.

 

What will NOT work in conjunction with anything else is “Send=Public”, as that obviates any more restrictive sending instructions.

 

One other “Send” parameter that I’ve found quite useful is the one that lets you configure a list to allow anybody who’s a member of one list to be able to be senders in another list. You simply indicate that it is another list by using parentheses:

 

Send=(SomeOtherList)

 

This says that any of the members of “SomeOtherList” can send to this list.

 

I hope this helps.

 

John Mangione

From: LISTSERV give-and-take forum [mailto:[log in to unmask]] On Behalf Of F J Kelley
Sent: Friday, October 10, 2014 12:53 PM
To: [log in to unmask]
Subject: Re: local= / service= local

 

Thanks Nathan,

--Joe

 


From: LISTSERV Site Administrators' Forum <[log in to unmask]> on behalf of Nathan Brindle <[log in to unmask]>
Sent: Friday, October 10, 2014 11:48 AM
To:
[log in to unmask]
Subject: Re: local= / service= local

 

Service= defines an area or areas outside which subscription requests are not accepted.  It has nothing to do with posting.

 

To restrict posting, I would be more likely to use something like

 

Send= *@*.university.edu, *@university.edu

Send= *@*.another.edu, *@another.edu

Send= *@*.last.edu, *@last.edu

 

That would restrict posting privileges to only addresses from those organizations.  Of course that doesn’t account for the possibility of a From: address being spoofed, so I’d probably also tack

 

Send= Confirm

 

at the end if I wanted to force confirmation before allowing the post.  It sort of depends on what kind of a list you’re talking about, I guess.

 

Nathan

 

From: LISTSERV Site Administrators' Forum [mailto:[log in to unmask]] On Behalf Of F J Kelley
Sent: Friday, October 10, 2014 11:38 AM
To:
[log in to unmask]
Subject: local= / service= local

 

We have a few lists whose configuration includes a block of "local= " stmts:

 

local= *.university.edu,university.edu

local= *.another.edu,another.edu

...

local= *.last.edu,last.edu

 

After this comes

 

Service= local

Confidential= Service

 

The list I am having problems with right now also uses

Send= Public

 

(it is a list used to notify a group about certain problem which might arise anywhere)

 

And they are getting spam.  Of course neither the "From: " nor the "Reply-To: " are in the local list.  Does "Local" simply control the visibility of the list or can it filter addresses?  On rereading the site managers manual, it would not seem to be able to do the latter.

--Joe

 

 


To unsubscribe from the LSTSRV-L list, click the following link:
http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1

 


To unsubscribe from the LSTSRV-L list, click the following link:
http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1

 


To unsubscribe from the LSTSRV-L list, click the following link:
http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1

 


To unsubscribe from the LSTSRV-L list, click the following link:
http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1

 


To unsubscribe from the LSTSRV-L list, click the following link:
http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1

 


To unsubscribe from the LSTSRV-L list, click the following link:
http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1



To unsubscribe from the LSTSRV-L list, click the following link:
http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1