Customer Notification System.
jwininger at ifncom.net
Thu Feb 23 02:43:31 UTC 2012
Well there isn't anything wrong with the mail list approach, but it is more complicated than sending email to a list of customers. We have several types of services (transport, ss7, managed Noc svc etc). Having the db backend would give us flexibility for future notifications based on type of service etc.
On Feb 22, 2012, at 6:02 AM, "Rich Kulawiec" <rsk at 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.
> (a) Use ASCII. Using PDF for this is insane.
> (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?
>> I have thought of possibly using a
>> mailing list type approach, but that gets us back to (almost) where we
>> are today.
> 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.
More information about the NANOG