Re: [PHP-DB] Sending filing attachments using PHP

[Oliver Block]

Am Freitag, 12. Mai 2006 00:33 schrieb Ron Piggott (PHP):
> Does any one know how to send a file attachment using PHP?

You need to reformulate the problem. Does any one know how to create a 
mime/mulipart message with php?



Best Regards,

Oliver

-- 
PHP Database Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php

Re: [PHP-DB] Sending filing attachments using PHP

[JupiterHost.Net]

there really aren't enough effort applied to educate those outside the IT
world.


Working on it :)


> but I still use PHP because it is still the most appropiate development
> enviroment for a small or middle sized web solution.

Why not use Perl, it has all the "pros" but does not have the cons :)


Because it has cons, and lots of them. It's not a language who was designed


 "it is still the most appropriate development environment.."As I 
stated previously, I'm not trying to do a Perl vs PHP debate but rather 
"use anything but PHP" the "why not use Perl" was directed at the 
statement.


In other words "Why is the most appropriate" when its a security problem 
and a hassle, and zillions of other technologies do the same stuff, and 
more, and much much better.



for web development and this becomes a hassle. Its language constructions


Why/ just output headers and HTML and you're done. Separate logic and 
presentation.



are not as intuitive as other languages, there are too many ways of doing
the same thing, and too many different "code conventions" (if they can be


Oi, did you even look at the url I sent? all the randomly named 
functions that do the same thing?



called as such). So it really becomes complicate to make one perl developer
work with another perl developer. There are too many basic data structures
for a scripting language, PHP arrays work better in almost any situation,
are easier to understand and use. Debugging a perl application requires a
higher level of programming skills.


Not really. You're just used to PHP data structures, thats all.

PHP doesn't have too much overhead when it's used in its most primitive 
way.


But when is it? Mostly never, people always need this or that option 
compiled in and pretty soon: a 20 Meg binary and lots of headache :)



Everything procedural, everything on arrays and only load what you need.
This way it can run as fast as anyone. But this can only be used for small
solutions and some medium web solutions, it isn't applyable to every need.


Thats a programmer doing a good job, and that can be done in any 
language. Its no positive feature of PHP.


--
PHP Database Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php

Re: [PHP-DB] Sending filing attachments using PHP

[Martin Alterisio]

2006/5/12, JupiterHost.Net <[EMAIL PROTECTED]>:



> It's a fact that I can't deny any of the bad points you have exposed
about
> PHP. I even agree with you that most of this problems are really awful
and
> it's pointless to hide them. But the fact that PHP is by preference the
> language for developing small and middle web solutions aimed to be
economic
> and rapidly developed is also undeniable. All languages have their pros
and
> cons, and trying to compare them outside of the context of the target
> market
> is pointless. It just happens that PHP pros fit better the desires of
the
> web solutions market, and they also don't care much about current PHP
cons.

Most people aren't aware of the cons, thats my point :)



Developers are aware (well most of them). Designers are not, project leaders
are not (with the exception of a few), marketing people are not, and all the
people higher up in the administration are not. This is mostly our fault,
there really aren't enough effort applied to educate those outside the IT
world.

For example:

  If Mr. big wig was aware that phpBB has a history if being uber
hackable and even being used in a rootkit scheme a time or two he'd not
choose PHP. But its shiny so he says "go with that it looks nice".

That is how its popularity has grown, ignorance of the facts.

> Anyway, this market is evolving and its needs are changing, so it's
normal
> for developers to try and anticipate future development needs and try to
> make PHP fit into other philosophies, methodologies or technologies it
was
> not designed to work with, and everyone who has tried this (including
me)
> have started to hate PHP in a certain way. But that's all there is to
it, I
> hate not having a proper application framework, I hate not having
> namespaces, I hate the overhead of working with OOP, I hate magic
quotes,
> but I still use PHP because it is still the most appropiate development
> enviroment for a small or middle sized web solution.

Why not use Perl, it has all the "pros" but does not have the cons :)



Because it has cons, and lots of them. It's not a language who was designed
for web development and this becomes a hassle. Its language constructions
are not as intuitive as other languages, there are too many ways of doing
the same thing, and too many different "code conventions" (if they can be
called as such). So it really becomes complicate to make one perl developer
work with another perl developer. There are too many basic data structures
for a scripting language, PHP arrays work better in almost any situation,
are easier to understand and use. Debugging a perl application requires a
higher level of programming skills.

In fact, I use it for several high volumn websites:

  - with persistent database connections and persistently running
