Exchange 2007 Content Conversion/Encoiding issue.

Hello



I have an Exchange 2007 RTM box running in a Windows 2003 only domain.

When we scan a document from our Dell 1815n multifunction and have the 
output emailed, the document shows up as encoded garble instead of an 
attached document. A message header from a bad email is below.

When we scan a document from the same device and send it to a mailbox that 
still lives on our last remaining Exchange 2003 server, the output from the 
scanner is attached as a PDF document normally.



Any ideas?



Thanks

Michael Buckley





Header from email recieved to Exchange 2007:

(server names and IPs have been replaced with X's)



eceived: from mail.xxx.xx (192.168.xx.x) by xx.xxx.xxx
 (192.168.xx.xx) with Microsoft SMTP Server id 8.0.685.24; Tue, 17 Apr 2007
 15:26:33 -0700
Received: from 192.168.xx.x ([192.168.xx.x]) by mail.xx.xx with
 Microsoft SMTPSVC(6.0.3790.3959);  Tue, 17 Apr 2007 15:26:30 -0700
From: <dellscanner@
Message-ID: <12891110460.0@t37>
To: <MBUCKLEY
Subject: =?utf-8?B?U2Nhbm5lZCBQYWdl?=
MIME-Version: 1.0
Content-Type: text/plain
Content-features: (& (& (dpi=100) (dpi-xyratio=[100/100]))
 (image-coding=MH))
Return-Path: dellscanner@
X-OriginalArrivalTime: 17 Apr 2007 22:26:30.0004 (UTC) 
FILETIME=[7211CB40:01C7813F]
Date: Tue, 17 Apr 2007 15:26:30 -0700
X-MS-Exchange-Organization-SCL: 4




first 8 lines or so of the body:

--11668007101709953148-1016437553937876489-2017287855890095725-6275025531135084631

Content-Type: TEXT/PLAIN; charset=ISO-8859-1







--11668007101709953148-1016437553937876489-2017287855890095725-6275025531135084631

Content-Type: application/pdf

Content-Transfer-Encoding: BASE64

Content-Disposition: attachment; filename="Scann001.pdf"



JVBERi0xLjQKJeH89vM0IDAgb2JqCjw8L1R5cGUvWE9iamVjdAovU3VidHlwZS9JbWFnZQov

V2lkdGggODMyCi9IZWlnaHQgMTA3OAovQml0c1BlckNvbXBvbmVudCAxCi9Db2xvclNwYWNl

L0RldmljZUdyYXkKL0ZpbHRlclsvQ0NJVFRGYXhEZWNvZGVdCi9EZWNvZGVQYXJtc1s8PC9D

0
mbuckley (3)
4/18/2007 11:47:20 PM
exchange.admin 57650 articles. 2 followers. Follow

10 Replies
239 Views

Similar Articles

[PageSpeed] 26

What is the format/content type supposed to be?  pdf?

The message itself is text/plain

Content-Type: TEXT/PLAIN; charset=ISO-8859-1

With an attachment that is application/pdf

Content-Type: application/pdf

So it appear to be encoded right.  By default,  pdf is mapped, so it's 
likely a client issue.  What client are you using?




"Michael Buckley" <mbuckley@softlanding.ca.nospamtome> wrote in message 
news:eOWu4PhgHHA.4064@TK2MSFTNGP03.phx.gbl...
> Hello
>
>
>
> I have an Exchange 2007 RTM box running in a Windows 2003 only domain.
>
> When we scan a document from our Dell 1815n multifunction and have the 
> output emailed, the document shows up as encoded garble instead of an 
> attached document. A message header from a bad email is below.
>
> When we scan a document from the same device and send it to a mailbox that 
> still lives on our last remaining Exchange 2003 server, the output from 
> the scanner is attached as a PDF document normally.
>
>
>
> Any ideas?
>
>
>
> Thanks
>
> Michael Buckley
>
>
>
>
>
> Header from email recieved to Exchange 2007:
>
> (server names and IPs have been replaced with X's)
>
>
>
> eceived: from mail.xxx.xx (192.168.xx.x) by xx.xxx.xxx
> (192.168.xx.xx) with Microsoft SMTP Server id 8.0.685.24; Tue, 17 Apr 2007
> 15:26:33 -0700
> Received: from 192.168.xx.x ([192.168.xx.x]) by mail.xx.xx with
> Microsoft SMTPSVC(6.0.3790.3959);  Tue, 17 Apr 2007 15:26:30 -0700
> From: <dellscanner@
> Message-ID: <12891110460.0@t37>
> To: <MBUCKLEY
> Subject: =?utf-8?B?U2Nhbm5lZCBQYWdl?=
> MIME-Version: 1.0
> Content-Type: text/plain
> Content-features: (& (& (dpi=100) (dpi-xyratio=[100/100]))
> (image-coding=MH))
> Return-Path: dellscanner@
> X-OriginalArrivalTime: 17 Apr 2007 22:26:30.0004 (UTC) 
> FILETIME=[7211CB40:01C7813F]
> Date: Tue, 17 Apr 2007 15:26:30 -0700
> X-MS-Exchange-Organization-SCL: 4
>
>
>
>
> first 8 lines or so of the body:
>
> --11668007101709953148-1016437553937876489-2017287855890095725-6275025531135084631
>
> Content-Type: TEXT/PLAIN; charset=ISO-8859-1
>
>
>
>
>
>
>
> --11668007101709953148-1016437553937876489-2017287855890095725-6275025531135084631
>
> Content-Type: application/pdf
>
> Content-Transfer-Encoding: BASE64
>
> Content-Disposition: attachment; filename="Scann001.pdf"
>
>
>
> JVBERi0xLjQKJeH89vM0IDAgb2JqCjw8L1R5cGUvWE9iamVjdAovU3VidHlwZS9JbWFnZQov
>
> V2lkdGggODMyCi9IZWlnaHQgMTA3OAovQml0c1BlckNvbXBvbmVudCAxCi9Db2xvclNwYWNl
>
> L0RldmljZUdyYXkKL0ZpbHRlclsvQ0NJVFRGYXhEZWNvZGVdCi9EZWNvZGVQYXJtc1s8PC9D
> 


0
John
4/20/2007 12:10:46 AM
The document to be attached is a PDF... But the result is the same if we 
tell the scanner to do TIFF or JPEG.
Clients used: Outlook 2007, 2003, OWA 2007, Hotmail, Gmail, local ISP 
webmail, all with the same result.

the trick is that the messages that appear in all of those clients that have 
gone through Exchange 2007 are Base64 encoded and wrecked.
Messages that appear in all of those clients that go directly to Exchange 
2003 and go anywhere BUT 2007, have correct attachments and display 
correctly, but are 7Bit MIME encoded.

It seems that Exchange 2007 is re-converting them at some point and its 
blowing it up.
And further down the message it does show the application/pdf
">> Content-Type: application/pdf
>>
>> Content-Transfer-Encoding: BASE64"

Thanks


"John Fullbright" <fjohn@donotspamnetappdotcom> wrote in message 
news:O1TUaBugHHA.284@TK2MSFTNGP05.phx.gbl...
> What is the format/content type supposed to be?  pdf?
>
> The message itself is text/plain
>
> Content-Type: TEXT/PLAIN; charset=ISO-8859-1
>
> With an attachment that is application/pdf
>
> Content-Type: application/pdf
>
> So it appear to be encoded right.  By default,  pdf is mapped, so it's 
> likely a client issue.  What client are you using?
>
>
>
>
> "Michael Buckley" <mbuckley@softlanding.ca.nospamtome> wrote in message 
> news:eOWu4PhgHHA.4064@TK2MSFTNGP03.phx.gbl...
>> Hello
>>
>>
>>
>> I have an Exchange 2007 RTM box running in a Windows 2003 only domain.
>>
>> When we scan a document from our Dell 1815n multifunction and have the 
>> output emailed, the document shows up as encoded garble instead of an 
>> attached document. A message header from a bad email is below.
>>
>> When we scan a document from the same device and send it to a mailbox 
>> that still lives on our last remaining Exchange 2003 server, the output 
>> from the scanner is attached as a PDF document normally.
>>
>>
>>
>> Any ideas?
>>
>>
>>
>> Thanks
>>
>> Michael Buckley
>>
>>
>>
>>
>>
>> Header from email recieved to Exchange 2007:
>>
>> (server names and IPs have been replaced with X's)
>>
>>
>>
>> eceived: from mail.xxx.xx (192.168.xx.x) by xx.xxx.xxx
>> (192.168.xx.xx) with Microsoft SMTP Server id 8.0.685.24; Tue, 17 Apr 
>> 2007
>> 15:26:33 -0700
>> Received: from 192.168.xx.x ([192.168.xx.x]) by mail.xx.xx with
>> Microsoft SMTPSVC(6.0.3790.3959);  Tue, 17 Apr 2007 15:26:30 -0700
>> From: <dellscanner@
>> Message-ID: <12891110460.0@t37>
>> To: <MBUCKLEY
>> Subject: =?utf-8?B?U2Nhbm5lZCBQYWdl?=
>> MIME-Version: 1.0
>> Content-Type: text/plain
>> Content-features: (& (& (dpi=100) (dpi-xyratio=[100/100]))
>> (image-coding=MH))
>> Return-Path: dellscanner@
>> X-OriginalArrivalTime: 17 Apr 2007 22:26:30.0004 (UTC) 
>> FILETIME=[7211CB40:01C7813F]
>> Date: Tue, 17 Apr 2007 15:26:30 -0700
>> X-MS-Exchange-Organization-SCL: 4
>>
>>
>>
>>
>> first 8 lines or so of the body:
>>
>> --11668007101709953148-1016437553937876489-2017287855890095725-6275025531135084631
>>
>> Content-Type: TEXT/PLAIN; charset=ISO-8859-1
>>
>>
>>
>>
>>
>>
>>
>> --11668007101709953148-1016437553937876489-2017287855890095725-6275025531135084631
>>
>> Content-Type: application/pdf
>>
>> Content-Transfer-Encoding: BASE64
>>
>> Content-Disposition: attachment; filename="Scann001.pdf"
>>
>>
>>
>> JVBERi0xLjQKJeH89vM0IDAgb2JqCjw8L1R5cGUvWE9iamVjdAovU3VidHlwZS9JbWFnZQov
>>
>> V2lkdGggODMyCi9IZWlnaHQgMTA3OAovQml0c1BlckNvbXBvbmVudCAxCi9Db2xvclNwYWNl
>>
>> L0RldmljZUdyYXkKL0ZpbHRlclsvQ0NJVFRGYXhEZWNvZGVdCi9EZWNvZGVQYXJtc1s8PC9D
>>
>
> 

0
mbuckley (3)
4/20/2007 2:08:59 AM
You can force 7 bit MIME in Exchange 2007.


"Michael Buckley" <mbuckley@softlanding.ca.nospamtome> wrote in message 
news:OrKitDvgHHA.4692@TK2MSFTNGP04.phx.gbl...
> The document to be attached is a PDF... But the result is the same if we 
> tell the scanner to do TIFF or JPEG.
> Clients used: Outlook 2007, 2003, OWA 2007, Hotmail, Gmail, local ISP 
> webmail, all with the same result.
>
> the trick is that the messages that appear in all of those clients that 
> have gone through Exchange 2007 are Base64 encoded and wrecked.
> Messages that appear in all of those clients that go directly to Exchange 
> 2003 and go anywhere BUT 2007, have correct attachments and display 
> correctly, but are 7Bit MIME encoded.
>
> It seems that Exchange 2007 is re-converting them at some point and its 
> blowing it up.
> And further down the message it does show the application/pdf
> ">> Content-Type: application/pdf
>>>
>>> Content-Transfer-Encoding: BASE64"
>
> Thanks
>
>
> "John Fullbright" <fjohn@donotspamnetappdotcom> wrote in message 
> news:O1TUaBugHHA.284@TK2MSFTNGP05.phx.gbl...
>> What is the format/content type supposed to be?  pdf?
>>
>> The message itself is text/plain
>>
>> Content-Type: TEXT/PLAIN; charset=ISO-8859-1
>>
>> With an attachment that is application/pdf
>>
>> Content-Type: application/pdf
>>
>> So it appear to be encoded right.  By default,  pdf is mapped, so it's 
>> likely a client issue.  What client are you using?
>>
>>
>>
>>
>> "Michael Buckley" <mbuckley@softlanding.ca.nospamtome> wrote in message 
>> news:eOWu4PhgHHA.4064@TK2MSFTNGP03.phx.gbl...
>>> Hello
>>>
>>>
>>>
>>> I have an Exchange 2007 RTM box running in a Windows 2003 only domain.
>>>
>>> When we scan a document from our Dell 1815n multifunction and have the 
>>> output emailed, the document shows up as encoded garble instead of an 
>>> attached document. A message header from a bad email is below.
>>>
>>> When we scan a document from the same device and send it to a mailbox 
>>> that still lives on our last remaining Exchange 2003 server, the output 
>>> from the scanner is attached as a PDF document normally.
>>>
>>>
>>>
>>> Any ideas?
>>>
>>>
>>>
>>> Thanks
>>>
>>> Michael Buckley
>>>
>>>
>>>
>>>
>>>
>>> Header from email recieved to Exchange 2007:
>>>
>>> (server names and IPs have been replaced with X's)
>>>
>>>
>>>
>>> eceived: from mail.xxx.xx (192.168.xx.x) by xx.xxx.xxx
>>> (192.168.xx.xx) with Microsoft SMTP Server id 8.0.685.24; Tue, 17 Apr 
>>> 2007
>>> 15:26:33 -0700
>>> Received: from 192.168.xx.x ([192.168.xx.x]) by mail.xx.xx with
>>> Microsoft SMTPSVC(6.0.3790.3959);  Tue, 17 Apr 2007 15:26:30 -0700
>>> From: <dellscanner@
>>> Message-ID: <12891110460.0@t37>
>>> To: <MBUCKLEY
>>> Subject: =?utf-8?B?U2Nhbm5lZCBQYWdl?=
>>> MIME-Version: 1.0
>>> Content-Type: text/plain
>>> Content-features: (& (& (dpi=100) (dpi-xyratio=[100/100]))
>>> (image-coding=MH))
>>> Return-Path: dellscanner@
>>> X-OriginalArrivalTime: 17 Apr 2007 22:26:30.0004 (UTC) 
>>> FILETIME=[7211CB40:01C7813F]
>>> Date: Tue, 17 Apr 2007 15:26:30 -0700
>>> X-MS-Exchange-Organization-SCL: 4
>>>
>>>
>>>
>>>
>>> first 8 lines or so of the body:
>>>
>>> --11668007101709953148-1016437553937876489-2017287855890095725-6275025531135084631
>>>
>>> Content-Type: TEXT/PLAIN; charset=ISO-8859-1
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> --11668007101709953148-1016437553937876489-2017287855890095725-6275025531135084631
>>>
>>> Content-Type: application/pdf
>>>
>>> Content-Transfer-Encoding: BASE64
>>>
>>> Content-Disposition: attachment; filename="Scann001.pdf"
>>>
>>>
>>>
>>> JVBERi0xLjQKJeH89vM0IDAgb2JqCjw8L1R5cGUvWE9iamVjdAovU3VidHlwZS9JbWFnZQov
>>>
>>> V2lkdGggODMyCi9IZWlnaHQgMTA3OAovQml0c1BlckNvbXBvbmVudCAxCi9Db2xvclNwYWNl
>>>
>>> L0RldmljZUdyYXkKL0ZpbHRlclsvQ0NJVFRGYXhEZWNvZGVdCi9EZWNvZGVQYXJtc1s8PC9D
>>>
>>
>>
> 


0
John
4/23/2007 1:48:37 PM
Excellent.
How?


"John Fullbright" <fjohn@donotspamnetappdotcom> wrote in message 
news:O9iKZ4ahHHA.4596@TK2MSFTNGP05.phx.gbl...
> You can force 7 bit MIME in Exchange 2007.
>
>
> "Michael Buckley" <mbuckley@softlanding.ca.nospamtome> wrote in message 
> news:OrKitDvgHHA.4692@TK2MSFTNGP04.phx.gbl...
>> The document to be attached is a PDF... But the result is the same if we 
>> tell the scanner to do TIFF or JPEG.
>> Clients used: Outlook 2007, 2003, OWA 2007, Hotmail, Gmail, local ISP 
>> webmail, all with the same result.
>>
>> the trick is that the messages that appear in all of those clients that 
>> have gone through Exchange 2007 are Base64 encoded and wrecked.
>> Messages that appear in all of those clients that go directly to Exchange 
>> 2003 and go anywhere BUT 2007, have correct attachments and display 
>> correctly, but are 7Bit MIME encoded.
>>
>> It seems that Exchange 2007 is re-converting them at some point and its 
>> blowing it up.
>> And further down the message it does show the application/pdf
>> ">> Content-Type: application/pdf
>>>>
>>>> Content-Transfer-Encoding: BASE64"
>>
>> Thanks
>>
>>
>> "John Fullbright" <fjohn@donotspamnetappdotcom> wrote in message 
>> news:O1TUaBugHHA.284@TK2MSFTNGP05.phx.gbl...
>>> What is the format/content type supposed to be?  pdf?
>>>
>>> The message itself is text/plain
>>>
>>> Content-Type: TEXT/PLAIN; charset=ISO-8859-1
>>>
>>> With an attachment that is application/pdf
>>>
>>> Content-Type: application/pdf
>>>
>>> So it appear to be encoded right.  By default,  pdf is mapped, so it's 
>>> likely a client issue.  What client are you using?
>>>
>>>
>>>
>>>
>>> "Michael Buckley" <mbuckley@softlanding.ca.nospamtome> wrote in message 
>>> news:eOWu4PhgHHA.4064@TK2MSFTNGP03.phx.gbl...
>>>> Hello
>>>>
>>>>
>>>>
>>>> I have an Exchange 2007 RTM box running in a Windows 2003 only domain.
>>>>
>>>> When we scan a document from our Dell 1815n multifunction and have the 
>>>> output emailed, the document shows up as encoded garble instead of an 
>>>> attached document. A message header from a bad email is below.
>>>>
>>>> When we scan a document from the same device and send it to a mailbox 
>>>> that still lives on our last remaining Exchange 2003 server, the output 
>>>> from the scanner is attached as a PDF document normally.
>>>>
>>>>
>>>>
>>>> Any ideas?
>>>>
>>>>
>>>>
>>>> Thanks
>>>>
>>>> Michael Buckley
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> Header from email recieved to Exchange 2007:
>>>>
>>>> (server names and IPs have been replaced with X's)
>>>>
>>>>
>>>>
>>>> eceived: from mail.xxx.xx (192.168.xx.x) by xx.xxx.xxx
>>>> (192.168.xx.xx) with Microsoft SMTP Server id 8.0.685.24; Tue, 17 Apr 
>>>> 2007
>>>> 15:26:33 -0700
>>>> Received: from 192.168.xx.x ([192.168.xx.x]) by mail.xx.xx with
>>>> Microsoft SMTPSVC(6.0.3790.3959);  Tue, 17 Apr 2007 15:26:30 -0700
>>>> From: <dellscanner@
>>>> Message-ID: <12891110460.0@t37>
>>>> To: <MBUCKLEY
>>>> Subject: =?utf-8?B?U2Nhbm5lZCBQYWdl?=
>>>> MIME-Version: 1.0
>>>> Content-Type: text/plain
>>>> Content-features: (& (& (dpi=100) (dpi-xyratio=[100/100]))
>>>> (image-coding=MH))
>>>> Return-Path: dellscanner@
>>>> X-OriginalArrivalTime: 17 Apr 2007 22:26:30.0004 (UTC) 
>>>> FILETIME=[7211CB40:01C7813F]
>>>> Date: Tue, 17 Apr 2007 15:26:30 -0700
>>>> X-MS-Exchange-Organization-SCL: 4
>>>>
>>>>
>>>>
>>>>
>>>> first 8 lines or so of the body:
>>>>
>>>> --11668007101709953148-1016437553937876489-2017287855890095725-6275025531135084631
>>>>
>>>> Content-Type: TEXT/PLAIN; charset=ISO-8859-1
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> --11668007101709953148-1016437553937876489-2017287855890095725-6275025531135084631
>>>>
>>>> Content-Type: application/pdf
>>>>
>>>> Content-Transfer-Encoding: BASE64
>>>>
>>>> Content-Disposition: attachment; filename="Scann001.pdf"
>>>>
>>>>
>>>>
>>>> JVBERi0xLjQKJeH89vM0IDAgb2JqCjw8L1R5cGUvWE9iamVjdAovU3VidHlwZS9JbWFnZQov
>>>>
>>>> V2lkdGggODMyCi9IZWlnaHQgMTA3OAovQml0c1BlckNvbXBvbmVudCAxCi9Db2xvclNwYWNl
>>>>
>>>> L0RldmljZUdyYXkKL0ZpbHRlclsvQ0NJVFRGYXhEZWNvZGVdCi9EZWNvZGVQYXJtc1s8PC9D
>>>>
>>>
>>>
>>
>
> 

0
mbuckley (3)
4/23/2007 2:10:42 PM
On the receive connector on the transport server.

http://technet.microsoft.com/en-us/library/bb125139.aspx

EightBitMimeEnabled





"michael Buckley" <mbuckley@softlanding.ca.nospam> wrote in message 
news:OfLbwFbhHHA.4288@TK2MSFTNGP03.phx.gbl...
> Excellent.
> How?
>
>
> "John Fullbright" <fjohn@donotspamnetappdotcom> wrote in message 
> news:O9iKZ4ahHHA.4596@TK2MSFTNGP05.phx.gbl...
>> You can force 7 bit MIME in Exchange 2007.
>>
>>
>> "Michael Buckley" <mbuckley@softlanding.ca.nospamtome> wrote in message 
>> news:OrKitDvgHHA.4692@TK2MSFTNGP04.phx.gbl...
>>> The document to be attached is a PDF... But the result is the same if we 
>>> tell the scanner to do TIFF or JPEG.
>>> Clients used: Outlook 2007, 2003, OWA 2007, Hotmail, Gmail, local ISP 
>>> webmail, all with the same result.
>>>
>>> the trick is that the messages that appear in all of those clients that 
>>> have gone through Exchange 2007 are Base64 encoded and wrecked.
>>> Messages that appear in all of those clients that go directly to 
>>> Exchange 2003 and go anywhere BUT 2007, have correct attachments and 
>>> display correctly, but are 7Bit MIME encoded.
>>>
>>> It seems that Exchange 2007 is re-converting them at some point and its 
>>> blowing it up.
>>> And further down the message it does show the application/pdf
>>> ">> Content-Type: application/pdf
>>>>>
>>>>> Content-Transfer-Encoding: BASE64"
>>>
>>> Thanks
>>>
>>>
>>> "John Fullbright" <fjohn@donotspamnetappdotcom> wrote in message 
>>> news:O1TUaBugHHA.284@TK2MSFTNGP05.phx.gbl...
>>>> What is the format/content type supposed to be?  pdf?
>>>>
>>>> The message itself is text/plain
>>>>
>>>> Content-Type: TEXT/PLAIN; charset=ISO-8859-1
>>>>
>>>> With an attachment that is application/pdf
>>>>
>>>> Content-Type: application/pdf
>>>>
>>>> So it appear to be encoded right.  By default,  pdf is mapped, so it's 
>>>> likely a client issue.  What client are you using?
>>>>
>>>>
>>>>
>>>>
>>>> "Michael Buckley" <mbuckley@softlanding.ca.nospamtome> wrote in message 
>>>> news:eOWu4PhgHHA.4064@TK2MSFTNGP03.phx.gbl...
>>>>> Hello
>>>>>
>>>>>
>>>>>
>>>>> I have an Exchange 2007 RTM box running in a Windows 2003 only domain.
>>>>>
>>>>> When we scan a document from our Dell 1815n multifunction and have the 
>>>>> output emailed, the document shows up as encoded garble instead of an 
>>>>> attached document. A message header from a bad email is below.
>>>>>
>>>>> When we scan a document from the same device and send it to a mailbox 
>>>>> that still lives on our last remaining Exchange 2003 server, the 
>>>>> output from the scanner is attached as a PDF document normally.
>>>>>
>>>>>
>>>>>
>>>>> Any ideas?
>>>>>
>>>>>
>>>>>
>>>>> Thanks
>>>>>
>>>>> Michael Buckley
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> Header from email recieved to Exchange 2007:
>>>>>
>>>>> (server names and IPs have been replaced with X's)
>>>>>
>>>>>
>>>>>
>>>>> eceived: from mail.xxx.xx (192.168.xx.x) by xx.xxx.xxx
>>>>> (192.168.xx.xx) with Microsoft SMTP Server id 8.0.685.24; Tue, 17 Apr 
>>>>> 2007
>>>>> 15:26:33 -0700
>>>>> Received: from 192.168.xx.x ([192.168.xx.x]) by mail.xx.xx with
>>>>> Microsoft SMTPSVC(6.0.3790.3959);  Tue, 17 Apr 2007 15:26:30 -0700
>>>>> From: <dellscanner@
>>>>> Message-ID: <12891110460.0@t37>
>>>>> To: <MBUCKLEY
>>>>> Subject: =?utf-8?B?U2Nhbm5lZCBQYWdl?=
>>>>> MIME-Version: 1.0
>>>>> Content-Type: text/plain
>>>>> Content-features: (& (& (dpi=100) (dpi-xyratio=[100/100]))
>>>>> (image-coding=MH))
>>>>> Return-Path: dellscanner@
>>>>> X-OriginalArrivalTime: 17 Apr 2007 22:26:30.0004 (UTC) 
>>>>> FILETIME=[7211CB40:01C7813F]
>>>>> Date: Tue, 17 Apr 2007 15:26:30 -0700
>>>>> X-MS-Exchange-Organization-SCL: 4
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> first 8 lines or so of the body:
>>>>>
>>>>> --11668007101709953148-1016437553937876489-2017287855890095725-6275025531135084631
>>>>>
>>>>> Content-Type: TEXT/PLAIN; charset=ISO-8859-1
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --11668007101709953148-1016437553937876489-2017287855890095725-6275025531135084631
>>>>>
>>>>> Content-Type: application/pdf
>>>>>
>>>>> Content-Transfer-Encoding: BASE64
>>>>>
>>>>> Content-Disposition: attachment; filename="Scann001.pdf"
>>>>>
>>>>>
>>>>>
>>>>> JVBERi0xLjQKJeH89vM0IDAgb2JqCjw8L1R5cGUvWE9iamVjdAovU3VidHlwZS9JbWFnZQov
>>>>>
>>>>> V2lkdGggODMyCi9IZWlnaHQgMTA3OAovQml0c1BlckNvbXBvbmVudCAxCi9Db2xvclNwYWNl
>>>>>
>>>>> L0RldmljZUdyYXkKL0ZpbHRlclsvQ0NJVFRGYXhEZWNvZGVdCi9EZWNvZGVQYXJtc1s8PC9D
>>>>>
>>>>
>>>>
>>>
>>
>>
> 


0
John
4/23/2007 6:27:49 PM
I changed the EightBitMimeEnabled and BinaryMimeEnabled setting on both 
recieve connectors and it hasn't made any difference.

The thing is that if i copy the text in the body into a base64 decoder, it 
prompts be to download a pdf file that contains the scanned image.


"John Fullbright" wrote:

> On the receive connector on the transport server.
> 
> http://technet.microsoft.com/en-us/library/bb125139.aspx
> 
> EightBitMimeEnabled
> 
> 
> 
> 
> 
> "michael Buckley" <mbuckley@softlanding.ca.nospam> wrote in message 
> news:OfLbwFbhHHA.4288@TK2MSFTNGP03.phx.gbl...
> > Excellent.
> > How?
> >
> >
> > "John Fullbright" <fjohn@donotspamnetappdotcom> wrote in message 
> > news:O9iKZ4ahHHA.4596@TK2MSFTNGP05.phx.gbl...
> >> You can force 7 bit MIME in Exchange 2007.
> >>
> >>
> >> "Michael Buckley" <mbuckley@softlanding.ca.nospamtome> wrote in message 
> >> news:OrKitDvgHHA.4692@TK2MSFTNGP04.phx.gbl...
> >>> The document to be attached is a PDF... But the result is the same if we 
> >>> tell the scanner to do TIFF or JPEG.
> >>> Clients used: Outlook 2007, 2003, OWA 2007, Hotmail, Gmail, local ISP 
> >>> webmail, all with the same result.
> >>>
> >>> the trick is that the messages that appear in all of those clients that 
> >>> have gone through Exchange 2007 are Base64 encoded and wrecked.
> >>> Messages that appear in all of those clients that go directly to 
> >>> Exchange 2003 and go anywhere BUT 2007, have correct attachments and 
> >>> display correctly, but are 7Bit MIME encoded.
> >>>
> >>> It seems that Exchange 2007 is re-converting them at some point and its 
> >>> blowing it up.
> >>> And further down the message it does show the application/pdf
> >>> ">> Content-Type: application/pdf
> >>>>>
> >>>>> Content-Transfer-Encoding: BASE64"
> >>>
> >>> Thanks
> >>>
> >>>
> >>> "John Fullbright" <fjohn@donotspamnetappdotcom> wrote in message 
> >>> news:O1TUaBugHHA.284@TK2MSFTNGP05.phx.gbl...
> >>>> What is the format/content type supposed to be?  pdf?
> >>>>
> >>>> The message itself is text/plain
> >>>>
> >>>> Content-Type: TEXT/PLAIN; charset=ISO-8859-1
> >>>>
> >>>> With an attachment that is application/pdf
> >>>>
> >>>> Content-Type: application/pdf
> >>>>
> >>>> So it appear to be encoded right.  By default,  pdf is mapped, so it's 
> >>>> likely a client issue.  What client are you using?
> >>>>
> >>>>
> >>>>
> >>>>
> >>>> "Michael Buckley" <mbuckley@softlanding.ca.nospamtome> wrote in message 
> >>>> news:eOWu4PhgHHA.4064@TK2MSFTNGP03.phx.gbl...
> >>>>> Hello
> >>>>>
> >>>>>
> >>>>>
> >>>>> I have an Exchange 2007 RTM box running in a Windows 2003 only domain.
> >>>>>
> >>>>> When we scan a document from our Dell 1815n multifunction and have the 
> >>>>> output emailed, the document shows up as encoded garble instead of an 
> >>>>> attached document. A message header from a bad email is below.
> >>>>>
> >>>>> When we scan a document from the same device and send it to a mailbox 
> >>>>> that still lives on our last remaining Exchange 2003 server, the 
> >>>>> output from the scanner is attached as a PDF document normally.
> >>>>>
> >>>>>
> >>>>>
> >>>>> Any ideas?
> >>>>>
> >>>>>
> >>>>>
> >>>>> Thanks
> >>>>>
> >>>>> Michael Buckley
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>> Header from email recieved to Exchange 2007:
> >>>>>
> >>>>> (server names and IPs have been replaced with X's)
> >>>>>
> >>>>>
> >>>>>
> >>>>> eceived: from mail.xxx.xx (192.168.xx.x) by xx.xxx.xxx
> >>>>> (192.168.xx.xx) with Microsoft SMTP Server id 8.0.685.24; Tue, 17 Apr 
> >>>>> 2007
> >>>>> 15:26:33 -0700
> >>>>> Received: from 192.168.xx.x ([192.168.xx.x]) by mail.xx.xx with
> >>>>> Microsoft SMTPSVC(6.0.3790.3959);  Tue, 17 Apr 2007 15:26:30 -0700
> >>>>> From: <dellscanner@
> >>>>> Message-ID: <12891110460.0@t37>
> >>>>> To: <MBUCKLEY
> >>>>> Subject: =?utf-8?B?U2Nhbm5lZCBQYWdl?=
> >>>>> MIME-Version: 1.0
> >>>>> Content-Type: text/plain
> >>>>> Content-features: (& (& (dpi=100) (dpi-xyratio=[100/100]))
> >>>>> (image-coding=MH))
> >>>>> Return-Path: dellscanner@
> >>>>> X-OriginalArrivalTime: 17 Apr 2007 22:26:30.0004 (UTC) 
> >>>>> FILETIME=[7211CB40:01C7813F]
> >>>>> Date: Tue, 17 Apr 2007 15:26:30 -0700
> >>>>> X-MS-Exchange-Organization-SCL: 4
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>> first 8 lines or so of the body:
> >>>>>
> >>>>> --11668007101709953148-1016437553937876489-2017287855890095725-6275025531135084631
> >>>>>
> >>>>> Content-Type: TEXT/PLAIN; charset=ISO-8859-1
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>> --11668007101709953148-1016437553937876489-2017287855890095725-6275025531135084631
> >>>>>
> >>>>> Content-Type: application/pdf
> >>>>>
> >>>>> Content-Transfer-Encoding: BASE64
> >>>>>
> >>>>> Content-Disposition: attachment; filename="Scann001.pdf"
> >>>>>
> >>>>>
> >>>>>
> >>>>> JVBERi0xLjQKJeH89vM0IDAgb2JqCjw8L1R5cGUvWE9iamVjdAovU3VidHlwZS9JbWFnZQov
> >>>>>
> >>>>> V2lkdGggODMyCi9IZWlnaHQgMTA3OAovQml0c1BlckNvbXBvbmVudCAxCi9Db2xvclNwYWNl
> >>>>>
> >>>>> L0RldmljZUdyYXkKL0ZpbHRlclsvQ0NJVFRGYXhEZWNvZGVdCi9EZWNvZGVQYXJtc1s8PC9D
> >>>>>
> >>>>
> >>>>
> >>>
> >>
> >>
> > 
> 
> 
> 
0
Buckley (1)
4/24/2007 10:00:01 PM
Quoting form KB 836555

"Q7: What is Content-Transfer-Encoding?

A7: Different mail systems handle data differently, and some earlier mail 
systems cannot handle multimedia data.

To work around systems that cannot handle multimedia data, an encoding 
scheme is used to convert the data to a uniform 7-bit format. When the 
recipient receives the message, the data is restored to its original format. 
Some examples of Content-Transfer-Encoding formats are:
      . Quoted-printable
      . Base64
      . 8-bit
      . 7-bit
      . Binary



Q8: How is Transfer-Encoding implemented in Exchange 5.5?

A8: Exchange 5.5 encodes in quoted-printable format or in 7-bit format, as 
required. Additionally, Exchange 5.5 encodes messages in base64 format if 
25% of the message is made up of 8-bit characters (that is, characters that 
are outside the US-ASCII range). This applies only to the message body; 
attachments are always base64-encoded.

Q9: How is Transfer-Encoding implemented in Exchange 2000 Server?

A9: Routing group boundaries and SMTP target destinations determine how 
Exchange 2000 Server encodes mail. Exchange 2000 will encode as 
quoted-printable or 7-bit or Transport-Neutral Encapsulation Format (TNEF) 
when sending between two servers/recipients in different routing groups, and 
to the Internet.

Exchange 2000 Server will encode in Binary or Summary TNEF when sending to a 
recipient/server in the same routing group.

Q10: How is Transfer-Encoding implemented in Microsoft Exchange Server 2003?

A10: When routing group boundaries, Exchange and SMTP target destinations 
also determine how Exchange Server 2003 encodes mail.

In mixed mode, Exchange Server 2003 encodes as quoted-printable or 7-bit 
(TNEF format) when sending between two servers/recipients in different 
routing groups and to the Internet.

In native mode, Exchange Server 2003 encodes in Binary (Summary TNEF) when 
sending to a recipient/server in the same or other routing groups."

If you disable 8bit mime, then you should be using a 7 bit format like 
quoted printable.  I wonder if a service needs to restrat to take effect.

John



"Michael Buckley" <Michael Buckley@discussions.microsoft.com> wrote in 
message news:FA3A13EA-02CE-4797-BB1B-05662BCE807D@microsoft.com...
>I changed the EightBitMimeEnabled and BinaryMimeEnabled setting on both
> recieve connectors and it hasn't made any difference.
>
> The thing is that if i copy the text in the body into a base64 decoder, it
> prompts be to download a pdf file that contains the scanned image.
>
>
> "John Fullbright" wrote:
>
>> On the receive connector on the transport server.
>>
>> http://technet.microsoft.com/en-us/library/bb125139.aspx
>>
>> EightBitMimeEnabled
>>
>>
>>
>>
>>
>> "michael Buckley" <mbuckley@softlanding.ca.nospam> wrote in message
>> news:OfLbwFbhHHA.4288@TK2MSFTNGP03.phx.gbl...
>> > Excellent.
>> > How?
>> >
>> >
>> > "John Fullbright" <fjohn@donotspamnetappdotcom> wrote in message
>> > news:O9iKZ4ahHHA.4596@TK2MSFTNGP05.phx.gbl...
>> >> You can force 7 bit MIME in Exchange 2007.
>> >>
>> >>
>> >> "Michael Buckley" <mbuckley@softlanding.ca.nospamtome> wrote in 
>> >> message
>> >> news:OrKitDvgHHA.4692@TK2MSFTNGP04.phx.gbl...
>> >>> The document to be attached is a PDF... But the result is the same if 
>> >>> we
>> >>> tell the scanner to do TIFF or JPEG.
>> >>> Clients used: Outlook 2007, 2003, OWA 2007, Hotmail, Gmail, local ISP
>> >>> webmail, all with the same result.
>> >>>
>> >>> the trick is that the messages that appear in all of those clients 
>> >>> that
>> >>> have gone through Exchange 2007 are Base64 encoded and wrecked.
>> >>> Messages that appear in all of those clients that go directly to
>> >>> Exchange 2003 and go anywhere BUT 2007, have correct attachments and
>> >>> display correctly, but are 7Bit MIME encoded.
>> >>>
>> >>> It seems that Exchange 2007 is re-converting them at some point and 
>> >>> its
>> >>> blowing it up.
>> >>> And further down the message it does show the application/pdf
>> >>> ">> Content-Type: application/pdf
>> >>>>>
>> >>>>> Content-Transfer-Encoding: BASE64"
>> >>>
>> >>> Thanks
>> >>>
>> >>>
>> >>> "John Fullbright" <fjohn@donotspamnetappdotcom> wrote in message
>> >>> news:O1TUaBugHHA.284@TK2MSFTNGP05.phx.gbl...
>> >>>> What is the format/content type supposed to be?  pdf?
>> >>>>
>> >>>> The message itself is text/plain
>> >>>>
>> >>>> Content-Type: TEXT/PLAIN; charset=ISO-8859-1
>> >>>>
>> >>>> With an attachment that is application/pdf
>> >>>>
>> >>>> Content-Type: application/pdf
>> >>>>
>> >>>> So it appear to be encoded right.  By default,  pdf is mapped, so 
>> >>>> it's
>> >>>> likely a client issue.  What client are you using?
>> >>>>
>> >>>>
>> >>>>
>> >>>>
>> >>>> "Michael Buckley" <mbuckley@softlanding.ca.nospamtome> wrote in 
>> >>>> message
>> >>>> news:eOWu4PhgHHA.4064@TK2MSFTNGP03.phx.gbl...
>> >>>>> Hello
>> >>>>>
>> >>>>>
>> >>>>>
>> >>>>> I have an Exchange 2007 RTM box running in a Windows 2003 only 
>> >>>>> domain.
>> >>>>>
>> >>>>> When we scan a document from our Dell 1815n multifunction and have 
>> >>>>> the
>> >>>>> output emailed, the document shows up as encoded garble instead of 
>> >>>>> an
>> >>>>> attached document. A message header from a bad email is below.
>> >>>>>
>> >>>>> When we scan a document from the same device and send it to a 
>> >>>>> mailbox
>> >>>>> that still lives on our last remaining Exchange 2003 server, the
>> >>>>> output from the scanner is attached as a PDF document normally.
>> >>>>>
>> >>>>>
>> >>>>>
>> >>>>> Any ideas?
>> >>>>>
>> >>>>>
>> >>>>>
>> >>>>> Thanks
>> >>>>>
>> >>>>> Michael Buckley
>> >>>>>
>> >>>>>
>> >>>>>
>> >>>>>
>> >>>>>
>> >>>>> Header from email recieved to Exchange 2007:
>> >>>>>
>> >>>>> (server names and IPs have been replaced with X's)
>> >>>>>
>> >>>>>
>> >>>>>
>> >>>>> eceived: from mail.xxx.xx (192.168.xx.x) by xx.xxx.xxx
>> >>>>> (192.168.xx.xx) with Microsoft SMTP Server id 8.0.685.24; Tue, 17 
>> >>>>> Apr
>> >>>>> 2007
>> >>>>> 15:26:33 -0700
>> >>>>> Received: from 192.168.xx.x ([192.168.xx.x]) by mail.xx.xx with
>> >>>>> Microsoft SMTPSVC(6.0.3790.3959);  Tue, 17 Apr 2007 15:26:30 -0700
>> >>>>> From: <dellscanner@
>> >>>>> Message-ID: <12891110460.0@t37>
>> >>>>> To: <MBUCKLEY
>> >>>>> Subject: =?utf-8?B?U2Nhbm5lZCBQYWdl?=
>> >>>>> MIME-Version: 1.0
>> >>>>> Content-Type: text/plain
>> >>>>> Content-features: (& (& (dpi=100) (dpi-xyratio=[100/100]))
>> >>>>> (image-coding=MH))
>> >>>>> Return-Path: dellscanner@
>> >>>>> X-OriginalArrivalTime: 17 Apr 2007 22:26:30.0004 (UTC)
>> >>>>> FILETIME=[7211CB40:01C7813F]
>> >>>>> Date: Tue, 17 Apr 2007 15:26:30 -0700
>> >>>>> X-MS-Exchange-Organization-SCL: 4
>> >>>>>
>> >>>>>
>> >>>>>
>> >>>>>
>> >>>>> first 8 lines or so of the body:
>> >>>>>
>> >>>>> --11668007101709953148-1016437553937876489-2017287855890095725-6275025531135084631
>> >>>>>
>> >>>>> Content-Type: TEXT/PLAIN; charset=ISO-8859-1
>> >>>>>
>> >>>>>
>> >>>>>
>> >>>>>
>> >>>>>
>> >>>>>
>> >>>>>
>> >>>>> --11668007101709953148-1016437553937876489-2017287855890095725-6275025531135084631
>> >>>>>
>> >>>>> Content-Type: application/pdf
>> >>>>>
>> >>>>> Content-Transfer-Encoding: BASE64
>> >>>>>
>> >>>>> Content-Disposition: attachment; filename="Scann001.pdf"
>> >>>>>
>> >>>>>
>> >>>>>
>> >>>>> JVBERi0xLjQKJeH89vM0IDAgb2JqCjw8L1R5cGUvWE9iamVjdAovU3VidHlwZS9JbWFnZQov
>> >>>>>
>> >>>>> V2lkdGggODMyCi9IZWlnaHQgMTA3OAovQml0c1BlckNvbXBvbmVudCAxCi9Db2xvclNwYWNl
>> >>>>>
>> >>>>> L0RldmljZUdyYXkKL0ZpbHRlclsvQ0NJVFRGYXhEZWNvZGVdCi9EZWNvZGVQYXJtc1s8PC9D
>> >>>>>
>> >>>>
>> >>>>
>> >>>
>> >>
>> >>
>> >
>>
>>
>> 


0
John
4/24/2007 11:54:22 PM
Let's look in technet:

http://technet.microsoft.com/en-us/library/bb232174.aspx
and
http://technet.microsoft.com/en-us/library/bb310794.aspx


"Michael Buckley" <Michael Buckley@discussions.microsoft.com> wrote in 
message news:FA3A13EA-02CE-4797-BB1B-05662BCE807D@microsoft.com...
>I changed the EightBitMimeEnabled and BinaryMimeEnabled setting on both
> recieve connectors and it hasn't made any difference.
>
> The thing is that if i copy the text in the body into a base64 decoder, it
> prompts be to download a pdf file that contains the scanned image.
>
>
> "John Fullbright" wrote:
>
>> On the receive connector on the transport server.
>>
>> http://technet.microsoft.com/en-us/library/bb125139.aspx
>>
>> EightBitMimeEnabled
>>
>>
>>
>>
>>
>> "michael Buckley" <mbuckley@softlanding.ca.nospam> wrote in message
>> news:OfLbwFbhHHA.4288@TK2MSFTNGP03.phx.gbl...
>> > Excellent.
>> > How?
>> >
>> >
>> > "John Fullbright" <fjohn@donotspamnetappdotcom> wrote in message
>> > news:O9iKZ4ahHHA.4596@TK2MSFTNGP05.phx.gbl...
>> >> You can force 7 bit MIME in Exchange 2007.
>> >>
>> >>
>> >> "Michael Buckley" <mbuckley@softlanding.ca.nospamtome> wrote in 
>> >> message
>> >> news:OrKitDvgHHA.4692@TK2MSFTNGP04.phx.gbl...
>> >>> The document to be attached is a PDF... But the result is the same if 
>> >>> we
>> >>> tell the scanner to do TIFF or JPEG.
>> >>> Clients used: Outlook 2007, 2003, OWA 2007, Hotmail, Gmail, local ISP
>> >>> webmail, all with the same result.
>> >>>
>> >>> the trick is that the messages that appear in all of those clients 
>> >>> that
>> >>> have gone through Exchange 2007 are Base64 encoded and wrecked.
>> >>> Messages that appear in all of those clients that go directly to
>> >>> Exchange 2003 and go anywhere BUT 2007, have correct attachments and
>> >>> display correctly, but are 7Bit MIME encoded.
>> >>>
>> >>> It seems that Exchange 2007 is re-converting them at some point and 
>> >>> its
>> >>> blowing it up.
>> >>> And further down the message it does show the application/pdf
>> >>> ">> Content-Type: application/pdf
>> >>>>>
>> >>>>> Content-Transfer-Encoding: BASE64"
>> >>>
>> >>> Thanks
>> >>>
>> >>>
>> >>> "John Fullbright" <fjohn@donotspamnetappdotcom> wrote in message
>> >>> news:O1TUaBugHHA.284@TK2MSFTNGP05.phx.gbl...
>> >>>> What is the format/content type supposed to be?  pdf?
>> >>>>
>> >>>> The message itself is text/plain
>> >>>>
>> >>>> Content-Type: TEXT/PLAIN; charset=ISO-8859-1
>> >>>>
>> >>>> With an attachment that is application/pdf
>> >>>>
>> >>>> Content-Type: application/pdf
>> >>>>
>> >>>> So it appear to be encoded right.  By default,  pdf is mapped, so 
>> >>>> it's
>> >>>> likely a client issue.  What client are you using?
>> >>>>
>> >>>>
>> >>>>
>> >>>>
>> >>>> "Michael Buckley" <mbuckley@softlanding.ca.nospamtome> wrote in 
>> >>>> message
>> >>>> news:eOWu4PhgHHA.4064@TK2MSFTNGP03.phx.gbl...
>> >>>>> Hello
>> >>>>>
>> >>>>>
>> >>>>>
>> >>>>> I have an Exchange 2007 RTM box running in a Windows 2003 only 
>> >>>>> domain.
>> >>>>>
>> >>>>> When we scan a document from our Dell 1815n multifunction and have 
>> >>>>> the
>> >>>>> output emailed, the document shows up as encoded garble instead of 
>> >>>>> an
>> >>>>> attached document. A message header from a bad email is below.
>> >>>>>
>> >>>>> When we scan a document from the same device and send it to a 
>> >>>>> mailbox
>> >>>>> that still lives on our last remaining Exchange 2003 server, the
>> >>>>> output from the scanner is attached as a PDF document normally.
>> >>>>>
>> >>>>>
>> >>>>>
>> >>>>> Any ideas?
>> >>>>>
>> >>>>>
>> >>>>>
>> >>>>> Thanks
>> >>>>>
>> >>>>> Michael Buckley
>> >>>>>
>> >>>>>
>> >>>>>
>> >>>>>
>> >>>>>
>> >>>>> Header from email recieved to Exchange 2007:
>> >>>>>
>> >>>>> (server names and IPs have been replaced with X's)
>> >>>>>
>> >>>>>
>> >>>>>
>> >>>>> eceived: from mail.xxx.xx (192.168.xx.x) by xx.xxx.xxx
>> >>>>> (192.168.xx.xx) with Microsoft SMTP Server id 8.0.685.24; Tue, 17 
>> >>>>> Apr
>> >>>>> 2007
>> >>>>> 15:26:33 -0700
>> >>>>> Received: from 192.168.xx.x ([192.168.xx.x]) by mail.xx.xx with
>> >>>>> Microsoft SMTPSVC(6.0.3790.3959);  Tue, 17 Apr 2007 15:26:30 -0700
>> >>>>> From: <dellscanner@
>> >>>>> Message-ID: <12891110460.0@t37>
>> >>>>> To: <MBUCKLEY
>> >>>>> Subject: =?utf-8?B?U2Nhbm5lZCBQYWdl?=
>> >>>>> MIME-Version: 1.0
>> >>>>> Content-Type: text/plain
>> >>>>> Content-features: (& (& (dpi=100) (dpi-xyratio=[100/100]))
>> >>>>> (image-coding=MH))
>> >>>>> Return-Path: dellscanner@
>> >>>>> X-OriginalArrivalTime: 17 Apr 2007 22:26:30.0004 (UTC)
>> >>>>> FILETIME=[7211CB40:01C7813F]
>> >>>>> Date: Tue, 17 Apr 2007 15:26:30 -0700
>> >>>>> X-MS-Exchange-Organization-SCL: 4
>> >>>>>
>> >>>>>
>> >>>>>
>> >>>>>
>> >>>>> first 8 lines or so of the body:
>> >>>>>
>> >>>>> --11668007101709953148-1016437553937876489-2017287855890095725-6275025531135084631
>> >>>>>
>> >>>>> Content-Type: TEXT/PLAIN; charset=ISO-8859-1
>> >>>>>
>> >>>>>
>> >>>>>
>> >>>>>
>> >>>>>
>> >>>>>
>> >>>>>
>> >>>>> --11668007101709953148-1016437553937876489-2017287855890095725-6275025531135084631
>> >>>>>
>> >>>>> Content-Type: application/pdf
>> >>>>>
>> >>>>> Content-Transfer-Encoding: BASE64
>> >>>>>
>> >>>>> Content-Disposition: attachment; filename="Scann001.pdf"
>> >>>>>
>> >>>>>
>> >>>>>
>> >>>>> JVBERi0xLjQKJeH89vM0IDAgb2JqCjw8L1R5cGUvWE9iamVjdAovU3VidHlwZS9JbWFnZQov
>> >>>>>
>> >>>>> V2lkdGggODMyCi9IZWlnaHQgMTA3OAovQml0c1BlckNvbXBvbmVudCAxCi9Db2xvclNwYWNl
>> >>>>>
>> >>>>> L0RldmljZUdyYXkKL0ZpbHRlclsvQ0NJVFRGYXhEZWNvZGVdCi9EZWNvZGVQYXJtc1s8PC9D
>> >>>>>
>> >>>>
>> >>>>
>> >>>
>> >>
>> >>
>> >
>>
>>
>> 


0
John
4/25/2007 12:22:50 AM
So,

I looked very carefully at one that did work for me and:

------=_NextPart_000_000D_01C786B5.9E8B2470
Content-Type: image/jpeg;
 name="attdc2aa.jpg"
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
 filename="attdc2aa.jpg"

/9j/4AAQSkZJRgABAQEAYABgAAD/2wBDAAoHBwgHBgoICAgLCgoLDhgQDg0NDh0VFhEYIx8lJCIf
IiEmKzcvJik0KSEiMEExNDk7Pj4+JS5ESUM8SDc9Pjv/2wBDAQoLCw4NDhwQEBw7KCIoOzs7Ozs7


Then I intentionally mucked it up to look like yours (removed the ; 
name="attdc2aa.jpg");

------=_NextPart_000_000D_01C786B5.9E8B2470
Content-Type: image/jpeg
Content-Transfer-Encoding: base64
Content-Disposition: attachment;  filename="attdc2aa.jpg"

/9j/4AAQSkZJRgABAQEAYABgAAD/2wBDAAoHBwgHBgoICAgLCgoLDhgQDg0NDh0VFhEYIx8lJCIf



 and it broke.

So, then I wen looking for an answer as to why and found: 
http://support.microsoft.com/kb/323226

Specifically "Messages that are composed by MIME clients as a 
multipart/mixed MIME message without a "name" parameter for the 
"content-type" or an optional "filename" parameter for the 
"content-disposition" header may not be rendered correctly when received by 
Exchange.".  I seems that for Exchange 2007, instead of one or the other you 
must have the name parameter.   I think it's time to call PSS, or Dell, or 
Both.

John Fullbright





"Michael Buckley" <Michael Buckley@discussions.microsoft.com> wrote in 
message news:FA3A13EA-02CE-4797-BB1B-05662BCE807D@microsoft.com...
>I changed the EightBitMimeEnabled and BinaryMimeEnabled setting on both
> recieve connectors and it hasn't made any difference.
>
> The thing is that if i copy the text in the body into a base64 decoder, it
> prompts be to download a pdf file that contains the scanned image.
>
>
> "John Fullbright" wrote:
>
>> On the receive connector on the transport server.
>>
>> http://technet.microsoft.com/en-us/library/bb125139.aspx
>>
>> EightBitMimeEnabled
>>
>>
>>
>>
>>
>> "michael Buckley" <mbuckley@softlanding.ca.nospam> wrote in message
>> news:OfLbwFbhHHA.4288@TK2MSFTNGP03.phx.gbl...
>> > Excellent.
>> > How?
>> >
>> >
>> > "John Fullbright" <fjohn@donotspamnetappdotcom> wrote in message
>> > news:O9iKZ4ahHHA.4596@TK2MSFTNGP05.phx.gbl...
>> >> You can force 7 bit MIME in Exchange 2007.
>> >>
>> >>
>> >> "Michael Buckley" <mbuckley@softlanding.ca.nospamtome> wrote in 
>> >> message
>> >> news:OrKitDvgHHA.4692@TK2MSFTNGP04.phx.gbl...
>> >>> The document to be attached is a PDF... But the result is the same if 
>> >>> we
>> >>> tell the scanner to do TIFF or JPEG.
>> >>> Clients used: Outlook 2007, 2003, OWA 2007, Hotmail, Gmail, local ISP
>> >>> webmail, all with the same result.
>> >>>
>> >>> the trick is that the messages that appear in all of those clients 
>> >>> that
>> >>> have gone through Exchange 2007 are Base64 encoded and wrecked.
>> >>> Messages that appear in all of those clients that go directly to
>> >>> Exchange 2003 and go anywhere BUT 2007, have correct attachments and
>> >>> display correctly, but are 7Bit MIME encoded.
>> >>>
>> >>> It seems that Exchange 2007 is re-converting them at some point and 
>> >>> its
>> >>> blowing it up.
>> >>> And further down the message it does show the application/pdf
>> >>> ">> Content-Type: application/pdf
>> >>>>>
>> >>>>> Content-Transfer-Encoding: BASE64"
>> >>>
>> >>> Thanks
>> >>>
>> >>>
>> >>> "John Fullbright" <fjohn@donotspamnetappdotcom> wrote in message
>> >>> news:O1TUaBugHHA.284@TK2MSFTNGP05.phx.gbl...
>> >>>> What is the format/content type supposed to be?  pdf?
>> >>>>
>> >>>> The message itself is text/plain
>> >>>>
>> >>>> Content-Type: TEXT/PLAIN; charset=ISO-8859-1
>> >>>>
>> >>>> With an attachment that is application/pdf
>> >>>>
>> >>>> Content-Type: application/pdf
>> >>>>
>> >>>> So it appear to be encoded right.  By default,  pdf is mapped, so 
>> >>>> it's
>> >>>> likely a client issue.  What client are you using?
>> >>>>
>> >>>>
>> >>>>
>> >>>>
>> >>>> "Michael Buckley" <mbuckley@softlanding.ca.nospamtome> wrote in 
>> >>>> message
>> >>>> news:eOWu4PhgHHA.4064@TK2MSFTNGP03.phx.gbl...
>> >>>>> Hello
>> >>>>>
>> >>>>>
>> >>>>>
>> >>>>> I have an Exchange 2007 RTM box running in a Windows 2003 only 
>> >>>>> domain.
>> >>>>>
>> >>>>> When we scan a document from our Dell 1815n multifunction and have 
>> >>>>> the
>> >>>>> output emailed, the document shows up as encoded garble instead of 
>> >>>>> an
>> >>>>> attached document. A message header from a bad email is below.
>> >>>>>
>> >>>>> When we scan a document from the same device and send it to a 
>> >>>>> mailbox
>> >>>>> that still lives on our last remaining Exchange 2003 server, the
>> >>>>> output from the scanner is attached as a PDF document normally.
>> >>>>>
>> >>>>>
>> >>>>>
>> >>>>> Any ideas?
>> >>>>>
>> >>>>>
>> >>>>>
>> >>>>> Thanks
>> >>>>>
>> >>>>> Michael Buckley
>> >>>>>
>> >>>>>
>> >>>>>
>> >>>>>
>> >>>>>
>> >>>>> Header from email recieved to Exchange 2007:
>> >>>>>
>> >>>>> (server names and IPs have been replaced with X's)
>> >>>>>
>> >>>>>
>> >>>>>
>> >>>>> eceived: from mail.xxx.xx (192.168.xx.x) by xx.xxx.xxx
>> >>>>> (192.168.xx.xx) with Microsoft SMTP Server id 8.0.685.24; Tue, 17 
>> >>>>> Apr
>> >>>>> 2007
>> >>>>> 15:26:33 -0700
>> >>>>> Received: from 192.168.xx.x ([192.168.xx.x]) by mail.xx.xx with
>> >>>>> Microsoft SMTPSVC(6.0.3790.3959);  Tue, 17 Apr 2007 15:26:30 -0700
>> >>>>> From: <dellscanner@
>> >>>>> Message-ID: <12891110460.0@t37>
>> >>>>> To: <MBUCKLEY
>> >>>>> Subject: =?utf-8?B?U2Nhbm5lZCBQYWdl?=
>> >>>>> MIME-Version: 1.0
>> >>>>> Content-Type: text/plain
>> >>>>> Content-features: (& (& (dpi=100) (dpi-xyratio=[100/100]))
>> >>>>> (image-coding=MH))
>> >>>>> Return-Path: dellscanner@
>> >>>>> X-OriginalArrivalTime: 17 Apr 2007 22:26:30.0004 (UTC)
>> >>>>> FILETIME=[7211CB40:01C7813F]
>> >>>>> Date: Tue, 17 Apr 2007 15:26:30 -0700
>> >>>>> X-MS-Exchange-Organization-SCL: 4
>> >>>>>
>> >>>>>
>> >>>>>
>> >>>>>
>> >>>>> first 8 lines or so of the body:
>> >>>>>
>> >>>>> --11668007101709953148-1016437553937876489-2017287855890095725-6275025531135084631
>> >>>>>
>> >>>>> Content-Type: TEXT/PLAIN; charset=ISO-8859-1
>> >>>>>
>> >>>>>
>> >>>>>
>> >>>>>
>> >>>>>
>> >>>>>
>> >>>>>
>> >>>>> --11668007101709953148-1016437553937876489-2017287855890095725-6275025531135084631
>> >>>>>
>> >>>>> Content-Type: application/pdf
>> >>>>>
>> >>>>> Content-Transfer-Encoding: BASE64
>> >>>>>
>> >>>>> Content-Disposition: attachment; filename="Scann001.pdf"
>> >>>>>
>> >>>>>
>> >>>>>
>> >>>>> JVBERi0xLjQKJeH89vM0IDAgb2JqCjw8L1R5cGUvWE9iamVjdAovU3VidHlwZS9JbWFnZQov
>> >>>>>
>> >>>>> V2lkdGggODMyCi9IZWlnaHQgMTA3OAovQml0c1BlckNvbXBvbmVudCAxCi9Db2xvclNwYWNl
>> >>>>>
>> >>>>> L0RldmljZUdyYXkKL0ZpbHRlclsvQ0NJVFRGYXhEZWNvZGVdCi9EZWNvZGVQYXJtc1s8PC9D
>> >>>>>
>> >>>>
>> >>>>
>> >>>
>> >>
>> >>
>> >
>>
>>
>> 


0
John
4/25/2007 5:20:30 AM
Thank you John for your help. 
I have already spoken to Dell and they claim its outside of thier service 
boundary.
I'll see about calling PSS, but now we know... and as they say, knowing is 
half the battle.

Thank you again.

"John Fullbright" wrote:

> So,
> 
> I looked very carefully at one that did work for me and:
> 
> ------=_NextPart_000_000D_01C786B5.9E8B2470
> Content-Type: image/jpeg;
>  name="attdc2aa.jpg"
> Content-Transfer-Encoding: base64
> Content-Disposition: attachment;
>  filename="attdc2aa.jpg"
> 
> /9j/4AAQSkZJRgABAQEAYABgAAD/2wBDAAoHBwgHBgoICAgLCgoLDhgQDg0NDh0VFhEYIx8lJCIf
> IiEmKzcvJik0KSEiMEExNDk7Pj4+JS5ESUM8SDc9Pjv/2wBDAQoLCw4NDhwQEBw7KCIoOzs7Ozs7
> 
> 
> Then I intentionally mucked it up to look like yours (removed the ; 
> name="attdc2aa.jpg");
> 
> ------=_NextPart_000_000D_01C786B5.9E8B2470
> Content-Type: image/jpeg
> Content-Transfer-Encoding: base64
> Content-Disposition: attachment;  filename="attdc2aa.jpg"
> 
> /9j/4AAQSkZJRgABAQEAYABgAAD/2wBDAAoHBwgHBgoICAgLCgoLDhgQDg0NDh0VFhEYIx8lJCIf
> 
> 
> 
>  and it broke.
> 
> So, then I wen looking for an answer as to why and found: 
> http://support.microsoft.com/kb/323226
> 
> Specifically "Messages that are composed by MIME clients as a 
> multipart/mixed MIME message without a "name" parameter for the 
> "content-type" or an optional "filename" parameter for the 
> "content-disposition" header may not be rendered correctly when received by 
> Exchange.".  I seems that for Exchange 2007, instead of one or the other you 
> must have the name parameter.   I think it's time to call PSS, or Dell, or 
> Both.
> 
> John Fullbright
> 
> 
> 
> 
> 
> "Michael Buckley" <Michael Buckley@discussions.microsoft.com> wrote in 
> message news:FA3A13EA-02CE-4797-BB1B-05662BCE807D@microsoft.com...
> >I changed the EightBitMimeEnabled and BinaryMimeEnabled setting on both
> > recieve connectors and it hasn't made any difference.
> >
> > The thing is that if i copy the text in the body into a base64 decoder, it
> > prompts be to download a pdf file that contains the scanned image.
> >
> >
> > "John Fullbright" wrote:
> >
> >> On the receive connector on the transport server.
> >>
> >> http://technet.microsoft.com/en-us/library/bb125139.aspx
> >>
> >> EightBitMimeEnabled
> >>
> >>
> >>
> >>
> >>
> >> "michael Buckley" <mbuckley@softlanding.ca.nospam> wrote in message
> >> news:OfLbwFbhHHA.4288@TK2MSFTNGP03.phx.gbl...
> >> > Excellent.
> >> > How?
> >> >
> >> >
> >> > "John Fullbright" <fjohn@donotspamnetappdotcom> wrote in message
> >> > news:O9iKZ4ahHHA.4596@TK2MSFTNGP05.phx.gbl...
> >> >> You can force 7 bit MIME in Exchange 2007.
> >> >>
> >> >>
> >> >> "Michael Buckley" <mbuckley@softlanding.ca.nospamtome> wrote in 
> >> >> message
> >> >> news:OrKitDvgHHA.4692@TK2MSFTNGP04.phx.gbl...
> >> >>> The document to be attached is a PDF... But the result is the same if 
> >> >>> we
> >> >>> tell the scanner to do TIFF or JPEG.
> >> >>> Clients used: Outlook 2007, 2003, OWA 2007, Hotmail, Gmail, local ISP
> >> >>> webmail, all with the same result.
> >> >>>
> >> >>> the trick is that the messages that appear in all of those clients 
> >> >>> that
> >> >>> have gone through Exchange 2007 are Base64 encoded and wrecked.
> >> >>> Messages that appear in all of those clients that go directly to
> >> >>> Exchange 2003 and go anywhere BUT 2007, have correct attachments and
> >> >>> display correctly, but are 7Bit MIME encoded.
> >> >>>
> >> >>> It seems that Exchange 2007 is re-converting them at some point and 
> >> >>> its
> >> >>> blowing it up.
> >> >>> And further down the message it does show the application/pdf
> >> >>> ">> Content-Type: application/pdf
> >> >>>>>
> >> >>>>> Content-Transfer-Encoding: BASE64"
> >> >>>
> >> >>> Thanks
> >> >>>
> >> >>>
> >> >>> "John Fullbright" <fjohn@donotspamnetappdotcom> wrote in message
> >> >>> news:O1TUaBugHHA.284@TK2MSFTNGP05.phx.gbl...
> >> >>>> What is the format/content type supposed to be?  pdf?
> >> >>>>
> >> >>>> The message itself is text/plain
> >> >>>>
> >> >>>> Content-Type: TEXT/PLAIN; charset=ISO-8859-1
> >> >>>>
> >> >>>> With an attachment that is application/pdf
> >> >>>>
> >> >>>> Content-Type: application/pdf
> >> >>>>
> >> >>>> So it appear to be encoded right.  By default,  pdf is mapped, so 
> >> >>>> it's
> >> >>>> likely a client issue.  What client are you using?
> >> >>>>
> >> >>>>
> >> >>>>
> >> >>>>
> >> >>>> "Michael Buckley" <mbuckley@softlanding.ca.nospamtome> wrote in 
> >> >>>> message
> >> >>>> news:eOWu4PhgHHA.4064@TK2MSFTNGP03.phx.gbl...
> >> >>>>> Hello
> >> >>>>>
> >> >>>>>
> >> >>>>>
> >> >>>>> I have an Exchange 2007 RTM box running in a Windows 2003 only 
> >> >>>>> domain.
> >> >>>>>
> >> >>>>> When we scan a document from our Dell 1815n multifunction and have 
> >> >>>>> the
> >> >>>>> output emailed, the document shows up as encoded garble instead of 
> >> >>>>> an
> >> >>>>> attached document. A message header from a bad email is below.
> >> >>>>>
> >> >>>>> When we scan a document from the same device and send it to a 
> >> >>>>> mailbox
> >> >>>>> that still lives on our last remaining Exchange 2003 server, the
> >> >>>>> output from the scanner is attached as a PDF document normally.
> >> >>>>>
> >> >>>>>
> >> >>>>>
> >> >>>>> Any ideas?
> >> >>>>>
> >> >>>>>
> >> >>>>>
> >> >>>>> Thanks
> >> >>>>>
> >> >>>>> Michael Buckley
> >> >>>>>
> >> >>>>>
> >> >>>>>
> >> >>>>>
> >> >>>>>
> >> >>>>> Header from email recieved to Exchange 2007:
> >> >>>>>
> >> >>>>> (server names and IPs have been replaced with X's)
> >> >>>>>
> >> >>>>>
> >> >>>>>
> >> >>>>> eceived: from mail.xxx.xx (192.168.xx.x) by xx.xxx.xxx
> >> >>>>> (192.168.xx.xx) with Microsoft SMTP Server id 8.0.685.24; Tue, 17 
> >> >>>>> Apr
> >> >>>>> 2007
> >> >>>>> 15:26:33 -0700
> >> >>>>> Received: from 192.168.xx.x ([192.168.xx.x]) by mail.xx.xx with
> >> >>>>> Microsoft SMTPSVC(6.0.3790.3959);  Tue, 17 Apr 2007 15:26:30 -0700
> >> >>>>> From: <dellscanner@
> >> >>>>> Message-ID: <12891110460.0@t37>
> >> >>>>> To: <MBUCKLEY
> >> >>>>> Subject: =?utf-8?B?U2Nhbm5lZCBQYWdl?=
> >> >>>>> MIME-Version: 1.0
> >> >>>>> Content-Type: text/plain
> >> >>>>> Content-features: (& (& (dpi=100) (dpi-xyratio=[100/100]))
> >> >>>>> (image-coding=MH))
> >> >>>>> Return-Path: dellscanner@
> >> >>>>> X-OriginalArrivalTime: 17 Apr 2007 22:26:30.0004 (UTC)
> >> >>>>> FILETIME=[7211CB40:01C7813F]
> >> >>>>> Date: Tue, 17 Apr 2007 15:26:30 -0700
> >> >>>>> X-MS-Exchange-Organization-SCL: 4
> >> >>>>>
> >> >>>>>
> >> >>>>>
> >> >>>>>
> >> >>>>> first 8 lines or so of the body:
> >> >>>>>
> >> >>>>> --11668007101709953148-1016437553937876489-2017287855890095725-6275025531135084631
> >> >>>>>
> >> >>>>> Content-Type: TEXT/PLAIN; charset=ISO-8859-1
> >> >>>>>
> >> >>>>>
> >> >>>>>
> >> >>>>>
> >> >>>>>
> >> >>>>>
> >> >>>>>
> >> >>>>> --11668007101709953148-1016437553937876489-2017287855890095725-6275025531135084631
> >> >>>>>
> >> >>>>> Content-Type: application/pdf
> >> >>>>>
> >> >>>>> Content-Transfer-Encoding: BASE64
> >> >>>>>
> >> >>>>> Content-Disposition: attachment; filename="Scann001.pdf"
> >> >>>>>
> >> >>>>>
> >> >>>>>
> >> >>>>> JVBERi0xLjQKJeH89vM0IDAgb2JqCjw8L1R5cGUvWE9iamVjdAovU3VidHlwZS9JbWFnZQov
> >> >>>>>
> >> >>>>> V2lkdGggODMyCi9IZWlnaHQgMTA3OAovQml0c1BlckNvbXBvbmVudCAxCi9Db2xvclNwYWNl
> >> >>>>>
> >> >>>>> L0RldmljZUdyYXkKL0ZpbHRlclsvQ0NJVFRGYXhEZWNvZGVdCi9EZWNvZGVQYXJtc1s8PC9D
> >> >>>>>
> >> >>>>
> >> >>>>
> >> >>>
> >> >>
> >> >>
> >> >
> >>
> >>
> >> 
> 
> 
> 
0
4/25/2007 4:28:03 PM
Reply:

Similar Artilces:

PF Permission Issue
I have a Contact PF on my Exchange 2003 (running on Windows 2003 Server) server that my users have been accessing for some time now. All other folders are OK but this particular one even though the users, myself included are listed as "Owner", no one is able to copy or move items to it. The message says that the item has been moved or deleted or you may not have sufficient permission. The user is able however to create new items. Thanks, Rafael ...

Exchange in SBS2003 R2
I installed Windows SBS 2003 R2 on a Dell server, everything was working well untill I got the whole network on it. I have about 40 users with mailboxes but a max of 25 users is logon at anytime. The problem I am having is Outlook clients are performing very slow. Other services such as printing and file access are not affected. Now I am wondering if I shouldn't used SBS 2003. I did a little research before going with SBS and found that many people are using SBS2003 with about 40 - 50 users. Here are my Dell PowerEdge 1800 Server Specs 4 160GB SATA 7200 RPM HDD on a RAID 5 confi...

How disable postmaster reply in exchange 5.5
I receive mail from virus in my Exchange 5.5 with this format name@mydomain with a virus attached My exchange server reply with postmaster with the original mail attached. I think that this is Mydoom virus. Please help me to disable NDR messages for any e-mail sent to an invalid address. Virus send e-mail with field FROM with addres that want attack and my exchange reply with postmaster with the original mail that contain mydoom virus. Excuse me for my bad english. It is not possible to disable generation of NDR with E55. Why not install antivirus for Exchange? ALEX wrote: > I rece...

Access 2007 and Vista code problem
I am developing a database on a XP SP2 machine. On a form I have created some buttons with event procedures that run 2 queries and open a form. I sent the db to someone running Access 2007 on a Vista machine and nothing happens when she clicks the buttons and there are no messages. I know nothing about Vista so thanks in advance for any help. Tim Might be a reference problem, have them open the open a code window and click tools references. See what says missing and tell them what should be there, Add it and it should work. Duff "Tim Reid" <TimReid@discussions.micr...

Delegates for SBS2003 Exchange
have SBS2003 Eexchange. users can delegate their folders in Oultook client, but does not have the properties button available after adding users from global address list, to set permissions on folders....the button is grayed out. Do I have to enable this feature somewhere on the server in excahnge manager or AD? ...

Outlook 2007 Search always returns no matches
Any search I do in Outlook 2007's new search box returns no matches. I watched the Indexing Status as it progressed, and now it says "Outlook has finished indexing all of your items" But, searching on anything, even the word "The" or "a" returns no results. I'm searching all Outlook items. I'm on an Exchange Server via VPN. Anyone have any suggestions? I uninstalled Office and re-installed and the problem went away... "Tom" <none@none.com> wrote in message news:%23yGP6NPOHHA.2140@TK2MSFTNGP03.phx.gbl... > Any search I do i...

conversion 04-07-04
anything change over the years.....can Filemaker Pro 4.0 be converted to Access ?? please reply on the Newsgroup, thanks Hi Cat, Not much has changed on this front. You have to export the data from FM into a format Access can read (e.g. CSV), import that into Access, massage the data into a relational structure, and finally re-create the functionality of the FM database using Access's native concepts and tools. On Tue, 6 Apr 2004 19:32:19 -0700, "Cat" <anonymous@discussions.microsoft.com> wrote: >anything change over the years.....can Filemaker Pro 4.0 >be con...

Microsoft Exchange Server
I am using Outlook 2003 for my emails from microsoft exchange server. A few days back I neede to reinstall my windows. Everything with the installation and configuration goes fine at my outlook 2003 but I am unable to get back all of my inbox and Sent items from my microsoft exchange server. I can see some of the items in my inbox and some in sent items however a lot of things are still missing. Can anyone help for this problem? Early response is highly appreciated. Thankyou all, Best Regards, Rizwan. Submitted using http://www.outlookforums.com Are all messages shown whe...

Publisher 2007 frequently crashes
Hello all, I'm having some difficulty with Publisher 2007. Whenever I try to open a particular file, the program crashes. I get no error message, except that Publisher needs to close. I've run Office Diagnostics (twice), with no results. I can open other Publisher files. The file that I am trying to open is an internal website for the company I work for. This file began acting strangely a couple of weeks ago - it wouldn't insert a duplicate page for a while, but I found a workaround, so I didn't worry about it. However, now I think that it may be a part of a larger probl...

Add PowerPoint 2007 to Office Basic
I have Office Basic installed on my laptop and need to add PowerPoint. What is the most recommended, easiest and least expensive way to do this? ...

Using Access 2003 on client to see Sharepoint 2007
Testing a Sharepoint environment and I can easily manipulate and run the database from Access 2007, but when I try to use Access 2003 it wants me to save the database to a location. The Access 2003 has the compatiblity pack, but it seems to not work when I download it. So the question is using Sharepoint 2007 and posting the Access 2007 format to it, can a user go to the sharepoint site and use a 2003 Access database that has the compatibility pack and open without having to download it? -- Message posted via http://www.accessmonster.com Send check for $500.00 to: David A Jenn...

Use exchange from a trusted domain
Hi folks, I have domain a and domain b. Domain a is all set upp with exchange etc. Domain b was bought, and they don't have exchange. I have trust between the domains and file sharing and authentication are ok. What we want to do is, make users on domain b and let them use the exchange (on a seperate storage) on domain a. The users on domain b must logon to domain b, but need to have mailbox on domain a. Domain a are running on win2003 and exchange 2003. Domain are running on win2003 with forest and domain ready for exchange. Any advices? thanks in advance, - Bjarni Hi, Thi...

Change the Exchange Virtual Directory to different website
I would like to remove the exchange virtual directory default website and move it another website which is currently redirecting to the website I want to delete. Meaning rather than logon to OWA as http://www.wheresmylunch.com/exchange (current default website) I want to move to http://www.getyourownsandwich,com/exchange. I am using Exchange 2000 server. Rube You would change the host header on the current website. -- Hope that helps, Dan Townsend This posting is provided "AS IS" with no warranties, and confers no rights. Please do not send email to this address, post a reply t...

VCard issue #2
This is a weird problem, but when I send a vcard to someone, it shows up in my sent items as a vcf file, and has a vcard icon on it, but when the recipient gets the VCard, it shows up as msg file, with an envelope icon as the attachment. When I open it, nothing is there - it's empty. I can't find anything regarding this problem on google or MS's website. Anybody have any ideas? Is it a problem with Outlook? Do I need to do a detect and repair, a reinstallation? Thanks for your help! Does the same happen when you send a message to yourself? Is he/she able to see it w...

Outlook 2007 Calendar -> Outlook 2003
In the past I could forward appointments and birthdays from one PC to another, if both PC's had Office 2003. I just tried forwarding a birthday from Outlook 2007 to Outlook 2003 and it doesn't work. I get the email in 2003. Open it, open the calendar item, then click on Save & Close. No error message. But it's not there. Neither in the current month or for next year. I forwarded it as a reoccurring item, that's the only way it will let you do that. Has anyone else been able to do this? Or, is this a backward compatibility issue? It's odd.... this works fine for...

compact database in VBA access 2007
Hello, I have recently upgrade to office 2007 from office 2003. To compact a database from within the database itself, I used the follwing code. Unfortunately it no longer works in access 2007. Is there some similar code that will work? Public Function FncCompactTheCurrentDB() CommandBars("Menu Bar"). _ Controls("Tools"). _ Controls("Database utilities"). _ Controls("Compact and repair database..."). _ accDoDefaultAction End Function Thank You, SL On Thu, 28 Jan 2010 17:34:01 -0800, SL <SL@discussions.microsoft....

Merge code issues with Publisher 2003
It seems whenever the data source is altered, the merge code fields have to be reinserted in the Publisher document. Is this normal? The data source starts in Excel and is then saved as a .txt file to retain number formatting on final merge. ...

Creating Text Box in Publisher 2007 Crashes the Application
Hello, we have a clean install of Publisher 2007 under Windows XP SP2, and when we try to create a text box in a document, (both an existing document and a blank document), publisher crashes. Office is fully patched. I ran Office Diagnostics from the help menu and no problems were found and the issue persists. Any thoughts on how to resolve the issue? Thanks, Syd See if selecting a different printer as default helps. How to view error signatures if an Office program experiences a serious error and quits http://support.microsoft.com/kb/289508/en-us -- Mary Sauer MSFT MVP http://of...

2 Domains, 1 Exchange Server
Hi, We're trying to go with 2 seperate 2003 domains, but with only one Exchange 2003 Server. What would be needed for the domain that the Exchange server is not in to access e-mail? We've contemplated having those users use OWA, but would really like them to be able to use Outlook 2003. We're a school district and want to segregate the kids domain from the administration domain, but only have funding for one Exchnage server. Any ideas\help will be appreciated. TIA. Hi, This should explain what it requires: http://support.microsoft.com/?id=278888 Leif "tj woo...

Create Exchange mailbox from command line
I'm writing a script using dsadd and I was wondering if it's possible to create an exchange mailbox from the command line. Donovan Maybe not exactly what you want but it may help: http://www.joeware.net/win/free/tools/exchmbx.htm -- Neil Hobson Exchange MVP For Exchange news, links, and tips, check: http://www.msexchangeblog.com "Donovan Linton" <DonovanLinton@discussions.microsoft.com> wrote in message news:D9C839EF-883D-4E2E-8BE9-57782582F043@microsoft.com... > I'm writing a script using dsadd and I was wondering if it's possible to > create an ...

MS Access 2007 code not running
I have created a brand new database in Access 2007 and linked some VB code to run on Form_Load. This code worked perfect with no problems the day I created it. Now today I opened the same form and it is not running the Form_Load code anymore (and yes it is still there, I did not delete it). I got frustrated so I copied and pasted the code to Form_Current and several On_Change events and set breakpoints at the beginning of all the events just to see if it was the Form_Load that was not triggering, but NO events are triggering my VB code. Any ideas? See this page: http://accessjunkie.com/fa...

Quattro Pro .wb1 conversion
I am trying to convert a file created in an older version of Quattro Pro. It has an extension of '.wb1'. The Microsoft fix for QP7 (qp7conv.exe) doesn't work. Thanks T Quit asking the same question over and over and disregarding the responses!!!!! "Tom" <anonymous@discussions.microsoft.com> wrote in message news:531101c49127$f126f230$a301280a@phx.gbl... : I am trying to convert a file created in an older version : of Quattro Pro. It has an extension of '.wb1'. : : The Microsoft fix for QP7 (qp7conv.exe) doesn't work. : : Thanks : T ...

MS Project 2007 question
Hello, I am developing a simple schedule with no resources but 2 tasks out of 100 are hazardous and I would like to make the schedule so that when these tasks occur, no other tasks can occur. In other words, even though all tasks are moving around as the schedule is being developed, I would like to make sure no other tasks can be scheduled wherever these 2 hazardous tasks fall. These 2 tasks are serial to every other task in the schedule. Is there a way to do this? Thanks for your help. Mike Create two milestones. Use milestone 1 as the successor task to all tasks th...

Office 2007 Templates & Themes
Is there anyway the content for Office 2007 at the MS Office web site could be made available to Office:Mac users. Currently need to have OGA validation via ActiveX control or from Office for Windows programs. Surely Mac users could be given access! Dave We have asked that question. We don't have an answer yet (at least, it wasn't "No", that would have been quick!). They are trying to work out how to let us in without letting in all the people using the competitor products. I think they will set up a mirror on the MacTopia site that will allow us to reach the ones tha...

RPC Over HTTP on Single Server
I have installed Exchange 2003 SP1 on a single server and installed and configured OWA. In following KB 833401, it says to add reg. entries to the \NTDS service. I don't have Active Directory installed on the computer. How do I ensure a proper configuration (see below), when this option is not avail. since I did not install AD, as suggested, on the Exchange 2003 server. "Configure all your global catalogs to use specific ports for RPC over HTTP for directory services" HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NTDS\Parameters\NSPI interface protocol sequences...