09-15-2010
command line MIME?
Is there a commandline MIME encoder?
standard on solaris 10.
(a-la uuencode)
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
:confused:
I am a programmer, but need to work with UNIX in this particular situation. I am used to the plain "mail -s" command and also familiar with how to send attachments in html... but I now need to send an email (not an attachment) in html format so I can embed links... etc.
I am told... (2 Replies)
Discussion started by: cgardiner
2 Replies
2. UNIX for Advanced & Expert Users
I have a problem while sending attachement , it is displying Content into body of mail (Junk Data) instead of attachment (zip format) in Linux, same code is working in Sun Solaris..
I have read query in this site , need to set MIME type to mailx componment. Please help me how to set MIME type..... (1 Reply)
Discussion started by: suneel
1 Replies
3. UNIX for Dummies Questions & Answers
Hi,
I am trying to launch an ogg movie from a pdf file which has been produced with pdflatex and
\movie
{\centerline{\includegraphics
{grafiques_xerrades/un_manolo_amb_camera.pdf}}}
{hlims_xerrades/XocCumuls.ogg}
The switch "externalviewer" makes kpdf launch the default... (5 Replies)
Discussion started by: pau
5 Replies
4. Shell Programming and Scripting
hey,
i need some help with mime and hebrew.
i have a script sending a multipart mime . the problem is that the subject is recived in jibrish. i need to know how to explictly define charset for the subject.
i would appericiate any help,
thanx in advance,
rafi (0 Replies)
Discussion started by: rafiyaari
0 Replies
5. Shell Programming and Scripting
Hi Everyone,
I have a question related to using MIME::Lite module in perl.Below i mentioned code blocks used for sending mail through MIME::Lite.
$msg = MIME::Lite -> new (
From => $from,
To => $to,
Subject... (0 Replies)
Discussion started by: DILEEP410
0 Replies
6. Shell Programming and Scripting
Hi,
I am using the below code for sending attachment in UNIX but only blank attachment is coming in email even the content is not coming.
Please help!!!
export CONTENT="${DIR}/${RUN_DATE}_mailbody.txt"
export SUBJECT="Search Result for Pattern - ${1}"
export ATTACH=${2}
(
echo... (9 Replies)
Discussion started by: rajesshh
9 Replies
7. Shell Programming and Scripting
Hi all,
i'm using the pearl package MIME::Lite zu send eMails via sendmail. I have the problem, that in the "Received From" part oft the email header occure the user and the hostname of my machine. I'd like to have a name or an email address instead of that:
Received: from... (0 Replies)
Discussion started by: andi25
0 Replies
8. Shell Programming and Scripting
my requirement is,
consider a file output
cat output
blah sdjfhjkd jsdfhjksdh
sdfs 23423 sdfsdf sdf"sdfsdf"sdfsdf"""""dsf
hellow there
this doesnt look good
et cetc etc
etcetera
i want to replace a line of line number 4 ("this doesnt look good") with some other line
... (3 Replies)
Discussion started by: vivek d r
3 Replies
9. Shell Programming and Scripting
Sed command to replace a line in a file using line number from the output of a pipe.
Is it possible to replace a whole line piped from someother command into a file at paritcular line...
here is some basic execution flow..
the line number is 412
lineNo=412
Now i have a line... (1 Reply)
Discussion started by: vivek d r
1 Replies
10. Shell Programming and Scripting
I am looking for help in processing of those options: '-n' or '-p'
I understand what they do and how to use them.
But, I would like to use them with more than one file (and without any shell-loop; loading the 'perl' once.)
I did try it and -n works on 2 files.
Question is:
- is it possible to... (6 Replies)
Discussion started by: alex_5161
6 Replies
LEARN ABOUT NETBSD
mimencode
MIMENCODE(1) General Commands Manual MIMENCODE(1)
NAME
mimencode - Translate to and from mail-oriented encoding formats
(Same program also installed as "mmencode".)
SYNOPSIS
mimencode[-u] [-b] [-q] [-p] [file name] [-o outputfile]
DESCRIPTION
The mimencode program simply converts a byte stream into (or out of) one of the standard mail encoding formats defined by MIME, the pro-
posed standard for internet multimedia mail formats. Such an encoding is necessary because binary data cannot be sent through the mail.
The encodings understood by mimencode are preferable to the use of the uuencode/uudecode programs, for use in mail, in several respects
that were important to the authors of MIME.
By default, mimencode reads standard input, and sends a "base64" encoded version of the input to standard output.
The (really not necessary) "-b" option tells mimencode to use the "base64" encoding.
The "-q" option tells mimencode to use the "quoted-printable" encoding instead of base64.
The "-u" option tells mimencode to decode the standard input rather than encode it.
The "-p" option tells mimencode to translate decoded CRLF sequences into the local newline convention during decoding and to do the reverse
during encoding. This option is only meaningful when -b (base64 encoding) is in effect.
If a file name argument is given, input is read from that file rather than from standard input.
The "-o" option, which must be followed by a file name, sends output to the named file rather than to standard output.
RATIONALE
Mimencode is intended to be a replacement for uuencode for mail and news use. The reason is simple: uuencode doesn't work very well in a
number of circumstances and ways. In particular, uuencode uses characters that don't translate well across all mail gateways (particularly
ASCII <-> EBCDIC gateways). Also, uuencode is not standard -- there are several variants floating around, encoding and decoding things in
different and incompatible ways, with no "standard" on which to base an implementation. Finally, uuencode does not generally work well in
a pipe, although some variants have been modified to do so. Mimencode implements the encodings which were defined for MIME as uuencode
replacements, and should be considerably more robust for email use.
SEE ALSO
metamail(1), mailto(1)
BUGS
This program was originally distributed as "mmencode". That name turns out to conflict with a program of the same name that is part of the
Slate software from BBN, but totally changing the name to mimencode would create other problems (notably with portability to systems where
the left half of file names is limited to 8 characters). Currently, it is being distributed with links under BOTH names. The programs in
the distribution that call the program all call it as "mimencode", so the "mmencode" version may be deleted at sites where it causes a
problem. (The source files are still named "mmencode" rather than "mimencode".)
COPYRIGHT
Copyright (c) 1991 Bell Communications Research, Inc. (Bellcore)
Permission to use, copy, modify, and distribute this material for any purpose and without fee is hereby granted, provided that the above
copyright notice and this permission notice appear in all copies, and that the name of Bellcore not be used in advertising or publicity
pertaining to this material without the specific, prior written permission of an authorized representative of Bellcore. BELLCORE MAKES NO
REPRESENTATIONS ABOUT THE ACCURACY OR SUITABILITY OF THIS MATERIAL FOR ANY PURPOSE. IT IS PROVIDED "AS IS", WITHOUT ANY EXPRESS OR IMPLIED
WARRANTIES.
AUTHOR
Nathaniel S. Borenstein
Bellcore Prototype Release 1 MIMENCODE(1)