From: Wietse Venema (wietseporcupine.org)
Date: Tue May 03 2005 - 09:36:58 CDT

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Geoff Gibbs:
> Unfortunately our institute is being closed down.

I hope you find a good place.

> I am setting up a server, which can be left somewhere, which
> will cater for 3 groups of people :-
>
> Forward mail
> Reject mail, giving their new address
> Reject mail, giving a helpful message
>
> I have used the firewall set-up from the documentation, with no
> local delivery. I can handle the groups thus :-
>
> Forward mail - virtual maps
> Reject with new address - relocated maps
> Reject with message - transport maps with 'error:message'
>
> This seeems to work ok, but I would like the 3rd option to be
> for any address not covered by the first 2. The relocated maps
> seem to overide the transport maps, which is fine, but,
> not surprisingly, the transport maps overide the virtual maps.
> I could arrange the transport maps to be a pcre to match
> anything except those in the virtual maps, but this does not seem
> very satisfactory. Is there a better way to do this.

Instead of relocated(5), use transport(5). The relocated map
became redundant ever since transport maps can have addresses.

/etc/postfix/main.cf:
    virtual_alias_domains = example.com
    virtual_alias_maps = hash:/etc/postfix/virtual
    transport_maps = hash:/etc/postfix/transport

/etc/postfix/virtual:
    forwardedexample.com ...forwarded address...
    movedexample.com movedexample.com
    otherexample.com otherexample.com
    
/etc/postfix/transport:
    movedexample.com error:5.1.6 User has moved to <xxyy.zz>
    example.com error:5.1.1 Account is terminated

It may be possible to do this with fewer map entries but the
above should take care of it.

The above assumes Postfix 2.3 enhanced status codes, which will
make error reports much more informative to people with GUI mail
client software.

        Wietse

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]