Re: [Mimedefang] ADMINISTRIVIA: Yahoo users may not post to this mailing list
David F. Skoll d...@roaringpenguin.com wrote: I regret to inform Yahoo users that they may no longer post to any mailing list hosted on lists.roaringpenguin.com. The madness has spread to AOL effective yesterday 4/22. host -t txt _dmarc.aol.com _dmarc.aol.com descriptive text v=DMARC1\; p=reject\; pct=100\; rua=mailto:d...@rua.agari.com\; ruf=mailto:d...@ruf.agari.com\;; Joseph Brennan Columbia University Information Technology ___ NOTE: If there is a disclaimer or other legal boilerplate in the above message, it is NULL AND VOID. You may ignore it. Visit http://www.mimedefang.org and http://www.roaringpenguin.com MIMEDefang mailing list MIMEDefang@lists.roaringpenguin.com http://lists.roaringpenguin.com/mailman/listinfo/mimedefang
Re: [Mimedefang] ADMINISTRIVIA: Yahoo users may not post to this mailing list
On Wed, Apr 23, 2014 at 9:32 AM, Joseph Brennan bren...@columbia.edu wrote: The madness has spread to AOL effective yesterday 4/22. host -t txt _dmarc.aol.com _dmarc.aol.com descriptive text v=DMARC1\; p=reject\; pct=100\; rua=mailto:d...@rua.agari.com\; ruf=mailto:d...@ruf.agari.com\;; So, is it time for mailing lists to rewrite the From: header? I've always preferred ones that supply a Reply-To: back to the list so people don't accidentally answer off-list anyway, but I know there are arguments on the other side. -- Les Mikesell lesmikes...@gmail.com ___ NOTE: If there is a disclaimer or other legal boilerplate in the above message, it is NULL AND VOID. You may ignore it. Visit http://www.mimedefang.org and http://www.roaringpenguin.com MIMEDefang mailing list MIMEDefang@lists.roaringpenguin.com http://lists.roaringpenguin.com/mailman/listinfo/mimedefang
Re: [Mimedefang] ADMINISTRIVIA: Yahoo users may not post to this mailing list
On 4/23/2014 10:32 AM, Joseph Brennan wrote: David F. Skoll d...@roaringpenguin.com wrote: I regret to inform Yahoo users that they may no longer post to any mailing list hosted on lists.roaringpenguin.com. The madness has spread to AOL effective yesterday 4/22. host -t txt _dmarc.aol.com _dmarc.aol.com descriptive text v=DMARC1\; p=reject\; pct=100\; rua=mailto:d...@rua.agari.com\; ruf=mailto:d...@ruf.agari.com\;; Thanks Joseph, As a side-note, the code framework I posted a week or so ago for Yahoo! has been working very well for our mailing lists. I'm going to work on generalizing my code and doing a DMARC check prior to posting for any domains. Some people might want to consider things like the new DMARC code in the latest mailman release candidate but I like fixing this with things like MD where it's more generic and customizable at the same time. Will share code when I'm done. Regards, KAM ___ NOTE: If there is a disclaimer or other legal boilerplate in the above message, it is NULL AND VOID. You may ignore it. Visit http://www.mimedefang.org and http://www.roaringpenguin.com MIMEDefang mailing list MIMEDefang@lists.roaringpenguin.com http://lists.roaringpenguin.com/mailman/listinfo/mimedefang
Re: [Mimedefang] ADMINISTRIVIA: Yahoo users may not post to this mailing list
Les wrote on 04/23/2014 11:01:22 AM: So, is it time for mailing lists to rewrite the From: header? I've always preferred ones that supply a Reply-To: back to the list so people don't accidentally answer off-list anyway, but I know there are arguments on the other side. That seems to be the consensus on the Listserv(TM) mailing lists. They are doing it selectively after doing a DNS Query and detecting the broken setting. See http://peach.ease.lsoft.com/scripts/wa-peach.exe?A2=ind1404L=LSTOWN-LF=S=P=61953 Confidentiality Notice: This electronic message and any attachments may contain confidential or privileged information, and is intended only for the individual or entity identified above as the addressee. If you are not the addressee (or the employee or agent responsible to deliver it to the addressee), or if this message has been addressed to you in error, you are hereby notified that you may not copy, forward, disclose or use any part of this message or any attachments. Please notify the sender immediately by return e-mail or telephone and delete this message from your system. ___ NOTE: If there is a disclaimer or other legal boilerplate in the above message, it is NULL AND VOID. You may ignore it. Visit http://www.mimedefang.org and http://www.roaringpenguin.com MIMEDefang mailing list MIMEDefang@lists.roaringpenguin.com http://lists.roaringpenguin.com/mailman/listinfo/mimedefang
Re: [Mimedefang] ADMINISTRIVIA: Yahoo users may not post to this mailing list
On Wed, Apr 23, 2014 at 10:26 AM, wbr...@e1b.org wrote: So, is it time for mailing lists to rewrite the From: header? I've always preferred ones that supply a Reply-To: back to the list so people don't accidentally answer off-list anyway, but I know there are arguments on the other side. That seems to be the consensus on the Listserv(TM) mailing lists. They are doing it selectively after doing a DNS Query and detecting the broken setting. See http://peach.ease.lsoft.com/scripts/wa-peach.exe?A2=ind1404L=LSTOWN-LF=S=P=61953 That's ummm, interesting, that you can't see their example format without a login. But it looks like they want to rewrite the Reply-To: as the original sender which seems very wrong, at least for technical lists where most posters would never want to request a private reply.And doing anything 'selectively' also seems wrong if you ever expect users to catch on to how a system works. -- Les Mikesell lesmikes...@gmail.com ___ NOTE: If there is a disclaimer or other legal boilerplate in the above message, it is NULL AND VOID. You may ignore it. Visit http://www.mimedefang.org and http://www.roaringpenguin.com MIMEDefang mailing list MIMEDefang@lists.roaringpenguin.com http://lists.roaringpenguin.com/mailman/listinfo/mimedefang
Re: [Mimedefang] ADMINISTRIVIA: Yahoo users may not post to this mailing list
Les wrote on 04/23/2014 12:29:40 PM: That's ummm, interesting, that you can't see their example format without a login. But it looks like they want to rewrite the Reply-To: as the original sender which seems very wrong, at least for technical lists where most posters would never want to request a private reply.And doing anything 'selectively' also seems wrong if you ever expect users to catch on to how a system works. Sorry about that login to unmask issue... Here is the full text of that post on the LISTSERV List Owner's Forum: ** This is posted from my yahoo.com account to illustrate L-Soft's solution to the From: address re-write issue. We think it is superior because it works as follows: -LISTSERV does a DNS lookup on the From: address to see if a re-write for DMARC Reject reasons is needed. We are already handling *@aol.com addresses automatically and immediately. -If From: address re-write is necessary, you can see the format: [token]-dmarc-requ...@listserv.xyz.com. The numerical [token] is unique to each LISTSERV instance. -Reply-To: field is populated with non-rewritten address so private reply-to-sender will actually go to sender as expected and not be accidentally posted to the list. -Return-Path: field is also populated with PROBE format non-rewritten address so that true bad-addresses bounces can be handled correctly. -List mail should still filter into the correct mail folder so users will not complain about 'lost' mail. This is a fix server admins can install and forget, and everything just works like before. No need for everyone to change their habits and their folder rules for incoming mail. No need for special configuration settings. No need to monitor the trade press for daily updates. ** The sender's Yahoo address was rewritten to be Ben Parker 0007fbf933af-dmarc-requ...@peach.ease.lsoft.com where peach.ease.lsoft.com is the list host. The reply-to field is only set on lists configured to reply to sender. It is not set on lists configured to reply to the list. I am on several technical lists (bind-users and dns-operations ) that reply by default to the sender. Yeah, the whole thing sucks. But unless we come up with a 1,000lb gorilla to take on the 800lb gorillas, we'll have to resort to this sort of guerrilla warfare. Confidentiality Notice: This electronic message and any attachments may contain confidential or privileged information, and is intended only for the individual or entity identified above as the addressee. If you are not the addressee (or the employee or agent responsible to deliver it to the addressee), or if this message has been addressed to you in error, you are hereby notified that you may not copy, forward, disclose or use any part of this message or any attachments. Please notify the sender immediately by return e-mail or telephone and delete this message from your system. ___ NOTE: If there is a disclaimer or other legal boilerplate in the above message, it is NULL AND VOID. You may ignore it. Visit http://www.mimedefang.org and http://www.roaringpenguin.com MIMEDefang mailing list MIMEDefang@lists.roaringpenguin.com http://lists.roaringpenguin.com/mailman/listinfo/mimedefang
[Mimedefang] ADMINISTRIVIA: Yahoo users may not post to this mailing list
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello, I regret to inform Yahoo users that they may no longer post to any mailing list hosted on lists.roaringpenguin.com. The reason is a recent policy change by Yahoo to their DMARC policy that makes third-party servers reject mailing list traffic as forged. See http://emailskinny.com/2014/04/07/yahoo-mail-brings-the-pain-with-dmarc-policy-change/ for a discussion. Yahoo users may continue to subscribe to our lists, but if they wish to post to this list, they should obtain a non-Yahoo email address to do so. Regards, David. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iD8DBQFTTUDHwYQuKhJvQuARAiWLAKCkIhHM2ckWrFrRCLDuOkG38ApGFwCcCvhL daTYmqB+PgjTWyJ+NukZJ4Q= =0cNu -END PGP SIGNATURE- ___ NOTE: If there is a disclaimer or other legal boilerplate in the above message, it is NULL AND VOID. You may ignore it. Visit http://www.mimedefang.org and http://www.roaringpenguin.com MIMEDefang mailing list MIMEDefang@lists.roaringpenguin.com http://lists.roaringpenguin.com/mailman/listinfo/mimedefang
