LSTOWN-L Archives

LISTSERV List Owners' Forum

LSTOWN-L

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

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

Print Reply
"Gray, Nathan W - graynw" <[log in to unmask]>
Fri, 11 Apr 2014 14:47:53 +0000
text/plain (1 lines)
Ben

	While my list doesn’t have anyone from the domains listed, I do

appreciate the time you took to post this information. It is much

appreciated. 



Have a great weekend!





Nathan W. Gray

Systems Administrator

Campus Card Services

James Madison University

[log in to unmask]

540-568-2879

†











On 4/11/14, 10:42 AM, "Ben Parker" <[log in to unmask]> wrote:



>So what do we know about what is going on?  What magic LISTSERV settings

>do I

>need to work around this?  Should I turn off or change my auto-delete

>settings?  What can I as a list owner do?

>

>First, let's be clear on what is happening.

>

>A subscriber/list member from *@besteffort.com address (or other private

>domain) posts a message to your list.  It goes to all subscribers.  No

>problem

>for anyone.

>

>A subscriber/list member from *@yahoo.com posts a message (or a reply to

>the

>above message) to your list.  This will go to some subscribers, but will

>NOT

>go to subscribers/list members at yahoo.com or

>hotmail.com/live.com/msn.com/

>outlook.com, Comcast.net, Gmail.com and several other domains.  Messages

>to

>these domains will not only not be delivered but will be bounced/refused

>as if

>the recipients at those domains do not exist.  Thus, after a few such

>messages, your subscribers/list members at all of those problematic

>domains

>are at risk to be auto-deleted from your list(s).  This may amount to more

>than half of your total subscribers.

>

>

>What can you do about this?  Immediate solutions:

>

>For now, you must prevent subscribers/list members from *@yahoo.com

>addresses

>from posting any messages to your list.  They simply cannot participate in

>your list if they send from a *@yahoo.com address.  They can receive and

>read

>messages from other subscribers/list members and they can send from

>another

>address, if they have one.

>

> The LISTSERV command is:    QUIET SET listname NOPOST FOR *@yahoo.*

>

>Send a message to your list explaining the issue and what action members

>from

>*@yahoo.com addresses will need to take to continue to participate in the

>list.  (Basically, get a new email address.)

>

>

>ALTERNATIVE:  You can set all members from *@yahoo.com addresses to REVIEW

>status.  This means their messages will come to a moderator/editor of your

>list.  The moderator/editor can then forward/repost the message so that it

>comes from their own address, not from the *@yahoo.com address that

>originally

>posted the message.  This can be a lot of work and for some lists the

>traffic

>is simply too great for this to be a viable option.

>

> The LISTSERV command is:    QUIET SET listname REVIEW FOR *@yahoo.*

>

>

>----------------

>The simple answer is that for the moment, you cannot allow list members

>with

>*@yahoo.com addresses to post messages to your lists.

>

>

>1. Should we put a filter in place to preclude new yahoo accounts?

>

> LIst configuration setting:    Filter= also, *@yahoo.*

>

>Yes, this will prevent posted messages, and new subscribers from posting

>messages or joining your list.

>

>

>2. Are digests included in Yahoo's trap?

>

>No. Digests are formed by and sent from LISTSERV@... Even though there

>may be

>messages from *@yahoo.* within the Digest, the From: address is

>LISTSERV@...

>and this does not cause any problem.  But you need to set ALL subscribers

>to

>Digest:

>

>The LISTSERV command is:    QUIET SET listname DIGEST FOR *@*

>

>

>Longer term solutions:

>

>L-Soft is working on a change to LISTSERV that will basically re-write the

>From: *@yahoo.com addresses to something that does not cause the

>bounce/rejection problem.  This requires changes at the server level and

>is

>not accessible to subscribers or List Owners.  This is in testing now.

>One

>problem with this approach is that such re-written From: addresses will

>likely

>go into your "spam" folder where you may not see them.  Although this is

>problematic in itself, this is somewhat better than not allowing any

>messages

>from *@yahoo.com address at all.

>

>############################

>

>To unsubscribe from the LSTOWN-L list:

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

>or click the following link:

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





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



To unsubscribe from the LSTOWN-L list:

write to: mailto:[log in to unmask]

or click the following link:

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


ATOM RSS1 RSS2