Feb 14, 1997, 2:39 PM
Post #3 of 4
(1658 views)
Permalink
Patrick Farley writes:
> Does anyone have smap running with qmail here?
No. But we just moved a smap-frontend-for-sendmail setup to a
qmail-frontend-for-sendmail setup on one firewall. (Sendmail is still
there only because of the rush we were in to get smap(d) off the
machine, we'll probably translate the userdb/mailertable to a qmail
setup soon.)
Smap was dropping connections all over the place. Symptoms: smap
writes the first 4K bytes of it's own header + message, hangs, the
remote end times out after an hour, smap exits with the following
message in the logs:
Feb 13 12:00:21 <firewall> smap[23750]:
SMTP QUIT with no message <relay>/<ip-address>
This is incorrect, of course, coz the headers + top of body are
already in the 4K buffer it's written out to xmaNNNNNN.
This machine isn't doing much right now, qmail reported 4100
deliveries yesterday. If smap cannot cope with that...
If the above isn't sufficient to dissuade you, you might want to look
hard at how smapd runs the queue...it sleeps when there're bound to be
messages in the queue. Not forking too much might be a feature, to
sleep when there's work available is not.
-Sudish