[150414] in North American Network Operators' Group
RE: Customer Notification System.
daemon@ATHENA.MIT.EDU (Vinny_Abello@Dell.com)
Thu Feb 23 14:29:46 2012
From: <Vinny_Abello@Dell.com>
To: <jcdill.lists@gmail.com>, <nanog@nanog.org>
Date: Thu, 23 Feb 2012 19:28:52 +0000
In-Reply-To: <4F4688F6.9000608@gmail.com>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
Paraphrasing someone else........ I would encourage my competitors to send =
notifications to their customers in PDF format.
:)
-Vinny
-----Original Message-----
From: JC Dill [mailto:jcdill.lists@gmail.com]=20
Sent: Thursday, February 23, 2012 1:44 PM
To: NANOG list
Subject: Re: Customer Notification System.
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 fr=
om 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=20
as a list of circuit IDs as a pdf. Use plain text. Ditto for the rest=20
of your exported DOCs.
When there are exceptions, when you need to include an image (sparingly,=20
not because marketing thought it was a good idea to bling up all your=20
emails), or a table, send in HTML with plain text. Don't make the=20
recipient start up another program to open an attachment.
jc
