[Declude.JunkMail] FW: [sniffer] Sniffer Notifications now failing declude spamheaders test

2005-01-03 Thread Marc Catuogno
I don't mean to be a nag but this was just posted to the sniffer forum and is exactly what I was talking about. It is almost 48 hours after the first post discussing this bug and there is still no e-mail from Declude that I am aware of that has gone out. -Original Message-From:

Re: [Declude.JunkMail] FW: [sniffer] Sniffer Notifications now failing declude spamheaders test

2005-01-03 Thread [EMAIL PROTECTED]
Hi, The inevitable in light of new management? Thanks, Andrew Baldwin [EMAIL PROTECTED] http://www.thumpernet.com 315-282-0020 Monday, January 3, 2005, 11:30:22 AM, you wrote: I don't mean to be a nag but this was just posted to the sniffer forum and is exactly what I was talking about.

Re: [Declude.JunkMail] FW: [sniffer] Sniffer Notifications now failing declude spamheaders test

2005-01-03 Thread Pete McNeil
On Monday, January 3, 2005, 11:30:22 AM, Marc wrote: MC I don't mean to be a nag but this was just posted to the MC sniffer forum and is exactly what I was talking about. It is MC almost 48 hours after the first post discussing this bug and MC there is still no e-mail from Declude that I am

Re: [Declude.JunkMail] FW: [sniffer] Sniffer Notifications now failing declude spamheaders test

2005-01-03 Thread Matt
IMO, let CPHZ decide how they want to handle their customers, and let the customers decide how to handle CPHZ. Things have already been said, and similar feelings are shared among many others, but I don't know that they have developed an understanding yet of the importance of 24/7/365 problem

Re[2]: [Declude.JunkMail] FW: [sniffer] Sniffer Notifications now failing declude spamheaders test

2005-01-03 Thread [EMAIL PROTECTED]
Hi, I have a support contract, I'm NOT one of those inexperienced users, and I DO primarily rely on the list for info. Anyway you slice it, no notice from Declude about the issue (we figured it out on our own the hard way when customers started complaining) and I confirmed there was an issue