Solved

powershell : sending e-mails : "newline" problem

Posted on 2009-05-19
2
3,677 Views
Last Modified: 2012-05-07
Hello,

I have a .BAT calling a .PS1 with output redirection to a log file :
powershell -command "& 'C:\script.ps1' " > C:\script.log

The PS1 is just doing some "echo $something" sometimes
The log file is correctly generated

Then my .BAT calls another PS1 script (see below) to e-mail the log file via an Exchange server. (the log file is args0] in the .BAT)
I'm checking the e-mail with OL2007

* When I send the content as an attachment, it's OK but it's boring to have to open the file
* When I send the content inline => all newlines disappear!!! everything is on one line depending on my outlook window size

I don't know if it's related to Outlook or Powershell (or both). I can't find in OL any place to check the real e-mail content (like headers and body)
I can't find any "System.Net.Mail.MailMessage" object property to force some encoding or raw text format.

Can someone help me?
Thank you
if ($args[0]) {
	$file = $args[0]
# todo : test-path $file
 
 
	$emailFrom = "bla@bla.com"
	$emailTo = "some@one.fr"
	$subject = "powershell / logs"
 
 
# if I want it as an attached file to see newlines
	#$body = "log file attached"
# if I want it inline
	$body = Get-Content $file
	$smtpServer = "my_smtp"
 
 
	$msg = new-object System.Net.Mail.MailMessage $emailFrom, $emailTo, $subject, $body
 
 
# below When I want the log file attached, instead of inline
	#$attachment = new-object System.Net.Mail.Attachment $fichier
	#$msg.Attachments.Add($attachment)
 
 
	$client = new-object System.Net.Mail.SmtpClient $smtpServer
	$client.Send($msg)
} else { echo "arg missing" }

Open in new window

0
Comment
Question by:mchkorg
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
2 Comments
 
LVL 4

Accepted Solution

by:
peter_field earned 500 total points
ID: 24448866
PowerShell only outputs newlines, not a carriage return when it is redirected via CMD.

http://www.microsoft.com/technet/scriptcenter/topics/msh/cmdlets/add-content.mspx

Outlook must not be able to handle this (you will find notepad doesn't like this, but wordpad does, so support on Windows is not entirely consistent).

In your PowerShell script that sends the email, try this:

$body = Get-Content $file | %{ "$_`r" }

Open in new window

0
 
LVL 7

Author Closing Comment

by:mchkorg
ID: 31582962
Great!
It took me some times to understand it was all about \n and \r as my log files are correct with notepad - maybe windows server's notepad is different from XP's
I didn't check in hexa

Regards
0

Featured Post

Resolve Critical IT Incidents Fast

If your data, services or processes become compromised, your organization can suffer damage in just minutes and how fast you communicate during a major IT incident is everything. Learn how to immediately identify incidents & best practices to resolve them quickly and effectively.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Recently we ran in to an issue while running some SQL jobs where we were trying to process the cubes.  We got an error saying failure stating 'NT SERVICE\SQLSERVERAGENT does not have access to Analysis Services. So this is a way to automate that wit…
The viewer will learn how to dynamically set the form action using jQuery.
Exchange organizations may use the Journaling Agent of the Transport Service to archive messages going through Exchange. However, if the Transport Service is integrated with some email content management application (such as an antispam), the admini…

752 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question