From izak at upfrontsystems.co.za Mon Nov 1 14:42:07 2010 From: izak at upfrontsystems.co.za (Izak Burger) Date: Mon, 01 Nov 2010 15:42:07 +0200 Subject: [Tracker-discuss] Fwd: Abuse Message [AbuseID:025FD3:14]: AbuseAOL: Email Feedback Report for IP 88.198.142.26 Message-ID: <4CCEC3AF.6090607@upfrontsystems.co.za> Someone at AOL thinks a password reset message is spam. Any ideas on how this happened? -------- Original Message -------- Subject: Abuse Message [AbuseID:025FD3:14]: AbuseAOL: Email Feedback Report for IP 88.198.142.26 Date: Mon, 1 Nov 2010 14:32:08 +0100 From: abuse at hetzner.de Reply-To: abuse at hetzner.de Dear Mr Roche Compaan, We have received information about spam or abuse from scomp at aol.net. This is an information email only and doesn't require any further action on your part. It's your choice to investigate the complaint. We do not expect any response. Following hint should assist you to evaluate the submitted information from AOL. So you can determine which AOL email address has caused the complaint: In the complaint email from AOL you will find a message ID and a timestamp. These two information enables you to find the AOL mailbox in the mailserver logfiles which caused the complaint. Important note: When you reply to us, please leave the abuse ID [AbuseID:025FD3:14] unchanged in the subject line. Best Regards, Hetzner-Support Hetzner Online AG Stuttgarter Str. 1 91710 Gunzenhausen Tel: +49 [0] 9831 610061 Fax: +49 [0] 9831 61006-2 abuse at hetzner.de www.hetzner.de Register Court: Registergericht Ansbach, HRB 3204 Management Board: Dipl. Ing. (FH) Martin Hetzner Chairwoman of the Supervisory Board: Diana Rothhan ----- attachment ----- Return-path: Envelope-to: abuse at hetzner.de Delivery-date: Mon, 01 Nov 2010 14:31:10 +0100 Received: from [205.188.249.66] (helo=omr-d22.mx.aol.com) by lms.your-server.de with esmtp (Exim 4.69) (envelope-from ) id 1PCuTd-0002Ud-1k for abuse at hetzner.de; Mon, 01 Nov 2010 14:31:10 +0100 Received: from scmp-d07.mail.aol.com (scmp-d07.mail.aol.com [172.18.176.226]) by omr-d22.mx.aol.com (v117.7) with ESMTP id MAILOMRD226-7d694ccec110248; Mon, 01 Nov 2010 09:30:56 -0400 Received: from scomp at aol.net by scmp-d07.mail.aol.com; Mon, 01 Nov 2010 09:30:52 EDT To: abuse at hetzner.de From: scomp at aol.net Date: Mon, 01 Nov 2010 09:30:52 EDT Subject: Email Feedback Report for IP 88.198.142.26 MIME-Version: 1.0 Content-Type: multipart/report; report-type=feedback-report; boundary="boundary-1138-29572-2659438-23860" X-AOL-INRLY: bugs.python.org [88.198.142.26] scmp-d07 X-Loop: scomp X-AOL-IP: 172.18.176.226 Message-ID: <201011010930.7d694ccec110248 at omr-d22.mx.aol.com> X-Virus-Scanned: Clear (ClamAV 0.96/12194/Mon Nov 1 13:20:42 2010) X-Spam-Score: 0.1 (/) Delivered-To: he1-abuse at hetzner.de --boundary-1138-29572-2659438-23860 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit This is an email abuse report for an email message with the message-id of 20101101132845.56E68780BE at psf.upfronthosting.co.za received from IP address 88.198.142.26 on Mon, 1 Nov 2010 09:28:46 -0400 (EDT) For information, please review the top portion of the following page: http://postmaster.aol.com/tools/fbl.html For information about AOL E-mail guidelines, please see http://postmaster.aol.com/guidelines/ If you would like to cancel or change the configuration for your FBL please use the tool located at: http://postmaster.aol.com/waters/fbl_change_form.html --boundary-1138-29572-2659438-23860 Content-Disposition: inline Content-Type: message/feedback-report Feedback-Type: abuse User-Agent: AOL SComp Version: 0.1 Received-Date: Mon, 1 Nov 2010 09:28:46 -0400 (EDT) Source-IP: 88.198.142.26 Reported-Domain: bugs.python.org Redacted-Address: redacted Redacted-Address: redacted@ --boundary-1138-29572-2659438-23860 Content-Type: message/rfc822 Content-Disposition: inline Return-Path: Received: from mtain-di05.r1000.mx.aol.com (mtain-di05.r1000.mx.aol.com [172.29.64.9]) by air-mf09.mail.aol.com (v129.4) with ESMTP id MAILINMF092-8bfa4ccec08e3; Mon, 01 Nov 2010 09:28:46 -0400 Received: from psf.upfronthosting.co.za (bugs.python.org [88.198.142.26]) by mtain-di05.r1000.mx.aol.com (Internet Inbound) with ESMTP id 2BE4838000088 for ; Mon, 1 Nov 2010 09:28:46 -0400 (EDT) Received: from psf.upfronthosting.co.za (localhost [10.0.0.1]) by psf.upfronthosting.co.za (Postfix) with ESMTP id 56E68780BE for ; Mon, 1 Nov 2010 14:28:45 +0100 (CET) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Subject: Password reset for Roundup tracker To: redacted at writeme.com From: Roundup tracker Date: Mon, 01 Nov 2010 13:28:45 +0000 Precedence: bulk X-Roundup-Name: Roundup tracker X-Roundup-Loop: hello X-Roundup-Version: 1.4.10 Content-Transfer-Encoding: quoted-printable Message-Id: <20101101132845.56E68780BE at psf.upfronthosting.co.za> x-aol-global-disposition: S X-AOL-REROUTE: YES x-aol-sid: 3039ac1d40094ccec08d1b4a X-AOL-IP: 88.198.142.26 X-AOL-SPF: domain : issues.roundup-tracker.org SPF : none X-Mailer: Unknown (No Version) The password has been reset for username "Devian". Your password is now: usRoN1Sx --boundary-1138-29572-2659438-23860-- From stephen at xemacs.org Tue Nov 2 02:40:47 2010 From: stephen at xemacs.org (Stephen J. Turnbull) Date: Tue, 02 Nov 2010 10:40:47 +0900 Subject: [Tracker-discuss] Fwd: Abuse Message [AbuseID:025FD3:14]: AbuseAOL: Email Feedback Report for IP 88.198.142.26 In-Reply-To: <4CCEC3AF.6090607@upfrontsystems.co.za> References: <4CCEC3AF.6090607@upfrontsystems.co.za> Message-ID: <87iq0gjye8.fsf@uwakimon.sk.tsukuba.ac.jp> Izak Burger writes: > Someone at AOL thinks a password reset message is spam. Any ideas on how > this happened? This is very common with AOL. First (most likely in this case) AOL puts the SPAM button right next to the DELETE button, and AFAIK there's no feedback to the user making it inconvenient to miss. From the user's point of view, they both just make the message disappear. I suppose the confirmation message is a little bit different, but I don't read those messages from my MUAs. I don't suppose anyone reads them at AOL, either, unless they didn't want to delete the message. Second (probably not applicable to someone with a Python tracker account, though), that's the user base that AOL targets: ignorant and loving it. Many AOL users apparently think of any unwanted mail as spam, even if they requested it themselves and later changed their minds. Third, it could be a joe job: somebody who doesn't like the user signed them up for a bunch of mailing lists. I've also heard rumors of bots doing this to grab email addresses out of the list traffic, but that seems pretty perverse, even for a bot, when it's so easy to create a throwaway account that won't upset anybody somewhere and sign that up. From izak at upfrontsystems.co.za Tue Nov 2 08:29:52 2010 From: izak at upfrontsystems.co.za (Izak Burger) Date: Tue, 02 Nov 2010 09:29:52 +0200 Subject: [Tracker-discuss] Fwd: Abuse Message [AbuseID:025FD3:14]: AbuseAOL: Email Feedback Report for IP 88.198.142.26 In-Reply-To: <87iq0gjye8.fsf@uwakimon.sk.tsukuba.ac.jp> References: <4CCEC3AF.6090607@upfrontsystems.co.za> <87iq0gjye8.fsf@uwakimon.sk.tsukuba.ac.jp> Message-ID: <4CCFBDF0.7020107@upfrontsystems.co.za> On 02/11/2010 03:40, Stephen J. Turnbull wrote: > This is very common with AOL. First (most likely in this case) AOL That was my feeling too. Hetzner says its our choice to do something about it or not. I'm going to go with do nothing unless some kind of pattern or repeat shows up. regards, Izak From metatracker at psf.upfronthosting.co.za Tue Nov 2 17:18:24 2010 From: metatracker at psf.upfronthosting.co.za (Ezio Melotti) Date: Tue, 02 Nov 2010 16:18:24 +0000 Subject: [Tracker-discuss] [issue358] Deltas in summary report In-Reply-To: <1288554579.37.0.646958578756.issue358@psf.upfronthosting.co.za> Message-ID: <1288714704.3.0.807712016006.issue358@psf.upfronthosting.co.za> Ezio Melotti added the comment: This should be fixed now in r86121. ---------- status: testing -> resolved _______________________________________________________ PSF Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Tue Nov 2 17:40:37 2010 From: metatracker at psf.upfronthosting.co.za (R David Murray) Date: Tue, 02 Nov 2010 16:40:37 +0000 Subject: [Tracker-discuss] [issue120] Allow users to report msg/file instances as misclassified In-Reply-To: <87sl79vn7r.fsf@uterus.efod.se> Message-ID: <1288716037.4.0.169088032656.issue120@psf.upfronthosting.co.za> R David Murray added the comment: Reclassification requires elevated tracker privileges, for a good reason (can't have spambots reclassifying their own messages :) If triage people don't have access to this function that should probably be changed. At that point we could document that the way to request reclassification is to post a new message asking for the reclassification. Then a triage person can fix it. (The interface, by the way, is accessed from the 'view' of the message, if you have the appropriate privileges.) _______________________________________________________ PSF Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Tue Nov 2 18:00:37 2010 From: metatracker at psf.upfronthosting.co.za (R David Murray) Date: Tue, 02 Nov 2010 17:00:37 +0000 Subject: [Tracker-discuss] [issue354] Sort List Doesn't Work In-Reply-To: <1284679226.41.0.993855464132.issue354@psf.upfronthosting.co.za> Message-ID: <1288717237.5.0.951323910229.issue354@psf.upfronthosting.co.za> R David Murray added the comment: Works fine for me. And I disagree, I think the default sort by activity is the best choice, and I think the placement at the bottom of the screen is good because putting them at the top would be a waste of prime screen real estate. ---------- nosy: +r.david.murray status: unread -> resolved _______________________________________________________ PSF Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Wed Nov 3 00:47:03 2010 From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?=C3=89ric_Araujo?=) Date: Tue, 02 Nov 2010 23:47:03 +0000 Subject: [Tracker-discuss] [issue120] Allow users to report msg/file instances as misclassified In-Reply-To: <87sl79vn7r.fsf@uterus.efod.se> Message-ID: <1288741623.68.0.985242456388.issue120@psf.upfronthosting.co.za> ?ric Araujo added the comment: > Reclassification requires elevated tracker privileges, for a good reason Right. Is there a list of users with admin rights somewhere? > If triage people don't have access to this function that should probably be > changed. [...] (The interface, by the way, is accessed from the 'view' of the > message, if you have the appropriate privileges I can?t test right now, I don?t remember the id of my message that was classified as spam. Will test as soon as possible. _______________________________________________________ PSF Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Wed Nov 3 09:56:43 2010 From: metatracker at psf.upfronthosting.co.za (anatoly techtonik) Date: Wed, 03 Nov 2010 08:56:43 +0000 Subject: [Tracker-discuss] [issue357] Bootstrapping class not in Py.BOOTSTRAP_TYPES In-Reply-To: <1288536792.61.0.21495685169.issue357@psf.upfronthosting.co.za> Message-ID: <1288774603.68.0.771143192859.issue357@psf.upfronthosting.co.za> anatoly techtonik added the comment: Sergei, where did you get that link? http://bugs.jython.org/Project/bugs.html ---------- nosy: +techtonik status: resolved -> chatting _______________________________________________________ PSF Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Wed Nov 3 13:25:10 2010 From: metatracker at psf.upfronthosting.co.za (Sergei) Date: Wed, 03 Nov 2010 12:25:10 +0000 Subject: [Tracker-discuss] [issue357] Bootstrapping class not in Py.BOOTSTRAP_TYPES In-Reply-To: <1288774603.68.0.771143192859.issue357@psf.upfronthosting.co.za> Message-ID: <4CD154A1.7060908@mail.ru> Sergei added the comment: Hi, Anatoly It's on the main page: http://bugs.jython.org/ (see on the left, "Community" and below "Reporting Bugs ") cheers On 11/03/2010 03:56 AM, anatoly techtonik wrote: > anatoly techtonik added the comment: > > Sergei, where did you get that link? http://bugs.jython.org/Project/bugs.html > > ---------- > nosy: +techtonik > status: resolved -> chatting > > _______________________________________________________ > PSF Meta Tracker > > _______________________________________________________ > > . > _______________________________________________________ PSF Meta Tracker _______________________________________________________ -------------- next part -------------- An HTML attachment was scrubbed... URL: From metatracker at psf.upfronthosting.co.za Wed Nov 3 14:20:29 2010 From: metatracker at psf.upfronthosting.co.za (anatoly techtonik) Date: Wed, 03 Nov 2010 13:20:29 +0000 Subject: [Tracker-discuss] [issue359] Broken links in sidepane of Jython tracker In-Reply-To: <1288790429.8.0.0376148595482.issue359@psf.upfronthosting.co.za> Message-ID: <1288790429.8.0.0376148595482.issue359@psf.upfronthosting.co.za> New submission from anatoly techtonik : See http://bugs.jython.org/ sidepane. Reporting bugs, Contributors and other links are broken. They look like http://bugs.jython.org/Project/bugs.html ---------- messages: 1852 nosy: techtonik priority: bug status: unread title: Broken links in sidepane of Jython tracker topic: jython _______________________________________________________ PSF Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Wed Nov 3 14:21:35 2010 From: metatracker at psf.upfronthosting.co.za (anatoly techtonik) Date: Wed, 03 Nov 2010 13:21:35 +0000 Subject: [Tracker-discuss] [issue357] Bootstrapping class not in Py.BOOTSTRAP_TYPES In-Reply-To: <1288536792.61.0.21495685169.issue357@psf.upfronthosting.co.za> Message-ID: <1288790495.43.0.951557193109.issue357@psf.upfronthosting.co.za> anatoly techtonik added the comment: Opened an issue about this at http://psf.upfronthosting.co.za/roundup/meta/issue359 ---------- superseder: +Broken links in sidepane of Jython tracker _______________________________________________________ PSF Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Wed Nov 3 15:16:49 2010 From: metatracker at psf.upfronthosting.co.za (Ezio Melotti) Date: Wed, 03 Nov 2010 14:16:49 +0000 Subject: [Tracker-discuss] [issue359] Broken links in sidepane of Jython tracker In-Reply-To: <1288790429.8.0.0376148595482.issue359@psf.upfronthosting.co.za> Message-ID: <1288793809.74.0.169898191632.issue359@psf.upfronthosting.co.za> Ezio Melotti added the comment: The attached patch fixes the menu to match the one on jython.org. The patch is untested but quite straightforward. I'll wait for an OK by some Jython developer before applying. ---------- assignedto: -> ezio.melotti nosy: +ezio.melotti status: unread -> in-progress _______________________________________________________ PSF Meta Tracker _______________________________________________________ -------------- next part -------------- Index: page.html =================================================================== --- page.html (revision 85128) +++ page.html (working copy) @@ -67,33 +67,29 @@