From roundup-admin at psf.upfronthosting.co.za  Fri Apr  4 16:20:37 2014
From: roundup-admin at psf.upfronthosting.co.za (Python tracker)
Date: Fri, 04 Apr 2014 14:20:37 +0000
Subject: [Tracker-discuss] Failed issue tracker submission
Message-ID: <20140404142037.534C156A1A@psf.upfronthosting.co.za>



The node specified by the designator in the subject of your message
("2107") does not exist.

Subject was: "[issue2107]"



Mail Gateway Help
=================
Incoming messages are examined for multiple parts:
 . In a multipart/mixed message or part, each subpart is extracted and
   examined. The text/plain subparts are assembled to form the textual
   body of the message, to be stored in the file associated with a "msg"
   class node. Any parts of other types are each stored in separate files
   and given "file" class nodes that are linked to the "msg" node.
 . In a multipart/alternative message or part, we look for a text/plain
   subpart and ignore the other parts.
 . A message/rfc822 is treated similar tomultipart/mixed (except for
   special handling of the first text part) if unpack_rfc822 is set in
   the mailgw config section.

Summary
-------
The "summary" property on message nodes is taken from the first non-quoting
section in the message body. The message body is divided into sections by
blank lines. Sections where the second and all subsequent lines begin with
a ">" or "|" character are considered "quoting sections". The first line of
the first non-quoting section becomes the summary of the message.

Addresses
---------
All of the addresses in the To: and Cc: headers of the incoming message are
looked up among the user nodes, and the corresponding users are placed in
the "recipients" property on the new "msg" node. The address in the From:
header similarly determines the "author" property of the new "msg"
node. The default handling for addresses that don't have corresponding
users is to create new users with no passwords and a username equal to the
address. (The web interface does not permit logins for users with no
passwords.) If we prefer to reject mail from outside sources, we can simply
register an auditor on the "user" class that prevents the creation of user
nodes with no passwords.

Actions
-------
The subject line of the incoming message is examined to determine whether
the message is an attempt to create a new item or to discuss an existing
item. A designator enclosed in square brackets is sought as the first thing
on the subject line (after skipping any "Fwd:" or "Re:" prefixes).

If an item designator (class name and id number) is found there, the newly
created "msg" node is added to the "messages" property for that item, and
any new "file" nodes are added to the "files" property for the item.

If just an item class name is found there, we attempt to create a new item
of that class with its "messages" property initialized to contain the new
"msg" node and its "files" property initialized to contain any new "file"
nodes.

Triggers
--------
Both cases may trigger detectors (in the first case we are calling the
set() method to add the message to the item's spool; in the second case we
are calling the create() method to create a new node). If an auditor raises
an exception, the original message is bounced back to the sender with the
explanatory message given in the exception.
-------------- next part --------------
Return-Path: <tracker-discuss at python.org>
X-Original-To: report at bugs.python.org
Delivered-To: roundup+tracker at psf.upfronthosting.co.za
Received: from mail.python.org (mail.python.org [82.94.164.166])
	by psf.upfronthosting.co.za (Postfix) with ESMTPS id 077F7568BE
	for <report at bugs.python.org>; Fri,  4 Apr 2014 16:20:37 +0200 (CEST)
Received: from albatross.python.org (localhost [127.0.0.1])
	by mail.python.org (Postfix) with ESMTP id 3g0jwh4xVqz7Lkk
	for <report at bugs.python.org>; Fri,  4 Apr 2014 16:20:36 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=python.org; s=200901;
	t=1396621236; bh=RTsCQxzD6xGLgz/op44uDomO9m3XB5rHQ4aHab0n6XA=;
	h=From:To:Subject:Date:From;
	b=Iu80BHHquLhoAYJCP2WRO54M02qeHwqjbNHM7TMtVTI+nyeaSZhpCRNJhGXlnYd6/
	 wgYvI/jKjdVQzaw3/MwrZ9eW3pWXbpbEKaxrmmb5JKf8viKYP7e32jfM4leS/9KpWO
	 KanMUO4Xvc0KGn45e9VZWFuVd1iyWVE0PsquSPRo=
Received: from localhost (HELO mail.python.org) (127.0.0.1)
  by albatross.python.org with SMTP; 04 Apr 2014 16:20:36 +0200
