[150411] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

Re: Customer Notification System.

daemon@ATHENA.MIT.EDU (JC Dill)
Thu Feb 23 13:45:12 2012

Date: Thu, 23 Feb 2012 10:44:06 -0800
From: JC Dill <jcdill.lists@gmail.com>
To: NANOG list <nanog@nanog.org>
In-Reply-To: <0BED6E4A-3731-4904-BE4D-83579FB6A3EB@ifncom.net>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org

On 22/02/12 6:46 PM, James Wininger wrote:
> Well we would not be sending the notification in an attachment, but there are times when it would be nice to send a list of circuit ids (exported from billing system as PDF) or some other exported doc to the notification.

Nice for WHO?  There is absolutely no need to export something as simple 
as a list of circuit IDs as a pdf.  Use plain text.  Ditto for the rest 
of your exported DOCs.

When there are exceptions, when you need to include an image (sparingly, 
not because marketing thought it was a good idea to bling up all your 
emails), or a table, send in HTML with plain text.  Don't make the 
recipient start up another program to open an attachment.

jc



home help back first fref pref prev next nref lref last post