Commit graph

5 commits

Author SHA1 Message Date
jmmv
8254b930b0 Update to 2.1.9. While here, convert to options.mk for the ipv6 option.
2004-10-01  Jeffrey Stedfast  <fejj@ximian.com>

	* README: Updated

	* configure.in: Bumped version to 2.1.9

2004-09-29  Jeffrey Stedfast  <fejj@ximian.com>

	* gmime/gmime-parser.c (parser_step_headers): Save the entire raw
	part header as well.
	(parser_init): Init the rawbuf (will be used for holding the raw
	part header).
	(parser_close): Free the rawbuf.
	(parser_construct_leaf_part): Set the raw header on the mime part.
	(parser_construct_multipart): Set the raw header on the multipart.
	(parser_construct_message): Don't use g_mime_message_set_mime_part
	or we'll end up clearing the raw header that we worked so hard to
	preserve.
	(parser_scan_message_part): Same.
	(parser_scan_multipart_face): Change comparison to >= so that we
	actually get rid of the last crlf sequence like we meant to.
	(parser_fill): Get rid of the atleast check (it isn't really
	needed and can cause breakage).

	* gmime/gmime-message.c (message_get_headers): Modified to only
	write part headers if the toplevel mime part contains the raw
	header.
	(message_write_to_stream): Same.
	(g_mime_message_set_mime_part): Clear the raw message headers
	since it obviously won't contain the raw message headers.
	(message_add_header): If any message headers change, clear the raw
	header from the toplebel mime part.
	(message_set_header): Same.

	* gmime/gmime-header.c (g_mime_header_set_raw): New function to
	set the raw part header (to be used in place of our own folding if
	available).
	(g_mime_header_has_raw): New function to check if the raw header
	is available.

2004-09-28  Peter Bloomfield  <PeterBloomfield@bellsouth.net>

	* gmime/gmime-multipart-signed.c (sign_prepare): Must treat
	multipart/signed and multipart/encrypetd parts as opaque
	(e.g. don't even attempt to change their encodings).

2004-09-13  Jeffrey Stedfast  <fejj@novell.com>

	* gmime/gmime-message.c (write_addrspec): New folding callback to
	use on addrspec headers.
	(g_mime_message_init): Register write_addrspec for all address
	headers.

	* gmime/gmime-utils.c (header_fold): Fixed the logic a bit for
	structured headers such that we don't break long tokens.

2004-08-22  Jeffrey Stedfast  <fejj@ximian.com>

	* README: Updated.

	* configure.in: Bumped the version to 2.1.8

	* gmime/gmime.h.in: #include <gmime/gmime-session-simple.h> for
	ia64 build fix on Debian (required because of the way gtk-doc's
	scan program works).

	* gmime/gmime-filter-enriched.c (enriched_to_html): Don't replace
	<nofill> with <pre>. Also, replace lone '\n's with a space as
	suggested by rfc1896.

2004-08-08  Jeffrey Stedfast  <fejj@ximian.com>

	* gmime/gmime-multipart-encrypted.c
	(g_mime_multipart_encrypted_encrypt): Don't set encrypted.asc as
	the filename anymore.

	* gmime/gmime-multipart-signed.c (g_mime_multipart_signed_sign):
	Added a hack for Balsa so it can support S/MIME. Also don't set
	the filename to signature.asc. Balsa maintainers don't want this
	*shrug*.
	(g_mime_multipart_signed_verify): Same. These changes really
	require a design change to CipherContext but that'll have to wait.

2004-08-04  Jeffrey Stedfast  <fejj@ximian.com>

	* configure.in: Changed the iconv-detect logic to not error-out on
	fail. The code can properly handle the case where iconv-detect.h
	doesn't exist, so let it do that instead.

2004-07-30  Jeffrey Stedfast  <fejj@novell.com>

	* gmime/gmime-utils.c (rfc2047_encode_get_rfc822_words): Don't use
	g_unichar_isspace() here, we only want to break 'words' on ascii
	lwsp.

2004-07-16  Jeffrey Stedfast  <fejj@ximian.com>

	* gmime/gmime.c (g_mime_init): Make intialisation ref-counted.
	(g_mime_shutdown): Updated.

2004-07-06  Jeffrey Stedfast  <fejj@ximian.com>

	* gmime/gmime-utils.c (rfc2047_encode_get_rfc822_words): Break
	apart long words so that they we don't generate encoded-word
	tokens that are >75 chars. Fixes bug #145497.
2004-11-14 16:48:55 +00:00
jlam
1a280185e1 Mechanical changes to package PLISTs to make use of LIBTOOLIZE_PLIST.
All library names listed by *.la files no longer need to be listed
in the PLIST, e.g., instead of:

	lib/libfoo.a
	lib/libfoo.la
	lib/libfoo.so
	lib/libfoo.so.0
	lib/libfoo.so.0.1

one simply needs:

	lib/libfoo.la

and bsd.pkg.mk will automatically ensure that the additional library
names are listed in the installed package +CONTENTS file.

Also make LIBTOOLIZE_PLIST default to "yes".
2004-09-22 08:09:14 +00:00
recht
f1af76129f update to gmime-2.1.7
This is a bugfix release (including a fix for a possible buffer overrun).
2004-07-23 15:08:56 +00:00
recht
3a425174e4 update to 2.1.6
From the ChangeLog it looks like there were only bugfixes and a few
minor API changes.
2004-07-04 23:10:50 +00:00
recht
c9cb3ded6b initial import of gmime-2.1.3
GMime is a set of utilities for parsing and creating messages using
the Multipurpose Internet Mail Extension (MIME) as defined by the
following RFCs:

 * 0822: Standard for the Format of Arpa Internet Text Messages
 * 1521: MIME (Multipurpose Internet Mail Extensions) Part One:
         Mechanisms for Specifying and Describing the Format of
         Internet Message Bodies
 * 1847: Security Multiparts for MIME: Multipart/Signed and
         Multipart/Encrypted
 * 1864: The Content-MD5 Header Field (Obsoletes rfc1544)
 * 2015: MIME Security with Pretty Good Privacy (PGP)
 * 2045: Multipurpose Internet Mail Extensions (MIME) Part One:
         Format of Internet Message Bodies
 * 2046: Multipurpose Internet Mail Extensions (MIME) Part Two:
         Media Types
 * 2047: Multipurpose Internet Mail Extensions (MIME) Part Three:
         Message Header Extensions for Non-ASCII Text
 * 2048: Multipurpose Internet Mail Extensions (MIME) Part Four:
         Registration Procedures
 * 2049: Multipurpose Internet Mail Extensions (MIME) Part Five:
         Conformance Criteria and Examples
 * 2183: Communicating Presentation Information in Internet Messages:
         The Content-Disposition Header Field
 * 2184: MIME Parameter Value and Encoded Word Extensions: Character
         Sets, Languages, and Continuations
 * 2231: MIME Parameter Value and Encoded Word Extensions: Character
         Sets, Languages, and Continuations (Obsoletes rfc2184)
 * 3156: MIME Security with OpenPGP (Updates rfc2015)
2004-04-08 13:39:29 +00:00