Matt Bayliss:
> Firstly, thanks for all the replies. Forget I said best practices, I agree
> it's a rubbish term - what I really meant was the best way to achieve what
> I want.
>
> I suppose I really have two requirements. 1) Monitoring devices that use
> this Postfix installation as a relay should be able to set the FROM address
> to an address that no one will ever read replies to, but that the mail
> server is "happy" with. In the event that the address finds its way onto
> some UCE list I never want an (unmanaged) mailbox to fill, hence the desire
> for email it does receive, sent to /dev/null.
>
> The other, separate requirement is 2) To be able to place an valid address
> in the To: field for BCC: group emails so that customers see "All Clients"
> or something instead of just the From address. Again, no-one will need to
> read email sent to this address as any replies will be sent to the valid
> from/reply-to address.
>
>
> Since I am running 2.3.3 I tried Wietse's suggestion:
>
>
> I placed the following line in /etc/postfix/main.cf:
>
> transport_maps = hash:/etc/postfix/transport
>
> And added...
>
> nore...@domain.com discard
>
> ...to /etc/postfix/transport
>
> Then I did:
>
> postmap hash:/etc/postfix/transport
>
> ...and...
>
> postfix reload
>
>
> However when I send mail to nore...@domain.com from an external source
> (Gmail) I get a bounceback and "Recipient address rejected: User unknown in
> local recipient table;" in the log.
In that case, create a virtual alias nore...@domain.com->nore...@domain.com
(so that the address is "known"), or use an access map with a discard"
action as suggested in this thread (so that it never reaches the
code path that tests the "user unknown" condition).
Wietse
