On Wed, Feb 17, 2010 at 08:06:58AM -0800, Ask Bjørn Hansen wrote: > If you don't do any heavy processing (spamassassin or virus scanning > basically) then ~20/second (or whatever a million day works out to > when your server is busiest) shouldn't be a problem. > > If you do spamassassin and such, that will be the resource intensive > part. qpsmtpd might help over other MTAs though in filtering more of > the mail in cheaper ways first.
Yes, we do. But that's already perl right now. The hardest thing is qmail-scanner as a qmail-queue wrapper. This forks a perl for every message that gets so far. In fact, some of the policy filtering is hidden in the greylisting daemon, because there it's perl and doesn't fork. > > 4. Is this the right place for bug reports about included plugins? > > Yup! Best form of bug reports are fixes in your github repository though. > We also have a little-used bug tracker at > http://code.google.com/p/smtpd/issues/list I've got to understand things a bit more before that ... Thanks alot Jost -- | Helft Spam ausrotten! HTML in Mail ist unhöflich. | | Postmaster, JAPH, manchmal Wahrsager am RZ der RUB | | Bitte immer an Funktionsadressen schreiben: postmas...@rub.de |
smime.p7s
Description: S/MIME cryptographic signature
