Configuring sendmail on Jaguar
Subject:   sendmail still does not do its job
Date:   2003-08-09 00:06:55
From:   anonymous2
I would like to use the php mail function on my local server, in order to test certain designs. it is more about sending mails versus receiving.
( actually i am a designer and I am not to much into the unix world :-)
I have tried to follow the o´reilly tutorial, but it didn´t work out, I guess because I was not able to execute the update script, or at least there was no response, like:
Restarting mail services

somebody mentioned that the os X developer tools have to be installed ? which part of it and where could I get them from ?

the last entry in my mail.log looks like this:

Aug 8 22:34:05 bruno sendmail[440]: File descriptors missing on startup: stdin, stdout, stderr; Bad file descriptor
Aug 8 22:34:06 bruno sendmail[440]: gethostbyaddr( failed: 3
Aug 8 22:34:06 bruno sendmail[460]: starting daemon (8.12.9): SMTP+queueing@01:00:00
Aug 8 22:34:06 bruno sendmail[462]: File descriptors missing on startup: stdin, stdout, stderr; Bad file descriptor
Aug 8 22:34:06 bruno sendmail[463]: starting daemon (8.12.9): queueing@01:00:00

thanks a lot for your help

Full Threads Oldest First

Showing messages 1 through 1 of 1.

  • sendmail still does not do its job
    2003-09-09 09:52:09  anonymous2 [View]

    The OS X Developer Tools installer is (or should be) in
    /Applications/Installers/Developer Tools/

    Just install the whole package.

    Once you've done that, the program "m4" should be in /usr/bin, and /usr/bin should always be in your $PATH, so from any Terminal window you should be able to run the update script and get the expected messages.

    I don't know what the "Bad file descriptor" stuff is all about. It doesn't sound related to your missing DevTools. After you've installed the DevTools and rerun update, check for these messages again. If they're still happening, come back here, and perhaps someone will be able to help.

    The gethostbyaddr failure is more-or-less expected: your machine appears to be behind a NAT firewall. See the last page of the article for some pointers on dealing with this. Since you're more interested in sending that receiving mail, the NAT shouldn't be a terrible issue, but (as the article says) make very sure that the mail you send out can be replied to (arriving in some other, "real" mail box). That can be done by providing a "Reply-To:" header pointing to the real box, or by providing the real box as "From:".