instances of the script
(which is the *only* positive PHP has, except it means running PHP
as "nobody" and with really really bad permissions)
  - without doing *anything* with apache
  - works with SuExec so it runs as the user so the permissions can be
700 and config files 600 - try that with PHP without days of fiddling
and breaking stuff and finally giving up ;)

Now you have the only "benefit" of PHP (but better) without *any* of its
downside.

> I'm guessing this part, but I think you think alike and that's the
reason
> you're still on this list and trying to make a point out of your bad
> experiences with PHP. We can still hope that this problems will be
solved

It won't, for "backwards compatibility" they'll have to keep the cobbled
up mess. Or else make it new from scratch and remove the crap, but in
that case itd be a brand new langauge and would have all the problems
inherent with that :)



I think they have proved they don't care too much about backward
compatibility. You have just to see what happened to the [] and {} string
operator: deprecated, undeprecated and so on. They only care about keeping
the core features of PHP (those that really made the language stand where it
is).


Thanks for sharing your opinion and concerns, I really appreciate them.

My pleasure, I've been managing hundreds of servers for nearly a decade
and PHP has always had seriouse drawbacks. I've really honestly tried to
make a go of it but its just to much overhead to be worth it, IMHO :)



PHP doesn't have too much overhead when it's used in its most primitive way.
Everything procedural, everything on arrays and only load what you need.
This way it can run as fast as anyone. But this can only be used for small
solutions and some medium web solutions, it isn't applyable to every need.

--

PHP Database Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php

Re: [PHP-DB] Sending filing attachments using PHP

[JupiterHost.Net]

Bastien Koert wrote:


Then Please, stop posting here...it just is not constructive...


I will, but I think it is

If you have these issues that need addressing to make it a better 
langauge, then talk to the nice people at Zend and get invovled in 
making things better.


No thanks, trying to get out of that pit of despair. I am however trying 
to help make things better by doing non-PHP stuff.



All the rest if useless diatribe.


Its not useless if one person benefits from it and at least considers 
that an alternative to PHP may be a better choice and that PHP is not 
gods gift to nerds but rather Satan's snare of the nerds :)


--
PHP Database Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php

Re: [PHP-DB] Sending filing attachments using PHP

[Bastien Koert]

Then Please, stop posting here...it just is not constructive...

If you have these issues that need addressing to make it a better langauge, 
then talk to the nice people at Zend and get invovled in making things 
better.


All the rest if useless diatribe.

Regards

Bastien



From: "JupiterHost.Net" <[EMAIL PROTECTED]>
To: PHP DB 
Subject: Re: [PHP-DB] Sending filing attachments using PHP
Date: Fri, 12 May 2006 15:39:44 -0500



It's a fact that I can't deny any of the bad points you have exposed about
PHP. I even agree with you that most of this problems are really awful and
it's pointless to hide them. But the fact that PHP is by preference the
language for developing small and middle web solutions aimed to be 
economic
and rapidly developed is also undeniable. All languages have their pros 
and
cons, and trying to compare them outside of the context of the target 
market

is pointless. It just happens that PHP pros fit better the desires of the
web solutions market, and they also don't care much about current PHP 
cons.


Most people aren't aware of the cons, thats my point :)

For example:
 If Mr. big wig was aware that phpBB has a history if being uber hackable 
and even being used in a rootkit scheme a time or two he'd not choose PHP. 
But its shiny so he says "go with that it looks nice".


That is how its popularity has grown, ignorance of the facts.


Anyway, this market is evolving and its needs are changing, so it's normal
for developers to try and anticipate future development needs and try to
make PHP fit into other philosophies, methodologies or technologies it was
not designed to work with, and everyone who has tried this (including me)
have started to hate PHP in a certain way. But that's all there is to it, 
I

hate not having a proper application framework, I hate not having
namespaces, I hate the overhead of working with OOP, I hate magic quotes,
but I still use PHP because it is still the most appropiate development
enviroment for a small or middle sized web solution.


Why not use Perl, it has all the "pros" but does not have the cons :)

In fact, I use it for several high volumn websites:
 - with persistent database connections and persistently running instances 
of the script
   (which is the *only* positive PHP has, except it means running PHP as 
"nobody" and with really really bad permissions)

 - without doing *anything* with apache
 - works with SuExec so it runs as the user so the permissions can be 700 
and config files 600 - try that with PHP without days of fiddling and 
breaking stuff and finally giving up ;)


Now you have the only "benefit" of PHP (but better) without *any* of its 
downside.



