Re: [dspam-users] postfix + dspam + transports

Mark Rogers wrote:
> This is mostly a postfix problem, but I think it more likely that
> someone who uses postfix+dspam will understand it, hence mailing here
> not to a postfix list. Hope that's OK.
>
> I have a working postfix+dspam configuration, that accepts mail,
> passes it to dspam, then delivers it to local mailboxes via postfix on
> port 10026.
>
> I now need to handle additional domains but which will now forward to
> another smtp server after dspam checking. If I add the domain into my
> transports map it forwards it fine, except that it happens before the
> dspam check.
>
> I have now added a different transport map to the postfix on port
> 10026 which contains the smtp: forward address, but postfix then
> complained that the user was invalid: "status=bounced (unknown user:
> user@my.domain)".
>
> I tried adding the user to my virtual_mailbox_maps so that at least
> Postfix gets an answer for @my.domain, but now Postfix seems to have
> actually managed to deliver it to that "mailbox" (the mailbox value
> was a dummy value, but Postfix has created a new mailbox by that name
> and dropped it there). The mail added to that mailbox doesn't have
> dspam headers, so I guess it's bypassed checking too.
>
> So I'm missing something here! What I want is for Postfix to accept
> anything for that domain (or, optionally, just users for that domain
> that I specifiy), pass it through dspam, then forward it to the
> nominated SMTP server (queuing it if the server isn't available for
> any reason).
>

This is a postfix configuration issue. Followups on the postfix users list.

If mail for a domain is to be relayed to a remote server, then add the
domain to relay_domains. Please put the valid addresses in
relay_recipient_maps to avoid backscatter (accept then bounce). you can
either have a copy of the list, use *sql/ldap or if all that is not
feasible, adequately use reject_unverified_recipient (do this only for
your relay domains).

If you post on the postfix users list for problems, make sure to read
the DEBUG README. In particular, always shows logs (not excerpts) and
configuration (generally the output of 'postconf -n').
Received on Tue Feb 5 11:30:43 2008