[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: evolution header: Mime-version: 1.0



Am Donnerstag, den 04.06.2009, 09:30 +0200 schrieb Christoph Höger:
> Am Mittwoch, den 03.06.2009, 10:09 -0700 schrieb Johannes Erdfelt:
> > On Wed, Jun 03, 2009, Christoph Höger <choeger cs tu-berlin de> wrote:
> > > I see a small problem with evolution when sending to mailinglists. 
> > > Obviously evolution puts: Mime-version: 1.0 in the header, hypermail
> > > searches for MIME-version: and cannot find that string. So it adds it.
> > > In turn my mail provider bounces the return message that should be sent
> > > to me complaining about duplicate header field.
> > > 
> > > So who is wrong here? Hypermail or evolution? Is non uppercase letter
> > > Mime-version allowed? Anyone knowing the answer?
> > 
> > Hypermail.
> > 
> > Headers should be matched in a case insensitive manner.
> > 
> > JE
> 
> Where do you get that conclusion from? I can only cite RFC 2045 which
> says:
> 
> > Messages composed in accordance with this document MUST include such
> >    a header field, with the following verbatim text:
> > 
> >      MIME-Version: 1.0

Found RFC 5234 myself. Thanks.

Attachment: signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]