I'm guessing this part, but I think you think alike and that's the reason
you're still on this list and trying to make a point out of your bad
experiences with PHP. We can still hope that this problems will be solved


It won't, for "backwards compatibility" they'll have to keep the cobbled up 
mess. Or else make it new from scratch and remove the crap, but in that 
case itd be a brand new langauge and would have all the problems inherent 
with that :)


> Thanks for sharing your opinion and concerns, I really appreciate them.

My pleasure, I've been managing hundreds of servers for nearly a decade and 
PHP has always had seriouse drawbacks. I've really honestly tried to make a 
go of it but its just to much overhead to be worth it, IMHO :)


--
PHP Database Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php



--
PHP Database Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php

Re: [PHP-DB] Sending filing attachments using PHP

[JupiterHost.Net]

It's a fact that I can't deny any of the bad points you have exposed about
PHP. I even agree with you that most of this problems are really awful and
it's pointless to hide them. But the fact that PHP is by preference the
language for developing small and middle web solutions aimed to be economic
and rapidly developed is also undeniable. All languages have their pros and
cons, and trying to compare them outside of the context of the target 
market

is pointless. It just happens that PHP pros fit better the desires of the
web solutions market, and they also don't care much about current PHP cons.


Most people aren't aware of the cons, thats my point :)

For example:
 If Mr. big wig was aware that phpBB has a history if being uber 
hackable and even being used in a rootkit scheme a time or two he'd not 
choose PHP. But its shiny so he says "go with that it looks nice".


That is how its popularity has grown, ignorance of the facts.


Anyway, this market is evolving and its needs are changing, so it's normal
for developers to try and anticipate future development needs and try to
make PHP fit into other philosophies, methodologies or technologies it was
not designed to work with, and everyone who has tried this (including me)
have started to hate PHP in a certain way. But that's all there is to it, I
hate not having a proper application framework, I hate not having
namespaces, I hate the overhead of working with OOP, I hate magic quotes,
but I still use PHP because it is still the most appropiate development
enviroment for a small or middle sized web solution.


Why not use Perl, it has all the "pros" but does not have the cons :)

In fact, I use it for several high volumn websites:
 - with persistent database connections and persistently running 
instances of the script
   (which is the *only* positive PHP has, except it means running PHP 
as "nobody" and with really really bad permissions)

 - without doing *anything* with apache
 - works with SuExec so it runs as the user so the permissions can be 
700 and config files 600 - try that with PHP without days of fiddling 
and breaking stuff and finally giving up ;)


Now you have the only "benefit" of PHP (but better) without *any* of its 
downside.



I'm guessing this part, but I think you think alike and that's the reason
you're still on this list and trying to make a point out of your bad
experiences with PHP. We can still hope that this problems will be solved


It won't, for "backwards compatibility" they'll have to keep the cobbled 
up mess. Or else make it new from scratch and remove the crap, but in 
that case itd be a brand new langauge and would have all the problems 
inherent with that :)


> Thanks for sharing your opinion and concerns, I really appreciate them.

My pleasure, I've been managing hundreds of servers for nearly a decade 
and PHP has always had seriouse drawbacks. I've really honestly tried to 
make a go of it but its just to much overhead to be worth it, IMHO :)


--
PHP Database Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php

Re: [PHP-DB] Sending filing attachments using PHP

[Martin Alterisio]

2006/5/12, Martin Alterisio <[EMAIL PROTECTED]>:


...


I hate not having a proper application framework,



...





Sorry, there is a mistake there. I meant to say that I hate not having an
application server, although I also think currently available framework are
just not the way to go. They are too big and produce too much overhead.

Re: [PHP-DB] Sending filing attachments using PHP

[Martin Alterisio]

2006/5/12, JupiterHost.Net <[EMAIL PROTECTED]>:




Dwight Altman wrote:

> " Right after rebuilding php and apache and breaking PHP funtionality
for
> everyone, just so you can send a semi complex MIME message? That is the
> epitome of PHP's lameness and why I can't sit quietly by and not
> recommend an easy to install and use and maintain solution."
>
> This command breaks Apache?
> require("class.phpmailer.php");
> " And besides its in a non strutcutered way to maek it even more
> impossible to maintain."
>
> Classes and Object Oriented Programming?

Thanks Dwight, good info.

I'm speaking in generalitites of working with PHP not specifics
components of the technology.

As an example of this general clutter/bloat/mess that PHPs basic
paradigm is see:

http://tnx.nl/php

