Cron and Mail
I've been experimenting with cron and internal email. Nothing seems to work unless I start sendmail.
I suspect that cron cannot send mail unless a MTA is active. I'm guessing that cron uses whatever daemon occupies port 25. Is this correct? Sendmail seems like heavy overhead for a single workstation not connected to a LAN. I've discovered that sendmail expects a fully qualified domain name, otherwise the program takes a very long time to start and fills my logs with cantankerous error messages to that effect. A FQDN is senseless with a single workstation. Lastly, I really do not want to spend any time learning anything about sendmail. I have more important items on my to do list. :) Is there a more efficient solution that avoids running sendmail? All I want to do is allow cron to successfully send emails. Nothing more. Thanks. |
Quote:
Quote:
|
Quote:
Quote:
I was only offering a statement that I have other things I want to focus rather than spend time learning sendmail. Learning sendmail is not high on my list. I was only looking for a MTA replacement to avoid using sendmail. As I stated in my original post, I only want to be able to receive mail from cron events. Seems like sendmail is significant overkill for such a nominal need. |
Quote:
Quote:
Procmail recipe: Code:
# /home/mailcatch/procmail.conf Code:
# /etc/xinetd.d/smtp Code:
#!/bin/bash HTH |
Thanks for the info.
As mentioned, I modified my hosts file to add localdomain and sendmail is running fine. Perhaps the overhead is not as much as I imagine and all of this is spilled milk. All is fine in Mudville. :) My apologies for misunderstanding your previous response. I'm guessing you were being humorous or tongue-in-cheek, but I did not pause to consider that. :( |
And when did Slackware start using xinetd?
|
All times are GMT -5. The time now is 11:53 AM. |