Let postfix bypass MailScanner for specific recipients

[Glenn Steen]

On 13/01/2008, Hugo van der Kooij <hvdkooij at vanderkooij.org> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Drew Marshall wrote:
> | On 13 Jan 2008, at 16:08, Hugo van der Kooij wrote:
> |
> |> -----BEGIN PGP SIGNED MESSAGE-----
> |> Hash: SHA1
> |>
> |> UxBoD wrote:
> |> | Sorry, being dumb today! That wouldn't make any difference anyway as
> |> each line of the header is parsed.
> |>
> |> We need to have some sort of AND function on 2 regexp in postfix.
> |>
> |> Hugo.
> |
> | Hugo
> |
> | I have tried, with out success to do something similar before. The
> | problem is that Postfix doesn't have any 'not' or 'and' rule
> | understanding, which is pretty limiting, however, there might be an
> option.
> |
> | How does postfix receive your time critical mail? Is it possible to
> | inject it using the sendmail binary? If so you can set a regex to only
> | hold mail based on your server ID like thus:
> |
> | /^Received:(.*)by your\.mail-server\.name \(Postfix\)/   HOLD
>
> I will receive it from various remote servers (1 for now) by SMTP.
>
> Basically I send it with a custom perlscript to a remote SMTP server to
> start the timer and at the end of the chain it gets send back to me so I
> know the whole SMTP chain is alive and how long it took to process
> through the chain.
>
> The concept was deviced over a drink last friday night and by now the
> SMTP chain works I just need to parse the results and setup alerting if
> certain steps take to long.
>
> Hugo.
>
Hopefully the drink was a tasty... fruitjuice?!:-)

I suppose you've considered the possibility of a second listener? Have
a "high" port smtpd defined without the header check... have the
"respondee" send to that one...?
Or wouldn't that be feasible with what you're trying to do?

Cheers
-- 
-- Glenn
email: glenn < dot > steen < at > gmail < dot > com
work: glenn < dot > steen < at > ap1 < dot > se