> OK ... I understand that this will block port 783, BUT I don't understand why we would want to block port 783 since spamd uses port 783 for scanning e-mails. > According to what I read, spamd if given the e-mail via port 783 where it is scanned, and that you will not have the mail scanned by spamd if port 783 is blocked. > Maybe I am missing something.
This is exactly what I mean, I don't know the reason why Nick Hemmesch wrote with the release of the new SA toaster package, that this port should be blocked. And so, I don't know now if I should block the port or not :-) Here again the part of Nick's mail: > Second, close firewall port tcp 783 > Spamassassin needs this closed or it chokes communicating > on 127.0.0.1:783 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
