Andrew Kanaber writes: > Hi, > > I'm setting up an embedded machine that won't be able to send mail to > the internet and it seems excessive to leave smtpd running just so root > can receive cron job output, but I can't see a way to cut smtpd out of > the delivery chain because mail.local doesn't implement sendmail-style > command-line options (in particular it doesn't have the -t option to > extract the recipient from the message headers) so I can't use it in > place of smtpctl in /etc/mailer.conf.
It may seem that way but consider: in order to write to the file a sequence is going to be followed by whatever cron kicks off which is incredibly similar to that which is already being done by smtpd, only it's one you're going to have to write and manage yourself instead of being "just there" from day one and kept up to date by a bunch of developers who weirdly want to just produce safe, stable code for free. Why balk? > Is there some other way to do this? Is there a reason I've missed that > this is actually just a bad idea? I recommend doing nothing; that way this problem will solve itself by virtue of having already been solved and you can do something interesting, ie. literally anything other than email. Do you really need the extra few bytes of memory that a dud process takes up? Matthew
