Re: Mailfilter

2002-06-13 Thread Rocco Rutte 

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 re-enter it yourself.  Shouldn't be too
 difficult to add this though.

Right. What I didn't find out yet is how to change headers
on the fly...

Cheers, Rocco

Re: Mailfilter

2002-06-07 Thread Thorsten Haude 

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 good. If you don't mind, let me ask one more question
(since it's absolutely essential): what about reading mail
back from a pipe? For me, it's necessary to change stuff
within a pipe (Perl, mostly ;-) and then process it as usual.

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 re-enter it yourself.
Shouldn't be too difficult to add this though.

Thorsten
-- 
There is no drug known to man which becomes safer when its
production and distribution are handed over to criminals.

Mailfilter (was: Re: [Re: NuBe: upgrade question])

2002-06-06 Thread Rocco Rutte 

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 the wide range of Procmail rules you
 can find in the wild? (Certainly more than Maildrop
 rules.)

I think he's talking about the possibility to exluce certain
syntax elements into other files, say ``modules''. But, I've
had a quick look at Mail::Audit any maybe I'll spend some
time on it.

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
(sure, I could use multiple Mail::Audit filters to deliver
to, but...). Is that possible?

Cheers, Rocco

Re: Mailfilter

2002-06-06 Thread Thorsten Haude 

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
(sure, I could use multiple Mail::Audit filters to deliver
to, but...). Is that possible?
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);

Thorsten
-- 
The reasonable man adapts himself to the world;
the unreasonable one persists in trying to adapt the world to himself.
Therefore all progress depends on the unreasonable man.
- George Bernard Shaw

Re: Mailfilter

2002-06-06 Thread Rocco Rutte 

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 question
(since it's absolutely essential): what about reading mail
back from a pipe? For me, it's necessary to change stuff
within a pipe (Perl, mostly ;-) and then process it as usual.

I hope I don't have to pipe mail through my filter and than
pipe it into another instance of Mail::Audit...

Cheers, Rocco