Re: [PHP] Bounce messages

2012-09-21 Thread Lester Caine
David McGlone wrote: And Yes tamouse ... it's having to replace a block of return addresses with >just the list address to tidy things up. A long list of addresses can build >up when everyone uses 'reply all' where as many other lists just need >'reply' so nowadays I only use reply - and hopefull

Re: [PHP] Bounce messages

2012-09-21 Thread David McGlone
On Friday, September 21, 2012 11:31:36 PM Lester Caine wrote: > Ashley Sheridan wrote: > >> On 09/21/2012 12:40 AM, Lester Caine wrote: > >> > I know that the php list are one of the 'reply to sender' email > >> > handling > >> > camp rather than reply to list. I can cope with that now and handle t

[PHP] Re: PHP Re: PHP Bounce messages

2012-09-21 Thread Tim Streater
On 21 Sep 2012 at 20:56, tamouse mailing lists wrote: > On Fri, Sep 21, 2012 at 4:17 AM, Tim Streater wrote: >> On 21 Sep 2012 at 08:40, Lester Caine wrote: >> >>> I know that the php list are one of the 'reply to sender' email handling >>> camp rather than reply to list. >> >> I don't underst

Re: [PHP] Bounce messages

2012-09-21 Thread Lester Caine
Ashley Sheridan wrote: On 09/21/2012 12:40 AM, Lester Caine wrote: > I know that the php list are one of the 'reply to sender' email handling > camp rather than reply to list. I can cope with that now and handle the > multiple reply address problem this end so I ONLY reply to list. BUT is > there

Re: [PHP] Re: PHP Bounce messages

2012-09-21 Thread tamouse mailing lists
On Fri, Sep 21, 2012 at 4:17 AM, Tim Streater wrote: > On 21 Sep 2012 at 08:40, Lester Caine wrote: > >> I know that the php list are one of the 'reply to sender' email handling camp >> rather than reply to list. > > I don't understand this. I reply (not that I mail that often) just to the > lis

Re: [PHP] Bounce messages

2012-09-21 Thread Jim Lucas
On 09/21/2012 12:22 PM, Jeff Burcher wrote: Hi, I don't know if this is specifically what he is referring to when he says, "the 'reply to sender' email handling camp ", but I know that when I just click Reply it goes to the individual whose post I am commenting on. I need to click on Reply All

RE: [PHP] Bounce messages

2012-09-21 Thread Jeff Burcher
Hi, I don't know if this is specifically what he is referring to when he says, "the 'reply to sender' email handling camp ", but I know that when I just click Reply it goes to the individual whose post I am commenting on. I need to click on Reply All and several emails are in the blanks and I n

Re: [PHP] Bounce messages

2012-09-21 Thread Ashley Sheridan
On Fri, 2012-09-21 at 09:56 -0700, Jim Lucas wrote: > On 09/21/2012 12:40 AM, Lester Caine wrote: > > I know that the php list are one of the 'reply to sender' email handling > > camp rather than reply to list. I can cope with that now and handle the > > multiple reply address problem this end so

Re: [PHP] Bounce messages

2012-09-21 Thread Jim Lucas
On 09/21/2012 12:40 AM, Lester Caine wrote: I know that the php list are one of the 'reply to sender' email handling camp rather than reply to list. I can cope with that now and handle the multiple reply address problem this end so I ONLY reply to list. BUT is there no way of cleaning up the boun

Re: [PHP] Risks involved in MyISAM to Innodb

2012-09-21 Thread shiplu
On Fri, Sep 21, 2012 at 7:03 PM, Girish Talluru wrote: > Hi Guys, > > I have requirement to change my production database tables which are using > myISAM and now bcoz of some changes we have to move to Innodb. > > Can anyone suggest how the plan should be and risks involve? > > Thanks, > Girish Ta

Re: [PHP] Risks involved in MyISAM to Innodb

2012-09-21 Thread Ashley Sheridan
Girish Talluru wrote: >Thanks a lot Samuel. Appreciate your help. > >On Fri, Sep 21, 2012 at 6:20 AM, Samuel Lopes Grigolato < >samuel.grigol...@gmail.com> wrote: > >> Sure, the address you’re looking for is: http://lists.mysql.com/ >> >> ** ** >> >> Good hunting =) >> >> ** ** >> >> *D

[PHP] output compression when host has disabled mod_deflate, mod_gzip and php_value auto_prepend_file

2012-09-21 Thread edward eric pedersson
Hi My host, Host Papa (yes, they are rubbish) has disabled mod_deflate, mod_gzip and php_value auto_prepend_file so can't use them in .htaccess file. I would move host but I did not realise this was the case until I wanted to make use of them. I am tied in for three years so need to find a workaro

