Re: Re: Mail::Audit and Mail::SpamAssassin no longer getting along?

[Phil Thompson <ph...@dodgeit.com>]

File this under both:
  - too late
  - my own damn fault

but those of us who just do:
$cpan
cpan> install Mail::SpamAssassin

never get to *see* the UPGRADE file

I'm just saying it would have been nice if a question popped up under cpan's installation that asked "are you using Mail::Audit to filter your mail?" with a subsequent scary message. Maybe the question would only pop up if cpan noticed Mail::Audit was already installed.

I know, I know, you can't ever make EVERYONE happy. I don't want to come off as too much of a whiner, because I really love SpamAssassin. Maybe that's why I want it to be closer to perfect and prevent others from feeling my pain.


>Sounds like you forgot to read UPGRADE ;)
>
>Unfortunately, we had to drop Mail::Audit support -- our Message object
>representation needed better support for MIME structure modelling, and M:A
>didn't do that (unless the MIME::Base64 set of modules was used).  Since
>we didn't want to require MIME::Base64 and rely on that, nor did we want
>to maintain code to deal with two parallel message object models, we
>rewrote the Message object entirely and had to drop M:A support.
>
>The way to do it now is to extract the message as a string from M:A, and
>call $spamtest->parse($string).  (using an array ref also works.)