Here is a solution from Josh Jacob:

For those Mailsmith users who correspond with people using Microsoft Exchange/Outlook you may have run into problems when people have tried to send you attachments and the only thing you get is a file called "winmail.dat" or a file with the MIME type "application/ms-tnef." To make a long story short, I did lots of hunting on the net and on Microsoft's site and was able to write a program which will read the "winmail.dat" files and extract embedded documents out of them.

The program is called TNEF's Enough (the "winmail.dat" file is called a TNEF file) and is in a very early (and rough) form. It currently uses the SIOUX interface but I figured I'd release it now to get a reaction as to it's success. I've run it against all the files I have ever received and it works great.

If you are interested in trying this program out and letting me know if it works for you or doesn't that would be great. Here's where you can find it:

http://www.joshjacob.com/mydev/tnef/

Christian Smith tells it all:

"Chris's rules for sending attachments to the disadvantaged".

Rule 1: Never compress the file. Even on the off chance that you compress the file into a format handled by some utility available on Windows machines, odds are the person on the other end won't have anything that can handle it or won't know how to decompress it even if he does.

Rule 2: Make sure the file has a three character suffix appropriate for the file type. You may need to look this up before you send the file. If this is missing the person on the other end will be in a complete tizzy and will not know how to view/read/whatever the file.

Rule 3: First comes Apple Double, then comes Base64 and finally (if all else fails) use UUcode. Yes, it's the 21st century and yet there are still email clients out there which can't handle anything newer than an encoding scheme developed by the Spanish Inquisition.

Rule 4: If at all possible, use plain text. If you don't think it is possible, think again. Repeat previous step as necessary ;-)

I hope you have as much fun reading this as I had writing it. Despite any amusement value, I'm quite serious about all of the above. Enjoy.

> I've always shied away from Apple Double, cos I thought 'It's got
> Apple in the title and therefore isn't cross-platform' and I always
> use Base64 (with no compression)... So if Apple Double is officially
> Good, why so??? Does it send PC users the data fork and the resource
> fork as separate files? (guessing at 'double') and if it does I
> assume Mac clients just stitch them back together again... Hmmm.
> Please, will someone set me on the path to attachment
> enlightenment...

That is exactly what it does. The two parts of the file are attached separately, each encoded using Base64 encoding (typically). PC clients just extract the data fork and Mac clients extract both parts.

Som information from Ulf Kress about where to find more info

• Macintosh Internet File Format Primer <http://db.tidbits.com/getbits.acgi?tbart=05066>
• Email Attachment Formats Explained <http://db.tidbits.com/getbits.acgi?tbart=05787>
• Email Attachments: Who Does What <http://db.tidbits.com/getbits.acgi?tbart=05794>

        +++ An error occurred while sending mail to "smtp.bar.com".
                    
        Application error code 22315
        No additional information is available.

Why does this happen, and what can I do to fix it?

A: In order to thwart the efforts of spammers, many system administrators are configuring their SMTP server software to check the domain of the sender, and refuse the message if the sending domain is not a known or "trusted" domain. When using a "mail drop" service such as iname.com or pobox.com, this can lead to difficulty in sending messages, even though you're a legitimate user. Consider the following example from the Email Accounts window:

In the "Checking" settings:

        POP Server Name:    pop.my-isp.com
        User ID:            joe_user

        SMTP Server Name:   smtp.pobox.com
        Reply Address:      joe_user@pobox.com

        550 <joe_user@pop.my-isp.com>... Relaying Denied

This occurs because pobox's mail server doesn't know the domain "my-isp.com", and consequently assumes that the attempt is being made by a spammer, and refuses to accept the message for delivery.

To resolve this situation within Mailsmith, set up a "Send Only" account (which you can do using Mailsmith 1.0.1 or later). In the "Checking" settings, leave the POP server name and User ID blank. Given the above example, you would specify the following in the "Sending" settings:

        SMTP Server Name:   smtp.pobox.com
        Reply Address:      joe_user@pobox.com

If you wish, you can make this account the default account by selecting its name and clicking the "Make Default" button; this will make it the default account through which outgoing messages are sent.

Thereafter, when you use this account to send, Mailsmith will inform the SMTP server that the message is being sent from "joe_user@pobox.com" (or whatever your actual reply address is), and the server will accept the message for delivery.

1. First, in the accounts window it possible to associate a signature to an account.
2. It's also possible to make stationaries that define account, signature, priority, etc. You can then use them when composing new emails.

1. Create it directly from the save dialog
   1. Make an email message with the content and options you want to have.
   2. Choose Save
   3. When the dialog comes up asking for the name, check the stationary checkbox at the bottom of the dialog.
2. Using Finder
   1. Make an email message with the content and options you want to have.
   2. Save to disk
   3. Switch to Finder
   4. Select the message and choose "Get Info"
   5. Check the "Stationary" check box

Mailsmith supports sending mail in Binhex, Apple Double, Apple Single, and UUcode formats.

AppleSingle and AppleDouble are both -binary- packaging conventions, and do not specify or imply the transfer encoding. However, Mailsmith uses the Base64 encoding scheme to encode data when Apple Double and Apple Single are used.

Rich Siegel has written a fairly detailed tech notes on this subject which is available at:

http://www.macemail.com/pages/appledouble.shtml

Some email clients use Base64 without specifying a packaging convention. This is not strictly correct behaviour, but Mailsmith can receive and decode mail sent in this fashion. It will however not send mail in this fashion.

As for compression, the next release of Mailsmith will offer integrated compression using the Stuffit compression engine. If this is installed you will be able to automatically compress outgoing attachments and decompress incoming ones.

Actually, I'm quite sure that the mail is still on that server.

Well, I seem to have assumed to much when providing the previous version of this answer ... should learn to get all the facts before writing something down ... Here is what I have learned the last few days:

