- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: UUEncode
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-25-2002 11:33 AM
тАО09-25-2002 11:33 AM
UUEncode
John Hicks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-25-2002 11:48 AM
тАО09-25-2002 11:48 AM
Re: UUEncode
I'm no expert on this but I did work or it yesterday (searching the forums, trying a number of suggestions). Here's what I found to work for me on my HP-UX 11.0 box.
Create a file specifying what to email. Mine is named "include". It's contents are:
[include MSexcel.xls application/octet-stream base64]
[include MSword.doc application/octet-stream base64]
[include text.txt application/octet-stream base64]
Send the files like this:
elm -s "Subject text" somebody@somewhere.com
This delivers MSexcel.xls, MSword.doc, and text.txt as 3 separate attachments that I can open on my PC without problem using Excel, Word, and notepad respectively. This worked with my Outlook and Lotus Notes email clients both.
I found other posts saying to use "[include text.txt text/plain base64]" for ascii files however doing that caused text.txt to be sent in the body of the message instead of as an attachment.
Darrell
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-25-2002 12:19 PM
тАО09-25-2002 12:19 PM
Re: UUEncode
Correct me if I'm wrong, but I don't think the problem is with uuencode. I believe it is mailx which didn't include MIME headers in 10.20, but does since 11.00. At least here Outlook doesn't recognize uuencoded files in messages sent with MIME headers. If mailx is used with the -m option, then Outlook correctly detects the uuencoded attachment.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-25-2002 12:30 PM
тАО09-25-2002 12:30 PM
Re: UUEncode
When they upgraded, did they load any patch bundles?
Does the message look like this (close?):
" This message uses a character set that is not supported by the Internet Service. To view the original message content, open the attached message. If the text doesn't display correctly, save the attachment to disk, and then open it using a viewer that can display the original character set."
Have them check that PHNE_16390 is on the system (no reboot required to install).
Hope this helps
Chris
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-27-2002 02:59 PM
тАО09-27-2002 02:59 PM
Re: UUEncode
We are 11.0 and found the problem related to the receiver's mail server.
This was corrected by using
mailx -m
example:
ux2dos path_to/file_to_send | uuencode attachment name.txt | mailx -m -s "Subject" john.doe@somewhere.com
That example sends the file as an attachment which I believe you are attempting. Redirect into the body will work with the mailx -m as well.
best of luck.
dl
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-27-2002 03:01 PM
тАО09-27-2002 03:01 PM
Re: UUEncode
typo should have read
attachment_name.text
dl