Re: [PHP] Bounce messages

2012-09-21 Thread Paul M Foster
On Fri, Sep 21, 2012 at 08:40:23AM +0100, Lester Caine wrote: > I know that the php list are one of the 'reply to sender' email > handling camp rather than reply to list. I can cope with that now > and handle the multiple reply address problem this end so I ONLY > reply to list. BUT is there no wa

Re: [PHP] Risks involved in MyISAM to Innodb

2012-09-21 Thread Girish Talluru
Thanks a lot Samuel. Appreciate your help. On Fri, Sep 21, 2012 at 6:20 AM, Samuel Lopes Grigolato < samuel.grigol...@gmail.com> wrote: > Sure, the address you’re looking for is: http://lists.mysql.com/ > > ** ** > > Good hunting =) > > ** ** > > *De:* Girish Talluru [mailto:girish.dev1..

RES: [PHP] Risks involved in MyISAM to Innodb

2012-09-21 Thread Samuel Lopes Grigolato
Sure, the address you're looking for is: http://lists.mysql.com/ Good hunting =) De: Girish Talluru [mailto:girish.dev1...@gmail.com] Enviada em: sexta-feira, 21 de setembro de 2012 10:15 Para: Samuel Lopes Grigolato Cc: php-general@lists.php.net Assunto: Re: [PH

Re: [PHP] Risks involved in MyISAM to Innodb

2012-09-21 Thread Girish Talluru
Samuel, Can you please send the DBMS list address? Thanks, Girish On Fri, Sep 21, 2012 at 6:08 AM, Samuel Lopes Grigolato < samuel.grigol...@gmail.com> wrote: > I would start trying my DBMS user list. Or maybe you're afraid of impacts > on > PHP code? > > Cheers. > > -Mensagem original-

RES: [PHP] Risks involved in MyISAM to Innodb

2012-09-21 Thread Samuel Lopes Grigolato
I would start trying my DBMS user list. Or maybe you're afraid of impacts on PHP code? Cheers. -Mensagem original- De: Girish Talluru [mailto:girish.dev1...@gmail.com] Enviada em: sexta-feira, 21 de setembro de 2012 10:04 Para: php-general@lists.php.net Assunto: [PHP] Risks involved in M

Re: [PHP] Warning at PDO:Firebird driver manual page removed.

2012-09-21 Thread Davi Marcondes Moreira
Dear Lester, Thank you very much for your attention. You gave me the exact explanation which solved all my doubts about using PDO:Firebird. Actually I'm building step by step a abstract layer file for general use on these projects, and it works fine for us, using the php_interbase extension funct

[PHP] Re: PHP Bounce messages

2012-09-21 Thread Tim Streater
On 21 Sep 2012 at 08:40, Lester Caine wrote: > I know that the php list are one of the 'reply to sender' email handling camp > rather than reply to list. I don't understand this. I reply (not that I mail that often) just to the list, if possible. Why would I do anything else? -- Cheers -- T

Re: [PHP] about PHP's filter_var function

2012-09-21 Thread Sebastian Krebs
Am 20.09.2012 19:54, schrieb Jim Lucas: On 09/20/2012 10:00 AM, Matijn Woudt wrote: On Thu, Sep 20, 2012 at 6:03 PM, Jim Lucas wrote: On 09/20/2012 02:35 AM, Sebastian Krebs wrote: Plaseplease update... 5.1.6 is from 2006! I read the "it's required", but I can't imagine _anything_ that it's

Re: [PHP] Bounce messages

2012-09-21 Thread Matijn Woudt
Op 21 sep. 2012 09:41 schreef "Lester Caine" het volgende: > > I know that the php list are one of the 'reply to sender' email handling camp rather than reply to list. I can cope with that now and handle the multiple reply address problem this end so I ONLY reply to list. BUT is there no way of cl

[PHP] Bounce messages

2012-09-21 Thread Lester Caine
I know that the php list are one of the 'reply to sender' email handling camp rather than reply to list. I can cope with that now and handle the multiple reply address problem this end so I ONLY reply to list. BUT is there no way of cleaning up the bounce emails we all get when posting to the li

Re: [PHP] Warning at PDO:Firebird driver manual page removed.

2012-09-21 Thread Lester Caine
Davi Marcondes Moreira wrote: The question is: why the warning message was removed, and now this extension is safe for use, without risks of being discontinued or depreciated? Davi The current version of the extension is stable and a number of the initial bugs have been cleared up. If you use