On 2007-01-23 16:29:38 +0100, Hans Salvisberg wrote: > Michael Holzt wrote: > >>Peter J. Holzer wrote that "It's basically the same patch as for 0.28." > >>and I was able to dig that one up somewhere as qpsmtpd-xinetd.tar.gz, > >>which also includes run.xi -- that seems like a step in the right > >>direction, but how do I tell this thing to run on port 25? > > > >I have no knowledge about xinetd, but i guess there is a generic way in > >xinetd to tell it the port. Don't you have any other services in xinetd > >and can lookup how its done there? > > Good idea, I'll try that. What throws me off is why Peter would post the > tcpserver-xinetd.patch without the other non-trivial files in > qpsmtpd-xinetd.tar. The patch alone seems pretty useless, and I wonder > whether the other files are also still "basically the same as for 0.28".
Not quite. run.xi (now renamed to in.qpsmtpd) became substantially simpler since 0.28, since logging is now different (and a lot more flexible). The xinetd config file is pretty much the same, but that was nothing special. I posted the patch because it concerns qpsmtpd directly and I needed someone to commit it. At the time I didn't have commit access to the repository. The other two files (which are now almost trivial) don't concern qpsmtpd directly. They are also not completely generic: They expect a certain file system layout and also some details of the configuration. So at the time I was happy to have them reside only in the RPM for which they were written. (I think I promised to check them into the repository anyway but forgot about it. I'll attach them for now). > >>4. Well, xinetd seems to be out of favor anyway, and this link > >>http://wiki.qpsmtpd.org/inetd?DokuWiki=9f8ba8fcd90e3c53f6a715c256a51775&do=revisions > >>shows that there used to be an xinetd page in the wiki, but it was moved > >>two weeks ago by jamtur01, and since then it has vanished. > > > >The last revision of the page can be seen here: > >http://wiki.qpsmtpd.org/deploy:inetd?rev=1168341647 > > > >It just states, that inetd and xinetd doesn't work. > > Thanks. So it's Peter's word against Wiki's word. It also says "If you > have a good reason for using (x)inetd, tell us on the mailing list!" -- The Wiki's word is my word in this case - it seems I was the last person to edit that page before it was moved. Xinetd was broken for quite some time until someone noticed it, so I was wondering whether it was worth the (admittedly small) effort to fix it again. Well, xinetd support does work again, so the question is now moot. > I don't know whether my reason (because my qmail-smtpd runs that way) is > a good one. You can surely tell that I'm new to this, and it's difficult > for me to weigh the alternatives. Running from xinetd is fine for light traffic. It is also nice for test sites, because new plugins and configurations will be picked up automatically without any need to restart the service. OTOH, the only way to stop the service is to edit the xinetd config. hp -- _ | Peter J. Holzer | I know I'd be respectful of a pirate |_|_) | Sysadmin WSR | with an emu on his shoulder. | | | [EMAIL PROTECTED] | __/ | http://www.hjp.at/ | -- Sam in "Freefall"
#!/bin/sh export QPSMTPD_CONFIG=/etc/qpsmtpd exec /usr/bin/qpsmtpd 2> /dev/null
# default: on
# description: The telnet server serves telnet sessions; it uses \
# unencrypted username/password pairs for authentication.
service smtp
{
flags = REUSE
socket_type = stream
wait = no
user = smtpd
groups = yes
server = /usr/sbin/in.qpsmtpd
log_on_failure += USERID
disable = yes
rlimit_as = 128M
instances = 40
per_source = 10
cps = 50 10
}
signature.asc
Description: Digital signature
