> Such e-mails are created by OWA in some situations (I haven't figured > out when). I'd call this an unfortunate, yet legitimate, situation, > since avoiding it would require changing the default configuration of > a major application. Not that I think M$ has a good reason to do it, > but neither end users nor administrators appear to be "tweaking" > settings to make mail go out encoded.
Sandy, believe it or not, I had a Exchange administrator reply to me on a MS newsgroup board that BASE64 is MIME, and if you do not want OWA to use that, you have to chose Uuencode. While I never followed up or asked any ones opinion, not that it has come up again, read through the attached text file and see what you think. John Tolmachoff MCSE, CSSA IT Manager, Network Engineer RelianceSoft, Inc. Fullerton, CA 92835 www.reliancesoft.com
Here's some info on MIME and BASE64 with links to the RFC's http://hunnysoft.com/mime/ The only way to get Exchange not to use BASE64 is to have it use UUEncode. Don't quote me, but that's been my experience. "John Tolmachoff" <[EMAIL PROTECTED]> wrote in message news:#Wj4a4OnCHA.2392@TK2MSFTNGP12... > If I am corrrect, BASE64 is a implimentation of MIME, most commonaly used > for attachments. > > There are other versions or implimentations of MIME. > > From all the messages I have looked at, OWA on Exchange 2000 is the only > "client" that is encoding the body in BASE64. > > Messages sent from Outlook Express or Outlook 200x, whether by POP3 or MAPI > are encoded by the settings of the client, which in most cases is MIME > version 1. > > Only the messages from OWA are being caught as having BASE64 encoding in the > body, with our without an attachment. > > "Greg Kelley" <[EMAIL PROTECTED]> wrote in message > news:ubUb2iymCHA.1448@TK2MSFTNGP11... > > BASE64 is also known as MIME. I did not give the best instructions below: > > > > 1. Go go System Manager > > 2. Double click on Global Settings > > 3. Click on Internet Message Formats > > 4. On the right hand side, right click on Default and click on Properties > > 5. Click on the Message Format tab and you can see where there is MIME (or > > BASE64) and UUEncode > > > > What I noticed is that some servers don't like MIME, so I setup different > > rules for them instead of modifying the Default settings: > > > > 1. Once in Internet Message Formats, right click on the right hand side > and > > click on New and then Domain > > 2. Supply a descriptive name and then in the "SMTP domain" box put in the > > domain (aol.com, test.com, etc.) that does not like BASE64 > > 3. Click on Apply and then go to the Message Format tab > > 4. Change the Message encoding to be UUEncode > > > > Now any e-mail going to that domain will use UUEncode while the rest of > the > > e-mails will still use MIME or BASE64. > > > > -- > > Greg Kelley > > SS&G Technology Consulting, LLC > > (440) 505-5999 > > http://www.ssgtechnology.com > > > > "John Tolmachoff" <[EMAIL PROTECTED]> wrote in message > > news:#bFJOKlmCHA.2300@TK2MSFTNGP11... > > > BASE64 is not listed there, is there another name for it? > > > > > > "Greg Kelley" <[EMAIL PROTECTED]> wrote in message > > > news:#NHg14ZlCHA.2456@tkmsftngp04... > > > > Go to System Manager. Double click on Global Settings. Right click > on > > > the > > > > Default settings and click on Properties. Click on the Message Format > > tab > > > > and modify from there. > > > > > > > > -- > > > > Greg Kelley > > > > SS&G Technology Consulting, LLC > > > > (440) 505-5999 > > > > http://www.ssgtechnology.com > > > > > > > > "John Tolmachoff" <[EMAIL PROTECTED]> wrote in message > > > > news:uI#BKpNlCHA.1960@tkmsftngp04... > > > > > Messages sent from OWA on an Exchange2000 server are being tagged as > > > using > > > > > BASE64 encoding. > > > > > > > > > > How do I turn of BASE64 encoding? > > > > > > > > > > -- > > > > > John Tolmachoff > > > > > MCSE, CSSA > > > > > Fullerton, CA > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
