Displaying 4 results from an estimated 4 matches for "rfc1341".
2008 Mar 28
2
[PATCH] oggmerge, various
...nto text. If you think another would be
more appropriate, please tell which. If it would be text/x-kate, I'd see that
more for the textual representation, eg:
kate {
event {
from 0:0:0 to 0:1:0 "Hello, world!"
}
}
I quickly had a search and found:
http://www.w3.org/Protocols/rfc1341/4_Content-Type.html
which seems to corroborate the use of "text/foo" for actual text. However,
I'm not very familiar with all of this, so I'm happy to be corrected and the
content type to be changed.
2008 Mar 20
2
[PATCH] oggmerge, various
On 18/03/2008, Ivo Emanuel Gon?alves <justivo@gmail.com> wrote:
> On 3/17/08, ogg.k.ogg.k@googlemail.com <ogg.k.ogg.k@googlemail.com> wrote:
> > I'm not sure how to go about testing whether they're correct,
> > I know of no tools that check this.
>
>
> From the oggztools, oggz-validate should check properly for any errors.
should, but doesn't
2008 Mar 28
0
[PATCH] oggmerge, various
...ate, please tell which. If it would be text/x-kate, I'd see that
> more for the textual representation, eg:
>
> kate {
> event {
> from 0:0:0 to 0:1:0 "Hello, world!"
> }
> }
>
> I quickly had a search and found:
> http://www.w3.org/Protocols/rfc1341/4_Content-Type.html
> which seems to corroborate the use of "text/foo" for actual text. However,
> I'm not very familiar with all of this, so I'm happy to be corrected and the
> content type to be changed.
>
>
> _______________________________________________...
2006 Sep 11
1
Wrong content-type reported for messages with only a text/html body?
Hi all,
It looks like Dovecot 1.0rc7 reports the wrong content-type for messages
with only a text/html body. An example of such a message is:
---
From: mathijs at izecom.com
Subject: test
To: foobar at example.com
Content-Type: text/html;
test
---
When I talk IMAP to Dovecot directly using telnet and fetch the
bodystructure of this message, Dovecot replies:
* 1 FETCH (BODYSTRUCTURE