[ngw] Groupwise 2012: How to force outgoing mails to HTML-only?

Jeffrey D. Sessler jeff at scrippscollege.edu
Thu Aug 27 18:05:59 UTC 2015


I think GW is working as designed. Even if you compose in HTML, for compatibility reasons, it includes plain text. 

I’d focus on getting your mail security gateway working correctly. I just doesn’t make sense to try and fix something that’s not broken (Groupwise). 




On 8/27/15, 10:08 AM, "ngw-bounces+jeff=scrippscollege.edu at ngwlist.com on behalf of Thieu Hon TRAN" <ngw-bounces+jeff=scrippscollege.edu at ngwlist.com on behalf of k-ngwlist at thtran.de> wrote:

>Yes, I know why most mail-clients default to sending two parts or asking 
>the user if s/he wants to send both or just one version. And as you 
>probably know, there have been lots of discussions and "wars" because 
>some prefer backwards compatibility (i.e. plain-text-lovers ;) while 
>others prefer small mails and don't like the software/server to send 
>redundant data. (HTML-only-fundamentalists, who hate legacy-software ;)
>
>But that's not what I was asking for. I know what I'm doing and I know 
>that Groupwise/GWIA does not adhere to what I selected in the 
>client-options. So I hope that somebody can help me to achieve what I 
>(urgently) need. Or maybe I misunderstood the settings?
>
>I currently have a problem with a bug in our Mailsecurity-Gateway. I 
>think I can work around this bug if the entire mailbody is encoded in 
>Base64. The recipients in this case are clear ("only" a few of our 
>customers) and I know they all use Outlook, so no problem with HTML-only 
>eMails ;)
>
>I opened an SR with Novell.... Wish me luck ;)
>
>    Hon.
>
>Jeffrey D. Sessler:
>> Most email clients I've used will always include both plain-text and HTML if the default compose is HTML. This is to provide backward compatibility for clients that don't understand HTML or for clients that default to reading in plain-text. Makes sense, a client that can't read HTML isn't going to then have support to convert the HTML to something readable.
>>
>> Groupwise in particular allows the two to be different i.e craft your HTML message, switch to plain-text, and craft that portion.
>>
>> At one time, I think the GW client even defaulted to sending plain-text in cases where the message composed in HTML format included no formatting i.e. no reason to bulk-up sending HTML if you're just sending "Hi, test"
>>
>> Jeff 
>>
>> -----Original Message-----
>> From: ngw-bounces+jeff=scrippscollege.edu at ngwlist.com [mailto:ngw-bounces+jeff=scrippscollege.edu at ngwlist.com] On Behalf Of Thieu Hon TRAN
>> Sent: Thursday, August 27, 2015 2:57 AM
>> To: NGWList <ngw at ngwlist.com>
>> Subject: [ngw] Groupwise 2012: How to force outgoing mails to HTML-only?
>>
>> Hello,
>>
>> we're using Groupwise 2012 SP2. "rpm -qa" shows: 
>> novell-groupwise-gwia-12.0.2-108211
>> The Groupwise-client is "Programversion 12.0.2 26.03.2013, Buildnumber 108211"
>>
>> Is it possible to force outgoing mails (to the internet) to html-only? I changed the client options for one mailuser:
>>
>> Client options > Environment > Layouts:
>>     * Allowed layouts for reading:
>>         [ ] Plain text
>>         [x] HTML (Standard)
>>     * Allowed layouts for composing
>>        [ ] Plain text
>>        [x] HTML (Standard)
>> -----------
>> [ ] deactivate HTML-layout  (unticked and LOCKED)
>>
>> Then I stopped the Groupwise-Client, startet Groupwise-Client and sent an eMail. The recipient still gets an eMail with the following:
>> [...]
>> ------1C8EE40D378E108958D32FD4E6EB3B19
>> Mime-Version: 1.0
>> Content-Type: multipart/mixed; boundary="=__Part6A5EEC54.0__="
>>
>> This is a MIME message. If you are reading this text, you may want to consider changing to a mail reader or gateway that understands how to properly handle MIME multipart messages.
>>
>> --=__Part6A5EEC54.0__=
>> Content-Type: multipart/alternative; boundary="=__Part6A5EEC54.1__="
>>
>> --=__Part6A5EEC54.1__=
>> Content-Type: text/plain; charset=UTF-8
>> Content-Transfer-Encoding: 8bit
>>
>> Test: äöüß
>>  
>> MfG, Tran
>>
>> --=__Part6A5EEC54.1__=
>> Content-Type: text/html; charset=UTF-8
>> Content-Transfer-Encoding: base64
>> Content-Description: HTML
>>
>> PEhUTUw+PEhFQUQ+DQo8TUVUQSBjb250ZW50PSJ0ZXh0L2h0bWw7IGNoYXJzZXQ9dXRmLTgi
>> PEhUTUw+PEhFQUQ+IGh0
>> dHAtZXF1aXY9Q29udGVudC1UeXBlPg0KPE1FVEEgbmFtZT1HRU5FUkFUT1IgY29udGVudD0iTVNI
>> VE1MIDguMDAuNjAwMS4yMzU4OCI+PC9IRUFEPg0KPEJPRFkgc3R5bGU9Ik1BUkdJTjogNHB4
>> VE1MIDguMDAuNjAwMS4yMzU4OCI+IDRw
>> eCAxcHg7IEZPTlQ6IDEwcHQgVmVyZGFuYSI+DQo8RElWPlRlc3Q6IMOkw7bDvMOfPC9ESVY+DQo8
>> RElWPiZuYnNwOzwvRElWPg0KPERJVj5NZkcsIFRyYW48L0RJVj48L0JPRFk+PC9IVE1MPg==
>>
>> --=__Part6A5EEC54.1__=--
>> --=__Part6A5EEC54.0__=--
>>
>> ------1C8EE40D378E108958D32FD4E6EB3B19
>> Content-Type: application/x-pkcs7-signature; name="smime.p7s"
>> Content-Transfer-Encoding: base64
>> [...]
>>
>> I'm trying to create HTML-only eMails, because I need mails with base64-encoding-only for testing.
>>
>>     Hon.
>>
>> _______________________________________________
>> ngw mailing list
>> ngw at ngwlist.com
>> http://ngwlist.com/mailman/listinfo/ngw
>> _______________________________________________
>> ngw mailing list
>> ngw at ngwlist.com
>> http://ngwlist.com/mailman/listinfo/ngw
>>   
>
>_______________________________________________
>ngw mailing list
>ngw at ngwlist.com
>http://ngwlist.com/mailman/listinfo/ngw


More information about the ngw mailing list