Hi Peter, On Sat, 29 Oct 2005 20:02:27 +0200 "Peter J. Holzer" <[EMAIL PROTECTED]> wrote:
> > I originally wrote the plugin for postfix 1.x, and I don't remember
> > if I didn't set any flags on purpose or if those flags were only
> > added with postfix 2.x.
>
> Postfix 2.2 knows about the following flags:
>
> #define CLEANUP_FLAG_NONE 0 /* No special features */
> #define CLEANUP_FLAG_BOUNCE (1<<0) /* Bounce bad messages */
> #define CLEANUP_FLAG_FILTER (1<<1) /* Enable content filter */
> #define CLEANUP_FLAG_HOLD (1<<2) /* Place message on hold */
> #define CLEANUP_FLAG_DISCARD (1<<3) /* Discard message silently */
> #define CLEANUP_FLAG_BCC_OK (1<<4) /* Ok to add auto-BCC
> addresses */
> #define CLEANUP_FLAG_MAP_OK (1<<5) /* Ok to map
> addresses */
>
> Postfix 1.1 only knew the first two. According to my notes I disabled
> CLEANUP_FLAG_BOUNCE on purpose and was unsure whether
> CLEANUP_FLAG_FILTER should be enabled.
>
> I agree with Hanno that CLEANUP_FLAG_MAP_OK should be set.
>
[...]
> (Another idea would of course be to make the flags configurable)
Ok, here we go :) The POD is adjusted, too .)
...another way to achieve more flexibility would be to add a 'mail'
hook in postfix-queue and set the
$transaction->notes('postfix-queue-flags', $self->{_queue_flags});
there and let some other plugin disable some or all flags depending on
what's incoming.
Oh, the Postfix.pm.diff is against the unpatched version of
Postfix.pm ...
Hanno
Postfix.pm.diff.gz
Description: Binary data
postfix-queue.diff.gz
Description: Binary data
