Files
evolution/camel
Dan Winship becf944b42 Handle raw 8-bit From data "correctly". (The same way we handle
raw 8-bit Subject data.)

	* camel-mime-utils.c (header_decode_mailbox): Take a charset arg
	and pass it to header_decode_string.
	(header_decode_address): Take a charset arg and pass it to
	header_decode_mailbox.
	(header_mailbox_decode): Likewise.
	(header_address_decode): Take a charset arg and pass it to
	header_decode_address.

	* camel-folder-summary.c (summary_format_address): Take a charset
	arg and pass to header_address_decode.
	(message_info_new, camel_message_info_new_from_header): Pass
	charset to summary_format_address

	* camel-internet-address.c (internet_decode): Update for
	header_address_decode change. (Unfortunately we don't have a
	charset to pass here.)

	* camel-mime-message.c (camel_mime_message_build_mbox_from): Move
	this here from camel-mbox-summary since the same functionality is
	needed by evolution-mail too (and update for header_address_decode
	change)

	* providers/local/camel-mbox-summary.c
	(camel_mbox_summary_build_from): Moved to CamelMimeMessage

svn path=/trunk/; revision=20430
2003-03-20 16:43:29 +00:00
..
2002-03-25 21:47:36 +00:00
2002-03-01 21:39:17 +00:00
2002-06-14 21:33:45 +00:00
2003-02-25 19:43:22 +00:00
2003-02-25 19:43:22 +00:00
2002-03-12 20:36:08 +00:00
2002-06-14 21:33:45 +00:00
2003-02-25 19:43:22 +00:00
2003-02-28 21:55:06 +00:00
2002-11-07 21:34:17 +00:00
2003-03-06 21:42:11 +00:00
2003-03-06 21:42:11 +00:00
2003-03-06 14:47:05 +00:00
2002-03-01 21:39:17 +00:00
2002-07-11 22:30:51 +00:00
2002-03-01 21:39:17 +00:00
2003-03-06 14:39:30 +00:00
2003-03-06 14:39:30 +00:00
2002-07-11 22:30:51 +00:00
2002-03-01 21:39:17 +00:00
2002-03-01 21:39:17 +00:00
2002-03-01 21:39:17 +00:00
2002-11-08 06:59:12 +00:00
2003-02-27 04:53:09 +00:00
2002-06-26 18:49:05 +00:00
2002-10-31 21:41:26 +00:00
2002-06-26 22:15:24 +00:00
2002-06-03 02:56:35 +00:00
2002-06-03 02:56:35 +00:00
2003-03-06 15:22:56 +00:00
2003-03-06 14:47:05 +00:00
2003-03-06 14:47:05 +00:00
2002-05-24 20:14:59 +00:00
2003-02-28 21:55:06 +00:00
2003-02-28 21:55:06 +00:00
2002-07-31 01:03:10 +00:00
2002-07-31 01:03:10 +00:00
2003-03-06 15:22:56 +00:00
2003-03-06 21:42:11 +00:00
2003-02-25 19:43:22 +00:00
2002-06-03 02:56:35 +00:00
2003-03-06 14:39:30 +00:00
2003-03-06 14:39:30 +00:00
2002-03-01 21:39:17 +00:00
2003-02-26 19:40:37 +00:00
2002-01-02 23:04:06 +00:00
2003-03-06 21:42:11 +00:00
2003-03-06 21:42:11 +00:00

                                   CAMEL
     

			A generic Messaging Library


                                   ----
				

Introduction:
-------------

Camel is a generic messaging library. It supports the standard 
messaging system for receiving and sending messages. It is the 
messaging backend for Evolution.

The name "camel" stands for ... nothing. Open area of development there.
You know, that "bazaar" thing. Maybe could we organize a big contest on
gnome-list to find the best explanation :)

Camel draws heavily from JavaMail and the IMAP4rev1 RFC. People
wanting to hack on a provider should read the JavaMail API
specification, but CMC and MAPI are of interest too.

 
Organization:
-------------

The library is roughly a set of abstract classes, some kind of generic
"interfaces" (IDL interfaces, not Java interfaces).

Particular implementations are called providers.

Here are the basic objects:

* CamelService : An abstract class representing an access to a server.
Handles the connection and authentication to any server.

* CamelStore (CamelService): A hierarchy of folders on a server.

* CamelFolder : An object containing messages. A folder is always
associated with a store.

* CamelMessage : An object contained in folders. Is defined by a set
of attributes and a content. (Attributes include: the date it was
received, the sender address, .....)

* CamelTransport (CamelService): A way to send messages.

....
...