On Thu, Nov 25, 2004 at 10:06:35PM -0800, Daniel Quinlan wrote: Hi Dan, good to hear from you again. > > However, this is gone from SA 3.x, and I don't find any equivalent > > option. Is always_add_report functionality gone in 3.x? > > That it was deprecated was documented in SA 2.6x:
Mmmh, I missed that apparently. > This option is deprecated in version 2.60 and later. It will be > removed in a future version. Instead, use the clear_headers and > add_header options to customize headers. I was looking for the header in the default config for spam instead of all, but I guess it is just hard coded inside the code instead of being in 10_misc.cf. Anyway, I looked some more, and indeed it was just a matter of writing add_header all Report _REPORT_ I added that to the wiki http://wiki.apache.org/spamassassin/UpgradeTo300?action=edit > > For that matter, there seems to be a fair amount of options that are > > just gone from SA 3.0, like num_check_received, check_mx_attempts, > > check_mx_delay, or rbleval I understand that some became obsolete, or > > stopped working due to code changes, but is there a resource for > > options that were migrated/changed? (yes, a few are in the upgrade > > file, but many seem to be missing there) > > The UPGRADE document. Anything lacking should be added to the Wiki page > listed therein. Yeah, I did read it of course, and didn't find the info in the wiki, but it's there now :) > > While I'm at it: My plugin is also quite sensitive how long SA takes > > to run since it's SMTP time, but I've found that SA 3.x can sometimes > > take quite a while to return, namely 66, 72, 81, 88, 74, 53 seconds in > > a few samples I've gotten just in the last hours. This is way too long > > for SMTP time response. > > If you have an example message that always takes a long time, please > send it to [EMAIL PROTECTED] Our weekly bayes+net runs seem > to include some dirt-slow messages as well. I'll see what I can do and if I can find some that are reproducable. > > My timelog code was removed because it apparently slowed SA down by a > > couple of percent or something, but it was quite useful to figure out > > why SA is taking so long to run, randomly, on some messages (i.e. I > > can't reproduce at will on the command line). Is there anything that > > replaces the timelog functionality, or do I need to rewrite it for SA > > 3.x? > > Perhaps it's something that could be written as a plugin... *shrug* Mmmh, not easily. For what I'm trying to do, direct access to the guts is easier :) Thanks for your reply Marc -- "A mouse is a device used to point at the xterm you want to type in" - A.S.R. Microsoft is to operating systems & security .... .... what McDonalds is to gourmet cooking Home page: http://marc.merlins.org/ | Finger [EMAIL PROTECTED] for PGP key
