RE: [Full-Disclosure] Interscan - path disclosure - WAS:SpamAssasin - path disclosure

[Bojan Zdrnja]

Title: Message

First of all, if you take a look at RFC822 you will see that X- headers stand for user defined field. This means that you can't really trust them - in this case, though, they were probably correct and they related to spam filtering on behalf of Spamassassin.   Now that we clarified what actually shows the path and that it has absolutely nothing with Spamassassin, the answer for your question is - yes, Spamassassin is often used with some antivirus programs.   Probably the best example of this is amavisd, which has integrated support for various anti-virus engines as well as spamassassin for spam tagging and filtering.   Regards,   Bojan Zdrnja -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of morning_wood Sent: Monday, 25 August 2003 1:17 p.m. To: ViLLaN; [EMAIL PROTECTED] Subject: [Full-Disclosure] Interscan - path disclosure - WAS:SpamAssasin - path disclosure ahhh, ok you are the first to specifically state " section of the header showing the path ".   thank you for the clarity.   Trend Interscan Viruswall has a path disclosure issue       So these products are often used in conjuntion with each other? Trend Interscan Viruswall and Spamassasin run on the same box and combining thier output?    i think im going to turbocharge, supercharge and nitrous my lawnmowers Briggs & Stratton. im sure i will cut more grass more better by stacking products and solutions together instead of purchasing the proper tool for the job.   morning_wood           ----- Original Message -----    From: ViLLaN To: [EMAIL PROTECTED] Sent: Sunday, August 24, 2003 5:41 PM Subject: RE: [Full-Disclosure] SpamAssasin - path disclosure 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..