JT Moree wrote:
Elliot Foster wrote:
I don't bother using tcpserver or tcpsvd anymore, I use the --port arg
like so:
#!/bin/sh
exec 2>&1 \
sh -c '
exec \
/usr/local/bin/softlimit -m 30000000 \
/usr/bin/perl -T -I/path/to/qpsmtpd/lib \
/path/to/qpsmtpd/qpsmtpd-forkserver \
--listen-address 0 \
--port 25 \
--port 465 \
--port 587 \
--limit-connections 40 \
--max-from-ip 10 \
--user smtpd
'
Does that help?
Thank you,
I have a few questions though.
* Isn't there a plugin to manage the max-from-ip setting? hosts_allow?
* Wouldn't it better to have this script get the --listen-address from
control/IP?
* If yes to the last question, wouldn't it be nicer to have a file
config/PORTS?
* and in general, would it be nice to use variables in config files
instead of hard coding everything into the script?
I know this is just the script you are using but I'm wondering if the
default scripts could be improved.
Perhaps a script called run_fork in addition to the run script? I am
also looking at the Sys V init scripts from the wiki.
Man, that's the last time I respond to someone who's curious to see how others
are doing things. :) My run file could probably be optimized, yes, but it
works for me.
None of your questions/assumptions above look unreasonable. In fact, they look
pretty sane. I would suggest modifying the config.sample/plugins to whatever
you think is reasonable, and sending it to the mailing list as a patch for
inclusion.
As far as my input goes, I think it should use the forkserver (or -prefork, if
it is considered stable) rather than depending on tcpserver, which may or may
not be installed (likely not, if the user isn't running qmail.) Having a run
file for each method (as you suggest) sounds good, too.
So, go for it!
Elliot
