| Re: Trouble with sending e-mail from simple php script [message #176521 is a reply to message #176518] |
Mon, 09 January 2012 00:00   |
Jerry Stuckle
Messages: 2598
Registered: September 2010
Karma:
|
Senior Member |
|
|
On 1/8/2012 5:53 PM, M. Strobel wrote:
> Am 08.01.2012 21:44, schrieb Jerry Stuckle:
>> On 1/8/2012 11:01 AM, M. Strobel wrote:
>>> Am 08.01.2012 16:39, schrieb Jerry Stuckle:
>>>> On 1/8/2012 10:33 AM, M. Strobel wrote:
>>>> > Am 08.01.2012 16:02, schrieb Jerry Stuckle:
>>>> >> On 1/8/2012 9:12 AM, M. Strobel wrote:
>>>> >>> Am 08.01.2012 10:20, schrieb C:
>>>> >>>>
>>>> >>>> Even if the message were rejected, I would still see
>>>> >>>> something
>>>> >>>> in that
>>>> >>>> frame, but I get only a blank frame. Client machine
>>>> >>>> rejecting the
>>>> >>>> message should not even be noticed by this PHP script, or
>>>> >>>> would it?
>>>> >>>>
>>>> >>> You have to learn how to find and read the log files. Your
>>>> >>> script
>>>> >>> will not show errors if it dies.
>>>> >>>
>>>> >>> On Linux log files are only readable by root.
>>>> >>>
>>>> >>> /Str.
>>>> >>
>>>> >> Log files are not always available, and PHP errors are often
>>>> >> not
>>>> >> written to logs (depending on the configuration - the
>>>> >> default is
>>>> >> to NOT write them).
>>>> >>
>>>> >> Also, if the log files exist, they may easily be set up to be
>>>> >> read by others than root.
>>>> >>
>>>> >
>>>> > Don't tell me, tell C.
>>>> >
>>>>
>>>> No, you're the one who made the claims. I'm just correcting your
>>>> misinformation.
>>>>
>>>> > And the standard on linux is that log files are only root
>>>> > readable. I don't think it helps anybody if we start discussing
>>>> > what could all be done with the log files.
>>>> >
>>>>
>>>> They can easily be changed - it has nothing to do with whether
>>>> you're using standard linux or not.
>>>>
>>>> > Please do not start arguing with me on this level. I did
>>>> > Coherent
>>>> > on a serial terminal at home before linux came up, and I was
>>>> > working in an IBM computing center back then.
>>>> >
>>>> > /Str.
>>>>
>>>> Great. I was programming an IBM 1410 with punched cards in the
>>>> 60's and an IBM employee in the 70's - both long before Linux
>>>> came up.
>>>>
>>>> When your statements are incorrect, I will correct them.
>>>>
>>> I was glad the punched cards were gone when I came. The old
>>> operator could sort them by hand.
>>>
>>> There was nothing wrong with my statements. If he says "no log
>>> file" (which is not true, he said "blank frame") or "0 bytes in
>>> it" we know more, meanwhile it makes sense to suggest a standard
>>> setup.
>>>
>>> /Str.
>>
>> No log file can be completely correct. The default setup for PHP
>> does not include writing errors to a log file.
>
> Checked, and true, log_errors is 0.
> But display_errors is STDOUT.
>
>> Even if the
>> errors are written to a log file (very unusual in a shared
>> hosting environment), he will probably not have access to those
>> files. The sysop can change the configuration (and some good
>> hosts do) to allow this, but it's uncommon.
> Is it? There would be no chance to find errors. Last 10 years I
> only have virtual and true servers.
Definitely true. To log errors to one file and give anyone access would
be a huge security violation for others on the server.
The server CAN be set up to have individual logs for each site with the
logs accessible to the user (i.e. one level below DOCUMENT_ROOT) can be
done, but it seldom is.
You find errors on your development system (which should be very similar
to your production one - i.e. same versions of PHP and MySQL, etc.)
then, once they are working, upload the code to your production server.
>>
>> You are the one who told him he needs to learn to find and read
>> the log files. And you're the one who said they can only be read
>> by root. Neither statement is correct.
> If he can delete php.ini he is on his own machine.
>>
>> But it matters not because there is nearly a 0% chance he will be
>> able to read the log files. So telling him to do it just sends
>> him off on a wild goose chase.
>>
> I agree to the chance. It is hard to give a basic course in some
> newsgroups posts.
>
>> And as I told him - a blank frame is a different problem than
>> email not being received. He needs to fix that first.
>>
> I told him, and it is incorrect, so I sent him into a loop ah
> goose chase, so he has no chance, and he listens to me instead of
> you, he needs to fix that first, that's my fault, because I don't
> care about security, ... Did I summon it up correctly?
>
> /Str.
Pretty much.
--
==================
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
jstucklex(at)attglobal(dot)net
==================
|
|
|
|
Calendar
Search
Help
Members
Register
Login
Home
]