North American Network Operators Group|
Date Prev | Date Next | Date Index | Thread Index | Author Index | Historical
Blogger.com posts still fails when posting to the NANOG list!
Hi, Apparently there is still some silly [f|s]oul who has to forward NANOG to blogger and blogger still doesn't handle multipart/signed and thus very nicely and totally anonymously reports that it fails. Thank you dear person who is forwarding his subscription to NANOG to his blogger account! This has been for over three months(*) now or something, clearly it is not annoying at all to the folks running the NANOG list and the person doing it clearly gets away with it. Could the blogger folks, who are seemingly uncontactable, please please please with sugar and strawbarries and whipcream on top include at least for what address this message is getting gatewayed for so that the subscription can be yanked from the NANOG list? Of course a full header trail would be even more useful. Google seems to say that this might be the one: http://www.gossamer-threads.com/lists/nanog/users/ Dear NANOG listadmins, is there anything pointing in that direction? Simple way to find out who is the culprit: spam everybody on the list with a subject of their email address and when it bounces from blogger.com check the subject in the message and then use some very huge LART tool to get rid of it. Greets, Jeroen </rant> * = http://www.merit.edu/mailinglist/mailarchives/old_archive/msg01712.html -- Return-Path: <email@example.com> X-Original-To: jeroen@purgatory Delivered-To: firstname.lastname@example.org Received: (qmail 23472 invoked from network); 23 Oct 2006 22:45:30 -0000 Received-SPF: neutral (gurgle.mediadesign.nl: 220.127.116.11 is neither permitted nor denied by domain of email@example.com) Received: from ftpout.blogger.com (HELO blogger.com) (18.104.22.168) by gurgle.mediadesign.nl (qpsmtpd/0.32) with ESMTP for firstname.lastname@example.org; Tue, 24 Oct 2006 00:45:29 +0200 Received: by blogger.com (Postfix, from userid 99) id B67D9B1C8A; Mon, 23 Oct 2006 15:52:03 -0700 (PDT) Received: from bla17.blogger.com (localhost [127.0.0.1]) by blogger.com (Postfix) with ESMTP id A0300B1C8E for <email@example.com>; Mon, 23 Oct 2006 15:52:03 -0700 (PDT) Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: Blogger post failed From: firstname.lastname@example.org To: email@example.com Message-Id: <20061023225203.A0300B1C8E@blogger.com> Date: Mon, 23 Oct 2006 15:52:03 -0700 (PDT) X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on bla17.blogger.com X-Spam-Status: No, score=-2.6 required=5.0 tests=ALL_TRUSTED,NO_REAL_NAME autolearn=failed version=3.0.2 X-Spam-Level: X-MD-Spam-Check-By: gurgle.mediadesign.nl X-MD-Spam-Status: No, hits=3.3 required=5.0 tests=AWL,DNS_FROM_RFC_POST,NO_REAL_NAME,SPF_NEUTRAL X-MD-Spam-Level: *** X-MD-Virus-Found: No Blogger does not accept multipart/signed files. Error code: 7.552C93 Original message: From: firstname.lastname@example.org Date: Mon, 23 Oct 2006 23:35:35 +0100 Subject: Re: Need help explaining in-addr.arpa to Limelight None