LSTSRV-L Archives

LISTSERV Site Administrators' Forum

LSTSRV-L

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Topic: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
F J Kelley <[log in to unmask]>
Thu, 2 Apr 2015 22:35:30 +0000
text/plain (1 lines)
For an "announcements" list, you're right.  We don't worry about those.  However, for discussion lists, it is a different story.  They were subscribed as "abc1234" but are trying to post as "my.name".   And cannot for the very sensible reason  that "my.name" is not a subscriber.  I've been thinking that changing the Send= to "Public,Confirm,Non-Member" might provide a workaround to accommodate changing subscriber addresses, but that would add its own problems.  



I'm kind of coming to the opinion this cannot be solved with the listserver (although Liam's suggestion about LCMDX may play a part). 

--Joe

________________________________________

From: LISTSERV Site Administrators' Forum <[log in to unmask]> on behalf of k p <[log in to unmask]>

Sent: Thursday, April 02, 2015 5:08 PM

To: [log in to unmask]

Subject: Re: bulk operations "change"?



First, I wonder if all that is actually necessary, since you say the

original assigned address still works after student customization.

What's the point of updating the LISTSERV system every time the students

pick some new moniker for themselves (supposing that the

machine-readable class rolls are all populated prior to customizing, so

the faculty will always be subscribing the original ID)?



All you actually need, in LISTSERV, is something that will get the

messages to the student inbox - LISTSERV would not *have to* be updated

unless a customized address is subscribed and gets re-customized.  But

in between the time of re-customizing and the time your update runs,

there may be messages sent which the student will not receive.  So

perhaps it is more important to keep customized versions of the address

OUT of LISTSERV, rather than work hard on getting them into it.



But to address your question:

Place the collection of change commands inside an "ok begin/end" block

in the body of an email message, send that email from a Postmaster

address to LISTSERV, then respond to the confirmation request it generates.



The ok begin/end method is in section 15.7 of the manual here:

http://www.lsoft.com/manuals/15.5/htmlhelp/site%20managers/SecurityFeaturesandFunctions.17.1.html









On 4/2/2015 4:31 PM, F J Kelley wrote:

> ​Hi,

>

> Our mail system is MS Office 365. We assign incoming students an email

> address in the form

>

> [log in to unmask] <mailto:[log in to unmask]>

>

> The students may customize that address to something like

> [log in to unmask] <mailto:[log in to unmask]>

>

> (actually, they seem to test different versions of the address).

>

> All of this is fine. But. The Registrar's Office provides the original

> ID assigned (in an Exchange environment, both addresses are proxies for

> a real address; the students actually only "SendAs" whatever the

> customized address is -- in Exchange terms, the "PrimarySMTPAddress". If

> no customization, the originally assigned one is used), and faculty can

> typically use a machine-readable version of the class roll to add

> subscribers to their class discussion lists.

>

> I change the addresses as the students customize their addresses, but

> the Registrar's Office will continue to use the original ID. I have a

> powershell script to collect the Primary SMTP addresses for all list

> subscribers (collected one list at a time from the list report on the

> web). From that, I can build a file with all the "quiet change listname

> old-address new-address" in it. Our listsever is on a Linux box and I

> can paste the entire "change" file into pine and update all the

> addresses via CJLI. Using the web, I can see how to issue a single

> change at a time (List Management -> Command", but no way to process an

> entire file of these. Or have I missed something (very, very possible).

>

> Yes, this is really clunky, for now it is what we have ...

>

> --Joe



############################



To unsubscribe from the LSTSRV-L list:

write to: mailto:[log in to unmask]

or 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:

write to: mailto:[log in to unmask]

or click the following link:

http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1


ATOM RSS1 RSS2