You can still email them via listserv from your dartmouth.edu address unless Dartmouth has set its DMARC setting to =reject They just can't post to your lists without generating message failures from email systems that have a DMARC setting turned on. Yahoo is broadcasting to the internet that all our yahoo.com email addresses need to achieve a strict DMARC validation from us or we shouldn't accept delivery of the yahoo.com email. Then gmail.com receives the yahoo.com email and gmail has DMARC enabled and decides that as part of being a good internet partner it should honor the yahoo.com request to validate the yahoo.com email before accepting it. The yahoo.com email sent to any list no longer is from the yahoo.com account but is from the listserv address. Gmail tries to validate the yahoo.com address against the listserv server IP address and fails. The email bounces. It's the group of email systems that have enabled DMARC recently that are causing all the heartache. Not sure is this confuses the issue more but that is how I understand it. It really seems to be a lack of an RFC specification about email lists to me. From: LISTSERV List Owners' Forum [mailto:[log in to unmask]] On Behalf Of William Schults Sent: Friday, April 11, 2014 9:33 AM To: [log in to unmask] Subject: Re: What to do about your Yahoo.com subscribers? Ben: I'd be interested in your opinion about how this would work: I'm considering setting the affected subscribers to "NOMAIL" and notifying them (via a separate e-mail, since ListServ generated messages aren't getting through to them....). They would still be able to post, but would have to read posts via the website. Would this prevent the error monitoring, since no e-mail is being sent back to them? I'd rather not "silence" 25% or more of our subscribers, even temporarily. Also, do you have any estimate on the release date for the software fix that LSOFT is working on? Thanks for keeping LSTOWN up to date on what is happening. Bill Schults Co-list-owner, [log in to unmask]<mailto:[log in to unmask]> **************************************************************** To post messages, send e-mail to: [log in to unmask]<mailto:[log in to unmask]> Set your e-mail application to PLAIN TEXT ONLY to post messages. To contact the list owner: [log in to unmask]<mailto:[log in to unmask]> ---------------------------------------------------------------- Web based archives and subscription management are available at: http://listserv.dartmouth.edu/Archives/uv-birders.html -----Original Message----- From: LISTSERV List Owners' Forum [mailto:[log in to unmask]] On Behalf Of Ben Parker Sent: Friday, April 11, 2014 10:43 AM To: [log in to unmask]<mailto:[log in to unmask]> Subject: [LSTOWN-L] What to do about your Yahoo.com subscribers? 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<mailto:*@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<mailto:*@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<mailto:*@yahoo.com> addresses from posting any messages to your list. They simply cannot participate in your list if they send from a *@yahoo.com<mailto:*@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.*<mailto:*@yahoo.*> Send a message to your list explaining the issue and what action members from *@yahoo.com<mailto:*@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<mailto:*@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<mailto:*@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.*<mailto:*@yahoo.*> ---------------- The simple answer is that for the moment, you cannot allow list members with *@yahoo.com<mailto:*@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.*<mailto:*@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.*<mailto:*@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<mailto:*@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<mailto:*@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 IMPORTANT NOTICE REGARDING THIS ELECTRONIC MESSAGE: This message is intended for the use of the person to whom it is addressed and may contain information that is privileged, confidential, and protected from disclosure under applicable law. If you are not the intended recipient, your use of this message for any purpose is strictly prohibited. If you have received this communication in error, please delete the message and notify the sender so that we may correct our records. ________________________________ To unsubscribe from the LSTOWN-L list, 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