We frequently see our exchange server try to dink with carriage control in messages from unix. A common exchange notification when you open the message is:
"extra line breaks in this message were removed" in a blue band at the email head.
Clicking on the band resores the "extra" line breaks.
and we have lines that were separate globbed together by exchange, just like in your example. This appears to be your problem, too. We get arround it:
Code:
# note we add .txt so windows can open the file with word
unix2dos logfile logfile.txt
uuencode logfile.txt logfile.txt | mail -s 'subject' who@where.com
Exchange does not mess with those attachments.
More of a UNIX-side solution
This User Gave Thanks to jim mcnamara For This Post:
ok, does anyone know how i can strip out fields i dont want from a mail spool file (eg: /var/mail/usermailbox) and dump to standard output (or file with > filename) ?? i tried using a bunch of grep -v 's but i realized that has two main problems, first of all, if anyone types the text im grepping... (6 Replies)
Hi. I have a Tru64 Unix V5.1 server that I would like to send emails using an exchange server we have on the same network as the smtp of this machine. What are the requirements/configuration that I need to do in order to make this possible. We are planning on emailing error messages and such from... (2 Replies)
Hi All,
I realized now that the root email is integrated with exchange. All the email of root is now being sent also to the aliases of aixadmin or to my email.
I would like to know how is AIX integrated to exchange. What would be modified on AIX? Probably modify these files: /etc/hosts,... (0 Replies)
i am new in AIX i am trying to write a script to take a backup for specific files on server to and check error log if backup success send email to administrator , script done except for sending mail , i try to configure sendmail on aix to use our exchange server to send emails but still get error... (0 Replies)
Hello All,
When i use the single quotes around the variables i am getting each line in the array as seperate in the email as shown in code2 & output2. But i don't want those single quotes to be printed but each array element should be printed as seperate line as when i remove those single quotes... (1 Reply)
About 5 years ago I used to use Evolution for its ability to interact with my companies Exchange 2003 server. I was wondering what Exchange compliant email clients you are actually using with either Exchange 2007 or 2010?
FYI I've tried Thunderbird and it just sucks. (5 Replies)
Hi friends,
I have written a shell script which send a report to email address everyday.
The report is generated on UNIX server every day, Generated report is sent to 25 users through cron.
All 25 users have set different screen resolution for their monitor. The email looks wel formatted for... (4 Replies)
Discussion started by: Nakul_sh
4 Replies
LEARN ABOUT DEBIAN
bootlogd
BOOTLOGD(8) Linux System Administrator's Manual BOOTLOGD(8)NAME
bootlogd - record boot messages
SYNOPSIS
/sbin/bootlogd [-c] [-d] [-r] [-s] [-v] [ -l logfile ] [ -p pidfile ]
DESCRIPTION
Bootlogd runs in the background and copies all strings sent to the /dev/console device to a logfile. If the logfile is not accessible, the
messages will be kept in memory until it is.
OPTIONS -d Do not fork and run in the background.
-c Attempt to write to the logfile even if it does not yet exist. Without this option, bootlogd will wait for the logfile to appear
before attempting to write to it. This behavior prevents bootlogd from creating logfiles under mount points.
-r If there is an existing logfile called logfile rename it to logfile~ unless logfile~ already exists.
-s Ensure that the data is written to the file after each line by calling fdatasync(3). This will slow down a fsck(8) process running
in parallel.
-v Show version.
-l logfile
Log to this logfile. The default is /var/log/boot.
-p pidfile
Put process-id in this file. The default is no pidfile.
BUGS
Bootlogd works by redirecting the console output from the console device. (Consequently bootlogd requires PTY support in the kernel con-
figuration.) It copies that output to the real console device and to a log file. There is no standard way of ascertaining the real con-
sole device if you have a new-style /dev/console device (major 5, minor 1) so bootlogd parses the kernel command line looking for con-
sole=... lines and deduces the real console device from that. If that syntax is ever changed by the kernel, or a console type is used that
bootlogd does not know about then bootlogd will not work.
AUTHOR
Miquel van Smoorenburg, miquels@cistron.nl
SEE ALSO dmesg(8),fdatasync(3).
Jul 21, 2003 BOOTLOGD(8)