Received: from virt-7yvsjn.psf.osuosl.org (unknown [140.211.10.72])
	by mail.python.org (Postfix) with ESMTP
	for <report at bugs.python.org>; Fri,  4 Apr 2014 16:20:36 +0200 (CEST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
From: tracker-discuss at python.org
To: report at bugs.python.org
Subject: [issue2107]
Message-Id: <3g0jwh4xVqz7Lkk at mail.python.org>
Date: Fri,  4 Apr 2014 16:20:36 +0200 (CEST)

TmV3IGNoYW5nZXNldCBjNmU2M2JiMTMyZmIgYnkgQnJldHQgQ2Fubm9uIGluIGJyYW5jaCAnZGVm
YXVsdCc6Cm1lcmdlIGFsb25nIHcvIGZpeCBmb3IgaXNzdWUgIzIxMDcgKGNvbW1pdCBjOTIzOTE3
MWU0MjkpCmh0dHA6Ly9oZy5weXRob24ub3JnL2NweXRob24vcmV2L2M2ZTYzYmIxMzJmYgo=

From metatracker at psf.upfronthosting.co.za  Mon Apr 14 16:58:51 2014
From: metatracker at psf.upfronthosting.co.za (Michael Foord)
Date: Mon, 14 Apr 2014 14:58:51 +0000
Subject: [Tracker-discuss] [issue539] Link to tracker discuss mailing list
Message-ID: <1397487531.85.0.0953554719467.issue539@psf.upfronthosting.co.za>


New submission from Michael Foord:

Please add a link to the tracker discuss mailing list on bugs.python.org

http://mail.python.org/mailman/listinfo/tracker-discuss

----------
messages: 2850
nosy: mfoord
priority: wish
status: unread
title: Link to tracker discuss mailing list

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue539>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Tue Apr 15 01:13:50 2014
From: metatracker at psf.upfronthosting.co.za (Ezio Melotti)
Date: Mon, 14 Apr 2014 23:13:50 +0000
Subject: [Tracker-discuss] [issue539] Link to tracker discuss mailing list
In-Reply-To: <1397487531.85.0.0953554719467.issue539@psf.upfronthosting.co.za>
Message-ID: <1397517230.1.0.384133000599.issue539@psf.upfronthosting.co.za>


Ezio Melotti added the comment:

Why do you think this would be useful?
There's already a link to the meta-tracker, and indeed adding a link to tracker-discuss somewhere here might be ok.

----------
nosy: +ezio.melotti
status: unread -> chatting

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue539>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Tue Apr 15 16:33:02 2014
From: metatracker at psf.upfronthosting.co.za (Chris Rose)
Date: Tue, 15 Apr 2014 14:33:02 +0000
Subject: [Tracker-discuss] [issue540] Rietveld service is running with
	DEBUG=True
Message-ID: <1397572382.53.0.538532827064.issue540@psf.upfronthosting.co.za>


New submission from Chris Rose:

When Rietveld (http://bugs.python.org/review) issues an exception, it pops up the Django debug traceback viewer, which may leak sensitive information, and in any case cannot be a safe thing to do.

----------
messages: 2852
nosy: offby1
priority: urgent
status: unread
title: Rietveld service is running with DEBUG=True

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue540>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Tue Apr 15 17:41:51 2014
From: metatracker at psf.upfronthosting.co.za (Michael Foord)
Date: Tue, 15 Apr 2014 15:41:51 +0000
Subject: [Tracker-discuss] [issue539] Link to tracker discuss mailing list
In-Reply-To: <1397487531.85.0.0953554719467.issue539@psf.upfronthosting.co.za>
Message-ID: <1397576511.5.0.414042484937.issue539@psf.upfronthosting.co.za>


Michael Foord added the comment:

We get a lot of enquiries to webmaster at python.org about tracker problems. When the problems are about being unable to create an account I *can't* just send people to the metatracker as they won't be able to sign up to that either.

I didn't know the discuss list existed, so I think a link to it from the tracker would be useful.

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue539>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Tue Apr 15 22:31:13 2014
From: metatracker at psf.upfronthosting.co.za (Ezio Melotti)
Date: Tue, 15 Apr 2014 20:31:13 +0000
Subject: [Tracker-discuss] [issue539] Link to tracker discuss mailing list
In-Reply-To: <1397487531.85.0.0953554719467.issue539@psf.upfronthosting.co.za>
Message-ID: <1397593873.38.0.236396747727.issue539@psf.upfronthosting.co.za>


Ezio Melotti added the comment:

I wonder how they find webmaster at python.org.  On bugs.python.org there's a "Report tracker problem" link, so if they are having problems they should follow that link and either report the metaissue or, if we add a link to tracker-discuss here, report the issue to tracker-discuss.  If they failed to notice the "report a tracker problem" in the first place, I'm not sure adding another link will make a difference.

In short:
+0.5 about adding the link to the meta tracker;
-0 about adding it to bugs.python.org;

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue539>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Tue Apr 15 22:42:42 2014
From: metatracker at psf.upfronthosting.co.za (Michael Foord)
Date: Tue, 15 Apr 2014 20:42:42 +0000
Subject: [Tracker-discuss] [issue539] Link to tracker discuss mailing list
In-Reply-To: <1397487531.85.0.0953554719467.issue539@psf.upfronthosting.co.za>
Message-ID: <1397594562.44.0.161237414222.issue539@psf.upfronthosting.co.za>


Michael Foord added the comment:

People routinely email webmaster with every problem you can imagine. Tracker and PyPI issues form a substantial proportion of these issues despite both sub-sites having their own "report problems" link. A discoverable *email* solution might help a bit. It would have helped me :-) 

Adding it to the meta tracker would be next to useless, if their problem is a failure to register to the tracker then another tracker is likely to be no help. It's also not where I would have looked.

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue539>
_______________________________________________________

From rdmurray at bitdance.com  Wed Apr 16 23:02:11 2014
From: rdmurray at bitdance.com (R. David Murray)
Date: Wed, 16 Apr 2014 17:02:11 -0400
Subject: [Tracker-discuss] New mailing list for workflow/workflow
	infrastructure discussion/tasks
Message-ID: <20140416210212.48849250D09@webabinitio.net>

In case you missed it on the other lists I posted it to, we're planning
on having discussions about our roundup/rietveld setup and how to improve
it on the new core-workflow mailing list:

   https://mail.python.org/mailman/listinfo/core-workflow 

I'm certainly hoping that we will get more people interested in
contributing patches out of this, and there are early indications that
we will.

--David

From metatracker at psf.upfronthosting.co.za  Fri Apr 18 00:02:07 2014
From: metatracker at psf.upfronthosting.co.za (Ezio Melotti)
Date: Thu, 17 Apr 2014 22:02:07 +0000
Subject: [Tracker-discuss] [issue538] html-escaped link in message update
	collision message
In-Reply-To: <1396285537.51.0.358129889954.issue538@psf.upfronthosting.co.za>
Message-ID: <1397772127.82.0.562206252772.issue538@psf.upfronthosting.co.za>


Ezio Melotti added the comment:

I did that and everything seems to work fine.
I also reverted on all the trackers the previous fix that was avoiding the XSS by changing the templates, and checked that the XSS still fails.

----------
assignedto:  -> ezio.melotti
nosy: +ezio.melotti
status: chatting -> resolved

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue538>
_______________________________________________________

From techtonik at gmail.com  Mon Apr 21 16:47:59 2014
From: techtonik at gmail.com (anatoly techtonik)
Date: Mon, 21 Apr 2014 17:47:59 +0300
Subject: [Tracker-discuss] [issue527] HTTPS / SSL / Secure access
In-Reply-To: <1395565938.06.0.79268254731.issue527@psf.upfronthosting.co.za>
References: <1380348162.36.0.964046648568.issue527@psf.upfronthosting.co.za>
 <1395565938.06.0.79268254731.issue527@psf.upfronthosting.co.za>
Message-ID: <CAPkN8xLJXYjRn5exR29Z7DeCV3od7GyobSiSxAuFWqFzkyERQg@mail.gmail.com>

Martin, your trust in CACcrt doesn't make it secure. Ubuntu and Debian removed
it from distribution - see https://lwn.net/Articles/590879/ and
https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1258286

Please, reopen this bug and consider that Windows and Chrome users never had
this one installed.

On Sun, Mar 23, 2014 at 12:12 PM, Martin v. L?wis
<metatracker at psf.upfronthosting.co.za> wrote:
>
> Martin v. L?wis added the comment:
>
> Yes, it can be closed
>
> ----------
> status: chatting -> resolved


-- 
anatoly t.

From techtonik at gmail.com  Mon Apr 21 16:56:13 2014
From: techtonik at gmail.com (anatoly techtonik)
Date: Mon, 21 Apr 2014 17:56:13 +0300
Subject: [Tracker-discuss] Pseudo protection of b.p.o from MITM
Message-ID: <CAPkN8xKKzyh=SO7zagonpCWNDUGhY5qf+_KwEZdCynUSP5A4Tg@mail.gmail.com>

I am banned from trackers, so I can not add issues
that surround pydotorg infrastructure anymore, so I
hope to pass this on to someone:
http://psf.upfronthosting.co.za/roundup/meta/issue527

The b.p.o uses CAcert certificate that was never valid
on Windows and now removed from Ubuntu and Debian,
and yet, some people push the idea that it is OK to
continue using such certificate for b.p.o.

I disapprove the decision of these people and hope that
somebody from python community can change their
convoluted understanding of security. It is sad to see
such decisions in a once respectful environment to
learn from.

Thanks for your business. Bye.
-- 
anatoly t.

From stephen at xemacs.org  Tue Apr 22 03:22:44 2014
From: stephen at xemacs.org (Stephen J. Turnbull)
Date: Tue, 22 Apr 2014 10:22:44 +0900
Subject: [Tracker-discuss]  Pseudo protection of b.p.o from MITM
In-Reply-To: <CAPkN8xKKzyh=SO7zagonpCWNDUGhY5qf+_KwEZdCynUSP5A4Tg@mail.gmail.com>
References: <CAPkN8xKKzyh=SO7zagonpCWNDUGhY5qf+_KwEZdCynUSP5A4Tg@mail.gmail.com>
Message-ID: <87oazuqhsr.fsf@uwakimon.sk.tsukuba.ac.jp>

Anatoly, don't you know that cross-posting is a bad idea?[1]  If you
disagree with the management of bugs.python.org, tracker-discuss is
the right place to post.

anatoly techtonik writes:

 > The b.p.o uses CAcert certificate that was never valid on Windows

Of course it was valid, it was simply not trusted by default.  Given
Microsoft's historical aversion to "free" anything, that's a
completely null signal.

 > and now removed from Ubuntu and Debian, and yet, some people push
 > the idea that it is OK to continue using such certificate for
 > b.p.o.

As pointed out (and never denied) in the thread[2] explaining why
Debian removed CAcert, Debian's "include only 'trustworthy' root
certificates" policy is broken, both in theory and in practice.  With
regard to CAcert, there are no known exploits -- which is not true of
several of the other authorities in Debian's bundle (which is mostly
taken from Mozilla).

