Spamassassin is slow - any tips or good commercial alternative?

[Hugo van der Kooij]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Julian Field wrote:
| My advice would be to run
| MailScanner --debug --debug-sa
| as that will print out all the progress of SpamAssassin, including a
| timestamp at the start of each line so you can see where the holdups are.
| If you do that, and then show us where the holdups are, we may be able
| to help you some more.

DNS checks inside SA could be a real killer. Disable them and see what
happens. A good DNS forwarder on your machine will also improve things.

On the other hand you may have CPU and RAM to spare. In which case you
may add one or two more children to MS and see what happens.

But the bottom line is that email is a message forwarding protocol. It
may take several hops to delive the message. And 8 to 10 minutes is not
bad if you happen to have lived on the edge of a UUCP cloud.

Hugo.

- --
hvdkooij at vanderkooij.org               http://hugo.vanderkooij.org/
PGP/GPG? Use: http://hugo.vanderkooij.org/0x58F19981.asc

	A: Yes.
	>Q: Are you sure?
	>>A: Because it reverses the logical flow of conversation.
	>>>Q: Why is top posting frowned upon?

Bored? Click on http://spamornot.org/ and rate those images.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)

iD8DBQFIUi8cBvzDRVjxmYERAqPJAJ433+vq3pqJKsrWFRQnwR/BJoWY+QCfY695
+M4P/mz8G3tT/6GsrqfSrhg=
=yQJn
-----END PGP SIGNATURE-----