On Feb 17, 2010, at 8:28, Jost Krieger wrote: >> 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.
Oh - your performance with qpsmtpd will certainly be better than what you have now then! > In fact, some of the policy filtering is hidden in the greylisting > daemon, because there it's perl and doesn't fork. ... and the code cleaner. :-) >>> 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 ... Obviously. :-) I'm just pointing it out because for many users qpsmtpd is more of a development platform than an application; so if you are going to do work based on it then you'll be better off starting with a git clone than a tar ball. - ask -- http://develooper.com/ - http://askask.com/
