[Python-Dev] Failed issue tracker submission (original) (raw)

Python tracker roundup-admin at psf.upfronthosting.co.za
Tue Jun 26 08:50:12 CEST 2012

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

Subject was: "[issue15817]"

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. Id:mailgw.py,v1.1962008−07−2303:04:44richardExpId: mailgw.py,v 1.196 2008-07-23 03:04:44 richard Exp Id:mailgw.py,v1.1962008−07−2303:04:44richardExp -------------- next part -------------- Return-Path: <python-dev 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 7F8771CBB4 for <report at bugs.python.org>; Tue, 26 Jun 2012 08:50:11 +0200 (CEST) Received: from albatross.python.org (localhost [127.0.0.1]) by mail.python.org (Postfix) with ESMTP id 3WLyYb21g5zPJ4 for <report at bugs.python.org>; Tue, 26 Jun 2012 08:50:11 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=python.org; s=200901; t=1340693411; bh=MXGTWyOd852eyn+HLLV5N+r21/D3dyRf6FtHBCuUlYg=; h=Date:Message-Id:Content-Type:MIME-Version: Content-Transfer-Encoding:From:To:Subject; b=j1zqdBGYKFgD7k5LANirZo3rCACM1wxD40cuazDZxto1ONgx0w1wE7a25pHbx2yy7 AKsfTYuANuh77s8HKjmW8e6uZFggjVjANTloxwpTqIg6Iid3YV8qBGlfn9cl7VkPc5 7nKKJmtsUpV921/nU5jnixFcfeBNRbMLBqphj1uk= Received: from localhost (HELO mail.python.org) (127.0.0.1) by albatross.python.org with SMTP; 26 Jun 2012 08:50:11 +0200 Received: from dinsdale.python.org (svn.python.org [IPv6:2001:888:2000:d::a4]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by mail.python.org (Postfix) with ESMTPS for <report at bugs.python.org>; Tue, 26 Jun 2012 08:50:11 +0200 (CEST) Received: from localhost ([127.0.0.1] helo=dinsdale.python.org ident=hg) by dinsdale.python.org with esmtp (Exim 4.72) (envelope-from <python-dev at python.org>) id 1SjPbH-0001gC-32 for report at bugs.python.org; Tue, 26 Jun 2012 08:50:11 +0200 Date: Tue, 26 Jun 2012 08:50:11 +0200 Message-Id: <E1SjPbH-0001gC-32 at dinsdale.python.org> Content-Type: text/plain; charset="utf8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 From: python-dev at python.org To: report at bugs.python.org Subject: [issue15817]

TmV3IGNoYW5nZXNldCAxZmE1MGJiY2MyMWYgYnkgTGFycnkgSGFzdGluZ3MgaW4gYnJhbmNoICdk ZWZhdWx0JzoKSXNzdWUgIzE1ODE3OiBCdWdmaXg6IHJlbW92ZSB0ZW1wb3JhcnkgZGlyZWN0b3Jp ZXMgdGVzdF9zaHV0aWwgd2FzIGxlYXZpbmcKaHR0cDovL2hnLnB5dGhvbi5vcmcvY3B5dGhvbi9y ZXYvMWZhNTBiYmNjMjFmCg==

More information about the Python-Dev mailing list