Perhaps it's worth moving to a different free root authority, or maybe
even (gasp!)  paying for a well-known commercial certificate, but you
need to find one that satisfies the technical requirement posted by
Martin -- namely, that certs for a particular host should *not* allow
escalation of privilege to all hosts in the python.org domain.  (Note
that if we use a commercial service this probably becomes rather
expensive.)  There may be other requirements I don't know about.

Personally, since I think that the X.509 architecture is broken at the
top in practice (why is Verisign trustworthy? how about the Chinese
National Network Information Center? or the Japanese Ministry of
Education (my employer)? yet most systems -- including Windows --
default to trusting any certificate issued by any of them), having a
root cert that seems trustworthy to me, yet isn't trusted by default,
allowing me to *choose* to assign an appropriate amount of trust to
bugs.python.org, seems to be the most secure option.

I don't know if it's any better than a self-signed cert, of course.

 > I disapprove the decision of these people

What else is new?

 > and hope that somebody from python community can change their
 > convoluted understanding of security.

Security *is* convoluted, and your own understanding of it seems to
be limited since you misuse technical terms like "valid" (there's a
difference between "cannot be validated" and "not valid").


Footnotes: 
[1]  Among other things, it makes it likely that the ban on your
participation will be extended.


From metatracker at psf.upfronthosting.co.za  Tue Apr 22 22:14:43 2014
From: metatracker at psf.upfronthosting.co.za (R David Murray)
Date: Tue, 22 Apr 2014 20:14:43 +0000
Subject: [Tracker-discuss] [issue541] hotmail thinks bugs.python.org is a
	spam IP
