in reply to Sending E-mail attachment wihout using external module

You already have some specific answers. These are some additional observations:

  1. ...wihout (sic) using external module
    and
  2. ...where it's not possible to install a module for the purpose.

As a general rule (though not in this case), the phrase in 1 is justified only when the writer is interested in reinventing the wheel for educational purposes or cannot compile the module in question for the OS in use.

The clause in 2 is highly unlikely to be true (in terms of desired functionality) on any server for which the writer has the necessary permissions to install a script.

The reading suggested by moritz provides detail and in the Monastery's Tutorials section, you may find Installing Modules on a Web Server relevant, along with others in Installing Modules.

  • Comment on Re: Sending E-mail attachment wihout using external module

Replies are listed 'Best First'.
Re^2: Sending E-mail attachment wihout using external module
by Bloodnok (Vicar) on Nov 18, 2009 at 12:50 UTC
    Hmmm,

    In general I think you have a point, but beware of generalising too much - there are circumstances e.g. air gapped security sensitive systems, in which the propositions don't hold in a formal sense, but constraints e.g. security certification, on the installation of external, particularly public, code have the direct effect of causing them [the propositions] to appear to hold.

    Been there, seen it, eaten the T-shirt ... and bloody frustrating, but educational (because you are forced to re-invent the wheel in the interests of expediency), it is.

    A user level that continues to overstate my experience :-))

      ++ for an exception.

      But note the qualifiers, "as a general" (which I understand to mean there are exceptions) and "highly unlikely" which (implicitly at least), allows for exceptions?