Sorry I didn't post them before I was just trying to do a sanity check. Here they are:
--------------- Postfix Logs --------------- Jun 23 16:48:10 relay0 postfix/smtp[30504]: 5ED4F114BBC: to=<sa...@2co.com<mailto:sa...@2co.com>>, relay=mail.2co.com[64.128.185.221]:25, delay=0.98, delays=0.01/0.01/0.33/0.62, dsn=4.4.2, status=deferred (lost connection with mail.2co.com[64.128.185.221] while sending end of data -- message may Jun 23 18:02:08 relay0 postfix/smtp[1638]: 5ED4F114BBC: enabling PIX <CRLF>.<CRLF> workaround for mail.2co.com[64.128.185.221]:25 Jun 23 18:02:18 relay0 postfix/smtp[1638]: 5ED4F114BBC: to=<sa...@2co.com<mailto:sa...@2co.com>>, relay=mail.2co.com[64.128.185.221]:25, delay=4449, delays=4438/0.03/0.34/10, dsn=4.4.2, status=deferred (lost connection with mail.2co.com[64.128.185.221] while sending end of data -- message may be Jun 23 19:25:27 relay0 postfix/smtp[3204]: 5ED4F114BBC: enabling PIX <CRLF>.<CRLF> workaround for mail.2co.com[64.128.185.221]:25 Jun 23 19:25:37 relay0 postfix/smtp[3204]: 5ED4F114BBC: to=<sa...@2co.com<mailto:sa...@2co.com>>, relay=mail.2co.com[64.128.185.221]:25, delay=9448, delays=9438/0.02/0.08/10, dsn=4.4.2, status=deferred (lost connection with mail.2co.com[64.128.185.221] while sending end of data -- message may be Jun 23 22:12:08 relay0 postfix/smtp[6277]: 5ED4F114BBC: enabling PIX <CRLF>.<CRLF> workaround for mail.2co.com[64.128.185.221]:25 Jun 23 22:12:18 relay0 postfix/smtp[6277]: 5ED4F114BBC: to=<sa...@2co.com<mailto:sa...@2co.com>>, relay=mail.2co.com[64.128.185.221]:25, delay=19449, delays=19438/0.09/0.22/10, dsn=4.4.2, status=deferred (lost connection with mail.2co.com[64.128.185.221] while sending end of data -- message may b ---------- The Bounce ---------- Diagnostic information for administrators: Generating server: relay0.edhance.com<http://relay0.edhance.com> sa...@2co.com<mailto:sa...@2co.com> #< #4.4.2 X-Postfix; lost connection with mail.2co.com[64.128.185.221] while sending end of data -- message may be sent more than once> #SMTP# Original message headers: Received: from localhost (localhost.localdomain [127.0.0.1]) by relay0.edhance.com<http://relay0.edhance.com> (Postfix) with ESMTP id 5ED4F114BBC for <sa...@2co.com<mailto:sa...@2co.com>>; Wed, 23 Jun 2010 16:48:09 -0400 (EDT) X-Virus-Scanned: amavisd-new at edhance.com<http://edhance.com> Received: from relay0.edhance.com<http://relay0.edhance.com> ([127.0.0.1]) by localhost (relay0.edhance.com<http://relay0.edhance.com> [127.0.0.1]) (amavisd-new, port 10024) with LMTP id ZnncIBwzYHYa for <sa...@2co.com<mailto:sa...@2co.com>>; Wed, 23 Jun 2010 16:48:09 -0400 (EDT) Received: from exch1.studentsonly.com<http://exch1.studentsonly.com> (exch1.studentsonly.com<http://exch1.studentsonly.com> [10.10.200.21]) by relay0.edhance.com<http://relay0.edhance.com> (Postfix) with ESMTP id 1C289114BA1 for <sa...@2co.com<mailto:sa...@2co.com>>; Wed, 23 Jun 2010 16:48:09 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=edhance.com; s=edhancerelay; t=1277326089; bh=mNb0SI++JXpZI858TbHPbyYVy3g0asgBlypn/vc8F9I=; h=From:To:Date:Subject:Message-ID:References:In-Reply-To: Content-Type:Content-Transfer-Encoding:MIME-Version; z=From:=20Bjorn=20Larsen=20<first.l...@edhance.com<mailto:first.l...@edhance.com>>|To:=20"'sales @2co.com'"=20<sa...@2co.com<mailto:sa...@2co.com>>|Date:=20Wed,=2023=20Jun=202010=2016:4 8:44=20-0400|Subject:=20RE:=202CO.COM=20Sales=20Receipt=2041849348 58|Thread-Topic:=202CO.COM=20Sales=20Receipt=204184934858|Thread-I ndex:=20AcqUMooN4G53+UaSRDWmi9n40AzM4R+4r2ng|Message-ID:=20<28FFB7 6f86a155449265dbc461ea014a3305b68...@exch1.studentsonly.com<mailto:6f86a155449265dbc461ea014a3305b68...@exch1.studentsonly.com>>|Refer ences:=20<20100113092645.8350.qm...@pweb-04.2checkout.com<mailto:20100113092645.8350.qm...@pweb-04.2checkout.com>>|In-Repl y-To:=20<20100113092645.8350.qm...@pweb-04.2checkout.com<mailto:20100113092645.8350.qm...@pweb-04.2checkout.com>>|Accept-L anguage:=20en-US|Content-Language:=20en-US|X-MS-Has-Attach:=20|X-M S-TNEF-Correlator:=20|acceptlanguage:=20en-US|Content-Type:=20text /plain=3B=20charset=3D"utf-8"|Content-Transfer-Encoding:=20base64| MIME-Version:=201.0; b=DkaxKzLgfoBRegzA2rqtsSHGti/kw+OfOZ9m5dugMIPvWSUnLSxERyJSo9PDopPEr YlPgkbMDgW8cInxn1rJ5sgR+LC0BLAaF9RdR2/kMurprD1worTSn2maUWNEjDXA4kW /V4VEzLYP4UuOZyxz9qxGOOjXfnkrp6j40/31auQ= Received: from exch1.studentsonly.com<http://exch1.studentsonly.com> ([fe80::558d:fd4f:e878:175c]) by exch1.studentsonly.com<http://exch1.studentsonly.com> ([fe80::558d:fd4f:e878:175c%10]) with mapi; Wed, 23 Jun 2010 16:48:46 -0400 From: Bjorn Larsen <first.l...@edhance.com<mailto:first.l...@edhance.com>> To: "'sa...@2co.com<mailto:'sa...@2co.com>'" <sa...@2co.com<mailto:sa...@2co.com>> Date: Wed, 23 Jun 2010 16:48:44 -0400 Subject: RE: 2CO.COM<http://2CO.COM> Sales Receipt 418xxxx Thread-Topic: 2CO.COM<http://2CO.COM> Sales Receipt 418xxxx Thread-Index: AcqUMooN4G53+UaSRDWmi9n40AzM4R+4r2ng Message-ID: <28ffb76f86a155449265dbc461ea014a3305b68...@exch1.studentsonly.com<mailto:28ffb76f86a155449265dbc461ea014a3305b68...@exch1.studentsonly.com>> References: <20100113092645.8350.qm...@pweb-04.2checkout.com<mailto:20100113092645.8350.qm...@pweb-04.2checkout.com>> In-Reply-To: <20100113092645.8350.qm...@pweb-04.2checkout.com<mailto:20100113092645.8350.qm...@pweb-04.2checkout.com>> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 MIME-Version: 1.0 On Jul 1, 2010, at 5:45 PM, Matt Hayes wrote: On 07/01/2010 05:40 PM, James R. Marcus wrote: Slightly off topic, but a user has observed that any email sent in plain text is bounced, any mail sent as HTML gets sent. Has anyone encountered such an issue? My environment hasn't really changed in months and I'm confused. Thanks, James James, Do you have logs of the instances where 'plain text' emails bounced or were rejected? Would be quite helpful to see that if so! -Matt :: James R. Marcus | Director, IT Operations :: Edhance | jmar...@edhance.com<x-msg://103/jmar...@edhance.com> :: v: 617-475-5360 | m: 914-772-8533 :: web: www.edhance.com<http://www.edhance.com/>
