From js at codeartist.org Mon Nov 20 18:25:09 2006 From: js at codeartist.org (Jochen Schmidt) Date: Mon, 20 Nov 2006 19:25:09 +0100 Subject: [mel-base-devel] utf-8 char encoding Message-ID: <438702EA-4C7B-4C22-B2CA-618AE9920092@codeartist.org> Evrim ULU wrote: > I'm having difficulties while reading utf-8 encoded messages using > mel-base. It seems server stream is us-ascii encoded. Are there any > workarounds for this behaviour or a flexi-stream enchancment patch > that i've missed? I'm using 0.9.17 sbcl. Yes it was intentional to leave the server stream us-ascii encoded. One design-principle of mel-base was, that no message should be altered when it is transfered. I decided to write mel-base after I realized that a Python library, which I used to transfer my messages, altered the format in a braindead way. I've not looked at the code for a while, but it should not be to difficult to wrap a flexi-stream around a particular MESSAGE-BODY-STREAM or PART-BODY-STREAM. There is no real working support for inline MIME encodings yet - I've something half-done but it needs some work. Drop me a mail if this is still an issue for you - Perhaps I'm able to allocate some free time to look at it. ciao, Jochen -------------- next part -------------- An HTML attachment was scrubbed... URL: From js at codeartist.org Mon Nov 20 18:15:32 2006 From: js at codeartist.org (Jochen Schmidt) Date: Mon, 20 Nov 2006 19:15:32 +0100 Subject: [mel-base-devel] Hints about "idiomatic" use? Message-ID: Matthieu Villeneuve wrote: > So far I have a POP3 folder, and a kind of "send/receive" command > that fetches all messages from that folder, using the MEL:MESSAGES > function. I can already see the message headers correctly positioned. > Does that look like the right way to start? If you want to use POP3, then I would fetch all remote messages using COPY-FOLDER from the POP3 folder to a local Maildir-Folder. If you want, you can use MOVE- FOLDER to move instead of copy the messages. You can use MEL:MESSAGES if you want to display what messages are there without actually fetching the messages. The headers will get loaded on demand if you access a header field of a message. If you do access header data in bulk (for example accessing the "From" header-field on all messages) there is the function ENSURE-HEADERS-READ to ensure all headers are available locally before accessing them. > Once this is done, it looks like a message can be either a > MEL:RFC2822-BASIC-MESSAGE, or a MEL:MIME-MESSAGE. In both cases, is > there a simple way to get the message body? You can use MEL:PARTS to get a list of the MIME-Parts of the message. The body of a part can get accessed using MEL:PART-BODY-STRING (or MEL:PART-BODY-STREAM if you want a stream). If you just want the body of the message without taking MIME-Parts into account - you can just use MEL:MESSAGE-BODY-STREAM to access the complete body of the message. But: If you wanted to know how to fetch the body so that you can copy a remote messages body into a local mail-store: Don't do that - just use COPY-FOLDER and copy the whole message. ciao, Jochen -------------- next part -------------- An HTML attachment was scrubbed... URL: From js at codeartist.org Tue Nov 28 17:17:31 2006 From: js at codeartist.org (Jochen Schmidt) Date: Tue, 28 Nov 2006 18:17:31 +0100 Subject: [mel-base-devel] New mel-base release (0.8-0) Message-ID: <0E6D91E9-27E3-461E-A5E5-248BC13C257F@codeartist.org> I've integrated all patches I got last time into a new mel-base release. The new release is available at http://common-lisp.net/project/mel-base/release/mel-base_0.8-0.tar.gz and can get installed using ASDF-Install as ususal. Thanks for your support, Jochen