> On Wed, Oct 8, 2008 at 5:22 PM, mouss <[EMAIL PROTECTED]> wrote:
>[..]
> but if you have disabled address rewrite before the filter (this is a common
> setup. otherwise your virtual aliases would expand twice and you'll get
> duplicate mail), you'd better set the filter to the after-the-filter smtpd:
>
> <>  FILTER relay:[127.0.0.1]:10025

mmm.. actually I already tried something similar but I think I did
something wrong.

Forgive me if I'm asking something that should be obvious.

I used
<> FILTER localhost:10026
and I got this message in the logs:

[..]<>: Sender address triggers FILTER localhost:10026; from=<> to=[..]
and then
949E7C803C: from=<>, size=1842, nrcpt=1 (queue active)
949E7C803C: to=[..], relay=none, delay=2.4, delays=2.4/0.01/0/0,
dsn=4.3.0, status=deferred (mail transport unavailable)

I've in master.conf
# content filter loop back smtpd
localhost:10026 inet n - n - 20 smtpd
        -o smtpd_authorized_xforward_hosts=127.0.0.0/8
        -o smtpd_proxy_filter=
        -o content_filter=
        -o local_recipient_maps=
        -o smtpd_client_restrictions=
        -o smtpd_enforce_tls=no

What's wrong? The transport definition? the FILTER syntax?

Thanks for your help,
Diego.

Reply via email to