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:
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
logtail2
LOGTAIL(8) logtail2 manual LOGTAIL(8)NAME
logtail2 - print log file lines that have not been read
SYNOPSIS
logtail2 [-t] -flogfile [-ooffsetfile]
DESCRIPTION
logtail2 reads a specified file (usually a log file) and writes to the standard output that part of it which has not been read by previous
runs of logtail2. It prints the appropriate number of bytes from the end of logfile, assuming that all changes that are made to it are to
add new characters to it.
logfile must be a plain file. A symlink is not allowed.
logtail2 stores the information about how much of it has already been read in a separate file called offsetfile. offsetfile can be omit-
ted. If omitted, the file named logfile.offset in the same directory which contains logfile is used by default.
If offsetfile is not empty, the inode of logfile is checked. If the inode is changed, logtail2 uses the heuristics stored in
/usr/share/logtail/detectrotate/ to find a file that might be the rotated logfile and prints it starting with the stored offset. It then
proceeds to simply print the entire new file and generates a new offsetfile. If the inode is not changed but logfile is shorter than it
was at the last run of logtail2, it writes a warning message to the standard output.
OPTIONS -f logfile to be read after offset
-o offsetfile stores offset of previous run
-t test mode - do not change offset in offsetfile
RETURN VALUES
0 successful
65 cannot get the size of logfile
66 general file or directory access issue
73 cannot write offsetfile
AUTHOR
The original logtail was written in C by Craig H. Rowland <crowland@psionic.com>. This version of logtail is a modification of Paul Sloot-
man's re-implementation in perl. enhanced by the Debian Logcheck Team <logcheck-devel@lists.alioth.debian.org>.
This manual was written by Oohara Yuuma <oohara@libra.interq.or.jp> and enhanced by the Debian Logcheck Team
<logcheck-devel@lists.alioth.debian.org>..
SEE ALSO logcheck(8)Debian 28 Jul 2007 LOGTAIL(8)