On 04 Feb 03, Holger Wahlen (H(_dot_)Wahlen(_at_)gmx(_dot_)de) wrote:
I haven't done any testing, but I don't think you should include
"multipart" there if you're going to use lynx for the conversion. I
can't imagine getting decent results from sending an entire multipart
message to lynx - does that really work for you?
Isn't your lynx able to read from standard input? That would make the
temporary file and the locking unnecessary.
Not being too good with procmail, I was using a recipe picked off a
procmail webpage somewhere. I've now simplified the conversion down to
:0 BH
* ^Content-Type.*html|\
HTML
{
:0 fbw
| formail -a X-Converted-by: procmail and lynx
:0 fbw
| lynx -dump -stdin
}
which works fine for html-only messages, but not combined text and
html messages (and presumably other combined formats) the whole body
gets sent through lynx which tends to look rather confusing:
--------------000408030305010002070302 Content-Type: text/plain;
charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit
dual
format google www.google.com/>
--------------000408030305010002070302
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding:
7bit dual format [1]google
--------------000408030305010002070302--
References
1. http://www.google.com/
so obviously I should be converting just the html bit, but how can I
split that off? Any better ways of identifying html would also be
appreciated.
--
Stephen Patterson http://www.lexx.uklinux.net http://patter.mine.nu
steve(_at_)SPAM(_dot_)lexx(_dot_)uklinux(_dot_)net remove SPAM to reply
Linux Counter No: 142831 GPG Public key: 252B8B37
Last one down the pub's an MCSE
pgpfth6sWvCP9.pgp
Description: PGP signature