Previously, when our server received an email it would slap the rcpt to in the received headers by adding a for <...> any ideas what has changed?
Any pointers would be grateful.
Headers received today:
Return-Path: xxxxxxxxxxxxxxxxxxx@xxxxxxxxxxxxxxxx Received: from psmtp.com (exprod8mx220.postini.com [64.18.3.120]) by mail.pdinc.us (8.12.11.20060308/8.12.11) with SMTP id m7CCwh6o006066; Tue, 12 Aug 2008 08:58:44 -0400 Received: from source ([198.185.182.20]) (using TLSv1) by exprod8mx220.postini.com ([64.18.7.10]) with SMTP; Tue, 12 Aug 2008 05:58:42 PDT Received: from hq-exout01.anteon.com ([10.170.1.216]) by hq-ipt01.anteon.com with ESMTP; 12 Aug 2008 08:58:16 -0400 X-SENDER-IP: 10.170.1.216 X-SENDER-REPUTATION: None X-IronPort-AV: i="4.32,195,1217822400"; d="pdf'?doc'32?xls'32,32?zip'32,32,48?scan'32,32,48,208,217,32,48"; a="236730957:sNHT2674851018" Received: from HQ-EXVS05.anteon.com ([10.170.1.146]) by HQ-EXOUT01.anteon.com with Microsoft SMTPSVC(6.0.3790.3959); Tue, 12 Aug 2008 08:58:16 -0400 x-mimeole: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----_=_NextPart_001_01C8FC7B.15CE4044" Subject: SEAPORT E, RFP, Calibration Standards Management Support , Navy-FISC, Corona, CA, New - Incumbent Known, Due Date: 8/22/2008 6:00:00 PM, N00024-08-R-3381 Date: Tue, 12 Aug 2008 08:58:14 -0400 Message-ID: 2CFD33B485D9DE4E9DD95727F68FBBA85DD2C1@HQ-EXVS05.anteon.com X-MS-Has-Attach: yes X-MS-TNEF-Correlator: Thread-Topic: SEAPORT E, RFP, Calibration Standards Management Support , Navy-FISC, Corona, CA, New - Incumbent Known, Due Date: 8/22/2008 6:00:00 PM, N00024-08-R-3381 Thread-Index: Acj8exTmRKNp5IQVQnS543hWImbznw== From: "Hopwood, Geoff" xxxxxxxxxxxxxxxxxxx@xxxxxxxxxxxxxxxx Bcc: X-OriginalArrivalTime: 12 Aug 2008 12:58:16.0577 (UTC) FILETIME=[1652EF10:01C8FC7B] X-pstn-neptune: 1/1/1.00/92 X-pstn-levels: (S:99.90000/99.90000 CV: 0.0940 P:95.9108 ) X-pstn-settings: 1 (0.1500:0.1500) CV gt3 gt2 gt1 p X-pstn-addresses: from xxxxxxxxxxxxxxxxxxx@xxxxxxxxxxxxxxxx [125/4] X-pstn-cave-hit:
Headers received 2 years ago:
Received: from wrtlnx07.wrtech.com (wrtlnx07.wrtech.com [207.14.178.213]) by ns.pyerotechnics.com (8.11.6/8.11.6) with ESMTP id k7L8u4921189 for yyyyyyyyyyyyy@yyyyyyyyyyyyy; Mon, 21 Aug 2006 04:56:05 -0400
-- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- - - - Jason Pyeron PD Inc. http://www.pdinc.us - - Principal Consultant 10 West 24th Street #100 - - +1 (443) 269-1555 x333 Baltimore, Maryland 21218 - - - -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- This message is copyright PD Inc, subject to license 20080407P00.
Hi,
On Tue, Aug 12, 2008 at 09:38, Jason Pyeron jpyeron@pdinc.us wrote:
Previously, when our server received an email it would slap the rcpt to in the received headers by adding a for <...> any ideas what has changed?
In my (vast) experience with e-mail (most of it with Postfix though) I observed this behaviour when the message was for multiple recipients. IIRC, Postfix adds a "for <...>" only if the message is for one recipient only. Probably sendmail will do the same, as the problem is inherent to SMTP mail handling (where one message may be directed to multiple recipients). I remember the first time I noticed that I was puzzled by it as well.
HTH, Filipe