Re: Mail::Audit persistent running

Just to elaborate on the change I had to make to support Maildir

In my case I remember having to make the following change to 
Audit/List.pm

From

     my $deliver_filename = join '/', $dir, $name;

To

     my $deliver_filename = join '.', $dir, $name . '/';

I was wondering if things have changed to accomodate this today? And 
therefore
I could go ahead and safely update my ListDetector.

so you see normally if I'm using Mail::Audit::accept I'll be doing 
something like this.

"java.kvm-interest",

Where

$listsdir = $home/Maildir/.lists
$where = 'java.kvm-interest'

   $mail->accept("$listsdir.$where/");

So whilst Mail::Audit supports Maildir out of the box ListDetector 
makes some assumptions about Mbox.

Secondly, I had to add my own MyCommuniGatePro detector but honestly I 
cannot
remember why I had to this but it's changes looked like this

if (defined($x_listserver) && ($x_listserver =~ m/CommuniGate Pro LIST/)
) {
                 chomp $x_listserver;

                 my $sender = $head->get('Sender');
                 return undef unless defined($sender);
                 $sender =~ m/<(.+)>/ or return undef;
                 my $posting_address = $1;
                 $posting_address =~ m/(.+)@/ or return undef;
                 my $list_name = $1;

                 #my $rfc2919 = new 
Mail::ListDetector::Detector::RFC2919;
                 #my $list = ( $rfc2919->match($message) or new 
Mail::ListDetecto
r::List );
                 my $list = new Mail::ListDetector::List;

                 $list->listname($list_name);
                 $list->listsoftware($x_listserver);
                 $list->posting_address($posting_address);

                 return $list;
         } else {

Obviously at the time I couldn't rely on RFC2919 to work with the lists 
I was subscribed
to.

That said I know that currently I'm not using this change for some 
reason but I remember
it being necessary at the time.


On Dec 5, 2003, at 6:49 PM, Peter Oliver wrote:

> Is anyone running Mail::Audit under PPerl, PersistentPerl, or even
> mod_perl?
>
> I've just given it a quick go with a few test mailings, and one think 
> that
> I did notice is that LOG never gets closed, and hence the log doesn't 
> get
> written out in a timely fashion.  I'll knock up a patch.
>
> Can anyone who knows the code think of any other likely problems?  I'm
> understandably wary of just letting it loose on my mail and seeing what
> happens.
>
>
> Meanwhile, Mail::ListDetector helpfully comes with a bunch of tests 
> that
> fail the second time you run them under perperl.  Looks like
> Mail::SpamAssassin should work, though:
> http://use.perl.org/comments.pl?cid=13171&sid=8620
>
> -- 
> Peter Oliver
>
> _______________________________________________
> mail-audit mailing list
> [email protected]
> http://lists.netthink.co.uk/listinfo/mail-audit