Issue 161 - HTML Messages are rejected
Summary: HTML Messages are rejected
Status: CLOSED NOT_AN_OOO_ISSUE
Alias: None
Product: Infrastructure
Classification: Infrastructure
Component: Mailing lists (show other issues)
Version: current
Hardware: All All
: P3 Trivial (vote)
Target Milestone: ---
Assignee: Unknown
QA Contact: issues@www
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2000-11-16 18:49 UTC by stx123
Modified: 2004-11-29 19:18 UTC (History)
2 users (show)

See Also:
Issue Type: TASK
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments
multipart/alternative message generated by SO5.2 (4.74 KB, text/plain)
2001-08-03 08:16 UTC, stx123
no flags Details
Here is a more recent bounce (12/12/2000) (2.95 KB, text/plain)
2001-08-03 08:16 UTC, stx123
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description stx123 2000-11-16 18:49:42 UTC
HTML Messages for features@<project>.openoffice.org and interface-
announce@openoffice.org are rejected. As standardized headers for features and 
interface changes can't be written in ascii art, can HTML messages be allowed?
Comment 1 Unknown 2000-12-12 08:19:39 UTC
Reassigned to jeremy 
for ownership 
(to coordinate support from chris toward resolution)

Please verify this has been resolved, 
then close issue. 

BTW ... 
is this a duplicate issue?
Comment 2 Unknown 2000-12-12 17:59:20 UTC
Goolie,

Are you able to send and recieve HTML in announce?

--jeremy
Comment 3 Unknown 2000-12-12 18:21:52 UTC
Stefan the last I had heard on this issue was that
the features@test.openoffice.org list was acting
as Stefan wanted.  ie it was allowing HTML email
to be sent to the list, and it was displayed correctly.

If that isn't the case then I  need to know the circumstances
as last time I heard from Stefan this was resolved, or at
least he hadn't replied to my email with any problems.
Shane
Comment 4 stx123 2000-12-12 19:52:37 UTC
Created attachment 50 [details]
multipart/alternative message generated by SO5.2
Comment 5 stx123 2000-12-12 19:59:34 UTC
To summarize a phone call Shane and I had:
features@<project> and interface-announce@ooo seem to work fine (tested with 
features@test) as long as we generate messages with a web form. This form 
generats text/html parts only. We wil switch process going public by using the 
form on 1/2/2001.

The issue left (P2->P3) is that ezmlm doesn't accept MIME messages from 
StarOffice 5.2 which use multipart/alternative. see attachment....
Comment 6 Unknown 2000-12-12 20:19:04 UTC
I looked through the ezmlm-configurations on openoffice.org and noted that
the lists mentioned in this issue do not have 'mimeremove' or 'mimereject'
setting, therefore i'm curious why stefan got the bounce he attached to 
this issue:

> <features@test.openoffice.org>:
> ezmlm-send: fatal: Sorry, after removing unacceptable MIME parts from your
message I was left with nothing (#5.7.0)
> ezmlm-gate: fatal: Fatal error from child

One possible explanation: the bounce stefan sent is from Nov 29, 2000
and it's possible that someone has turned off the ezmlm-customizations which
would force bounces of messages containing HTML.

FYI, as of the time of this writing, the following are the only lists which 
have mimeremove set:

openoffice-ROOT-67-~tigrisq> ll */mimeremove
-rw-------    1 tigrisq  tigris       1599 Nov 21 17:44 project_leads/mimeremove
-rw-------    1 tigrisq  tigris       1599 Nov 15 17:32
project_owners/mimeremove
-rw-------    1 tigrisq  tigris       1599 Oct 24 13:16 test-edk/mimeremove
-rw-------    1 tigrisq  tigris       1599 Dec 12 11:54 test-edk2/mimeremove

(No lists have mimereject set).

The only additional piece of info I can give is to make sure that 
"a few extras" is turned off in the "advanced" mail list configuration
screen. For the lists mentioned in this issue, that appears to be the case. 

Note that ezmlm-make(1) describes the "a few extras" setting as such:

       -x   eXtra.  ezmlm-make will configure the list with a few
            extras: dir/mimeremove will be  configured  to  strip
            annoying  mime  parts such as excel spreadsheets, rtf
            text, html text etc from the messages. Messages  con-
            sisting solely of this Content-type will be rejected.
            See ezmlm-send(1) and ezmlm-reject(1) for more  info.

One other interesting hint from ezmlm-reject(1):

       ezmlm-reject does not handle rfc822 comments in ''Content-
       Type:''  lines  if  present  before  the type or boundary.
       This could be used to defeat the MIME rejection  function.
       OTOH,  this  function  is  intended to reduce garbage, not
       guarantee its elimination.
Comment 7 stx123 2000-12-12 20:51:33 UTC
Created attachment 51 [details]
Here is a more recent bounce (12/12/2000)
Comment 8 stx123 2000-12-12 20:56:47 UTC
P2->P3 (as promised :-)
Comment 9 Unknown 2001-02-02 00:07:19 UTC
To transfer jeremy's issues 
and as this relates to the technical infrastructure, 
reassigning to kat 
for ownership 
(to coordinate technical support as required toward resolution). 
Comment 10 Unknown 2001-02-13 20:37:17 UTC
Accepting issue. 
Neils, was the more recent bounce investigated and resolved?

Kathy
Comment 11 Unknown 2001-02-13 21:19:33 UTC
Sorry Neils, thought you were on the CC list for this issue. Has the most recent
bounce been investigated/resolved?

Kat
Comment 12 Unknown 2001-06-13 03:35:10 UTC
Entering on internal database for tracking pcn4546
Comment 13 Unknown 2001-06-13 18:19:21 UTC
Kat, Edk would be the person to handle this, and I would be
willing to bet it is fixed in SC 1.0.6

It should be brought up before QA, and then tested for in
the 1.0.X tree.  

The way I remember this getting handled on OpenOffice was for
Ed to just go in, and fix the ezmlm setting which were causing
problems.

Either way, I think anzu/our_solid_ezmlm_settings will now handle
HTML mail by default, but QA or edk would be able to answer
definitively.   Shane
Comment 14 Unknown 2001-06-13 18:32:16 UTC
Thank you for your input Shane. I will assign the pcn issue appropriately based
on your suggestions.

Kat
Comment 15 Unknown 2001-07-10 00:41:40 UTC
This has been confirmed as a problem with SC 1.0.6 and has been assigned to a
developer to be addressed.

Thank you
Kat
Comment 16 Unknown 2001-11-08 23:13:48 UTC
changing QA contact from bugs@ to issues@
Comment 17 Unknown 2002-01-15 18:46:18 UTC
Reassigning all of kat's open issues to support so that I can go through them.
Comment 18 lsuarezpotts 2002-01-15 18:59:01 UTC
reassigning to support. I believe that this paleolithic issue may be resolved in a next 
release... or has already been... or is totally irrelevant...
louis
Comment 19 Unknown 2002-01-15 21:31:22 UTC
This is still actually open internally, and is targeted for the 1.3
release.
Comment 20 Unknown 2002-05-17 20:35:40 UTC
Administrative Change; SC1.3 has been renamed SC2.0.
Comment 21 Unknown 2002-08-21 17:33:07 UTC
this item will be closed as the fix is in the 2.0 release
Comment 22 stx123 2002-08-21 17:46:16 UTC
If an item is fixed in a later SC release, please change status to
"resolved/later". Thanks, Stefan.
Comment 23 Unknown 2004-11-29 19:18:27 UTC
Closing this.