Path: csiph.com!usenet.pasdenom.info!weretis.net!feeder4.news.weretis.net!rt.uk.eu.org!newsfeed.xs4all.nl!newsfeed4.news.xs4all.nl!xs4all!newsgate.cistron.nl!newsgate.news.xs4all.nl!post.news.xs4all.nl!not-for-mail Return-Path: X-Original-To: python-list@python.org Delivered-To: python-list@mail.python.org X-Spam-Status: OK 0.004 X-Spam-Evidence: '*H*': 0.99; '*S*': 0.00; 'versions.': 0.07; 'appropriate.': 0.09; 'received:80.91': 0.09; 'received:80.91.229': 0.09; 'received:gmane.org': 0.09; 'received:list': 0.09; 'rfc': 0.09; 'subject:position': 0.09; 'python': 0.11; 'jan': 0.12; '2.7': 0.14; '2822,': 0.16; 'matters,': 0.16; 'pypi.': 0.16; 'received:80.91.229.3': 0.16; 'received:plane.gmane.org': 0.16; 'reedy': 0.16; 'subject:Add': 0.16; 'successive': 0.16; 'version?': 0.16; 'wrote:': 0.18; 'library': 0.18; 'possible,': 0.19; 'header:User-Agent:1': 0.23; 'issue,': 0.24; 'sorry,': 0.24; 'tracker': 0.26; 'header:X -Complaints-To:1': 0.27; 'header:In-Reply-To:1': 0.27; 'specifically': 0.29; 'usually': 0.31; '3.x': 0.31; 'covered': 0.32; 'url:python': 0.33; '"the': 0.34; 'requirement': 0.35; 'but': 0.35; 'there': 0.35; 'version': 0.36; 'smtp': 0.36; 'subject:?': 0.36; 'url:org': 0.36; 'should': 0.36; 'url:library': 0.38; 'to:addr:python-list': 0.38; 'issue': 0.38; 'pm,': 0.38; 'does': 0.39; 'supporting': 0.39; 'to:addr:python.org': 0.39; 'received:org': 0.40; 'improved': 0.60; 'mentioned': 0.61; 'new': 0.61; 'url:3': 0.61; 'received:173': 0.61; 'such': 0.63; 'managing': 0.66; 'ethan': 0.84; 'furman': 0.84; 'received:fios.verizon.net': 0.84; 'edwards': 0.91 X-Injected-Via-Gmane: http://gmane.org/ To: python-list@python.org From: Terry Reedy Subject: Re: Add "Received:" header to email msg in correct position? Date: Tue, 06 May 2014 14:16:33 -0400 References: Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Gmane-NNTP-Posting-Host: pool-173-75-254-207.phlapa.fios.verizon.net User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 In-Reply-To: X-BeenThere: python-list@python.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: General discussion list for the Python programming language List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Newsgroups: comp.lang.python Message-ID: Lines: 30 NNTP-Posting-Host: 2001:888:2000:d::a6 X-Trace: 1399407827 news.xs4all.nl 2918 [2001:888:2000:d::a6]:37557 X-Complaints-To: abuse@xs4all.nl Xref: csiph.com comp.lang.python:70981 On 5/5/2014 4:58 PM, Grant Edwards wrote: > On 2014-05-05, Ethan Furman wrote: >> I don't know that it matters, but which Python version? I usually does these days. > Sorry, should have mentioned it: 2.7.5 email has been improved with successive 3.x versions. https://docs.python.org/3/library/email.html#package-history There might be an email5 backport for 2.7 on pypi. If the prepend requirement is covered by "The email package is a library for managing email messages, including MIME and other RFC 2822-based message documents. It is specifically not designed to do any sending of email messages to SMTP (RFC 2821), NNTP, or other servers; those are functions of modules such as smtplib and nntplib. The email package attempts to be as RFC-compliant as possible, supporting in addition to RFC 2822, such MIME-related RFCs as RFC 2045, RFC 2046, RFC 2047, and RFC 2231." and the current 3.4/5 version does not prepend and there is no existing tracker issue, then a new issue would seem to be appropriate. -- Terry Jan Reedy