Hi
I've just started my adventure to make hypermail store binary attachments
instead of simply discarding them (and I'll make it deal with multiple lined
headers and proper mimed ones).
- I'll start modifying my own parse.c now. I guess it's the best fitted for
this.
- I'll extend the 'struct email' with a linked list of the new 'struct
attachment'. It'll contain file name to the binary, file type, name from
the mail, content-id etc. I store files right away, and break the
hypermail habit of keeping everything in memory since attached
(binary) files won't change no matter when they are written to disk :-)
I have not yet decided how to generate good unique-but-repeatable file
names for attachments. Any suggestions?
Daniel Stenberg - http://www.fts.frontec.se/~dast
ech`echo "xiun"|tr nu oc|sed 'sx\([sx]\)\([xoi]\)xo un\2\1 is xg'`ol
Received on Mon 27 Apr 1998 06:42:37 PM GMT