Kevin,
Well to provide the most flexibility we don't directly make the image an image tag or a file a direct file tag. This is because you might want to offer other flexibility (such as an image that points to the file, or possibly make the image a hyperlink, or maybe point the user to a hyperlink which loads the image and does not display the image directly within the email itself... Based on feedback (such as this) we are planning to offering additional tokens such as $(Image_ImageField) and/or $(Image_Link) and $(FileAttachment_Link) etc... This way you those users who want to still use the current implementation of these tokens can but other users can have fully working HTML for their specific needs.
So... In your case, keep in mind that file attachments and images have unique filenames. When you use the tags directly within an event you are listing the filenames only. This does not list the URL to the directory where they are at or the HTML to generate the image itself. So in your case.
To list the file attachment (either list it in the email or actually make it an attachment by clicking the chain icon) you need to point the URL to...
http://www.yoursite.com/portals/0/D...FileField) Additionally, for an image, you would need to click the insert image icon and set the URL to be:
http://www.yoursite.com/portals/0/D...mageField) This is also assuming you your portalID is 0.
We will try and get these enhancements I mentioned here on the 'short list' for the next minor release.
-Chad