RE: [Full-Disclosure] SpamAssasin - path disclosure

[ViLLaN]

Title: Message

No one is denying that Spamassasin is in use, they are saying that the section of the header showing the path (what your original post was about from what I understood), is Interscan, not Spamassasin..       -----Original Message----- From: morning_wood [mailto:[EMAIL PROTECTED] Sent: Monday, 25 August 2003 10:25 AM To: ViLLaN; [EMAIL PROTECTED] Subject: Re: [Full-Disclosure] SpamAssasin - path disclosure sigh http://www.google.com/search?hl=en&ie=UTF-8&oe=UTF-8&q=X-Spam-Checker-Version%3A+SpamAssassin+&btnG=Google+Search     1. http://www.cs.arizona.edu/computer.help/policy/spam_filtering.html 2. http://lists.suse.com/archive/suse-linux-e/2003-Apr/0554.html 3. http://spamassassin.org/doc/Mail_SpamAssassin_PerMsgStatus.html 4. http://lpsc.in2p3.fr/informatique/faq/spamassassin.html 5. http://www.unit.liu.se/irt/epost/spamassassin.html   still wrong?   Donnie Werner co-cofounder - Chief Technical Officer e2-labs Pvt Ltd       ----- Original Message ----- From: ViLLaN To: [EMAIL PROTECTED] Sent: Sunday, August 24, 2003 4:25 PM Subject: RE: [Full-Disclosure] SpamAssasin - path disclosure Kane is correct... Interscan viruswall is responsible for that quarantine..