hi Dan -- b) if you open a bug on the bugzilla, and attach the change as a patch (ie. "diff -u" output) to that, we can put it into the 3.2.x ruleset.
a) we'll test it as part of that ;) --j. Dan Barker writes: > OK, I added the subject "Delivery Status Notification" as __BOUNCE_STAT_FAIL > in 20.vbounce.cf and OR'd it in the huge meta rule (BOUNCE_MESSAGE) next to > __BOUNCE_DEL_FAIL (on or about line 105). > > I tested it and it works. > > What I don't know how to do is: > > a) Investigate the possibility of FP's due to this change. It "looks" OK to > me, but I don't have a large corpus of non-bounce delivery status > notifications against which to test (er, ah, I have none<g>) > > b) I don't know how to report this as an enhancement. I do have sample > emails (http://www.visioncomm.net/VBounce.txt, > http://www.visioncomm.net/VBounce2.txt, > http://www.visioncomm.net/VBounce3.txt). Would it go in bugzilla or > somewhere else? It's an add-on rule for me (3.1.7) but I think it's built in > to 3.2.x. > > Dan > > -----Original Message----- > From: Kai Schaetzl [mailto:[EMAIL PROTECTED] > Sent: Monday, August 20, 2007 6:17 AM > To: users@spamassassin.apache.org > Subject: Re: Why'd VBounce not hit? > > Dan Barker wrote on Sun, 19 Aug 2007 20:07:30 -0400: > > > I'll dig through this some tomorrow, and maybe open up a bug report, > > if it needs a more flexible subject. > > I think this is a good idea. > > Kai > > -- > Kai Schätzl, Berlin, Germany > Get your web at Conactive Internet Services: http://www.conactive.com
