Path: csiph.com!usenet.pasdenom.info!weretis.net!feeder4.news.weretis.net!rt.uk.eu.org!newsfeed.xs4all.nl!newsfeed2a.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.007 X-Spam-Evidence: '*H*': 0.99; '*S*': 0.00; 'receives': 0.04; 'method,': 0.09; 'rfc': 0.09; 'subject:position': 0.09; 'cc:addr :python-list': 0.11; 'python': 0.11; 'fixing.': 0.16; 'from:addr:rosuav': 0.16; 'from:name:chris angelico': 0.16; 'smtp,': 0.16; 'subject:Add': 0.16; ':-)': 0.16; 'wrote:': 0.18; 'do.': 0.18; 'app': 0.19; 'module': 0.19; 'trying': 0.19; "python's": 0.19; '>>>': 0.22; 'cc:addr:python.org': 0.22; 'headers': 0.24; 'mon,': 0.24; 'server.': 0.24; 'cc:2**0': 0.24; 'required.': 0.27; 'header:In-Reply-To:1': 0.27; 'appear': 0.29; 'specifically': 0.29; 'correct': 0.29; 'chris': 0.29; '[1]': 0.29; 'message-id:@mail.gmail.com': 0.30; "i'm": 0.30; '>>>>': 0.31; 'header,': 0.31; 'trivial': 0.31; 'probably': 0.32; 'figure': 0.32; 'supposed': 0.32; 'another': 0.32; 'says': 0.33; "i'd": 0.34; 'could': 0.34; "can't": 0.35; 'but': 0.35; 'received:google.com': 0.35; 'add': 0.35; 'there': 0.35; 'smtp': 0.36; 'subject:?': 0.36; 'url:org': 0.36; 'being': 0.38; 'ends': 0.38; 'issue': 0.38; 'pm,': 0.38; 'rather': 0.38; 'does': 0.39; 'how': 0.40; 'even': 0.60; 'easy': 0.60; 'received:': 0.65; 'route': 0.84; 'edwards': 0.91; 'to:none': 0.92; 'anywhere,': 0.93 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:cc :content-type; bh=8Q31Iz0Dc0PkCsPPAYCBH8KbNaYUabLYIaSwwZVcvmg=; b=Ir7mTNuflqaJrfxMUEKrfcNFK7uZq6tqdz5CLucK+H7svdAda8/3OfjmZOoezzHB7W k1Us6ssgsXLj4agNrz+Kxkis16+lEmk24gFqzU++7yG9dXIfQN8xvaCNk/rJdKy1y/Hs sdaMWEX7+V3HFSRnGA8rhR12WfoVu2vjNfOYFZabHhEvPpF1ZfpDoGKEAh1Q4Mz06t5w vtIa7a4W1lXz7G4BQyDh2f2DNzXvQcFKti9snzw5SxRgqBBinP80f/oZeUinoGmsw6G3 92gR3Rjuh2pWCNIbzXcIvxDvf5whFkI8x+I77DI4uq+TSK3YTMSraFbWZd8TWrpUbf03 itkQ== MIME-Version: 1.0 X-Received: by 10.52.164.175 with SMTP id yr15mr286814vdb.59.1399372900185; Tue, 06 May 2014 03:41:40 -0700 (PDT) In-Reply-To: <5N2av.257203$q95.207421@fx22.am4> References: <5N2av.257203$q95.207421@fx22.am4> Date: Tue, 6 May 2014 20:41:40 +1000 Subject: Re: Add "Received:" header to email msg in correct position? From: Chris Angelico Cc: "python-list@python.org" Content-Type: text/plain; charset=UTF-8 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: 38 NNTP-Posting-Host: 2001:888:2000:d::a6 X-Trace: 1399372909 news.xs4all.nl 2934 [2001:888:2000:d::a6]:57153 X-Complaints-To: abuse@xs4all.nl Xref: csiph.com comp.lang.python:70954 On Tue, May 6, 2014 at 8:26 PM, alister wrote: > On Tue, 06 May 2014 19:47:54 +1000, Chris Angelico wrote: > >> On Tue, May 6, 2014 at 7:15 PM, alister >> wrote: >>> On Mon, 05 May 2014 19:51:15 +0000, Grant Edwards wrote: >>> >>>> I'm working on a Python app that receives an e-mail message via SMTP, >>>> does some trivial processing on it, and forwards it to another SMTP >>>> server. >>>> >>>> I'd like to do the polite thing and add a "Received:" header, but I >>>> can't figure out how to get Python's email module to add it in the >>>> correct place. It always ends up at the "bottom" of the headers below >>>> From: To: etc. It's supposed to go at the above all the Received: >>>> headers that where there when I received it. >>> >>> Is this required or just being polite? >>> what I mean is does the standard state the headers must be in a >>> particular order or can they appear anywhere, you may be spending time >>> trying to resolve an issue that does not need fixing. >> >> Yes, it's required. RFC 2821 [1] section 3.8.2 says "prepend". >> >> ChrisA >> >> [1] http://www.ietf.org/rfc/rfc2821.txt > > oh well, so much for the easy route :-) > This suggests the email module could do with amending so that headers can > be pretended as appended. Even if it's special-cased as a dedicated "prepend received header" method, that would probably do. I can't think of any other headers where you need to specifically order them rather than appending. ChrisA