http://issues.apache.org/SpamAssassin/show_bug.cgi?id=4636
------- Additional Comments From [EMAIL PROTECTED] 2005-10-19 23:06 ------- (In reply to comment #8) > Not really. What if I have another plugin that gets called at the same time > or earlier because it wants to do something, whereby it populates the cache? Since that other plugin should have gotten data normalized by the charset plugin but did not, that would definitely be a bug. > I'm not sure I follow here. Message and Message::Node are wholly separate > from the rest of the code, with the exception of a handful of calls into Util. > What does the SA code know about the message that doesn't come from Message or > Message::Node, which then those hook into? It's the other way around. Message and Message::Node have detailed knowledge of how SpamAssassin wants to view/render messages for matching. To have SpamAssassin's rendering of messages be configurable and/or controllable by plugins, those objects necessarily need a reference to the configuration/plugin state. > I would imagine that there wouldn't be a lot of overhead if there's not a lot > of normalization going on. If incoming messages aren't in any special > charset, I would assume a negligable time penalty to processing. Charset detection is likely to have to be run on everything, regardless of whether or not the messages are in a special charset. ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
