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

Python tracker roundup-admin at psf.upfronthosting.co.za
Mon Jul 2 20:36:31 CEST 2012

There was a problem with the message you sent: This issue can't be closed until issue 15031 is closed.

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 5E7D11CC7C for <report at bugs.python.org>; Mon, 2 Jul 2012 20:36:31 +0200 (CEST) Received: from albatross.python.org (localhost [127.0.0.1]) by mail.python.org (Postfix) with ESMTP id 3WQxxp54vszPJ6 for <report at bugs.python.org>; Mon, 2 Jul 2012 20:36:30 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=python.org; s=200901; t=1341254190; bh=bcoPtckr6VOn/nnWeOnKJxf0E8057TGiXziLdKxmDAU=; h=MIME-Version:Content-Type:Content-Transfer-Encoding:From:To: Subject:Message-Id:Date; b=LeXZP20cZnfbA2FHjnPNH2KEX5ZCGryZdBwT5XwAqbn2PrdQCxB0OJ766NdEkuI5N RlaB95Vz83qouHfh8sVxO8welo9E4UpoXVEEvwFt5/XYUtDG3eoVp6ufKpWCxut1Sj PDwgNWINBY5UPYtDB92G1S7YTLttEiQ/jt2a/vaE= Received: from localhost (HELO mail.python.org) (127.0.0.1) by albatross.python.org with SMTP; 02 Jul 2012 20:36:30 +0200 Received: from virt-7yvsjn.psf.osuosl.org (virt-7yvsjn.psf.osuosl.org [140.211.10.72]) by mail.python.org (Postfix) with ESMTP for <report at bugs.python.org>; Mon, 2 Jul 2012 20:36:30 +0200 (CEST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 From: python-dev at python.org To: report at bugs.python.org Subject: [issue15030] [status=closed; resolution=fixed; stage=committed/rejected] Message-Id: <3WQxxp54vszPJ6 at mail.python.org> Date: Mon, 2 Jul 2012 20:36:30 +0200 (CEST)

TmV3IGNoYW5nZXNldCBiNzQ2M2VjMTk4MGMgYnkgQnJldHQgQ2Fubm9uIGluIGJyYW5jaCAnZGVm YXVsdCc6CkNsb3NlcyAjMTUwMzA6IE1ha2UgaW1wb3J0bGliLmFiYy5QeVB5Y0xvYWRlciByZXNw ZWN0IHRoZSBuZXcgLnB5YwpodHRwOi8vaGcucHl0aG9uLm9yZy9jcHl0aG9uL3Jldi9iNzQ2M2Vj MTk4MGMK

More information about the Python-Dev mailing list