AF:
NF:0
PS:10
SRH:1
SFN:
DSR:
MID:<20090415145633.0c55c513@ripper.onstor.net>
CFG:
PT:0
S:andy.sharp@onstor.com
RQ:
SSV:mail.onstor.net
NSV:
SSH:
R:<patrick.haverty@onstor.com>
MAID:1
X-Sylpheed-Privacy-System:
X-Sylpheed-Sign:0
SCF:#mh/Mailbox/sent
RMID:#imap/andys@onstor.net@exch1.onstor.net/INBOX	0	102AB4F33EBBDB4C91915B145C8E9FB31284F9B4FD@exch1.onstor.net
X-Sylpheed-End-Special-Headers: 1
Date: Wed, 15 Apr 2009 14:58:41 -0700
From: Andrew Sharp <andy.sharp@onstor.com>
To: Patrick Haverty <patrick.haverty@onstor.com>
Subject: Re: Dell Openmanage IT Assistant and SNMP Messages
Message-ID: <20090415145841.51c2cad8@ripper.onstor.net>
In-Reply-To: <102AB4F33EBBDB4C91915B145C8E9FB31284F9B4FD@exch1.onstor.net>
References: <20090415131030.78b67971@ripper.onstor.net>
	<102AB4F33EBBDB4C91915B145C8E9FB31284F9B4FD@exch1.onstor.net>
