Problems Sending Attachments (Windows)

ISSUE:

I can't send attachments.

SOLUTION:

Firstly, how large is the attachment you're trying to send? Most Internet Service Providers have placed size limits on attachments. If you can send small attachments but not large ones, check with your Internet Service Provider and see if they have a limitation on outgoing messages.

If even small attachments won't go, in Eudora go to Tools: Options: Advanced Network. Increase the "Network Time Out" and "Network Time After" settings. Also, step down the buffer size from 4096 to 1024.

If it still fails and you're on a dial-up connection, quit Eudora and go to My Computer: Dial-Up Networking. Select your Connection Properties. Click on the Configure button and adjust your maximum speed to less than the dial-up connection speed.

ISSUE:

The attachments go out, but they aren't being received properly on the other end.

SOLUTION:

When your recipients receive attachments as garbled text within the body of the message, it means that the attached file didn't get decoded on arrival. This may be because the recipient's mail program doesn't know how to decode the encoding method you use, or it could be because a gateway somewhere between you and them changed the message's headers so it was undecodable. (AOL is especially bad about this, because their proprietary mail systems require gateways between their users and the Internet).

Try sending yourself attachments with various encoding methods. You can change the encoding method for an attachment you're sending out with the encoding icon at the top of a new message. By default, it's set to MIME (see http://www.eudora.com/techsupport/kb/1227hq.html for more information about encoding methods Eudora supports).

If the attachments you send yourself contained garbled text, your server or Internet Service Provider may have a problem; contact them. If the attachments you send yourself are OK, but some of your recipients have trouble receiving them, it's probably because the messages to them had their headers modified in transit, or because the recipient's mail program doesn't understand the encoding method you used.

What can you do? Well, you can try using a different encoding method. The Internet standard is MIME, and that's the best choice in most situations. If you're running into the problem we described above, try one or all of the following:

1. Use Uuencode or BinHex encoding.

2. Turn Quoted Printable Encoding off (the QP button at the top of an outgoing message).

3. If all else fails, try Uuencoding the attachment and having the recipient manually decode it. When they get it, if the Uuencoded message is still undecoded and included in the body of the message, have them copy all the garbled text into a single, plain-text file. Then have them run a Uudecoding utility on the text file. They can download a shareware Uudecoding utility from any shareware website.

--

KEYWORDS: ALLCARDS, EPWIN, ATTACHMENT, DECODE, MIME,BINHEX,ENCODING, UUENCODE, SEND