Re: Strange apache behaviour? (solved)
On Mon, Dec 10, 2001 at 12:57:02PM +1100, Craig Sanders wrote: > /etc/cron.daily is a conffile and will not be overwritten on upgrade > without dpkg asking you for permission. hmm... Strange. It happened twice on two different machines. I considered it a minor issue at the time. bob -- bob billsonemail: [EMAIL PROTECTED] ham: kc2wz /) [EMAIL PROTECTED] beekeeper -8|||} "Níl aon tinteán mar do thinteán féin." --DorothyLinux geek \)
Re: Strange apache behaviour? (solved)
On Sun, Dec 09, 2001 at 08:19:52PM -0500, Bob Billson wrote: > > apache builds, I was suggesting that this could be an optional > > feature maybe made in /etc/apache/cron.conf, > > I agree. Why not file a "wishlist" bug report against apache? > > > /etc/cron.daily/apache is marked as a conf file, so the next time > > apache is updated/upgraded, the changes will be overwritten and yet > > again need to be manually changed. See the problem? > > Yup and I agree. I've had my changes overwritten as well. Add that > to the wishlist bug report and see if the package maintainer agrees. huh? /etc/cron.daily is a conffile and will not be overwritten on upgrade without dpkg asking you for permission. $ cat /var/lib/dpkg/info/apache.conffiles /etc/init.d/apache /etc/cron.daily/apache /etc/apache/cron.conf isn't a conffile. it's copied from /usr/share/doc/apache/examples/cron.conf *only* if it doesn't already exist. i don't know why he did it like that. i would have just made it a conffile btw, i wrote the /etc/apache/cron.conf thing and edited the apache cron.daily script to use it a few years ago and submitted it as a patch. its purpose was to provide a way for the sysadmin to specify when the log files should be rotated as there wasn't really any sensible default. small sites might like weekly, but large sites probably want daily. i think netgod added the CHOWN bit himself. it wouldn't be hard at all to add another variable for permissions, defaulting to the current 640. craig -- craig sanders <[EMAIL PROTECTED]> Fabricati Diem, PVNC. -- motto of the Ankh-Morpork City Watch
Re: Strange apache behaviour? (solved)
On Mon, Dec 10, 2001 at 05:28:00AM +1100, Jason Lim wrote: > Yeap, I already replied on that and posted the correct lines to change. Sorry, I was having a "mental moment". :) > apache builds, I was suggesting that this could be an optional feature > maybe made in /etc/apache/cron.conf, I agree. Why not file a "wishlist" bug report against apache? > /etc/cron.daily/apache is marked as a conf file, so the next time apache > is updated/upgraded, the changes will be overwritten and yet again need to > be manually changed. See the problem? Yup and I agree. I've had my changes overwritten as well. Add that to the wishlist bug report and see if the package maintainer agrees. bob -- bob billsonemail: [EMAIL PROTECTED] ham: kc2wz /) [EMAIL PROTECTED] beekeeper -8|||} "Níl aon tinteán mar do thinteán féin." --DorothyLinux geek \)
Re: Strange apache behaviour? (solved)
On Mon, Dec 10, 2001 at 12:57:02PM +1100, Craig Sanders wrote: > /etc/cron.daily is a conffile and will not be overwritten on upgrade > without dpkg asking you for permission. hmm... Strange. It happened twice on two different machines. I considered it a minor issue at the time. bob -- bob billsonemail: [EMAIL PROTECTED] ham: kc2wz /) [EMAIL PROTECTED] beekeeper -8|||} "Níl aon tinteán mar do thinteán féin." --DorothyLinux geek \) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Strange apache behaviour? (solved)
On Sun, Dec 09, 2001 at 08:19:52PM -0500, Bob Billson wrote: > > apache builds, I was suggesting that this could be an optional > > feature maybe made in /etc/apache/cron.conf, > > I agree. Why not file a "wishlist" bug report against apache? > > > /etc/cron.daily/apache is marked as a conf file, so the next time > > apache is updated/upgraded, the changes will be overwritten and yet > > again need to be manually changed. See the problem? > > Yup and I agree. I've had my changes overwritten as well. Add that > to the wishlist bug report and see if the package maintainer agrees. huh? /etc/cron.daily is a conffile and will not be overwritten on upgrade without dpkg asking you for permission. $ cat /var/lib/dpkg/info/apache.conffiles /etc/init.d/apache /etc/cron.daily/apache /etc/apache/cron.conf isn't a conffile. it's copied from /usr/share/doc/apache/examples/cron.conf *only* if it doesn't already exist. i don't know why he did it like that. i would have just made it a conffile btw, i wrote the /etc/apache/cron.conf thing and edited the apache cron.daily script to use it a few years ago and submitted it as a patch. its purpose was to provide a way for the sysadmin to specify when the log files should be rotated as there wasn't really any sensible default. small sites might like weekly, but large sites probably want daily. i think netgod added the CHOWN bit himself. it wouldn't be hard at all to add another variable for permissions, defaulting to the current 640. craig -- craig sanders <[EMAIL PROTECTED]> Fabricati Diem, PVNC. -- motto of the Ankh-Morpork City Watch -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Strange apache behaviour? (solved)
On Mon, Dec 10, 2001 at 05:28:00AM +1100, Jason Lim wrote: > Yeap, I already replied on that and posted the correct lines to change. Sorry, I was having a "mental moment". :) > apache builds, I was suggesting that this could be an optional feature > maybe made in /etc/apache/cron.conf, I agree. Why not file a "wishlist" bug report against apache? > /etc/cron.daily/apache is marked as a conf file, so the next time apache > is updated/upgraded, the changes will be overwritten and yet again need to > be manually changed. See the problem? Yup and I agree. I've had my changes overwritten as well. Add that to the wishlist bug report and see if the package maintainer agrees. bob -- bob billsonemail: [EMAIL PROTECTED] ham: kc2wz /) [EMAIL PROTECTED] beekeeper -8|||} "Níl aon tinteán mar do thinteán féin." --DorothyLinux geek \) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Strange apache behaviour? (solved)
Yeap, I already replied on that and posted the correct lines to change. All I was saying was that since this was a recent change in the latest apache builds, I was suggesting that this could be an optional feature maybe made in /etc/apache/cron.conf, to allow people to stay with the original previous way of doing things. I don't think /etc/cron.daily/apache is marked as a conf file, so the next time apache is updated/upgraded, the changes will be overwritten and yet again need to be manually changed. See the problem? - Original Message - From: "Bob Billson" <[EMAIL PROTECTED]> To: Sent: Monday, December 10, 2001 2:02 AM Subject: Re: Strange apache behaviour? (solved) > On Sun, Dec 09, 2001 at 01:16:03PM +1100, Jason Lim wrote: > > I know about that option... > > but it doesn't CHMOD... it only chowns. > > Right. And look at /etc/cron.daily/apache. You'll see where > owner/permissions are set depending on its value, as Pete said. Edit to > suit your situation. > > bob > -- > bob billsonemail: [EMAIL PROTECTED] ham: kc2wz /) > [EMAIL PROTECTED] beekeeper -8|||} > "Níl aon tinteán mar do thinteán féin." --DorothyLinux geek \) > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > >
Re: Strange apache behaviour? (solved)
Yeap, I already replied on that and posted the correct lines to change. All I was saying was that since this was a recent change in the latest apache builds, I was suggesting that this could be an optional feature maybe made in /etc/apache/cron.conf, to allow people to stay with the original previous way of doing things. I don't think /etc/cron.daily/apache is marked as a conf file, so the next time apache is updated/upgraded, the changes will be overwritten and yet again need to be manually changed. See the problem? - Original Message - From: "Bob Billson" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, December 10, 2001 2:02 AM Subject: Re: Strange apache behaviour? (solved) > On Sun, Dec 09, 2001 at 01:16:03PM +1100, Jason Lim wrote: > > I know about that option... > > but it doesn't CHMOD... it only chowns. > > Right. And look at /etc/cron.daily/apache. You'll see where > owner/permissions are set depending on its value, as Pete said. Edit to > suit your situation. > > bob > -- > bob billsonemail: [EMAIL PROTECTED] ham: kc2wz /) > [EMAIL PROTECTED] beekeeper -8|||} > "Níl aon tinteán mar do thinteán féin." --DorothyLinux geek \) > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Strange apache behaviour? (solved)
On Sun, Dec 09, 2001 at 01:16:03PM +1100, Jason Lim wrote: > I know about that option... > but it doesn't CHMOD... it only chowns. Right. And look at /etc/cron.daily/apache. You'll see where owner/permissions are set depending on its value, as Pete said. Edit to suit your situation. bob -- bob billsonemail: [EMAIL PROTECTED] ham: kc2wz /) [EMAIL PROTECTED] beekeeper -8|||} "Níl aon tinteán mar do thinteán féin." --DorothyLinux geek \)
Re: Strange apache behaviour? (solved)
On Sun, Dec 09, 2001 at 01:16:03PM +1100, Jason Lim wrote: > I know about that option... > but it doesn't CHMOD... it only chowns. Right. And look at /etc/cron.daily/apache. You'll see where owner/permissions are set depending on its value, as Pete said. Edit to suit your situation. bob -- bob billsonemail: [EMAIL PROTECTED] ham: kc2wz /) [EMAIL PROTECTED] beekeeper -8|||} "Níl aon tinteán mar do thinteán féin." --DorothyLinux geek \) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Strange apache behaviour? (solved)
I know about that option... but it doesn't CHMOD... it only chowns. - Original Message - From: "Bob Billson" <[EMAIL PROTECTED]> To: Sent: Sunday, December 09, 2001 11:58 AM Subject: Re: Strange apache behaviour? (solved) > On Sun, Dec 09, 2001 at 08:05:17AM +1100, Jason Lim wrote: > > Perhaps Johnie could make this an optional setting in > > /etc/apache/cron.conf or something like that...? > > There is: > > .# Whether to chown logfiles to the user/group Apache runs as. > APACHE_CHOWN_LOGFILES=0 > ^^ This should be 0 *not* 1, which I think is Debian's > default. > > This is used by /etc/cron.daily/apache. The server logs should root.adm or > root.root with 640 permissions. Having the same that runs the server > owner/group write permissions to the logs is asking for trouble. Nor > should the world normally be able to look them. > > bob > -- > bob billsonemail: [EMAIL PROTECTED] ham: kc2wz /) > [EMAIL PROTECTED] beekeeper -8|||} > "Níl aon tinteán mar do thinteán féin." --DorothyLinux geek \) > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > >
Re: Strange apache behaviour? (solved)
I know about that option... but it doesn't CHMOD... it only chowns. - Original Message - From: "Bob Billson" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Sunday, December 09, 2001 11:58 AM Subject: Re: Strange apache behaviour? (solved) > On Sun, Dec 09, 2001 at 08:05:17AM +1100, Jason Lim wrote: > > Perhaps Johnie could make this an optional setting in > > /etc/apache/cron.conf or something like that...? > > There is: > > .# Whether to chown logfiles to the user/group Apache runs as. > APACHE_CHOWN_LOGFILES=0 > ^^ This should be 0 *not* 1, which I think is Debian's > default. > > This is used by /etc/cron.daily/apache. The server logs should root.adm or > root.root with 640 permissions. Having the same that runs the server > owner/group write permissions to the logs is asking for trouble. Nor > should the world normally be able to look them. > > bob > -- > bob billsonemail: [EMAIL PROTECTED] ham: kc2wz /) > [EMAIL PROTECTED] beekeeper -8|||} > "Níl aon tinteán mar do thinteán féin." --DorothyLinux geek \) > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Strange apache behaviour? (solved)
On Sun, Dec 09, 2001 at 08:05:17AM +1100, Jason Lim wrote: > Perhaps Johnie could make this an optional setting in > /etc/apache/cron.conf or something like that...? There is: .# Whether to chown logfiles to the user/group Apache runs as. APACHE_CHOWN_LOGFILES=0 ^^ This should be 0 *not* 1, which I think is Debian's default. This is used by /etc/cron.daily/apache. The server logs should root.adm or root.root with 640 permissions. Having the same that runs the server owner/group write permissions to the logs is asking for trouble. Nor should the world normally be able to look them. bob -- bob billsonemail: [EMAIL PROTECTED] ham: kc2wz /) [EMAIL PROTECTED] beekeeper -8|||} "Níl aon tinteán mar do thinteán féin." --DorothyLinux geek \)
Re: Strange apache behaviour? (solved)
Thanks... The lines to change are: do if [ -f $LOG ] then if [ "$APACHE_CHOWN_LOGFILES" = "1" ] then savelog -c $APACHE_OLD_LOGS -m 640 -u $USR -g $GRP \ $LOG > /dev/null else savelog -c $APACHE_OLD_LOGS -m 640 -u root -g adm \ $LOG > /dev/null fi fi done changing 640 to 644. This should work... will wait a few days to make sure there are no side-effects to this. Perhaps Johnie could make this an optional setting in /etc/apache/cron.conf or something like that...? Sincerely, Jas - Original Message - From: "Peter Billson" <[EMAIL PROTECTED]> To: "Jason Lim" <[EMAIL PROTECTED]> Cc: Sent: Sunday, December 09, 2001 9:31 AM Subject: Re: Strange apache behaviour? > Jason, > Apaches log file ownership and permissions are set when they rotate in > /etc/cron.daily/apache (about line 90 or so). As pointed out there are > security issues to worry about so be careful. > > Pete > -- > http://www.elbnet.com > ELB Internet Services, Inc. > Web Design, Computer Consulting, Internet Hosting > > > Jason Lim wrote: > > > > Anyone figured out my apache problem (log file permissions)? > > > > I still haven't figured this one out yet. > > > > TIA, > > > > Jas > > > > - Original Message - > > From: "Jason Lim" <[EMAIL PROTECTED]> > > To: > > Sent: Saturday, December 08, 2001 1:52 AM > > Subject: Re: Strange apache behaviour? > > > > > Thats not very good security-wise to run webalizer as www-data, because > > if > > > a user ever finds a way to poison the log files, then webalizer will run > > > them as www-data, and possibly be able to fool around with apache too > > > (because they now run as the same user). > > > > > > A far better way (and much more direct) would be to have a way to change > > > apache's log files BACK to the previous permissions. > > > > > > I think if no one knows the answer i'll have to ask netgod himself... (i > > > think he is still the package maintainer?) > > > > > > Sincerely, > > > Jason > > > > > > - Original Message - > > > From: "Denis A. Kulgeyko" <[EMAIL PROTECTED]> > > > To: "Jason Lim" <[EMAIL PROTECTED]> > > > Sent: Friday, December 07, 2001 9:10 PM > > > Subject: Re: Strange apache behaviour? > > > > > > > > > > Hello ! > > > > > > > > > Do you know how to change the permissions of the log files apache > > > > > generates? > > > > > > > > > > -rw-r-1 www-data www-data 1372461 Dec 7 13:04 > > > apache-access.log > > > > > -rw-r-1 www-data www-data 740269 Dec 2 06:21 > > > > > apache-access.log.0 > > > > > -rw-r-1 www-data www-data44414 Nov 25 05:52 > > > > > apache-access.log.1.gz > > > > > -rw-rw-r--1 www-data www-data 167114 Sep 23 06:10 > > > > > apache-access.log.10.gz > > > > > -rw-rw-r--1 www-data www-data13069 Sep 16 06:06 > > > > > apache-access.log.11.gz > > > > > -rw-rw-r--1 www-data www-data14357 Sep 9 06:04 > > > > > apache-access.log.12.gz > > > > > -rw-rw-r--1 www-data www-data21209 Sep 2 06:24 > > > > > apache-access.log.13.gz > > > > > -rw-rw-r--1 www-data www-data 5979 Nov 19 2000 > > > > > apache-access.log.14.gz > > > > > -rw-rw-r--1 www-data www-data36771 Nov 18 06:23 > > > > > apache-access.log.2.gz > > > > > > > > > > It USED to be readable by all, now the persmissions have changed > > > (which in > > > > > my case screws up the webalizer processes run by users). > > > > > > > > > > Having a look at the changelog... > > > > > > > > > > apache (1.3.22-1) unstable; urgency=low > > > > > * Default ownership of logfiles is root/adm, perms 640 (closes: > > > > > #112675). > > > > > > > > > > Thats all nice a good... but how to I get it 644? I looked and can't > > > > > appear to find it. Closest thing I could find was in > > > > > /etc/apache/cron.conf, but that only sets the uid/gid, not the file > > > > > permissions of the logfiles. > > > > > > > > > > Any ideas? > > > > > > > > Run webalizer with permissions of group www-data and set appropriate > > > umask to > > > > user www-data (may be to loogrotate daemon too). > > > > > > > > -- > > > > With Best Regards, > > > > Denis A. Kulgeyko > > > > DK666-UANIC > > > > e-mail: [EMAIL PROTECTED] > > > > ICQ: 81607525 > > > > SMS: [EMAIL PROTECTED] > > > > -- > > > > UNIXes ... they are VERY friendly. > > > > But .. they chooses their friends VERY carefully ... :) > > > > ^]:wq! > > > > > > > > > > > > > -- > > > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > > > with a subject of "unsubscribe". Trouble? Contact > > [EMAIL PROTECTED] > > > > > > > > > > -- > > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] >
Re: Strange apache behaviour? (solved)
On Sun, Dec 09, 2001 at 08:05:17AM +1100, Jason Lim wrote: > Perhaps Johnie could make this an optional setting in > /etc/apache/cron.conf or something like that...? There is: .# Whether to chown logfiles to the user/group Apache runs as. APACHE_CHOWN_LOGFILES=0 ^^ This should be 0 *not* 1, which I think is Debian's default. This is used by /etc/cron.daily/apache. The server logs should root.adm or root.root with 640 permissions. Having the same that runs the server owner/group write permissions to the logs is asking for trouble. Nor should the world normally be able to look them. bob -- bob billsonemail: [EMAIL PROTECTED] ham: kc2wz /) [EMAIL PROTECTED] beekeeper -8|||} "Níl aon tinteán mar do thinteán féin." --DorothyLinux geek \) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Strange apache behaviour? (solved)
Thanks... The lines to change are: do if [ -f $LOG ] then if [ "$APACHE_CHOWN_LOGFILES" = "1" ] then savelog -c $APACHE_OLD_LOGS -m 640 -u $USR -g $GRP \ $LOG > /dev/null else savelog -c $APACHE_OLD_LOGS -m 640 -u root -g adm \ $LOG > /dev/null fi fi done changing 640 to 644. This should work... will wait a few days to make sure there are no side-effects to this. Perhaps Johnie could make this an optional setting in /etc/apache/cron.conf or something like that...? Sincerely, Jas - Original Message - From: "Peter Billson" <[EMAIL PROTECTED]> To: "Jason Lim" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Sunday, December 09, 2001 9:31 AM Subject: Re: Strange apache behaviour? > Jason, > Apaches log file ownership and permissions are set when they rotate in > /etc/cron.daily/apache (about line 90 or so). As pointed out there are > security issues to worry about so be careful. > > Pete > -- > http://www.elbnet.com > ELB Internet Services, Inc. > Web Design, Computer Consulting, Internet Hosting > > > Jason Lim wrote: > > > > Anyone figured out my apache problem (log file permissions)? > > > > I still haven't figured this one out yet. > > > > TIA, > > > > Jas > > > > - Original Message - > > From: "Jason Lim" <[EMAIL PROTECTED]> > > To: <[EMAIL PROTECTED]> > > Sent: Saturday, December 08, 2001 1:52 AM > > Subject: Re: Strange apache behaviour? > > > > > Thats not very good security-wise to run webalizer as www-data, because > > if > > > a user ever finds a way to poison the log files, then webalizer will run > > > them as www-data, and possibly be able to fool around with apache too > > > (because they now run as the same user). > > > > > > A far better way (and much more direct) would be to have a way to change > > > apache's log files BACK to the previous permissions. > > > > > > I think if no one knows the answer i'll have to ask netgod himself... (i > > > think he is still the package maintainer?) > > > > > > Sincerely, > > > Jason > > > > > > - Original Message - > > > From: "Denis A. Kulgeyko" <[EMAIL PROTECTED]> > > > To: "Jason Lim" <[EMAIL PROTECTED]> > > > Sent: Friday, December 07, 2001 9:10 PM > > > Subject: Re: Strange apache behaviour? > > > > > > > > > > Hello ! > > > > > > > > > Do you know how to change the permissions of the log files apache > > > > > generates? > > > > > > > > > > -rw-r-1 www-data www-data 1372461 Dec 7 13:04 > > > apache-access.log > > > > > -rw-r-1 www-data www-data 740269 Dec 2 06:21 > > > > > apache-access.log.0 > > > > > -rw-r-1 www-data www-data44414 Nov 25 05:52 > > > > > apache-access.log.1.gz > > > > > -rw-rw-r--1 www-data www-data 167114 Sep 23 06:10 > > > > > apache-access.log.10.gz > > > > > -rw-rw-r--1 www-data www-data13069 Sep 16 06:06 > > > > > apache-access.log.11.gz > > > > > -rw-rw-r--1 www-data www-data14357 Sep 9 06:04 > > > > > apache-access.log.12.gz > > > > > -rw-rw-r--1 www-data www-data21209 Sep 2 06:24 > > > > > apache-access.log.13.gz > > > > > -rw-rw-r--1 www-data www-data 5979 Nov 19 2000 > > > > > apache-access.log.14.gz > > > > > -rw-rw-r--1 www-data www-data36771 Nov 18 06:23 > > > > > apache-access.log.2.gz > > > > > > > > > > It USED to be readable by all, now the persmissions have changed > > > (which in > > > > > my case screws up the webalizer processes run by users). > > > > > > > > > > Having a look at the changelog... > > > > > > > > > > apache (1.3.22-1) unstable; urgency=low > > > > > * Default ownership of logfiles is root/adm, perms 640 (closes: > > > > > #112675). > > > > > > > > > > Thats all nice a good... but how to I get it 644? I looked and can't > > > > > appear to find it. Closest thing I could find was in > > > > > /etc/apache/cron.conf, but that only sets the uid/gid, not the file > > > > > permissions of the logfiles. > > > > > > > > > > Any ideas? > > > > > > > > Run webalizer with permissions of group www-data and set appropriate > > > umask to > > > > user www-data (may be to loogrotate daemon too). > > > > > > > > -- > > > > With Best Regards, > > > > Denis A. Kulgeyko > > > > DK666-UANIC > > > > e-mail: [EMAIL PROTECTED] > > > > ICQ: 81607525 > > > > SMS: [EMAIL PROTECTED] > > > > -- > > > > UNIXes ... they are VERY friendly. > > > > But .. they chooses their friends VERY carefully ... :) > > > > ^]:wq! > > > > > > > > > > > > > -- > > > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > > > with a subject of "unsubscribe". Trouble? Contact > > [EMAIL PROTECTED] > > > > > > > > > > -- > > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED
