Hi,

using PM 4.2b1, how can I force PM to send an attachment using, say
Base64 encoding? PM keeps telling me that the attachment will be
corrupted when sent with the specified encoding and that it will use
"Smart" instead. Sure enough, the file probably has a resource fork, but
I know for sure that the receiver will only read the data fork and losing
the resource is what I want.

I think previous versions would let me send the attachment in Base64
anyway, discarding the resource fork, if needed.

How can I make PM 4.2b1 use the encoding I deliberately set manually? I
tried all the modifier keys, but PM always resets to "Smart"...

Regards, Christian.


Reply via email to