This may just be an issue with Mail.app, but when ever a message is forwarded automatically by Mail.app the email content is not parsed properly. This occurs if you use a mail filtering rule or in my case Mail Act-On.

I’ve pastied an example message.

Has anyone else experienced this issue?

Same thing happens to me. I haev no idea what is causing it.

You know, I just now thought of setting up auto-forward rules for sending to Highrise after reading this post. Thanks!

[/beats head against wall]

I just played with this, and what I found is that the actual message content is also put in a mime attachment instead of the note (this is in addition to the weird formatting Joshua mentioned).

However, I also just did it on another message that didn’t have the problem. It seems to be only messages that have attachments that get screwed up.

I’ve submitted a ticket to support. We’ll see what they say.

Meanwhile, I’ve been trying to create an AppleScript for forwarding that can be called from a rule to see if that works. I’ve been unable to figure it out, though.

I did discover that it makes no difference whether you’re sending Windows Friendly Attachments or not. It also makes no difference if Mail is set to Plain or Rich text.

Support said that they will pass it on to the engineers for possible inclusion in the future.

What happens is that Mail encapsulates the forwarded message as a MIME attachment when forwarding via a rule. I’m guessing that some people who use certain Windows and web based clients would run into this problem a lot, too, because some Windows apps and webmail interfaces attach forwards by default, instead of quoting them inline.

I’ve set up a rule for MailActOn that forwards messages to Highrise. Thus, it’s two keystrokes to forward something.

Yes. What we’re referring to is that when there are attachments, messages forwarded in that way come through messed up.

Any fixes for this issue yet?

The issue does have to do with the whole Richtext vs Plaintext issue. I have my Mail.app set to always reply with plain text, great right? Well when I click reply, Mail.app converts the Richtext email to plaintext, works fine when sent to Highrise. If you just use the auto reply rules, Mail.app will forward the Richtext email as is. There is the problem.

It all comes down to Highrise supporting Richtext email.

In my case rich text isn’t the problem. It’s that Mail Act-On activated Forwarding Rule attaches the forwarded message as a mime attachment instead of using in-line, which is what it does if you forward by hand. I have not found a way to fix this yet.

Did this issue ever get resolved? I have held back on using Highrise b/c of this bug.

Bump… did anyone figure it out? Just getting started and stuck.

Thanks.

In my case rich text isn’t the problem. It’s that Mail Act-On activated Forwarding Rule attaches the forwarded message as a mime attachment instead of using in-line, which is what it does if you forward by hand. I have not found a way to fix this yet.

This is exactly what we are experiencing. A fix would be nice.

Not sure if this is the same issue, but when I send from mail.app to HR, dropbox address in the BCC.. I get e new contact added rather than attaching it to the existing contact with that email address?
any help would be appreciated.
Duncan

Well when I click reply, Mail.app converts the Richtext email to plaintext, works fine when sent to Highrise. If you just use the auto reply rules, Mail.app will forward the Richtext email as is. There is the problem.

Angelina

MINUTETRADERS | Buy/Sell AZ & Direct Termination Routes,Wholesale,TDM,VoIP