Hi,
* Thorsten Haude [02-06-07 19:45:07 +0200] wrote:
* Rocco Rutte [EMAIL PROTECTED] [02-06-07 08:02]:
I hope I don't have to pipe mail through my filter and than
pipe it into another instance of Mail::Audit...
There is only a pipe() that would leave Mail::Audit. Yes,
you would have to
Hi,
* Rocco Rutte [EMAIL PROTECTED] [02-06-07 08:02]:
* Thorsten Haude [02-06-07 06:14:30 +0200] wrote:
[ Perl::Mail::Audit ]
It stops by default, just like Procmail does, but you can
change that. I make backups at the beginning of my
ruleset:
$mail-accept({noexit = 1}, $backup);
Sounds
Hi,
* Thorsten Haude [2002-06-07 23:20:42 CEST] wrote:
* [EMAIL PROTECTED] [EMAIL PROTECTED] [02-06-06 21:54]:
The primary example of procmail's power is the ability
to create, call and distribute modules.
I never heard of these modules, neither has my manpage.
Are you talking about
Moin,
* Rocco Rutte [EMAIL PROTECTED] [02-06-07 05:18]:
This isn't exactly the right place to discuss, but I heavliy
rely on the cloning feature of procmail. The introduction to
Mail::Audit I've read doesn't say anything about this one
but Mail::Audit would stop after I take an action on a mail
Hi,
* Thorsten Haude [02-06-07 06:14:30 +0200] wrote:
[ Perl::Mail::Audit ]
It stops by default, just like Procmail does, but you can
change that. I make backups at the beginning of my
ruleset:
$mail-accept({noexit = 1}, $backup);
Sounds good. If you don't mind, let me ask one more
