literal

2004-02-18 Thread Chun-Ping Man (STÜBER SOFTWARE)
Dear IMAP-Community, in the chapter formal syntax of the rfc 3501 (IMAP) exist the definition literal (literal = {number}CRLF *CHAR8). That means I get following text?? {1234567890} sdhfios5345$§$%§$§uwehfviohseoiv fwsbfisehvuioweviouwehvioweh+##+''*' dawopdjawopdjopawjdopawjdop Is that

Re: literal

2004-02-18 Thread Abhijit Menon-Sen
At 2004-02-18 14:14:40 +0100, [EMAIL PROTECTED] wrote: Is that text(example) above correct for the type literal??? The length is wrong: There should be 1234567890 characters (a little over 1GB). But please don't post the correct example to the list. :-) -- ams

Compile error

2004-02-18 Thread Frimpong, Jacob
I am trying to install imap (imap-2002e.tar.Z) on Redhat 7.2 When I do "make slx", I get the following message: Building OS-dependent module If you get No such file error messages for files x509.h, ssl.h, pem.h, buffer.h, bio.h, and crypto.h, that means that OpenSSL is not installed

MIME and emails with disclaimers

2004-02-18 Thread HEARSON, CHRIS
When running the following command: 1 UID FETCH 51278 BODY.PEEK[1.MIME] I expect to and usually do receive the following response: * 163 FETCH (BODY[1.MIME] {52} Content-type: text/plain; charset=iso-8859-1 UID 51278) However, if I run the same command against a message that has a

Re: MIME and emails with disclaimers

2004-02-18 Thread Mark Crispin
If you want the Content-Type information, you need to fetch the BODYSTRUCTURE and not the .MIME parts. The .MIME parts only apply to subparts of a multipart. There is no reason to expect that 1.MIME will necessarily return anything interesting. -- Mark -- http://staff.washington.edu/mrc