[imp] Forwarding w/full headers and HTML attachment inline

[Michael M Slusarz]

Quoting Rick Emery <rick at emery.homelinux.net>:

> I feel like a real idiot asking what are probably some very stupid questions.
>
> First, a little background. I got a message from my ISP indicating that it
> couldn't charge my credit card for monthly service, and telling me to click a
> link to update my information. As you can probably guess, it's fraudulent,
> trying to scam me out of my credit card information (confirmed with my ISP's
> tech support).
>
> The message came in as a text message with an html attachment. The 
> text portion
> says that my "Email Client does not support MIME encoding".
>
> The HTML attachment is the message about my credit card, with the link.
>
> I tried to forward the message to my ISP's abuse address, but I got back an
> automated reply saying that they need full headers and everything inline (no
> attachments).
>
> 1. Can I send the message with full headers using IMP (and if so, how)?

Sure, if using HEAD.  In the mailbox screen, click the checkbox next to the
message you want to forward, and then click forward.  The *entire* contents of
the message will be attached to the resulting composed message as a
message/rfc822 part - this is probably exactly what the ISP is looking for.

> 2. When I forward the message, the HTML attachment shows attached at the
> bottom. If I change the disposition from "attachment" to "inline" and click
> "Update Attachment Information", I still get the message from the ISP. Their
> reply shows the original message I sent, and it shows the HTML as an
> attachment. Can I send it inline with IMP, and if so, how?

When you forward/reply, you are not sending any of the original headers in the
message.  You are simply either attaching parts of the original message or, in
the main text part, simply copying the text and some selected headers over.
This is why message/rfc822 is used - to preserve the message in an attachment
exactly how it was received by you.

michael

______________________________________________
Michael Slusarz [slusarz at bigworm.colorado.edu]
The University of Colorado at Boulder