Organization: Onstor
X-Mailer: Sylpheed-Claws 2.6.0 (GTK+ 2.8.20; x86_64-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

On Wed, 15 Apr 2009 13:43:15 -0700 Patrick Haverty
<patrick.haverty@onstor.com> wrote:

> Well I've been (recently) sending messages in plain text format and the default wrap is 76 characters, so I'm not sure why it isn't working.  And since I've switched to plain text messages I'm getting more complaints, about the lack of HTML for highlighting, etc.

As you can see, this was sent as one long line.

Not a big deal, you can skip the rest of this email if you want, but I
already typed it, so I'll send it.  ~:^)  My email client wraps long
lines, of course, so it's not a problem for me exactly, except when
replying, but I have seen the occassional email server rudely truncate
lines that exceed the technical limit.  Which they probably shouldn't
do, but whatever.  Somehow I've made a big deal out of absolutely
nothing.

I've only ever sent plain text, and I've rarely ever gotten any
comments.  Emails are supposed to be plain text, possibly with MIME
attachments, but never HTML directly in the body.  Outlook and Exchange
observe this rule and pretty much always send the proper format, even
if the default is for Outlook to display the HTML attachment as the
email itself.  Sending as HTML just means that every email contains two
copies of the actual message.  But whatever.  3/4 of everyone at Onstor
use Outlook and send these "double" emails, and my client just displays
the text only, so I try not to mention it too often.

Your client may have two settings, one for displaying your message as
you compose it, and another for wrapping it before it sends it.  I
think I've seen that before.

I know that Outlook does some bad stuff that it shouldn't do, when
displaying emails.  Like it doesn't observe the line endings as they
are in the original email, and instead tries to fill/justify/wrap in
it's own special way when it displays a message.  That is badness that
I haven't figured out how to fix.  There's probably a setting somewhere
in Outlook to make it stop doing this, but I haven't used Outlook in
close to a decade, so I'm a bit behind.  The really bad part is that
there doesn't seem to be any way to regain the original formatting of
the message.

I think I'll look into it further, however, now that you reminded me of
it.  It would make Larry's life easier if Outlook didn't do this to
some of the emails I send him.

> 
> -----Original Message-----
> From: Andy Sharp 
> Sent: Wednesday, April 15, 2009 1:11 PM
> To: Patrick Haverty
> Subject: Re: Dell Openmanage IT Assistant and SNMP Messages
> 
> This would be an option in your email client, which I assume is Outlook?  It's a pretty standard option in almost any email client known to man.  So you should find it somewhere in the config menus for Outlook.
> 
> The problem is that technically there is a line length limit for email messages, and some email servers might chop off lines in email messages longer than the limit.  Our email server, Exchange, doesn't care and ignores such things, but you never know where your email might end up.
> Also, it makes quoted replies difficult to read since the original line gets wrapped, but only the first line gets quoted.
> 
> Cheers,
> 
> a
> 
> On Wed, 15 Apr 2009 12:27:18 -0700 Patrick Haverty <patrick.haverty@onstor.com> wrote:
> 
> > Could you direct me to where I could set up a default wrap margin?  What email reader are you using?
> > 
> > -----Original Message-----
> > From: Andy Sharp
> > Sent: Wednesday, April 15, 2009 12:24 PM
> > To: Patrick Haverty
> > Cc: Rendell Fong; Brian Stark
> > Subject: Re: Dell Openmanage IT Assistant and SNMP Messages
> > 
> > On Wed, 15 Apr 2009 12:20:06 -0700 Patrick Haverty <patrick.haverty@onstor.com> wrote:
> > 
> > > While not ideal to have the Leopard be a SNMP trap client, it could save us the cost of an optional RAC (Remote Access Controller) by allowing us to use the Nexenta SNMP to emailer route. 
> > > 
> > 
> > Hm, OK.  You must know something I don't. ~:^)  BTW, could you please configure your email client (Outlick?) to autowrap at some reasonable right margin, like 72 or whatever the default is?  Thankyouverymuch.
> > 
> > 
> > > -----Original Message-----
> > > From: Andy Sharp
> > > Sent: Wednesday, April 15, 2009 12:14 PM
> > > To: Rendell Fong
> > > Cc: Patrick Haverty; Brian Stark
> > > Subject: Re: Dell Openmanage IT Assistant and SNMP Messages
> > > 
> > > Well, there are two programs, snmptrapd and snmpd on nexenta/solaris.
> > > I assume that if you configure/run snmptrapd, that it will listen for traps.  Not exactly sure what that would accomplish for us.  Normally in a production environment I would not want a leopard also configured to be a SNMP trap host client.  Would I?  Yes, I'm very proud of myself for using the proper SNMP terminology.  One day when I'm older I'll actually know what it means.  Oops, I'm already older.  Sigh.
> > > 
> > > 
> > > On Wed, 15 Apr 2009 12:02:50 -0700 Rendell Fong <rendell.fong@onstor.com> wrote:
> > > 
> > > > If OpenSolaris has a command like netstat you can check to see if any process is listening on udp port 162.  This port is normally used for receiving SNMP trap msgs.
> > > > 
> > > > ________________________________
> > > > From: Patrick Haverty
> > > > Sent: Wednesday, April 15, 2009 11:41 AM
> > > > To: Andy Sharp; Rendell Fong
> > > > Cc: Brian Stark
> > > > Subject: Dell Openmanage IT Assistant and SNMP Messages
> > > > 
> > > > I disabled the IPMI over LAN function of the system (which would 
> > > > not
> > > work in "teamed" or aggregated port configuration) and then verified that hardware event messages were still being sent from the PowerEdge server and received by IT assistant running on a remote computer.
> > > SNMP_Message1.JPG shows the alert as it is received (bold
> > > highlighting) and SNMP_Message2.JPG just shows the complete set of 
> > > messages (upper
> > > six) that come through when an AC cord is unplugged and then re-plugged.
> > > Note that the IP address 10.11.1.220 is the one setup in the BMC BIOS settings (mostly for IPMI use), so there is not any response to an SNMP query.  I think that means that if there is not any active monitoring when the event messages are sent, then they are lost.  I was unable to figure out how to get the BMC to send the alert to a destination that the Nexenta/OpenSolaris system noticed.  There may be an OpenSolaris service which could receive an SNMP alert, but when I tried setting up the appliances IP address as the destination address for alerts, I could not see any reflection in the /var/adm/messages file or NMS log file that would indicate the system saw the SNMP alert.
> > > > 
> > > > Pat
