Full Disclosure mailing list archives
RE: Interscan - path disclosure - WAS:SpamAssasin - path disclosure
From: "Bojan Zdrnja" <Bojan.Zdrnja () LSS hr>
Date: Mon, 25 Aug 2003 15:14:29 +1200
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: full-disclosure-admin () lists netsys com [mailto:full-disclosure-admin () lists netsys com] On Behalf Of morning_wood Sent: Monday, 25 August 2003 1:17 p.m. To: ViLLaN; full-disclosure () lists netsys com 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 <http://www.briggsandstratton.com/> 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 <mailto:villain () protonic com> To: full-disclosure () lists netsys com 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..
Current thread:
- SpamAssasin - path disclosure morning_wood (Aug 24)
- Re: SpamAssasin - path disclosure Evert Jan van Ramselaar (Aug 24)
- <Possible follow-ups>
- RE: SpamAssasin - path disclosure Kane Lightowler (Aug 24)
- Re: SpamAssasin - path disclosure morning_wood (Aug 24)
- RE: SpamAssasin - path disclosure ViLLaN (Aug 24)
- Re: SpamAssasin - path disclosure morning_wood (Aug 24)
- RE: SpamAssasin - path disclosure ViLLaN (Aug 24)
- Interscan - path disclosure - WAS:SpamAssasin - path disclosure morning_wood (Aug 24)
- Re: Interscan - path disclosure - WAS:SpamAssasin - path disclosure Steffen Kluge (Aug 24)
- RE: Interscan - path disclosure - WAS:SpamAssasin - path disclosure Bojan Zdrnja (Aug 24)
- Re: SpamAssasin - path disclosure morning_wood (Aug 24)
- Re: SpamAssasin - path disclosure Valdis . Kletnieks (Aug 27)
- Re: SpamAssasin - path disclosure morning_wood (Aug 24)