So try creating the message in a windows editor perhaps? Or in
outlook.
I've seen this exact behaviour when creating 8bit messages on OSX
which
looked ok in thunderbird/linux but looked like a bag of funnies in
outlook.
Thats neither an option nor an sollution.
Sending a message from mail.app to outlook works like it ought to.
At the end my cool new pike-timsieve module should insert the sieve
script. Also I don't see me buying an M$ pc just to insert sieve
scripts. Since I use mail.APP I get my own vacation note just fine.
But the note is there for customers not for myself (I already know
I'm on a holliday).
Furthermore it is sieve (read dbmail) which sets the encoding part,
not the script itself.
If I check the sieve script in the database, or with telnet at the
popserver everything is intact.
