Re: Empty resource fork in attachment

2003-09-15 Thread Kjell Olausson
Dan [EMAIL PROTECTED] wrote: Zach Selland, 11:24 AM, 9/15/03: On Mon, Sep 15, 2003, Dan Webb [EMAIL PROTECTED] wrote: In previous versions (pre-4.2) of PowerMail, I used to be able to attach MS Word documents and send them to PC users. In 4.2, it refuses to attach the file unless it

Re: Empty resource fork in attachment

2003-09-15 Thread Zach Selland
On Mon, Sep 15, 2003, Dan Webb [EMAIL PROTECTED] wrote: This seems weird. Is there a reason for it? I really hate this DOS file name extension stuff infecting my Mac. I think that it has more to do with OSX and it's preference for file name extensions than Powermail. I believe that Powermail

Re: Empty resource fork in attachment

2003-09-15 Thread Dan Webb
Zach Selland, 11:24 AM, 9/15/03: On Mon, Sep 15, 2003, Dan Webb [EMAIL PROTECTED] wrote: In previous versions (pre-4.2) of PowerMail, I used to be able to attach MS Word documents and send them to PC users. In 4.2, it refuses to attach the file unless it compresses the file with StuffIt, which

Re: Empty resource fork in attachment

2003-09-15 Thread Dan Webb
Zach Selland, 11:24 AM, 9/15/03: On Mon, Sep 15, 2003, Dan Webb [EMAIL PROTECTED] wrote: In previous versions (pre-4.2) of PowerMail, I used to be able to attach MS Word documents and send them to PC users. In 4.2, it refuses to attach the file unless it compresses the file with StuffIt, which

Re: Empty resource fork in attachment

2003-09-15 Thread Zach Selland
On Mon, Sep 15, 2003, Dan Webb [EMAIL PROTECTED] wrote: In previous versions (pre-4.2) of PowerMail, I used to be able to attach MS Word documents and send them to PC users. In 4.2, it refuses to attach the file unless it compresses the file with StuffIt, which is unacceptable. It turns out

Empty resource fork in attachment

2003-09-15 Thread Dan Webb
In previous versions (pre-4.2) of PowerMail, I used to be able to attach MS Word documents and send them to PC users. In 4.2, it refuses to attach the file unless it compresses the file with StuffIt, which is unacceptable. It turns out that MS Word documents have resource forks, but they're