[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[leafnode-list] using external scanners in leafnode2
- To: leafnode-list@xxxxxxxxxxxxxxxxxxxxxxxxxxxx
- Subject: [leafnode-list] using external scanners in leafnode2
- From: Cory Albrecht <cory@xxxxxxxxxxxxxx>
- Date: Wed, 26 Mar 2008 17:53:02 -0400
- Delivery-date: Wed, 26 Mar 2008 22:53:50 +0100
- Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAALHRFWHRDcmVhdGlvbiBUaW1l AFR1ZSAyOCBOb3YgMjAwNiAxNzozMDoxNCAtMDUwMJaEJzQAAAAHdElNRQfWCxwWKCbyV3gxAAAA CXBIWXMAAA7DAAAOwwHHb6hkAAAABGdBTUEAALGPC/xhBQAAABJQTFRF/f3xYEZZUjA43bGn+OPg o25rpFCjPwAAAeBJREFUeNrNU9uN4zAM5Mc2QC1UgASkgD2K/wtIKUBm2H8rNyPngOtgV4ltWcPn DC3yK1erNczGMz0shnmWjqUquLcMHISb5eZpA9BFjwW2man3tjcFcLv2RwAIuz0qbCSzAGqWB3Ds K7cpjlvpn37exrx6tRuw8Lza4FtkTGcuvISwlPxcBMxZ3SnP4IFbvuaE5xs4Dz2Aj7Gm+WBYVHBs AdBojImfoeaKA/z3G5gGn1OBAoTH9QY8x4cv7OqpCoydqjy8jhkrCdz9FUHx+cyNtl4zt24lUrXI RszpV1iOJ45TS0sYFMk4MW0hGePv0ogiB+tGSwudsKrdIEYj7QiCg/+AAokAnM7B65qJ5ybVivWQ RTvLtZhhQ0iIiSxVSFJGrLmhBK68Jaz0IHPEY2300ErjAAhT1kCo5S9wYvsfQIewubi+n0FAGUsg ys74wPEEjwTYhdZb2qC9B3bOAcJ8NUGkDWXGgoIclX0GrqiEq4KsF8bhCHX1QqBKgGh4AdggVfPi zJZexSsVIJMkGYw0Ti4AOwqEaZzZSTBF5ZED20grPWOgwYtzv8EWZrfll39xlll5Q1WNH4A4YgRk K0qa0dClehEA96fZot8L3xoIaPrnBvpRRnUIqB50OcBPrr9vNcBXAJgnIAAAAABJRU5ErkJggg==
- List-id: Discussions on the Leafnode Usenet software package <leafnode-list.dt.e-technik.uni-dortmund.de>
- Reply-to: cory@xxxxxxxxxxxxxx
- Sender: leafnode-list-bounces+list01=leafnode.de@xxxxxxxxxxxxxxxxxxxxxxxxxxxx
- User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.12) Gecko/20080213 Thunderbird/2.0.0.12 Mnenhy/0.7.5.666
Hello all,
Glad to see there's still some life to leafnode. I couldn't satisfy my
addiction to Usenet without it. (OK, well, I could, but it wouldn't be
as easy!)
Anyways, recently I've been thinking how nice it would be to be able to
scan all new messages with SpamAssassin or other tools commonly used to
scan email. Especially with all the crap that emerges from that haven of
spammers known as Google Groups. :-P
Many of these tools, like spamc for SpamAssassin work with stdin and
sometimes stdout and as such should be relatively easy to integrate.
Quickly looking over the leafenode2 source code, I had initially thought
that the way to patch things would be to modify readfilter() in
filterutil.c and struct filterentry in leafnode.h to allow adding new
actions to the filters file. However, while trying to follow through
store_stream() in store.c, it seems that store_stream is made to split
out the header and then run the filters on just the header and then use
that split off copy of the header to figure out final file
locations/links, xref/xover data and so forth.
I had hoped that this would be an easy patch, but is not to be. To me,
the filters file seems to be the logical place users would specify
scanners like SpamAssassin or ClamAV, but things are just not ideal for
adding a filter that would necessarily modify the post in the process.
Are there any suggestions as to why I might do to make a patches that
would stand a chance of getting added to leafnode2? Scanning my incoming
news with SpamAssassin, ClamAV and others is a feature I'd really like
to have in leafnode2.
--
Cory Albrecht
--
_______________________________________________
leafnode-list mailing list
leafnode-list@xxxxxxxxxxxxxxxxxxxxxxxxxxxx
https://www.dt.e-technik.uni-dortmund.de/mailman/listinfo/leafnode-list
http://leafnode.sourceforge.net/