[justwippet]

We're having the same issue here with 8830 Curves. Latest version BES and phone OS, and 6.5.7 on GW server and client.

Anybody found the silver bullet for this problem yet?

Thanks!

[jsconyers]

You mean 8330 Curves?

What is the OS on the devices?

[justwippet]

Thanks for responding.

Yes, 8330 Curves (wrote that before coffee). The OS is 4.5.0.77 and the BES for GW is 4.1.6.13.

Rich Content and Download Images Automatically are both enabled on the BES.

[the maddman]

Originally Posted by justwippet

We're having the same issue here with 8830 Curves. Latest version BES and phone OS, and 6.5.7 on GW server and client.

Anybody found the silver bullet for this problem yet?

Thanks!

Is that Groupwise version 6.5.7 on the server and client? You have to be running GW 7.0.3 with the latest FTF to get HTML emails to work.

[justwippet]

Thanks maddman. Can you point me to something that says that 'cause I have people swearing it should work with the 6.5.7 client updated to 11/6/06 (a consultant, for one).

And it's a 6.5.7 GWIA, by the way...

[the maddman]

Originally Posted by justwippet

Thanks maddman. Can you point me to something that says that 'cause I have people swearing it should work with the 6.5.7 client updated to 11/6/06 (a consultant, for one).

And it's a 6.5.7 GWIA, by the way...

I'm double checking the docs, and it looks like you're right. 6.5 should work if fully updated. Sorry, I've been running 7 so long my brain didn't handle the 6 version number right. What's the version of the post office? You should be able to get HTML email even without the Internet Agent running.

[justwippet]

Ha ha, I know the feeling!!

The PO is also 6.5.7. I was looking at the BB Compatibility Matrix and the recommended client IS 7.0.3 HP1 but the 6.5.7 client is, supposedly supported. This HTML issue seems to be pretty widespread with 6.5 but I've stumbled across a few posts from folks who have made it work somehow. So, I'm assuming there's hope, anyway. In typical RIM/Novell fashion, there's probably a "secret patch" out there somewhere!!

[the maddman]

Originally Posted by justwippet

Ha ha, I know the feeling!!

The PO is also 6.5.7. I was looking at the BB Compatibility Matrix and the recommended client IS 7.0.3 HP1 but the 6.5.7 client is, supposedly supported. This HTML issue seems to be pretty widespread with 6.5 but I've stumbled across a few posts from folks who have made it work somehow. So, I'm assuming there's hope, anyway. In typical RIM/Novell fashion, there's probably a "secret patch" out there somewhere!!

BES for Groupwise is definately very picky about what version of client is installed on the server. The 7.x clients seem to all work a lot better to me.

However, if it should work with 6.5, it should work right? Check out your MAGT log and look for lines mentioning HTML. I have entries that read:

[40000] (07/22 00:02:36.218):{0x1D44} GW Client Version: 7.0.3.1068, meets the minimum version: 7.0.2.0, so HTML processing can be supported.

And when an HTML email is processed I see:

[30000] (07/22 00:00:46.531):{0x7A4} HTML is enabled on the server, supported and enabled on the device.
[40000] (07/22 00:00:46.531):{0x7A4} Looking at message: [xxx] to see if message contains HTML.
[40000] (07/22 00:00:46.625):{0x7A4} HTML email requires 1117 bytes for 399 bytes of plain text
[40391] (07/22 00:00:46.906):{0x7A4} {xxx} RefId=-1187835311 references 1 image(s) (in 1500 bytes of body) 1 from MB, 0 from cache, 0 failed. 1 images (1639 bytes) pushed, 1 images (1639 bytes) cached
[30081] (07/22 00:00:46.906):{0x7A4} {xxx} Sending message to device, size=2427, EntryId=4853, RefId=-1187835311, TransactionId=-899323840, Tag=1858938
[40279] (07/22 00:00:46.906):{0x7A4} {xxx} SubmitToRelaySendQ, Tag=1858938

[justwippet]

Thanks for the Magt log idea...duh on my part.

Of course, it says:

[30000] (07/22 07:22:00.373):{0x11CC} HTML is enabled on the server, supported and enabled on the device.

I'm going to take a look at a couple of other things and see if they get me anywhere. According to everything I see - HTML SHOULD be working.