Hi
I use MIMEMessage:getAllHeaders() to read all the headers from messages.
In version 1.80 it works well, but after I upgraded to 1.82 on some message
the method gives no headers at all!
The only differense I can see is in the header :
Content-Transfer-Encoding that in some messages is :
Content-transfer-encoding

Is this a bug?

Lennart Mrli, Norway

>I use MIMEMessage:getAllHeaders() to read all the headers from messages.
>In version 1.80 it works well, but after I upgraded to 1.82 on some message
>the method gives no headers at all!
>The only differense I can see is in the header :
>Content-Transfer-Encoding that in some messages is :
>Content-transfer-encoding
>
>Is this a bug?

It is a bug - in the software that created the header with a
lower-case "t" in Transfer.

However, since it would be trivial to either make the search for the
tag case-insensitive or to correct (the memory copy of) the header, I
would recommend that Alaska make a fix.

Regards,

Phil Ide

Xbase++ FAQ
current release: 8,  Monday 4th February 2002, 14:54
***
* Xbase++ FAQ:
*  online  : http://www.idep.org.uk/xbase/xbfaq/xbfaq.htm
*          : www.software-braun.de/xbfaq/xbfaq.htm 
*  download: http://www.idep.org.uk/xbase/xbfaq.zip
*          : www.software-braun.de/xbfaq/xbfaq.zip 
***

Lennart,

Has anyone started "baumbart" lately ?
BaumBart 1.82 doesn't show new messages anymore.

I think it's the same problem: something in MIMEMessage being broke.

Regards,
Frans Vermeulen

Dear Frans,

> Has anyone started "baumbart" lately ?
> BaumBart 1.82 doesn't show new messages anymore.
>
> I think it's the same problem: something in MIMEMessage being broke.
>
Thanks for the hint. Ich checked it and opened an new PDR: 5263
http://www.alaska-software.com/cgi-bin/waa1gate.exe?WAA_PACKAGE=PUBLICDTS&WA
A_FORM=DISPLAYPDR&PDRID=5263

The matter is/was that Baumbart v1.80.284 used undocumented parameters
of MimeMessage() which were changed in 1.82.294 to be consistent with
the Documentation.

All Professional Subscribers does have the possibillity to fix it this way:

  change all
    MimeMessage():New( cMessage )
  to:
    MimeMessage():New():Parse( cMessage )

This will correct the behaviour of Baumbart.


With best regards,

Dominik Hayat
Technical Support
Alaska Software Technology AG

--------------------------------------------------------------------
Technical Support EMEA: support@de.alaska-software.com
Technical Support APRA: support@us.alaska-software.com
News Server:            news.alaska-software.com
Homepage:               http://www.alaska-software.com
WebKnowledgeBase:       http://www.alaska-software.com/kb
--------------------------------------------------------------------

Dominik,

> Thanks for the hint. Ich checked it and opened an new PDR: 5263

Thnx 
It works now, but only _on_the_baumbart-posted_messages_ ))

I don't know if I corrupted some code, but the message I reply to
at the moment, does not show with the new :parse(...) method.

The reason for this AFAICS is, there is no Content-Type in your message.

Anyway, just having a bit of fun with baumbart, which is, by the way
possibly very powerful, when you want to centralize news for many
readers on a network. It is able to serve as a newsserver when few
adaptions are made. I did not realize the possibilities before.

Regards,
Frans Vermeulen