[150383] in North American Network Operators' Group
Re: Customer Notification System.
daemon@ATHENA.MIT.EDU (James Wininger)
Wed Feb 22 21:41:47 2012
From: "James Wininger" <jwininger@ifncom.net>
In-Reply-To: <20120222110124.GA24779@gsp.org>
Date: Wed, 22 Feb 2012 21:43:31 -0500
To: "Rich Kulawiec" <rsk@gsp.org>
Cc: nanog@nanog.org
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
Well there isn't anything wrong with the mail list approach, but it is more c=
omplicated than sending email to a list of customers. We have several types o=
f services (transport, ss7, managed Noc svc etc). Having the db backend woul=
d give us flexibility for future notifications based on type of service etc.=
--=20
Jim Wininger
On Feb 22, 2012, at 6:02 AM, "Rich Kulawiec" <rsk@gsp.org> wrote:
> On Tue, Feb 21, 2012 at 05:58:19PM -0500, James Wininger wrote:
>> We would need to send notifications out to say about 400 customers.
>> Ideally the system would send an attached PDF. It would be great if this
>> system were SQL based etc.
>=20
> (a) Use ASCII. Using PDF for this is insane.
>=20
> (b) You're dealing with only 400 customers, yet you want the overhead
> and complexity of a SQL-capable database? Do you also engage a fleet
> of bulldozers when you want to plant a flower in the back yard?
>=20
>> I have thought of possibly using a
>> mailing list type approach, but that gets us back to (almost) where we
>> are today.=20
>=20
> Precisely what is wrong with a "mailing list type approach", using
> Mailman (which is the best available and what runs this list)? It handles=
> COI (mandatory for responsible and ethical operation of all mailing lists)=
,
> it runs on all varieties of 'nix, it plays nice with MTAs, it deals with
> most bounces in a sane fashion, etc.
>=20
> ---rsk
>=20
