From: Adam Bernstein (adamelectricembers.net)
Date: Thu Mar 16 2006 - 09:10:55 CST

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Ah -- while reading up on local(8), I came across frozen_delivered_to,
the description of which indicates that forwarding *should* update the
Delivered-to: header unless this parameter is set to "no", or unless
you're running pre-2.3 code. So I thought that was the answer to my
prayers, except I'm running 2.2.9, which apparently should have the old
behavior that updates the header; yet I've tested and seen that it
doesn't. Is the doc inaccurate regarding the old behavior? Alas, the
behavior is as expected in one way, in that the frozen_delivered_to
parameter has no effect in this version.

I'll try updating, at any rate.

       ab

Adam Bernstein wrote:
> Searched the archives, can't find the answer:
>
> We have SpamAssassin marking incoming messages, and then want to
> non-deliver spams if the recipient has a forwarder that's going to send
> them on to an account at Yahoo, AOL, etc. (We keep getting dinged for
> relaying spam, either automatically or because the users hit "This is
> spam" at the final destination, plus it's just a huge resource waste.)
> This means we need to do filtering on outgoing mail, and I thought my
> question was going to be on the best way to do that -- before-queue
> filtering? after-queue? header_checks vs. custom content filter? needs
> two different Postfix instances on different ports (I think yes)?
>
> But in fact, I've realized I have a more fundamental question. What the
> heck condition do I filter on? A forwarder doesn't rewrite or add a
> header, as far as I can see after setting one up and then shutting down
> Postfix to trap a forwarded message before it can be sent on. So if I
> can't filter on some kind of to: header, what can I filter on? Is there
> a way?
>
> Much obliged for any insight.
>
> ab
>

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]