Disclaimer: Note that that url is a comparison of Perl to PHP, which is
not what I'm saying in all this mess. Just look at each point of PHP and
if you don't see whay iots so bad look at how Perl does it and hopefully
it will make more clear where I'm coming from for at least part of my
argument (the deve part) that PHP has many negatives things about it
that are either not an issue in other langauges or are not nearly as
pronounced or common to run up against.

I'm very sorry if this makes some uncomfortable but note that I'm
pointing out downfalls of PHP, a "thing", I am not getting personal and
would appreciate the same courtesy. (which Dwight and Edward have done,
thanks ;p)

--
PHP Database Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php




It's a fact that I can't deny any of the bad points you have exposed about
PHP. I even agree with you that most of this problems are really awful and
it's pointless to hide them. But the fact that PHP is by preference the
language for developing small and middle web solutions aimed to be economic
and rapidly developed is also undeniable. All languages have their pros and
cons, and trying to compare them outside of the context of the target market
is pointless. It just happens that PHP pros fit better the desires of the
web solutions market, and they also don't care much about current PHP cons.

Anyway, this market is evolving and its needs are changing, so it's normal
for developers to try and anticipate future development needs and try to
make PHP fit into other philosophies, methodologies or technologies it was
not designed to work with, and everyone who has tried this (including me)
have started to hate PHP in a certain way. But that's all there is to it, I
hate not having a proper application framework, I hate not having
namespaces, I hate the overhead of working with OOP, I hate magic quotes,
but I still use PHP because it is still the most appropiate development
enviroment for a small or middle sized web solution.

I'm guessing this part, but I think you think alike and that's the reason
you're still on this list and trying to make a point out of your bad
experiences with PHP. We can still hope that this problems will be solved
without harming the spirit of PHP in future versions or future enhacements,
and that our needs will be somehow be heard. If not, well they will realize
soon that current trends are leading to a different kind of solutions (not
that utopic Web2.0 but a more realistic Web1.5).

Thanks for sharing your opinion and concerns, I really appreciate them.

Re: [PHP-DB] Sending filing attachments using PHP

[JupiterHost.Net]

Dwight Altman wrote:

" Right after rebuilding php and apache and breaking PHP funtionality for 
everyone, just so you can send a semi complex MIME message? That is the 
epitome of PHP's lameness and why I can't sit quietly by and not 
recommend an easy to install and use and maintain solution."


This command breaks Apache?
require("class.phpmailer.php");
" And besides its in a non strutcutered way to maek it even more 
impossible to maintain."


Classes and Object Oriented Programming?


Thanks Dwight, good info.

I'm speaking in generalitites of working with PHP not specifics 
components of the technology.


As an example of this general clutter/bloat/mess that PHPs basic 
paradigm is see:


http://tnx.nl/php

Disclaimer: Note that that url is a comparison of Perl to PHP, which is 
not what I'm saying in all this mess. Just look at each point of PHP and 
if you don't see whay iots so bad look at how Perl does it and hopefully 
it will make more clear where I'm coming from for at least part of my 
argument (the deve part) that PHP has many negatives things about it 
that are either not an issue in other langauges or are not nearly as 
pronounced or common to run up against.


I'm very sorry if this makes some uncomfortable but note that I'm 
pointing out downfalls of PHP, a "thing", I am not getting personal and 
would appreciate the same courtesy. (which Dwight and Edward have done, 
thanks ;p)


--
PHP Database Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php

Re: [PHP-DB] Sending filing attachments using PHP

[JupiterHost.Net]

Edward Vermillion wrote:
You've made it obvious by all of your replies that you have no idea  
what you're talking about,  so maybe it would be a good time to *not*  
reply and let the folks that know what they're talking about actually  
try to help people? Eh? Maybe?


a) Im speaking in generalitites of working with PHP not specifics 
componentss of the technology.


b) I am trying to help :)

Good day to all, sorry if I was to ambiguouse or I've offended

--
PHP Database Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php

RE: [PHP-DB] Sending filing attachments using PHP

[Dwight Altman]

" Right after rebuilding php and apache and breaking PHP funtionality for 
everyone, just so you can send a semi complex MIME message? That is the 
epitome of PHP's lameness and why I can't sit quietly by and not 
recommend an easy to install and use and maintain solution."

This command breaks Apache?
require("class.phpmailer.php");

" And besides its in a non strutcutered way to maek it even more 
impossible to maintain."

Classes and Object Oriented Programming?



