Hi The Bat! User Discussion list, On Sunday, April 06, 2003 at 21:08:46GMT -0500 (which was 9:08 PM where I live) Joseph N. wrote and made these points on the subject of "Spampal and NOD POPscan": JN> On Saturday, April 05, 2003, David Calvarese wrote in JN> <mid:[EMAIL PROTECTED]>:
DC>> http://www.spampal.org JN> David and Luc, JN> Thank you. I'll try Spampal. One question about setup, though. JN> Normally, I would have TB! connecting on port x to my AV's POPscanner, JN> which then connects out on port 110. Is it correct that I should keep JN> Spampal tuned in to the default port 110, and let Windows or Spampal JN> or my AV POPscanner figure out the rest? Or is there a better way to JN> go? I know with the 2.x betas (and presumably the release) the easiest way is to have spampal listen on port 111 and Nod32 set to monitor port 111 so it doesn't scan both before and after spampal. With the 1.x releases, umm, I forget how it needs to be set up in Nod. I THINK that you need to either do: Mail Client -> SpamPal -> AV Or Mail Client -> AV -> SpamPal My guess is that the first is better so the AV can scan stuff before SpamPal looks at it. I think you need to have Spampal set on another port, lets say 111 and Nod32 have port 110 set to go to your mail server then tell TB! that the server is localhost and the username is <username>@localhost where username is your username on your mail server. -- Best regards, David mailto:[EMAIL PROTECTED] Member of E-mailaholics International - Proud Member of The WELL PGP Key at http://search.keyserver.net:11371/pks/lookup?op=get&search=0xCC7E7664 Everything can be filed under "miscellaneous." ________________________________________________ Current version is 1.62 | "Using TBUDL" information: http://www.silverstones.com/thebat/TBUDLInfo.html
