I have run-into an issue with Exchange 2007, and was hoping that you could help me point what could be going wrong.
MIME-Version: 1.0Content-Type: Multipart/Voice-Message; boundary="--boundary.ipw.20070642122193.3645173988"Subject: Fax Message for you (MB27600) from 8675309Date: Thu, 21 Jun 2007 15:19:03 -0700 From: "Outside Caller" <non-mail-user@Local>Reply-To: "Amit" < non-mail-user@Local>To: 07liberty_1@productvalidation.localSender: "Tom R" <27975@PPPPP.pbx>Message-ID: <348885A4D32B4D439B5F65DECA1AB62C@ALPHA-LIBERTY-E \u003c/a\>\u003cfont color\u003d\"#cc0000\"\>>\u003c/font\>\u003c/p\>\n\u003cp\>\u003cbr\>\u003cfont color\u003d\"#cc0000\"\>This is a multi-part message in MIME format. \u003c/font\>\u003c/p\>\n\u003cp\>\u003cfont color\u003d\"#cc0000\"\>----boundary.ipw.20070642122193\u003cWBR\>.3645173988\u003cbr\>Content-Type: text/plain\u003cbr\>Content-Transfer-Encoding: 7bit\u003c/font\>\u003c/p\>\n\u003cp\>\u003cfont color\u003d\"#cc0000\"\>A fax was received at 15:19:03 on Thu 06/21/2007.\u003cbr\>----boundary.ipw.20070642122193\u003cWBR\>.3645173988\u003cbr\>Content-Type: image/tiff; name\u003d"00E247C2.tif"\u003cbr\>Content-Disposition: attachment; name\u003d"\n00E247C2.tif"; filename\u003d"00E247C2.tif"\u003cbr\>Content-Transfer-Encoding: base64\u003cbr\>X-Pages: 1\u003cbr\>Content-Description: <IT><FAX></FAX></IT>\u003cbr\>\u003c/font\>\u003c/p\>\n\u003cp\>\u003cfont color\u003d\"#cc0000\"\>\u003cfont color\u003d\"#000000\"\>If the same message is sent to Exchange 2003 or older - the following headers appear in the mail, just as they were composed.\u003c/font\>\u003c/font\>\u003c/p\>\n\u003cp\>\u003cfont color\u003d\"#cc0000\"\>Content-Type: image/tiff; name\u003d"00E247C2.tif"\u003cbr\>Content-Disposition: attachment; name\u003d"00E247C2.tif"; filename\u003d"00E247C2.tif"\u003cbr\>Content-Transfer-Encoding: base64\u003cbr\>\nX-Pages: 1\u003cbr\>Content-Description: <IT><FAX></FAX></IT>\u003c/font\>\u003c/p\>\n\u003cp\>\u003cfont color\u003d\"#cc0000\"\>But, \u003c/font\>\u003cfont color\u003d\"#000000\"\>if the message was delivered to Exchange 2007 with default settings out of the box - this is what the message ends-up looking like :\u003c/font\>\u003c/p\>\n\u003cp\>\u003cfont color\u003d\"#006600\"\>Received: from \u003ca href\u003d\"http://alpha-liberty-em.engineering.mycompany.com\" target\u003d\"_blank\" onclick\u003d\"return top.js.OpenExtLink(window,event,this)\"\>alpha-liberty-em.engineering\u003cWBR\>.mycompany.com\u003c/a\> (\u003ca href\u003d\"http://172.18.43.235\" target\u003d\"_blank\" onclick\u003d\"return top.js.OpenExtLink(window,event,this)\"\>172.18.43.235\u003c/a\>) by\u003cbr\> AlphaExch2007.ProductValidation\u003cWBR\>.local\n (\u003ca href\u003d\"http://172.17.180.12\" target\u003d\"_blank\" onclick\u003d\"return top.js.OpenExtLink(window,event,this)\"\>172.17.180.12\u003c/a\>) with Microsoft SMTP\u003cbr\> Server id 8.0.685.24; Mon, 25 Jun 2007 16:02:58 -0700\u003cbr\>Received: from /spool/local by localdomain with [XMail ",1] ); //--> >
This is a multi-part message in MIME format.
----boundary.ipw.20070642122193.3645173988Content-Type: text/plainContent-Transfer-Encoding: 7bit
A fax was received at 15:19:03 on Thu 06/21/2007.----boundary.ipw.20070642122193.3645173988Content-Type: image/tiff; name="00E247C2.tif"Content-Disposition: attachment; name=" 00E247C2.tif"; filename="00E247C2.tif"Content-Transfer-Encoding: base64X-Pages: 1Content-Description: <IT><FAX></FAX></IT>
If the same message is sent to Exchange 2003 or older - the following headers appear in the mail, just as they were composed.
Content-Type: image/tiff; name="00E247C2.tif"Content-Disposition: attachment; name="00E247C2.tif"; filename="00E247C2.tif"Content-Transfer-Encoding: base64X-Pages: 1Content-Description: <IT><FAX></FAX></IT>
But, if the message was delivered to Exchange 2007 with default settings out of the box - this is what the message ends-up looking like :
Received: from alpha-liberty-em.engineering.mycompany.com (172.18.43.235) by AlphaExch2007.ProductValidation.local (172.17.180.12) with Microsoft SMTP Server id 8.0.685.24; Mon, 25 Jun 2007 16:02:58 -0700Received: from /spool/local by localdomain with [XMail Server] for <\n\u003c/font\>\u003ca href\u003d\"mailto:07liberty_1@productvalidation.local\" target\u003d\"_blank\" onclick\u003d\"return top.js.OpenExtLink(window,event,this)\"\>\u003cfont color\u003d\"#006600\"\>07liberty_1@productvalidation\u003cWBR\>.local\u003c/font\>\u003c/a\>\u003cfont color\u003d\"#006600\"\>> from\u003cbr\> <\u003c/font\>\u003ca href\u003d\"mailto:07liberty_2@productvalidation.local\" target\u003d\"_blank\" onclick\u003d\"return top.js.OpenExtLink(window,event,this)\"\>\n\u003cfont color\u003d\"#006600\"\>07liberty_2@productvalidation\u003cWBR\>.local\u003c/font\>\u003c/a\>\u003cfont color\u003d\"#006600\"\>>; Mon, 25 Jun 2007 15:55:19 -0700\u003cbr\>From: Outside Caller <\u003c/font\>\u003ca href\u003d\"mailto:non-mail-user@mycompany.com\" target\u003d\"_blank\" onclick\u003d\"return top.js.OpenExtLink(window,event,this)\"\>\u003cfont color\u003d\"#006600\"\>\nnon-mail-user@mycompany.com\u003c/font\>\u003c/a\>\u003cfont color\u003d\"#006600\"\>>\u003cbr\>To: 07liberty_1 <\u003c/font\>\u003ca href\u003d\"mailto:07liberty_1@productvalidation.local\" target\u003d\"_blank\" onclick\u003d\"return top.js.OpenExtLink(window,event,this)\"\>\u003cfont color\u003d\"#006600\"\>07liberty_1@productvalidation\u003cWBR\>.local\u003c/font\>\u003c/a\>\u003cfont color\u003d\"#006600\"\>\n>\u003cbr\>Sender: Tom R <\u003c/font\>\u003ca href\u003d\"mailto:27975@mycompany.com\" target\u003d\"_blank\" onclick\u003d\"return top.js.OpenExtLink(window,event,this)\"\>\u003cfont color\u003d\"#006600\"\>27975@mycompany.com\u003c/font\>\u003c/a\>\u003cfont color\u003d\"#006600\"\>>\u003cbr\>Date: Mon, 25 Jun 2007 15:55:18 -0700\u003cbr\>Subject: Fax Message for you (MB27600) from 8675309\n\u003cbr\>Thread-Topic: Fax Message for you (MB27600) from 8675309\u003cbr\>Thread-Index: Ace3fPmkpHJ+dv7sTM6TaHGI1zEFhQ\u003cWBR\>\u003d\u003d\u003cbr\>Message-ID: <\u003c/font\>\u003ca href\u003d\"mailto:E866B8683EB84FE39C16E4F1C587DD15@ALPHA-LIBERTY-E\" target\u003d\"_blank\" onclick\u003d\"return top.js.OpenExtLink(window,event,this)\"\>\u003cfont color\u003d\"#006600\"\>\nE866B8683EB84FE39C16E4F1C587DD1\u003cWBR\>5@ALPHA-LIBERTY-E\u003c/font\>\u003c/a\>\u003cfont color\u003d\"#006600\"\>>\u003cbr\>Reply-To: Unkown User <\u003c/font\>\u003ca href\u003d\"mailto:non-mail-user@inter-tel.com\" target\u003d\"_blank\" onclick\u003d\"return top.js.OpenExtLink(window,event,this)\"\>\u003cfont color\u003d\"#006600\"\>non-mail-user@inter-tel.com\u003c/font\>\n\u003c/a\>\u003cfont color\u003d\"#006600\"\>>\u003cbr\>\u003cstrong\>\u003cfont style\u003d\"background-color:#ffffcc\"\>Accept-Language: en-US",1] ); //--> 1.12 (Win32/Ix86) LMAIL Server] for < 07liberty_1@productvalidation.local> from < 07liberty_2@productvalidation.local>; Mon, 25 Jun 2007 15:55:19 -0700From: Outside Caller < non-mail-user@mycompany.com>To: 07liberty_1 <07liberty_1@productvalidation.local >Sender: Tom R <27975@mycompany.com>Date: Mon, 25 Jun 2007 15:55:18 -0700Subject: Fax Message for you (MB27600) from 8675309 Thread-Topic: Fax Message for you (MB27600) from 8675309Thread-Index: Ace3fPmkpHJ+dv7sTM6TaHGI1zEFhQ==Message-ID: < E866B8683EB84FE39C16E4F1C587DD15@ALPHA-LIBERTY-E>Reply-To: Unkown User <non-mail-user@inter-tel.com >Accept-Language: en-US Content-Language: en-US\u003c/font\>\u003c/strong\>\u003cbr\>X-MS-Exchange-Organization\u003cWBR\>-AuthAs: Anonymous\u003cbr\>X-MS-Exchange-Organization\u003cWBR\>-AuthSource: \nAlphaExch2007.ProductValidation\u003cWBR\>.local\u003cbr\>X-MS-Has-Attach: yes\u003cbr\>X-MS-TNEF-Correlator:\u003cbr\>Content-Type: multipart/mixed;\u003cbr\> boundary\u003d"_002_E866B8683EB84FE\u003cWBR\>39C16E4F1C587DD15ALPHALIBERTYE\u003cWBR\>_"\u003cbr\>MIME-Version: 1.0\u003c/font\>\n\u003c/p\>\n\u003cp\>\u003cfont color\u003d\"#006600\"\>--_002_E866B8683EB84FE39C16E4F1\u003cWBR\>C587DD15ALPHALIBERTYE_\u003cbr\>Content-Type: text/plain; charset\u003d"iso-8859-1"\u003cbr\>Content-Transfer-Encoding: quoted-printable\u003c/font\>\u003c/p\>\n\u003cp\>\u003cfont color\u003d\"#006600\"\>A fax was received at 15:55:18 on Mon 06/25/2007.\u003c/font\>\u003c/p\>\n\u003cp\>\u003cfont color\u003d\"#006600\"\>--_002_E866B8683EB84FE39C16E4F1\u003cWBR\>C587DD15ALPHALIBERTYE_\u003cbr\>\u003cstrong\>\u003cfont style\u003d\"background-color:#ffffcc\"\>\u003cem\>Content-Type: image/tiff; name\u003d"00E7963B.tif"\u003cbr\>Content-Description: <IT><FAX></FAX></IT>.tif\n\u003cbr\>Content-Disposition: attachment; filename\u003d"00E7963B.tif"; size\u003d32060;\u003cbr\> creation-date\u003d"Mon, 25 Jun 2007 23:02:59 GMT";\u003cbr\> modification-date\u003d"Mon, 25 Jun 2007 23:02:59 GMT"\u003cbr\>Content-Transfer-Encoding: base64\n\u003c/em\>\u003c/font\>\u003c/strong\>\u003c/font\>\u003c/p\>\u003cfont color\u003d\"#006600\"\>\u003cstrong\>\u003cem\>\u003cfont style\u003d\"background-color:#ffffcc\"\>\u003c/font\>\u003c/em\>\u003c/strong\>\u003c/font\>\u003c/div\>\n\u003cdiv\>\u003cfont color\u003d\"#006600\"\>\u003cfont style\u003d\"background-color:#ffffff\" color\u003d\"#000000\"\>As you can see in the highlighted text \u003cfont color\u003d\"#cc0000\"\>Content-Disposition: , \u003cfont color\u003d\"#cc0000\"\>Content-Description: \u003c/font\>\u003c/font\>\n\u003cfont color\u003d\"#000000\"\>have been changed, and \u003cfont color\u003d\"#cc0000\"\>X-Pages: 1 \u003c/font\>\u003c/font\>\u003cfont color\u003d\"#000000\"\>has been removed. These headers are important for my script on the receiving end to work - and I have been unable to find a way to avoid these headers from being altered. \n\u003c/font\>\u003c/font\>\u003c/font\>\u003c/div\>\n\u003cdiv\>\u003cfont color\u003d\"#006600\"\>\u003cfont color\u003d\"#000000\"\>\u003c/font\>\u003c/font\> \u003c/div\>\n\u003cdiv\>\u003cfont color\u003d\"#006600\"\>\u003cfont color\u003d\"#000000\"\>My exchange box is configured to use the HUB transport. \u003c/font\>",1] ); //--> Content-Language: en-USX-MS-Exchange-Organization-AuthAs: AnonymousX-MS-Exchange-Organization-AuthSource: AlphaExch2007.ProductValidation.localX-MS-Has-Attach: yesX-MS-TNEF-Correlator:Content-Type: multipart/mixed; boundary="_002_E866B8683EB84FE39C16E4F1C587DD15ALPHALIBERTYE_"MIME-Version: 1.0
--_002_E866B8683EB84FE39C16E4F1C587DD15ALPHALIBERTYE_Content-Type: text/plain; charset="iso-8859-1"Content-Transfer-Encoding: quoted-printable
A fax was received at 15:55:18 on Mon 06/25/2007.
--_002_E866B8683EB84FE39C16E4F1C587DD15ALPHALIBERTYE_Content-Type: image/tiff; name="00E7963B.tif"Content-Description: <IT><FAX></FAX></IT>.tif Content-Disposition: attachment; filename="00E7963B.tif"; size=32060; creation-date="Mon, 25 Jun 2007 23:02:59 GMT"; modification-date="Mon, 25 Jun 2007 23:02:59 GMT"Content-Transfer-Encoding: base64
I apologize for not replying to this sooner. This message went into the spam bucket and we recently recovered it.
Can you tell me more about how the script works? I understand that it adds the header properties? Does the script send the message off a local SMTP relay which then sends it anonymously to the Exchange server? Does it send it to a Hub transport or to a Edge?
I will have to look into this but messages that are accepted anonymously will have certain properties stripped in order to protect the validity of the message. This is done so that spammers and virus writers cannot add attributes that could be used malicously.
- Joel
Well, we send the message as an anonymous-user - the machine that the message originates from does not happen to be a part of the Trusted servers either. We have the Hub transport enabled on Exchange.
I understand that the messages that are accepted anonymously will have certain properties stripped - but is there a possibility that we create a RULE to check for the presence of certain headers that can lead to the avoidance of the stripping of essential-headers .
I am open to other suggestions as well....
Can you try putting the IP address of the application server on the allow list? This should bypass filter, I honestly am not sure if it will still strip the headers.
The sure fire way would be to have the sending SMTP server provide login credentials to the Exchange server.... you would probably want to create a second receive connector for this.