Problems with eMail from Outlook Web Access

[westmanm]

I have a problem. I've got a setup with PagerGate where most of my users will be sending pages through OWA. The problem is that any messages sent this way have a grabled body. The from line comes through without any problem.
Messages are fine relayed through the same server if Outlook Express is the client, or if I use the GUI client. What could be causing this issue?

Thanks
Mike

[Tech Support]

Is is possible that OWA is configured to only send HTML formatted message bodys? For the most part, all email clients send a plain text version of a message even if they send an HTML formatted message as the primary body format. It is possible that OWA isn't doing this. The problem arises because you can't send HTML formatted documents to pagers, phones, etc.

Check if there is a setting in OWA to send plain text message bodys (at least in addition to the HTML bodys)

_________________
Tech Support
support@notepage.com
http://www.notepage.net

[westmanm]

Thanks for the quick reply. It's possible OWA is only sending HTML. Is there a way to have PageGate log the message body that it receives?

Thanks
Mike

[Tech Support]

Here is how you can capture the raw message:

1. Stop the PageGate server
2. In the PageGate program folder, rename pggmail.exe to pggmail.disabled
3. Start the PageGate server
4. Send a test message
5. Copy the raw file from PageGate's MailIn folder.
6. Stop PageGate
7. Rename pggmail.disabled to pggmail.exe
8. Start PageGate

Take a look at the file you copied in a text editor like notepad.
If you want us to take a look at it, send it attached to an email to forumsupport@notepage.com

_________________
Tech Support
support@notepage.com
http://www.notepage.net

[westmanm]

OK, I got to step 3 but there was no file created. Infact, it's not even lisening on port 25 anymore.

-Mike

[Tech Support]

I have tested the steps here a couple of times and I believe they are correct.

Make sure the file you are renaming is pggmail.exe.

Make sure you are giving PG enough time to star up. Having PG Monitor running ahead of time is usefull to see what is going on.

Give it another shot.

_________________
Tech Support
support@notepage.com
http://www.notepage.net

[westmanm]

Oops. Right file, wrong mailin folder. Anyways, I got the message and the file shows exactly what is transmitted to my pager. The message was:

Subj-Test
Body: Sup?

I've attached the raw file.

BTW, thanks for your help.

-Mike

[code]
Received: from <Michael.Westman@BellevueVFD.org> by pager.bellevuevfd.org ; 20 Jan 04 00:04:16 UT
X-NPSender: Michael.Westman@BellevueVFD.org
Received: from wsip-68-15-231-239.om.om.cox.net [68.15.231.239]
by svr1.dc.bridgescommunications.net
with XWall v3.28 ;
Mon, 19 Jan 2004 18:08:41 -0600
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
charset="utf-8"
Content-Transfer-Encoding: base64
Subject: Test
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
Date: Mon, 19 Jan 2004 18:08:40 -0600
Message-ID: <65113A4867536347B51718515965C19101C555@wsip-68-15-231-238.om.om.cox.net>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: Test
Thread-Index: AcPe6Y8hFm/eHso+Q5CiheSCLePIWg==
From: "Westman, Michael (324)" <Michael.Westman@BellevueVFD.org>
To: <michael.westman@pager.bellevuevfd.org>

U3VwPw0K
[/code]

[Tech Support]

The problem is the line:

Content-Transfer-Encoding: base64

This means that the body of the message has been encoded in 'base64'. This transfer encoding is typically used for non-text content, like attachments. There isn't anything readable in the body because of the encoding. There should be a setting somewhere in OWA to allow the body to be left unencoded.

_________________
Tech Support
support@notepage.com
http://www.notepage.net

[westmanm]

Off to Microsoft. Thanks for your help.

-Mike

[Tech Support]

If you come across the setting, it would be great if you could post it here for other users that may have the same problem.

Thanks.

_________________
Tech Support
support@notepage.com
http://www.notepage.net

[westmanm]

Here is what Microsoft said. I haven't gotten a chance to try it yet.
[quote]
If I understand correctly, you are using Exchange 2000 OWA to send mails, and you want to prevent the message from using base64 encoding. If I have misunderstood four concern, please let me know.

Based on my research, the MAPI clients have the option to send mail in plain text format, so these message were not being encoded. However, the OWA client does not have the option to send mail as plain text.

As a workaround, you can define the message format on Exchange 2000. Please perform the following steps:

1> Please make sure that you have installed the latest service pack for Exchange 2000 server.

2> On Exchange server 2000, open Exchange System Manager.

3> Expand Global Settings -> Internet Message Formats.

4> In the right pane, right click on Default, and click properties.

5> In Message Format tab, select "UUEncode".

6> Click OK.

NOTE: It's also possible to enable UUEncode only for the specified domain. To achieve this, you can create a new domain in Internet Message Formats, and modify the message format on that domain.

For more information, please refer to the following article:

319252 HOW TO: Send Internet E-Mail Messages in an Appropriate Format in
http://support.microsoft.com/?id=319252
[quote]

-Mike

[westmanm]

UPDATE: I followed the procedure above, and it worked great.

Thanks
Mike

[Tech Support]

Thank you for posting your findings Mike.

_________________
Tech Support
support@notepage.com
http://www.notepage.net