Ian Duggan:
> Nov 18 15:19:22 mail01 postfix/smtp[3333]: D9024B689D2:
> to=<test.scr...@gmail.com>, relay=none, delay=0.05, delays=0.05/0/0/0,
> dsn=5.4.6, status=bounced (mail for mail01.scribd.com loops back to
> myself)
>
> header_checks is here:
>
> header_checks:
> /^X-Vmta.*1$/ FILTER vmta1:
> /^X-Vmta.*2$/ FILTER vmta2:
> /^X-Vmta.*3$/ FILTER vmta3:
> /^X-Vmta.*4$/ FILTER vmta4:
> /^X-Vmta.*5$/ FILTER vmta5:
Could the problem be that FILTER, as documented, expects a destination?
FILTER transport:destination
Write a content filter request to the queue file, and inspect
the next input line. After the complete message is received it
will be sent through the specified external content filter.
More information about external content filters is in the Post-
fix FILTER_README file.
The header_checks(5) manpage does not say what happens when the
destination is omitted. The access(5) manpage refers to the
transports(5) manpage for syntax (the syntax depends on the type
of delivery agent).
The transports(5) manpage mentions that the destination defaults
to the recipient domain. However, the scheduler uses a different
default, which appears to be inconsistent. I wonder what would
break if this were to be changed.
For now, perhaps your header_checks rules can copy the recipient
domain to the FILTER command.
Wietse