-Original Message-
From: JupiterHost.Net [mailto:[EMAIL PROTECTED] 
Sent: Friday, May 12, 2006 10:10 AM
To: 'PHP DB'
Subject: Re: [PHP-DB] Sending filing attachments using PHP



Chris wrote:

> JupiterHost.Net wrote:
> 
>>
>>
>> Ing. Edwin Cruz wrote:
>>
>>> Have a look on this:
>>>
>>> http://framework.zend.com/manual/en/zend.mail.attachments.html
>>>
>>>
>>> It seems to be easy with zend framework
>>
>>
>>
>> How about a way to do it without having to install a huge system wide 
>> binary and configruation that might potentially break apache and all 
>> PHP sites?
>>
>> http://search.cpan.org/perldoc?Mail::Sender::Easy
>>
> 
> The OP is asking for a PHP solution and you point to cpan.. Hmm.

Yep, because PHP is not usually (some say *never*) the best solution 
*and* this *is* a PHP + DB list so the OP actually has nothing to do 
with thei slist anyway.

> phpmailer (phpmailer.sourceforge.net) handles everything for you.. even 
> if you want to roll your own, that code will give you a good starting 
> point.

Right after rebuilding php and apache and breaking PHP funtionality for 
everyone, just so you can send a semi complex MIME message? That is the 
epitome of PHP's lameness and why I can't sit quietly by and not 
recommend an easy to install and use and maintain solution.

And besides its in a non strutcutered way to maek it even more 
impossible to maintain.

Look at the EXAMPLE section of that url, see how incredibly easy and 
intuitive it is to sent complex emails?

And all the server admin has to do is:

perl -MCPAN -e 'install Mail::Sender::Easy;'

  - no fiddling with apache
  - no fiddling with the interpretet binary
  - no possibility of breaking anyone's scripts


Or else you could do liek the one guy and make your own MIME message but 
that is even dumber than insisting that PHP has to be used.

-- 

-- 
PHP Database Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php

Re: [PHP-DB] Sending filing attachments using PHP

[Stut]

JupiterHost.Net wrote:


Chris wrote:


JupiterHost.Net wrote:


Ing. Edwin Cruz wrote:


Have a look on this:

http://framework.zend.com/manual/en/zend.mail.attachments.html


It seems to be easy with zend framework



How about a way to do it without having to install a huge system 
wide binary and configruation that might potentially break apache 
and all PHP sites?


http://search.cpan.org/perldoc?Mail::Sender::Easy



The OP is asking for a PHP solution and you point to cpan.. Hmm.



Yep, because PHP is not usually (some say *never*) the best solution 
*and* this *is* a PHP + DB list so the OP actually has nothing to do 
with thei slist anyway.



Agreed, but the subject does say "using PHP".

phpmailer (phpmailer.sourceforge.net) handles everything for you.. 
even if you want to roll your own, that code will give you a good 
starting point.



Right after rebuilding php and apache and breaking PHP funtionality 
for everyone, just so you can send a semi complex MIME message? That 
is the epitome of PHP's lameness and why I can't sit quietly by and 
not recommend an easy to install and use and maintain solution.



Why are you rebuilding PHP and Apache? In what way does phpmailer (a 
completely PHP-based solution with no external dependancies) force you 
to do this and "break[ing] PHP functionality for everyone"?


And besides its in a non strutcutered way to maek it even more 
impossible to maintain.



I assume that's a generic dig at PHP. For me, the lack of an enforced 
structure makes it easier to maintain since it gives you the freedom to 
put in your own structure.


I don't know you from Adam, but for whatever reason you seem to hate 
PHP. I'm sure whatever it did it wasn't personal. Please do us all a 
favour and unsubscribe from this list, or at the very least please stop 
posting pointless and time-wasting answers.


-Stut

--
If ignorance is bliss, you must be in heaven!

--
PHP Database Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php

Re: [PHP-DB] Sending filing attachments using PHP

[JupiterHost.Net]

Edward Vermillion wrote:


Ummm... dude...

Zend Framework is NOT a "system wide binary"...


Semantics.

The point is its more fiddling, why fiddle (and likely break something) 
when you don't need to.


besides is like way beta right now... fun to play with, sure, but  
they're not really recommending it for production yet.


try phpmailer or some of the other mail classes


Getting closer, but now you better hope you have Pear or PECLsupport 
compiled in, if not, more fiddling


Or els e you have to use a php file that has some functions you can use 
(in no structered or organized way, lame lame lame)


--
PHP Database Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php

Re: [PHP-DB] Sending filing attachments using PHP

[JupiterHost.Net]

Chris wrote:


JupiterHost.Net wrote:




Ing. Edwin Cruz wrote:


Have a look on this:

http://framework.zend.com/manual/en/zend.mail.attachments.html


It seems to be easy with zend framework




How about a way to do it without having to install a huge system wide 
binary and configruation that might potentially break apache and all 
PHP sites?


http://search.cpan.org/perldoc?Mail::Sender::Easy



The OP is asking for a PHP solution and you point to cpan.. Hmm.


Yep, because PHP is not usually (some say *never*) the best solution 
*and* this *is* a PHP + DB list so the OP actually has nothing to do 
with thei slist anyway.


phpmailer (phpmailer.sourceforge.net) handles everything for you.. even 
if you want to roll your own, that code will give you a good starting 
point.


Right after rebuilding php and apache and breaking PHP funtionality for 
everyone, just so you can send a semi complex MIME message? That is the 
epitome of PHP's lameness and why I can't sit quietly by and not 
recommend an easy to install and use and maintain solution.


And besides its in a non strutcutered way to maek it even more 
impossible to maintain.


Look at the EXAMPLE section of that url, see how incredibly easy and 
intuitive it is to sent complex emails?


And all the server admin has to do is:

perl -MCPAN -e 'install Mail::Sender::Easy;'

 - no fiddling with apache
 - no fiddling with the interpretet binary
 - no possibility of breaking anyone's scripts


Or else you could do liek the one guy and make your own MIME message but 
that is even dumber than insisting that PHP has to be used.


--
PHP Database Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php

Re: [PHP-DB] Sending filing attachments using PHP

[Chris]

JupiterHost.Net wrote:



Ing. Edwin Cruz wrote:


Have a look on this:

http://framework.zend.com/manual/en/zend.mail.attachments.html


It seems to be easy with zend framework



How about a way to do it without having to install a huge system wide 
binary and configruation that might potentially break apache and all PHP 
sites?


http://search.cpan.org/perldoc?Mail::Sender::Easy



The OP is asking for a PHP solution and you point to cpan.. Hmm.

phpmailer (phpmailer.sourceforge.net) handles everything for you.. even 
if you want to roll your own, that code will give you a good starting point.


--
Postgresql & php tutorials
http://www.designmagick.com/

--
PHP Database Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php

Re: [PHP-DB] Sending filing attachments using PHP

[Edward Vermillion]

Ummm... dude...

Zend Framework is NOT a "system wide binary"...

besides is like way beta right now... fun to play with, sure, but  
they're not really recommending it for production yet.


try phpmailer or some of the other mail classes

Ed
On May 11, 2006, at 5:57 PM, JupiterHost.Net wrote:




Ing. Edwin Cruz wrote:

Have a look on this:
http://framework.zend.com/manual/en/zend.mail.attachments.html
It seems to be easy with zend framework


How about a way to do it without having to install a huge system  
wide binary and configruation that might potentially break apache  
and all PHP sites?


http://search.cpan.org/perldoc?Mail::Sender::Easy

--
PHP Database Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php



--
PHP Database Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php

Re: [PHP-DB] Sending filing attachments using PHP

[JupiterHost.Net]

Ing. Edwin Cruz wrote:

Have a look on this:

http://framework.zend.com/manual/en/zend.mail.attachments.html


It seems to be easy with zend framework


How about a way to do it without having to install a huge system wide 
binary and configruation that might potentially break apache and all PHP 
sites?


http://search.cpan.org/perldoc?Mail::Sender::Easy

--
PHP Database Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php

RE: [PHP-DB] Sending filing attachments using PHP

[Ing. Edwin Cruz]

Have a look on this:

http://framework.zend.com/manual/en/zend.mail.attachments.html


It seems to be easy with zend framework




-Mensaje original-
De: Ron Piggott (PHP) [mailto:[EMAIL PROTECTED] 
Enviado el: Jueves, 11 de Mayo de 2006 05:34 p.m.
Para: PHP DB
Asunto: [PHP-DB] Sending filing attachments using PHP


Does any one know how to send a file attachment using PHP?  

I have been using the mail() command to send e-mail in various scripts, but
have spotted a file attachment syntax to use on the php web page.

Ron

-- 
PHP Database Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php

-- 
PHP Database Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php

[PHP-DB] Sending filing attachments using PHP

[Ron Piggott (PHP)]

Does any one know how to send a file attachment using PHP?  

I have been using the mail() command to send e-mail in various scripts,
but have spotted a file attachment syntax to use on the php web page.

Ron

-- 
PHP Database Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php