• POP servers can be configured to mark email as read or they can be set to not to do this
• Mailsmith doesn't rely on this feature

Pre-1.5 versions: Not by using Mailsmith only. You have to use some macro program (KeyQuencer, OneClick) or a program like DragThing (my personal favourite)

As of version 1.5 you can assign a shortcut to a stationary. Use the Stationary palette that can be found in the Windows menu.

If the line with the ">" inserted starts with "From" the explaination is below, if not ... I don't know.

Emails to one person is collected in a "spool file" (on the machine where the person fetches the email). All messages are stored in the same file and to be able to see where one email starts and ends there has to be some rules of how an email can look. One such rule is that there should be an empty line separating emails and that an email starts with "From" (not "From:"!!), for example:

here is the last line of a previous message.

From bla bla bla bla

hfdklsj sadlkjfh alsdkfjh adskfljh daslkfjh 

From my desk fhlkdsa fdsalkjhf saldkjfh

The software would then be fooled to think that a new message would start at the last line above. To avoid problems like this a ">" (old convention) is inserted as the first char of any line that starts with a "From".

No, but take a look at the Edit Queued Messages script in René Brouwers archive

From version 1.1.6 it's possible to get the functionality of this script by using the "Re-send" command.

Version 1.5 adds a special mailbox called "draft", here you can save messages that are not ready to be sent, just double-click a message and you can continue editing them. When you queue the message, it will automatically be removed from the draft mailbox.

You have probably got an HTML formatted email ... but it was malformed and Mailsmith couldn't decipher it. However the message is saved as an enclosure "HTML Attachment" in the enclosures list. Double click it to view it in the preferred browser on your machine.

Note that from version 1.5 a rough text only version of the HTML message is displayed

See above

Note that from version 1.5 a rough text only version of the HTML message is displayed

You can do it using AppleScript. There is one such AppleScript at René Brouwers script archive and there is second one on my script page (parts of it comes from Renés script).

This feature was added in some of the 1.1.x versions and should also work in 1.5 ... if you are running OS 9. It doesn't work on OS X, to cite Jim Correia "X is multi-homing by nature and Mailsmith lets the OS decide if the destination is routable and what to do about it"

Date: Mon,  4 Jan 1999 21:43:49 +0100
From: Jan Erik Moström <xxxx@xxxxxx.xxx>
Subject: Test message
To: "xxxx@xxxxxx.xxx" <xxxx@xxxxxx.xxx>

A demo message

Date: Mon,  4 Jan 1999 21:45:25 +0100
From: Jan Erik Moström <xxxx@xxxxxx.xxx>
Subject: Fwd: Test message
To: "xxxx@xxxxxx.xxx" <xxxx@xxxxxx.xxx>

On 99-01-04 at 21:43, Jan Erik Moström <xxxx@xxxxxx.xxx> could have typed:

> A demo message

Date: Mon,  4 Jan 1999 21:45:44 +0100
From: Jan Erik Moström <xxxx@xxxxxx.xxx>
Subject: Test message
To: "xxxx@xxxxxx.xxx" <xxxx@xxxxxx.xxx>

A demo message

Note that forwarded mail has "Jan Erik Moström <xxxx@xxxxxx.xxx>" as sender although that the orginal sender was "Jan Erik Moström <xxxx@xxxxxx.xxx>", the redirected mail uses the orginal sender. The forwarded email also has a slightly different "Subject" line and quoted body text.

Not directly, you could probably hack something together using AppleScript and Cron or iSchedule (included with OS 9) or some similar program.

Yes, there are three different ways:

1. you can either open the "Email Accounts" window, select the account and hit "check now"
2. you could use this script
3. or simplest, use the "Check for new mail ..." command, note NOT the "Check for new mail" command

Mailsmith uses the last message received as a bookmark to see which messages are new, if you delete that it will download all messages again (all except those who have been deleted)

1. set up a filter that triggers a script that deletes the enclosure. For example

   if sent is true
   and to contains "Dunbar" then
   run script "Delete Enclosure
   

2. create a filter that deletes the enclosure. This is an example of how this can be done but you need to add a FilterMessage handler to it:

   on FilterMessage(msg_obj)
       tell application "Mailsmith 1.1"
           -- do something to the message
       end tell
   end
   

Here is a solution provided by Christian Smith:

Here is a filter criteria which should do the trick.

     if any header contains "Content-Type: multipart"

This will catch any message that has enclosures or has in-line data (text or otherwise). If you are just concerned with messages that have non-enclosure in-line data such as generated by some email client, you could use a multi-criteria filter like this:

    if any header contains "Content-Type: multipart"
    and has enclosures is not equal to true

Now, once you have identified a message that has in-line content, you could do several things. Easiest would be to just set a particular label. This would give you a visual clue in the message list of messages that have extra data.

You could also spin thru the message with an applescript and look at the various parts:

    on filtermessage(the_message)
        tell application "Mailsmith 1.1"
            set n to count parts of part 1 of the_message
            repeat with i from 1 to n
                get type of part i of part 1 of the_message
                get subtype of part i of part 1 of the_message
                get contents of part i of part 1 of the_message
            end repeat
        end tell
    end filtermessage

Based on the info returned by this script you could write the part out to disk or even delete the part.

You have perhaps noticed that Mailsmith doesn't disconnect (go to idle in the Connection Status window) despite the fact that all messages have been downloaded. Does it wait for filtering to complete?

Here is Rich Siegels answer:

If "Leave Mail on Server" is turned off, Mailsmith will disconnect from the server after the last message has been successfully stored in the incoming mailbox. Since automatic filtering is done concurrently, it can sometimes delay completion of mail storage, but Mailsmith's disconnection is tied to the completion of storage, not filtering.