>And I know, how I can handle this problem: Inside FileMaker I have to >resolve all the umlauts into two letters. It isn't smart, but it helps.
But this is what the standard tells you to do with the mail to as well. Space should be encoded to %20, so this means that umlauts would be %dc or %fc, which I tried by the way with PowerMail... a new issue occurred which prevented mail from using this at all, PM encoded it wrong, but I also didn't specify the encoding type, which I'm not convinced I can do with a simple mailto, for this I do think I'll need to process the data and in addition to encoding the message, manually write all the headers, which means I wouldn't use any commercial mail apps anyhow, I would use PostFix. That said, depending on what you are trying to do, it sounds like you're on the right track, but based on my quick experiments here, I think there is a lot more to it and I think if you pour over several of the standards you should find the answer (part of it is already staring us right in the face -- don't use 8-bit characters. That is spelled out in the RFC, yet you seem to want to ignore it. which to me already calls into question the bug. PM does seem to handle this situation rather oddly, but then I'm told not to do what I'm doing, so is it really a bug? My experience with QA departments would tell me that while it might not behave exactly correctly, it isn't misbehaving since the standard says not to do it). Best of luck with whatever it is you're going to be doing with this, but I doubt you'll get much traction from the PM engineers on this one either. Wayne