Message-ID: <1398197683.07.0.858405889619.issue541@psf.upfronthosting.co.za>


New submission from R David Murray:

Apr 22 17:32:16 psf postfix/smtp[3647]: 2CDF8568E0: to=<dupingping86 at hotmail.com>, relay=mx4.hotmail.com[65.55.37.120]:25, delay=0.66, delays=0.02/0/0.48/0.16, dsn=5.0.0, status=bounced (host mx4.hotmail.com[65.55.37.120] said: 550 SC-001 (COL0-MC4-F23) Unfortunately, messages from 46.4.197.70 weren't sent. Please contact your Internet service provider since part of their network is on our block list. You can also refer your provider to http://mail.live.com/mail/troubleshooting.aspx#errors. (in reply to MAIL FROM command))


A theory about the fact that we are getting classified as a spammer: when an email is received from an unknown address, roundup send back a reply that you have to register to post.  Since spammers use fake addresses, the victim of the spammer gets that message...and marks it as spam.

So we need to turn that off, and then figure out how to get off of hotmail's list (the URL included in the error is useless for that purpose).

----------
messages: 2857
nosy: r.david.murray
priority: bug
status: unread
title: hotmail thinks bugs.python.org is a spam IP

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue541>
_______________________________________________________

From roundup-admin at psf.upfronthosting.co.za  Wed Apr 23 03:55:16 2014
From: roundup-admin at psf.upfronthosting.co.za (Python tracker)
Date: Wed, 23 Apr 2014 01:55:16 +0000
Subject: [Tracker-discuss] Failed issue tracker submission
Message-ID: <20140423015516.0655F56A22@psf.upfronthosting.co.za>



There were problems handling your subject line argument list:
- property stage: 'committed/rejected' is not a stage.

Subject was: "[issue21330] [status=closed; resolution=fixed; stage=committed/rejected]"



Mail Gateway Help
=================
Incoming messages are examined for multiple parts:
 . In a multipart/mixed message or part, each subpart is extracted and
   examined. The text/plain subparts are assembled to form the textual
   body of the message, to be stored in the file associated with a "msg"
   class node. Any parts of other types are each stored in separate files
   and given "file" class nodes that are linked to the "msg" node.
 . In a multipart/alternative message or part, we look for a text/plain
   subpart and ignore the other parts.
 . A message/rfc822 is treated similar tomultipart/mixed (except for
   special handling of the first text part) if unpack_rfc822 is set in
   the mailgw config section.

Summary
-------
The "summary" property on message nodes is taken from the first non-quoting
section in the message body. The message body is divided into sections by
blank lines. Sections where the second and all subsequent lines begin with
a ">" or "|" character are considered "quoting sections". The first line of
the first non-quoting section becomes the summary of the message.

Addresses
---------
All of the addresses in the To: and Cc: headers of the incoming message are
looked up among the user nodes, and the corresponding users are placed in
the "recipients" property on the new "msg" node. The address in the From:
header similarly determines the "author" property of the new "msg"
node. The default handling for addresses that don't have corresponding
users is to create new users with no passwords and a username equal to the
address. (The web interface does not permit logins for users with no
passwords.) If we prefer to reject mail from outside sources, we can simply
register an auditor on the "user" class that prevents the creation of user
nodes with no passwords.

Actions
-------
The subject line of the incoming message is examined to determine whether
the message is an attempt to create a new item or to discuss an existing
item. A designator enclosed in square brackets is sought as the first thing
on the subject line (after skipping any "Fwd:" or "Re:" prefixes).

If an item designator (class name and id number) is found there, the newly
created "msg" node is added to the "messages" property for that item, and
any new "file" nodes are added to the "files" property for the item.

If just an item class name is found there, we attempt to create a new item
of that class with its "messages" property initialized to contain the new
"msg" node and its "files" property initialized to contain any new "file"
nodes.

Triggers
--------
Both cases may trigger detectors (in the first case we are calling the
set() method to add the message to the item's spool; in the second case we
are calling the create() method to create a new node). If an auditor raises
an exception, the original message is bounced back to the sender with the
explanatory message given in the exception.
-------------- next part --------------
Return-Path: <tracker-discuss at python.org>
X-Original-To: report at bugs.python.org
Delivered-To: roundup+tracker at psf.upfronthosting.co.za
Received: from mail.python.org (mail.python.org [IPv6:2001:888:2000:d::a6])
	by psf.upfronthosting.co.za (Postfix) with ESMTPS id 9EA8256A1E
	for <report at bugs.python.org>; Wed, 23 Apr 2014 03:55:15 +0200 (CEST)
Received: from albatross.python.org (localhost [127.0.0.1])
	by mail.python.org (Postfix) with ESMTP id 3gD4Tv2r28z7LjW
	for <report at bugs.python.org>; Wed, 23 Apr 2014 03:55:15 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=python.org; s=200901;
	t=1398218115; bh=TeQeyAEHfHi0+b8UYczQ78MlN6WrECoK1m9Y17K1oOw=;
	h=From:To:Subject:Date:From;
	b=eM09AWjlVfguM6dDQvDLuoV3ZPAYFl8VSjPixEjsStgd87X8I+hHcTrHT+xX38HPP
	 MHbXUnTyinSUWppEW7x6U2kI3WdxegfjB8X0CYmJKPtYuRd3tuHyoVk9NC0gbP97WN
	 AEvkT95jlai3kNzTfCnZTx+jYtO50t2BfGwubXRY=
Received: from localhost (HELO mail.python.org) (127.0.0.1)
  by albatross.python.org with SMTP; 23 Apr 2014 03:55:15 +0200
Received: from virt-7yvsjn.psf.osuosl.org (unknown [140.211.10.72])
	by mail.python.org (Postfix) with ESMTP
	for <report at bugs.python.org>; Wed, 23 Apr 2014 03:55:14 +0200 (CEST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
From: tracker-discuss at python.org
To: report at bugs.python.org
Subject: [issue21330] [status=closed; resolution=fixed;
 stage=committed/rejected]
Message-Id: <3gD4Tv2r28z7LjW at mail.python.org>
Date: Wed, 23 Apr 2014 03:55:15 +0200 (CEST)

TmV3IGNoYW5nZXNldCBiNDI4YjgwM2Y3MWYgYnkgQmVuamFtaW4gUGV0ZXJzb24gaW4gYnJhbmNo
ICcyLjcnOgpmaXggb2ZmLWJ5LW9uZSBlcnJvciAoY2xvc2VzICMyMTMzMCkKaHR0cDovL2hnLnB5
dGhvbi5vcmcvY3B5dGhvbi9yZXYvYjQyOGI4MDNmNzFmCgoKTmV3IGNoYW5nZXNldCA2NjBkNTNi
ZmIzMzIgYnkgQmVuamFtaW4gUGV0ZXJzb24gaW4gYnJhbmNoICczLjQnOgpmaXggb2ZmLWJ5LW9u
ZSBlcnJvciAoY2xvc2VzICMyMTMzMCkKaHR0cDovL2hnLnB5dGhvbi5vcmcvY3B5dGhvbi9yZXYv
NjYwZDUzYmZiMzMyCgoKTmV3IGNoYW5nZXNldCBhZTRhOTAwMGU5MjUgYnkgQmVuamFtaW4gUGV0
ZXJzb24gaW4gYnJhbmNoICdkZWZhdWx0JzoKbWVyZ2UgMy40ICgjMjEzMzApCmh0dHA6Ly9oZy5w
eXRob24ub3JnL2NweXRob24vcmV2L2FlNGE5MDAwZTkyNQo=

From roundup-admin at psf.upfronthosting.co.za  Thu Apr 24 20:23:24 2014
From: roundup-admin at psf.upfronthosting.co.za (Python tracker)
Date: Thu, 24 Apr 2014 18:23:24 +0000
Subject: [Tracker-discuss] Failed issue tracker submission
Message-ID: <20140424182324.77DF156A2A@psf.upfronthosting.co.za>



There were problems handling your subject line argument list:
- property stage: 'committed/rejected' is not a stage.

Subject was: "[issue21346] [status=closed; resolution=fixed; stage=committed/rejected]"



Mail Gateway Help
=================
Incoming messages are examined for multiple parts:
 . In a multipart/mixed message or part, each subpart is extracted and
   examined. The text/plain subparts are assembled to form the textual
   body of the message, to be stored in the file associated with a "msg"
   class node. Any parts of other types are each stored in separate files
   and given "file" class nodes that are linked to the "msg" node.
 . In a multipart/alternative message or part, we look for a text/plain
   subpart and ignore the other parts.
 . A message/rfc822 is treated similar tomultipart/mixed (except for
   special handling of the first text part) if unpack_rfc822 is set in
   the mailgw config section.

Summary
-------
The "summary" property on message nodes is taken from the first non-quoting
section in the message body. The message body is divided into sections by
blank lines. Sections where the second and all subsequent lines begin with
a ">" or "|" character are considered "quoting sections". The first line of
the first non-quoting section becomes the summary of the message.

Addresses
---------
All of the addresses in the To: and Cc: headers of the incoming message are
looked up among the user nodes, and the corresponding users are placed in
the "recipients" property on the new "msg" node. The address in the From:
header similarly determines the "author" property of the new "msg"
node. The default handling for addresses that don't have corresponding
users is to create new users with no passwords and a username equal to the
address. (The web interface does not permit logins for users with no
passwords.) If we prefer to reject mail from outside sources, we can simply
register an auditor on the "user" class that prevents the creation of user
nodes with no passwords.

Actions
-------
The subject line of the incoming message is examined to determine whether
the message is an attempt to create a new item or to discuss an existing
item. A designator enclosed in square brackets is sought as the first thing
on the subject line (after skipping any "Fwd:" or "Re:" prefixes).

If an item designator (class name and id number) is found there, the newly
created "msg" node is added to the "messages" property for that item, and
any new "file" nodes are added to the "files" property for the item.

If just an item class name is found there, we attempt to create a new item
of that class with its "messages" property initialized to contain the new
"msg" node and its "files" property initialized to contain any new "file"
nodes.

Triggers
--------
Both cases may trigger detectors (in the first case we are calling the
set() method to add the message to the item's spool; in the second case we
are calling the create() method to create a new node). If an auditor raises
an exception, the original message is bounced back to the sender with the
explanatory message given in the exception.
-------------- next part --------------
Return-Path: <tracker-discuss at python.org>
X-Original-To: report at bugs.python.org
Delivered-To: roundup+tracker at psf.upfronthosting.co.za
Received: from mail.python.org (mail.python.org [82.94.164.166])
	by psf.upfronthosting.co.za (Postfix) with ESMTPS id 2723956A29
	for <report at bugs.python.org>; Thu, 24 Apr 2014 20:23:24 +0200 (CEST)
Received: from albatross.python.org (localhost [127.0.0.1])
	by mail.python.org (Postfix) with ESMTP id 3gF6Mb5nKVz7Ljh
	for <report at bugs.python.org>; Thu, 24 Apr 2014 20:23:23 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=python.org; s=200901;
	t=1398363803; bh=KDn01Cgi6/T3YaXnHYVSqX9iWc7SyF8Xe8DXZPq14Fg=;
	h=From:To:Subject:Date:From;
	b=WfL/MrxBFwqDWODT3eBaE0QRrYXzrHg0hlIbELCr9K34c2u6lv5LUz+AwB7YYaD5A
	 ZDuVwF/QrKlb0o8uxSCtwN16NiLf9Bok5AwutGRJfLuXTdrm7fAJ9An17oUPaHp6in
	 lxktUi6a74v/T4hO/1SI/B1GUHUdSObLJvA7VqSA=
Received: from localhost (HELO mail.python.org) (127.0.0.1)
  by albatross.python.org with SMTP; 24 Apr 2014 20:23:23 +0200
Received: from virt-7yvsjn.psf.osuosl.org (unknown [140.211.10.72])
	by mail.python.org (Postfix) with ESMTP
	for <report at bugs.python.org>; Thu, 24 Apr 2014 20:23:23 +0200 (CEST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
From: tracker-discuss at python.org
To: report at bugs.python.org
Subject: [issue21346] [status=closed; resolution=fixed;
 stage=committed/rejected]
Message-Id: <3gF6Mb5nKVz7Ljh at mail.python.org>
Date: Thu, 24 Apr 2014 20:23:23 +0200 (CEST)

TmV3IGNoYW5nZXNldCAxYmViM2UwNTA3ZmEgYnkgWmFjaGFyeSBXYXJlIGluIGJyYW5jaCAnMi43
JzoKSXNzdWUgIzIxMzQ2OiBGaXggdHlwb3MgaW4gdGVzdF9pdGVydG9vbHMuICBQYXRjaCBieSBC
cmlhbiBLZWFybnMuCmh0dHA6Ly9oZy5weXRob24ub3JnL2NweXRob24vcmV2LzFiZWIzZTA1MDdm
YQoKCk5ldyBjaGFuZ2VzZXQgOTAxYjlhZmM5MThlIGJ5IFphY2hhcnkgV2FyZSBpbiBicmFuY2gg
JzMuNCc6Cklzc3VlICMyMTM0NjogRml4IHR5cG8sIG1ha2UgbWVzc2FnZSBjb25zaXN0ZW50IGlu
IHRlc3RfaXRlcnRvb2xzLgpodHRwOi8vaGcucHl0aG9uLm9yZy9jcHl0aG9uL3Jldi85MDFiOWFm
YzkxOGUKCgpOZXcgY2hhbmdlc2V0IDIxMDEyNTE1YzI0OSBieSBaYWNoYXJ5IFdhcmUgaW4gYnJh
bmNoICdkZWZhdWx0JzoKQ2xvc2VzICMyMTM0NjogTWVyZ2Ugd2l0aCAzLjQKaHR0cDovL2hnLnB5
dGhvbi5vcmcvY3B5dGhvbi9yZXYvMjEwMTI1MTVjMjQ5Cg==

From metatracker at psf.upfronthosting.co.za  Fri Apr 25 18:51:18 2014
From: metatracker at psf.upfronthosting.co.za (Roy Smith)
Date: Fri, 25 Apr 2014 16:51:18 +0000
Subject: [Tracker-discuss] [issue542] Can't log in to bug tracker after
	doing search
Message-ID: <1398444678.05.0.230348651832.issue542@psf.upfronthosting.co.za>


New submission from Roy Smith:

I went to http://bugs.python.org/ and performed a search, while not logged in.  This got me to:

http://bugs.python.org/issue?%40columns=id%2Cactivity%2Ctitle%2Ccreator%2Cassignee%2Cstatus%2Ctype&%40sort=-activity&%40filter=status&%40action=searchid&ignore=file%3Acontent&%40search_text=regular+expression&submit=search&status=-1%2C1%2C2%2C3

>From there, I attempted to login.  When I clicked the login button, I got:

broken form: multiple @action values submitted

Clearing the query string (i.e. everything from the "?" to the end in the URL) lets me log in normally.

----------
messages: 2858
nosy: roysmith
priority: bug
status: unread
title: Can't log in to bug tracker after doing search
topic: tracker

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue542>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Fri Apr 25 20:46:05 2014
From: metatracker at psf.upfronthosting.co.za (Ezio Melotti)
Date: Fri, 25 Apr 2014 18:46:05 +0000
Subject: [Tracker-discuss] [issue542] Can't log in to bug tracker after
	doing search
In-Reply-To: <1398444678.05.0.230348651832.issue542@psf.upfronthosting.co.za>
Message-ID: <1398451565.74.0.288091844313.issue542@psf.upfronthosting.co.za>


Ezio Melotti added the comment:

This is a known issue and a duplicate of http://psf.upfronthosting.co.za/roundup/meta/issue448.  Clearing the query string or clicking on the logo at the top-left are good workaround until we get this fixed.

----------
nosy: +ezio.melotti
status: unread -> resolved

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue542>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Fri Apr 25 21:30:25 2014
From: metatracker at psf.upfronthosting.co.za (Ezio Melotti)
Date: Fri, 25 Apr 2014 19:30:25 +0000
Subject: [Tracker-discuss] [issue448] Cannot log into search results page
In-Reply-To: <1333644181.93.0.427714955722.issue448@psf.upfronthosting.co.za>
Message-ID: <1398454225.31.0.517318934147.issue448@psf.upfronthosting.co.za>


Ezio Melotti added the comment:

The attached patch fixes the issue by changing action="#" to action="name_of_current_page". 
This loses the information about the query string (e.g. in case of search).  Since Roundup uses different pages for different issues, logging in from an issue page brings you the same page, however this doesn't work for pages that depend on the query string (e.g. searches).
Adding the query string in the action would be ineffective since this form uses POST.  If we really wanted to keep them we could try to convert the query string to hidden fields in the form, but then I'm not sure Roundup would recognize them if they are sent via POST.

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue448>
_______________________________________________________
-------------- next part --------------
diff --git a/html/page.html b/html/page.html
--- a/html/page.html
+++ b/html/page.html
@@ -180,7 +180,7 @@
 
         <li tal:condition="python:request.user.username=='anonymous'">
           <strong i18n:translate="">User</strong>
-          <form method="post" action="#">
+          <form method="post" tal:attributes="action string:${request/env/PATH_INFO}">
           <ul class="level-three">
             <li>
                 <tal:span i18n:translate="">Login</tal:span>&nbsp;(OpenID&nbsp;possible)<br />

From metatracker at psf.upfronthosting.co.za  Wed Apr 30 19:03:55 2014
From: metatracker at psf.upfronthosting.co.za (Ned Deily)
Date: Wed, 30 Apr 2014 17:03:55 +0000
Subject: [Tracker-discuss] [issue543] nosy list popup menu has become very
	slow
Message-ID: <1398877435.2.0.945868449831.issue543@psf.upfronthosting.co.za>


New submission from Ned Deily:

As of recently, when typing in the nosy list, I'm seeing a very noticeable delay before the popup list of suggested names appears and during that pause the browser is unresponsive.  Behavior noted in both Safari and FF on OS X.  It may be that the list is now much bigger than it used to be; I see a lot of unfamiliar names when the list finally appears.

----------
messages: 2861
nosy: ned.deily
priority: urgent
status: unread
title: nosy list popup menu has become very slow

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue543>
_______________________________________________________