02-15-2017
Issue with opening the UNIX mailx attachments on iPhone/iOS
I have created a simple log file (abc.log) with Hello World, from my UNIX script. At the end of the script, I have attached the log to my email using uuencode & mailx command.
THe email was send successfully and opening on my desktop without any issues.
I have the email sync with my iPhone too. When I tried to open the same attachment (abc.log), it is opening and showing all junk data.
I made a try with BlackBerry 10 device, it is opening without any issues.
I am using AIX 7.1 and latest iOS.
Please suggest, if I can try any other way ?
7 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hi
I want to use mailx command to send a message included more than one file.
I tried to use uuencode in pipe but it could only generate one file.
I would avoid using an archive file :p
Thanks to read you.
Mathieu (2 Replies)
Discussion started by: madmat
2 Replies
2. UNIX for Advanced & Expert Users
I have written the following code send multiple attachments using mailx
(uuencode file1 file1; uuencode file2 file2; uuencode file3 file3;) | mailx -s MultipleAttachments -r Sysadmin abc@xyz.com
The attachments are coming properly if the file1,2,3 are either pdf, text, doc. But if these files... (2 Replies)
Discussion started by: ramanam2004
2 Replies
3. AIX
I'm trying to send a mailx with an attachment, really I have not do it in a long time. I forgot (3 Replies)
Discussion started by: darioa
3 Replies
4. UNIX for Dummies Questions & Answers
Hi,
I have a requirement to save a mail attachment sent from Windows to a Solaris 9 server.
I'm using mailx on the server and have seen a few examples of how to attach a file for sending but none for how to save the attachment when receiving.
I can see the encoded text when I look at... (2 Replies)
Discussion started by: Jublio
2 Replies
5. Shell Programming and Scripting
Hi,
I am seeing some junk characters when I attach the second file, given below is the logic I used. Please help me resolving the issue.
( uuencode file1.txt file1.txt.lst && uuencode file2.txt file2.txt.lst ) > attachment.txt
cat body.txt attachment.txt > combinemail.txt
mailx -m... (7 Replies)
Discussion started by: prasperl
7 Replies
6. Shell Programming and Scripting
I have created a shell scripts and wanted to email users multiple attachments using mailx. I noticed that when I do a man on mailx I see and -a option for attachments. When I run a:
mailx -s "test attachments" -a include_file -a exclude_file testuser@mydomain.com
(Interrupt -- one more to... (1 Reply)
Discussion started by: metallica1973
1 Replies
7. Shell Programming and Scripting
Hello! I am writing a KornShell script that (in addition to other things) sends a file from a Unix directory to a SharePoint directory. However when executing the script there is no sign of the file on the SharePoint.
I have tested the script using my personal email as the destination and the... (3 Replies)
Discussion started by: mattkoz
3 Replies
log(8) System Manager's Manual log(8)
NAME
log - Records input and output from a program
SYNOPSIS
/usr/sbin/log <logfile> <command>
OPERANDS
The file in which to record the interaction being logged. The command to execute.
DESCRIPTION
The log program runs <command> and logs the input to and output from <command> to the <logfile> file. Input and output are logged until
<command> exits, the log program exits, and the exit status of <command> is returned.
The log program is used by the system installation procedure and the it(8) command to create the /var/adm/smlogs/install.log and
/var/adm/smlogs/it.log installation log files.
RESTRICTIONS
Because the log program is used in the installation standalone environment, program size was the greatest concern in its implementation.
The log program does not search for the PATH variable to locate <command> and error messages are terse.
The log program causes <command> to take standard input from and write standard output and standard error to UNIX pipes. Some commands
will not be able to operate in this environment; therefore, it is suggested that you use the script(1) command instead. UNIX shells will
not issue prompts when run from log unless the shell is started with an explicit interactive switch (-i for most shells). For example, log
foo.tmp /sbin/sh -i
In the previous example, foo.tmp is the name of <logfile>.
The log program intercepts end-of-file (usually Ctrl/d). Therefore programs which normally receive end-of-file as an exit command must
exit by some other means.
ERRORS
Log open error
Explanation:
The log program was unable to open <logfile>. Verify that the directory exists and that ownerships and permissions are set correctly.
Exec Error
Explanation:
The log program was unable to execute <command>. Verify that you specified a full pathname for <command> and that <command> is an exe-
cutable file.
Fork Error
Explanation:
The log program was unable to create one of the processes it requires to log data.
SEE ALSO
Commands: it(8), script(1)
log(8)