Debug to file is working. No database logging is working. Within the file debugging there are entries stating that SA has tried to create the databases:
12 March 2008 17:46:51 CreateTable: () create table sa_uptime( said varchar(15),uniqueid numeric, nYear numeric, nmonth numeric, nday numeric,upcycles numeric, downcycles numeric, maintenancecycles numeric, unavailablecycles numeric, totalcycles numeric,upseconds numeric, downseconds numeric, maintenanceseconds numeric, unavailableseconds numeric, totalseconds numeric) Dirk Bulinckx wrote: > Not sure to understand, so the debug logging (to DB) works and not the others? > Or are none of the DB loggings working, and are you refering to the debug (to > file) logging? > > Dirk Bulinckx. > > -----Original Message----- > From: Servers Alive Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of > Peter Shankland > Sent: Wednesday, March 12, 2008 7:01 PM > To: Servers Alive Discussion List > Subject: Re: [Fwd: Re: [SA-list] Uptime Logging to Database Problem] > > Yes, it is failing for all DB logging. I have got the file debugging > working on the new machine it is reporting that it tries to create the > tables / databases. > > Dirk Bulinckx wrote: > >> is it failing for the other db loggings too? >> >> Dirk Bulinckx. >> >> -----Original Message----- >> From: Servers Alive Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of >> Peter Shankland >> Sent: Wednesday, March 12, 2008 6:41 PM >> To: Servers Alive Discussion List >> Subject: Re: [Fwd: Re: [SA-list] Uptime Logging to Database Problem] >> >> No haven't got any failed login entries. I have now out Windows 2003 SP2 >> onto a clean machine and installed Servers Alive 6.1.2204. I have >> registered it, created an ODBC connection to a known good remote SQL2000 >> server and I still can't the database to create :( >> >> Any other suggestions? >> >> Thanks. >> >> Dirk Bulinckx wrote: >> >> >>> do you see within SQL a failed login when you try to create the table? >>> >>> Dirk Bulinckx. >>> >>> -----Original Message----- >>> From: Servers Alive Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of >>> [EMAIL PROTECTED] >>> Sent: Wednesday, March 12, 2008 2:00 PM >>> To: Servers Alive Discussion List >>> Subject: Re: [Fwd: Re: [SA-list] Uptime Logging to Database Problem] >>> >>> SQL user - the built in 'sa' user which has rights to do anything and >>> everything on the SQL box. >>> >>> "Dirk Bulinckx" <[EMAIL PROTECTED]> wrote: >>> >>> >>> >>> >>>> and the user you're using in a Windows or SQL user? >>>> >>>> Dirk Bulinckx. >>>> >>>> -----Original Message----- >>>> From: Servers Alive Discussion List [mailto:[EMAIL PROTECTED] On Behalf >>>> >>>> >>>> >>> Of >>> >>> >>> >>>> [EMAIL PROTECTED] >>>> Sent: Wednesday, March 12, 2008 11:40 AM >>>> To: Servers Alive Discussion List >>>> Subject: Re: [Fwd: Re: [SA-list] Uptime Logging to Database Problem] >>>> >>>> The SQL Server runs mixed authentication allowing both SQL and Windows >>>> >>>> >>>> >>> logins. >>> >>> >>> >>>> "Dirk Bulinckx" <[EMAIL PROTECTED]> wrote: >>>> >>>> >>>> >>>> >>>>> What type of authentication is used by your SQL server? Windows or SQL >>>>> authentication, >>>>> >>>>> Dirk Bulinckx. >>>>> >>>>> -----Original Message----- >>>>> From: Servers Alive Discussion List [mailto:[EMAIL PROTECTED] On Behalf >>>>> >>>>> >>>>> >>>> Of >>>> >>>> >>>> >>>>> [EMAIL PROTECTED] >>>>> Sent: Wednesday, March 12, 2008 10:30 AM >>>>> To: Servers Alive Discussion List >>>>> Subject: Re: [Fwd: Re: [SA-list] Uptime Logging to Database Problem] >>>>> >>>>> Have just tried switching on the other loggings to a database and these >>>>> >>>>> >>>>> >>>> aren't >>>> >>>> >>>> >>>>> working either. >>>>> >>>>> Have also checked out the sa user in SQL2005 and it is enabled and working >>>>> fine as have manually been able to create a database with no probs. >>>>> >>>>> Finally, I have also put DOMAIN\Domain Admins into SQL2005 as 'sysadmin' >>>>> >>>>> >>>>> >>> and >>> >>> >>> >>>>> ran ServersAlive service as a domain admin, but this still didn't create >>>>> >>>>> >>>>> >>> the >>> >>> >>> >>>>> database(s). Have reverted back to the Local System Account now. >>>>> >>>>> Any suggestions? >>>>> >>>>> "Dirk Bulinckx" <[EMAIL PROTECTED]> wrote: >>>>> >>>>> >>>>> >>>>> >>>>>> In ODBC theoreticaly the login is done via the given user (in ODBC), >>>>>> >>>>>> >>>>>> >>>>> sometimes >>>>> >>>>> >>>>> >>>>>> however with NT/Windows authentication even ODBC isn't able to handle >>>>>> >>>>>> >>>>>> >>>> this. >>>> >>>> >>>> >>>>>> Are you also using the other DB loggings and are they using the same >>>>>> >>>>>> >>>>>> >>> ODBC >>> >>> >>> >>>>>> credentials and are those working fine? >>>>>> >>>>>> >>>>>> Dirk Bulinckx. >>>>>> >>>>>> -----Original Message----- >>>>>> From: Servers Alive Discussion List [mailto:[EMAIL PROTECTED] On >>>>>> >>>>>> >>>>>> >>> Behalf >>> >>> >>> >>>>> Of >>>>> >>>>> >>>>> >>>>>> [EMAIL PROTECTED] >>>>>> Sent: Wednesday, March 12, 2008 10:00 AM >>>>>> To: Servers Alive Discussion List >>>>>> Subject: Re: [Fwd: Re: [SA-list] Uptime Logging to Database Problem] >>>>>> >>>>>> Thanks for the reply, but should it matter if the user who runs the SA >>>>>> >>>>>> >>>>>> >>>>> service >>>>> >>>>> >>>>> >>>>>> has access to create tables or not, as when you enter the DB details >>>>>> >>>>>> >>>>>> >>>> within >>>> >>>> >>>> >>>>> SA >>>>> >>>>> >>>>> >>>>>> it asks for a username and password? Here I have been using the 'sa' >>>>>> >>>>>> >>>>>> >>> user. >>> >>> >>> >>>>>> "Tobie Fysh" <[EMAIL PROTECTED]> wrote: >>>>>> >>>>>> >>>>>> >>>>>> >>>>>>> The user that Servers Alive is running as has rights to create a >>>>>>> >>>>>>> >>>>>>> >>> table? >>> >>> >>> >>>>>>> -----Original Message----- >>>>>>> From: Servers Alive Discussion List [mailto:[EMAIL PROTECTED] On >>>>>>> Behalf Of Peter Shankland >>>>>>> Sent: 11 March 2008 21:46 >>>>>>> To: Servers Alive Discussion List >>>>>>> Subject: [Fwd: Re: [SA-list] Uptime Logging to Database Problem] >>>>>>> >>>>>>> Have just tried creating a new ODBC connection to a different SQL2000 >>>>>>> server and changing the setup within SA to point to this ODBC >>>>>>> >>>>>>> >>>>>>> >>> connection >>> >>> >>> >>>>>>> instead. Unfortunatly, I still can't create the table so at least it >>>>>>> rules out a problem with the local copy of SQL2005. >>>>>>> >>>>>>> Has anyone else had any difficulties getting Uptime logging to a DB? >>>>>>> >>>>>>> Thanks. >>>>>>> >>>>>>> -------- Original Message -------- >>>>>>> Subject: Re: [SA-list] Uptime Logging to Database Problem >>>>>>> Date: Fri, 07 Mar 2008 11:25:38 +0100 >>>>>>> From: [EMAIL PROTECTED] >>>>>>> Reply-To: Servers Alive Discussion List <[email protected]> >>>>>>> To: Servers Alive Discussion List <[email protected]> >>>>>>> >>>>>>> >>>>>>> >>>>>>> Hi Dirk, >>>>>>> >>>>>>> When I run as an app, the table still dosn't get created. The >>>>>>> >>>>>>> >>>>>>> >>> following >>> >>> >>> >>>>>>> is from the debug debug log file: >>>>>>> >>>>>>> 07 March 2008 10:10:47 CreateTable: () create table salive( said >>>>>>> varchar(15),uniqueid numeric, nYear numeric, nmonth numeric, nday >>>>>>> numeric,upcycles numeric, downcycles numeric, maintenancecycles >>>>>>> >>>>>>> >>>>>>> >>> numeric, >>> >>> >>> >>>>>>> unavailablecycles numeric, totalcycles numeric,upseconds numeric, >>>>>>> downseconds numeric, maintenanceseconds numeric, unavailableseconds >>>>>>> >>>>>>> I don't think this should matter but I am running MySQL on the same >>>>>>> server. Obviously, I have had to set up an ODBC connection to the >>>>>>> >>>>>>> >>>>>>> >>> local >>> >>> >>> >>>>>>> SQL2005 instance and this works fine, hence the reason I can't see >>>>>>> >>>>>>> >>>>>>> >>> MySQL >>> >>> >>> >>>>>>> would be an issue - thought I should mention it though. >>>>>>> >>>>>>> Thanks. >>>>>>> >>>>>>> Pete. >>>>>>> >>>>>>> Dirk Bulinckx wrote: >>>>>>> >>>>>>> >>>>>>> >>>>>>>> When running as app, and when you say the table doesn't get created, >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>> what >>>>>>> does >>>>>>> >>>>>>> >>>>>>> >>>>>>>> the debuglogfile show for that as reason? >>>>>>>> >>>>>>>> Dirk Bulinckx. >>>>>>>> >>>>>>>> -----Original Message----- >>>>>>>> From: Servers Alive Discussion List [mailto:[EMAIL PROTECTED] On >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>> Behalf >>>>>>> Of >>>>>>> >>>>>>> >>>>>>> >>>>>>>> Peter Shankland >>>>>>>> Sent: Friday, February 15, 2008 3:20 PM >>>>>>>> To: Servers Alive Discussion List >>>>>>>> Subject: Re: [SA-list] Uptime Logging to Database Problem >>>>>>>> >>>>>>>> Sorry it has taken so long to reply... >>>>>>>> >>>>>>>> Q: Could it be that you're running app and service at the same >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>> time? >>>>>>> >>>>>>> >>>>>>> >>>>>>>> A: Definatly just running the service >>>>>>>> >>>>>>>> Q: Does the service user have rights to the directory where the >>>>>>>> logfile should be created? >>>>>>>> A: Yes, running as local admin >>>>>>>> >>>>>>>> Q: If you run it as app does it then create the file/table? >>>>>>>> A: If I run as app the debug file does get created, but the table >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>> dosn't >>>>>>> >>>>>>> >>>>>>> >>>>>>>> Q: Are you checking via a remote connection or directly on the >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>> system >>>>>>> >>>>>>> >>>>>>> >>>>>>>> A: Always run through RDC using the command 'mstsc /console' >>>>>>>> >>>>>>>> Thanks. >>>>>>>> >>>>>>>> Dirk Bulinckx wrote: >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>>> Could it be that you're running app and service at the same time? >>>>>>>>> does the service user have rights to the directory were the logfile >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>> should >>>>>>> be >>>>>>> >>>>>>> >>>>>>> >>>>>>>>> created? >>>>>>>>> If you run it as app does it then create the file/table? >>>>>>>>> Are you checking this via a remote connection or directly on the >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>> system? >>>>>>> >>>>>>> >>>>>>> >>>>>>>>> Dirk Bulinckx. >>>>>>>>> >>>>>>>>> -----Original Message----- >>>>>>>>> From: Servers Alive Discussion List [mailto:[EMAIL PROTECTED] On >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>> Behalf >>>>>>> Of >>>>>>> >>>>>>> >>>>>>> >>>>>>>>> Peter Shankland >>>>>>>>> Sent: Sunday, February 10, 2008 2:40 PM >>>>>>>>> To: Servers Alive Discussion List >>>>>>>>> Subject: Re: [SA-list] Uptime Logging to Database Problem >>>>>>>>> >>>>>>>>> I have now got the debug logging to 'stay' with the changes I have >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>> made >>>>>>> >>>>>>> >>>>>>> >>>>>>>>> by restarting the service, but even though I have the debug logging >>>>>>>>> >>>>>>>>> >>>>>>>>> >>> >>> >>> >>>>>>>>> enabled and set to maximum, I get no log file created :(. This is >>>>>>>>> >>>>>>>>> >>>>>>>>> >>> the >>> >>> >>> >>>>>>>>> same sort of problem as I am getting with the SQL Uptime logging. >>>>>>>>> >>>>>>>>> Peter Shankland wrote: >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>>> It is running as a Service. Whenever I try to enable debug logging >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>> to >>>>>>> >>>>>>> >>>>>>> >>>>>>>>>> file, I put in the details, click apply then ok and then when I go >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>> back >>>>>>> >>>>>>> >>>>>>> >>>>>>>>>> into the setup the changes I have made revert to defaults, it all >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>> the >>>>>>> >>>>>>> >>>>>>> >>>>>>>>>> changes have dissapeared! >>>>>>>>>> >>>>>>>>>> Very strange >>>>>>>>>> >>>>>>>>>> Dirk Bulinckx wrote: >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>>> How is SA running, as service or as app? >>>>>>>>>>> Does the debuglog (file based) show any errors? >>>>>>>>>>> >>>>>>>>>>> Dirk Bulinckx. >>>>>>>>>>> >>>>>>>>>>> -----Original Message----- >>>>>>>>>>> From: Servers Alive Discussion List [mailto:[EMAIL PROTECTED] >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>> On >>> >>> >>> >>>>>>> Behalf >>>>>>> >>>>>>> >>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>> Of >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>>>>> Peter Shankland >>>>>>>>>>> Sent: Sunday, February 10, 2008 1:35 PM >>>>>>>>>>> To: Servers Alive Discussion List >>>>>>>>>>> Subject: [SA-list] Uptime Logging to Database Problem >>>>>>>>>>> >>>>>>>>>>> I am using Servers Alive v6.1 and, on the same server, have SQL >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>> Express >>>>>>> >>>>>>> >>>>>>> >>>>>>>>>>> 2005 installed as I want to be able to log uptime / downtime to a >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>> DB. >>>>>>> >>>>>>> >>>>>>> >>>>>>>>>>> I have created the ODBC connection and it tests ok but when I go >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>> into SA >>>>>>> >>>>>>> >>>>>>> >>>>>>>>>>> and Uptime Logging --> To Database, I enter all the correct >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>> information >>>>>>> >>>>>>> >>>>>>> >>>>>>>>>>> and press Create Table but the table never does create. >>>>>>>>>>> >>>>>>>>>>> I have also tried manually creating the DB and then just >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>> configuring SA >>>>>>> >>>>>>> >>>>>>> >>>>>>>>>>> to use it but no user tables ever get created. >>>>>>>>>>> >>>>>>>>>>> Any suggestions / ideas? >>>>>>>>>>> >>>>>>>>>>> Thanks. >>>>>>>>>>> >>>>>>>>>>> To unsubscribe send a message with UNSUBSCRIBE as subject to >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>> [email protected] >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>>>> If you use auto-responders (like out-of-the-office messages), >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>> then >>> >>> >>> >>>>>>> make >>>>>>> sure >>>>>>> >>>>>>> >>>>>>> >>>>>>>>>>> that they are not send to the list nor to the individual members >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>> of >>> >>> >>> >>>>>>> the >>>>>>> list >>>>>>> >>>>>>> >>>>>>> >>>>>>>>>>> that send a message. Doing this will get you removed from the >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>> list. >>>>>>> >>>>>>> >>>>>>> >>>>>>>>>>> To unsubscribe send a message with UNSUBSCRIBE as subject to >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>> [email protected] >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>>>> If you use auto-responders (like out-of-the-office messages), >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>> then >>> >>> >>> >>>>>>> make >>>>>>> sure >>>>>>> >>>>>>> >>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>> that they are not send to the list nor to the individual members of >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>> the >>>>>>> list >>>>>>> >>>>>>> >>>>>>> >>>>>>>>> that send a message. Doing this will get you removed from the >>>>>>>>> >>>>>>>>> >>>>>>>>> >>> list. >>> >>> >>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>> To unsubscribe send a message with UNSUBSCRIBE as subject to >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>> [email protected] >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>>> If you use auto-responders (like out-of-the-office messages), then >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>> make >>>>>>> sure >>>>>>> >>>>>>> >>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>> that they are not send to the list nor to the individual members of >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>> the >>>>>>> list >>>>>>> >>>>>>> >>>>>>> >>>>>>>>> that send a message. Doing this will get you removed from the >>>>>>>>> >>>>>>>>> >>>>>>>>> >>> list. >>> >>> >>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>> To unsubscribe send a message with UNSUBSCRIBE as subject to >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>> [email protected] >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>>> If you use auto-responders (like out-of-the-office messages), then >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>> make >>>>>>> sure >>>>>>> >>>>>>> >>>>>>> >>>>>>>>> that they are not send to the list nor to the individual members of >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>> the >>>>>>> list >>>>>>> >>>>>>> >>>>>>> >>>>>>>>> that send a message. Doing this will get you removed from the >>>>>>>>> >>>>>>>>> >>>>>>>>> >>> list. >>> >>> >>> >>>>>>>>> To unsubscribe send a message with UNSUBSCRIBE as subject to >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>> [email protected] >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>>> If you use auto-responders (like out-of-the-office messages), then >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>> make >>>>>>> sure >>>>>>> >>>>>>> >>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>> that they are not send to the list nor to the individual members of >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>> the list >>>>>>> >>>>>>> >>>>>>> >>>>>>>> that send a message. Doing this will get you removed from the list. >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>> To unsubscribe send a message with UNSUBSCRIBE as subject to >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>> [email protected] >>>>>>> >>>>>>> >>>>>>> >>>>>>>> If you use auto-responders (like out-of-the-office messages), then >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>> make sure >>>>>>> >>>>>>> >>>>>>> >>>>>>>> that they are not send to the list nor to the individual members of >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>> the list >>>>>>> >>>>>>> >>>>>>> >>>>>>>> that send a message. Doing this will get you removed from the list. >>>>>>>> >>>>>>>> To unsubscribe send a message with UNSUBSCRIBE as subject to >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>> [email protected] >>>>>>> >>>>>>> >>>>>>> >>>>>>>> If you use auto-responders (like out-of-the-office messages), then >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>> make sure >>>>>>> that they are not send to the list nor to the individual members of >>>>>>> >>>>>>> >>>>>>> >>> the >>> >>> >>> >>>>>>> list >>>>>>> that send a message. Doing this will get you removed from the list. >>>>>>> >>>>>>> >>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>> To unsubscribe send a message with UNSUBSCRIBE as subject to >>>>>>> [email protected] >>>>>>> If you use auto-responders (like out-of-the-office messages), then >>>>>>> >>>>>>> >>>>>>> >>> make >>> >>> >>> >>>>>>> sure that they are not send to the list nor to the individual members >>>>>>> >>>>>>> >>>>>>> >>> of >>> >>> >>> >>>>>>> the list that send a message. Doing this will get you removed from >>>>>>> >>>>>>> >>>>>>> >>> the >>> >>> >>> >>>>>>> list. >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>> To unsubscribe send a message with UNSUBSCRIBE as subject to >>>>>> [email protected] >>>>>> If you use auto-responders (like out-of-the-office messages), then make >>>>>> >>>>>> >>>>>> >>>> sure >>>> >>>> >>>> >>>>>> that they are not send to the list nor to the individual members of the >>>>>> >>>>>> >>>>>> >>>> list >>>> >>>> >>>> >>>>>> that send a message. Doing this will get you removed from the list. >>>>>> >>>>>> To unsubscribe send a message with UNSUBSCRIBE as subject to >>>>>> [email protected] >>>>>> If you use auto-responders (like out-of-the-office messages), then make >>>>>> >>>>>> >>>>>> >>>> sure >>>> >>>> >>>> >>>>>> that they are not send to the list nor to the individual members of the >>>>>> >>>>>> >>>>>> >>>> list >>>> >>>> >>>> >>>>>> that send a message. Doing this will get you removed from the list. >>>>>> >>>>>> >>>>>> >>>>>> >>>>> To unsubscribe send a message with UNSUBSCRIBE as subject to >>>>> [email protected] >>>>> If you use auto-responders (like out-of-the-office messages), then make >>>>> >>>>> >>>>> >>> sure >>> >>> >>> >>>>> that they are not send to the list nor to the individual members of the >>>>> >>>>> >>>>> >>> list >>> >>> >>> >>>>> that send a message. Doing this will get you removed from the list. >>>>> >>>>> To unsubscribe send a message with UNSUBSCRIBE as subject to >>>>> [email protected] >>>>> If you use auto-responders (like out-of-the-office messages), then make >>>>> >>>>> >>>>> >>> sure >>> >>> >>> >>>>> that they are not send to the list nor to the individual members of the >>>>> >>>>> >>>>> >>> list >>> >>> >>> >>>>> that send a message. Doing this will get you removed from the list. >>>>> >>>>> >>>>> >>>>> >>>> To unsubscribe send a message with UNSUBSCRIBE as subject to >>>> [email protected] >>>> If you use auto-responders (like out-of-the-office messages), then make >>>> sure >>>> that they are not send to the list nor to the individual members of the >>>> list >>>> that send a message. Doing this will get you removed from the list. >>>> >>>> To unsubscribe send a message with UNSUBSCRIBE as subject to >>>> [email protected] >>>> If you use auto-responders (like out-of-the-office messages), then make >>>> sure >>>> that they are not send to the list nor to the individual members of the >>>> list >>>> that send a message. Doing this will get you removed from the list. >>>> >>>> >>>> >>>> >>> To unsubscribe send a message with UNSUBSCRIBE as subject to >>> >>> >> [email protected] >> >> >>> If you use auto-responders (like out-of-the-office messages), then make sure >>> that they are not send to the list nor to the individual members of the list >>> that send a message. Doing this will get you removed from the list. >>> >>> To unsubscribe send a message with UNSUBSCRIBE as subject to >>> >>> >> [email protected] >> >> >>> If you use auto-responders (like out-of-the-office messages), then make sure >>> >>> >> that they are not send to the list nor to the individual members of the list >> that send a message. Doing this will get you removed from the list. >> >> >>> >>> >> To unsubscribe send a message with UNSUBSCRIBE as subject to >> > [email protected] > >> If you use auto-responders (like out-of-the-office messages), then make sure >> that they are not send to the list nor to the individual members of the list >> that send a message. Doing this will get you removed from the list. >> >> To unsubscribe send a message with UNSUBSCRIBE as subject to >> > [email protected] > >> If you use auto-responders (like out-of-the-office messages), then make sure >> > that they are not send to the list nor to the individual members of the list > that send a message. Doing this will get you removed from the list. > >> >> > > To unsubscribe send a message with UNSUBSCRIBE as subject to > [email protected] > If you use auto-responders (like out-of-the-office messages), then make sure > that they are not send to the list nor to the individual members of the list > that send a message. Doing this will get you removed from the list. > > To unsubscribe send a message with UNSUBSCRIBE as subject to > [email protected] > If you use auto-responders (like out-of-the-office messages), then make sure > that they are not send to the list nor to the individual members of the list > that send a message. Doing this will get you removed from the list. > > > To unsubscribe send a message with UNSUBSCRIBE as subject to [email protected] If you use auto-responders (like out-of-the-office messages), then make sure that they are not send to the list nor to the individual members of the list that send a message. Doing this will get you removed from the list.
