Anonymous_User Absent Member.
Absent Member.
2412 views

API Gateway has no HTML from Exchange to GroupWise

Greetings everyone, thanks in advance for helping with my issue. Here's my
problem... when an Exchange user sends a HTML email to a GroupWise user
through the API email connector, the email arrives in GroupWise as plain
text and is some times missing content as a result. How can I get these
messages from Exchange to GroupWise in HTML format through the connector.

Some additional information... when a GroupWise user sends a HTML email
through the API email connector to an Exchange user, the Exchange user
does get the HTML message but as an attachment, which is acceptable for
us. I'm running GroupWise 6.5 and Exchange 2003. I'm using the 4.1 SP2 API
gateway and everything is working properly except for HTML messages from
Exchange users to GroupWise users.

Also, if I use internet addressing (not the API connector) the messages
route out to the internet and then back in and keep their HTML format.
Using this method doesn't give me the address book sync or free/busy
search for the calendar though which makes it undesirable.

Thanks,
Kurt

Labels (1)
0 Likes
3 Replies
Anonymous_User Absent Member.
Absent Member.

Re: API Gateway has no HTML from Exchange to GroupWise

AFAIK, this is the way it's always been with the API Gateway.....


After all, it's been around long before html mails....

All I can think of, is upgrading to GW7, and then use the Exchange gateway


--
Best Regards

Tommy Mikkelsen

IT Quality A/S
Denmark

Novell Support Forums SYSOP

Please Report back any success or failure, That way we all learn

Sorry, but no support through email

"I hate bugs".......Tommy Lee Jones, MIB

Be a GroupWiseR, go http://www.groupwiser.net
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: API Gateway has no HTML from Exchange to GroupWise

Why can I send HTML email from GroupWise to Exchange then? The Microsoft
side pieces being used are from Exchange 2003 which knows about HTML. If I
can send HTML one way, the connector must know how to handle the format.
Is it documented somewhere that HTML isn't supported through this older
connector?

I can use the new connector (version 2.0) without moving to GroupWise 7,
right? Using the new connector can I use internet email addresses through
the connector instead of the GroupWise addressing (user@domain.com instead
of GWdomain.GWpostoffice.NDSusername)? Are there any other advantages or
disadvantages of the new 2.0 connector? Is it possible to build and test
the new connector with the old connector still in place? My biggest issue
is that the old connector has been in place for years and will be missed
the minute I take it down to try to implement the new connector. Any tips
or "gotchas" with the new connector that you are aware of?

Thanks for you help,
Kurt

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: API Gateway has no HTML from Exchange to GroupWise

Kurt Cortese wrote:

> Why can I send HTML email from GroupWise to Exchange then? The Microsoft side pieces being used are from Exchange
> 2003 which knows about HTML. If I can send HTML one way, the connector must know how
> to handle the format. Is it documented somewhere that HTML isn't supported through
> this older connector?


Can't find anything documented about this.....

And maybe GW and Exchange handles html mails different....
(In GroupWise, it's simply an attachment named text.html)



> I can use the new connector (version 2.0) without moving to GroupWise 7, right?

I have no idea.....and it's not supported anyway.....

>Using the new connector can I use internet email addresses through the connector
>instead of the GroupWise addressing (user@domain.com instead of GWdomain.GWpostoffice.NDSusername)?


Yes

>Are there any other advantages or disadvantages of the new 2.0 connector? Is it possible to build and
> test the new connector with the old connector still in place? My biggest issue is that the old connector
>has been in place for years and will be missed the minute I take it down to try to implement the new
>connector. Any tips or "gotchas" with the new connector that you are aware of?


I beleave, that due to a native IE addressing,you could simply create a new ext-domain for the new gateway,
but will have all users dubbled in the addressbook until then.....
Why not setup a testlab instead of playing with the production ?


Regarding tips etc.....I've never played with it 😉


--
Best Regards

Tommy Mikkelsen

IT Quality A/S
Denmark

Novell Support Forums SYSOP

Please Report back any success or failure, That way we all learn

Sorry, but no support through email

"I hate bugs".......Tommy Lee Jones, MIB

Be a GroupWiseR, go http://www.groupwiser.net
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.