On Mon, Mar 29, 2010 at 02:32:23PM +0200, Dirk Taggesell wrote:
> there is an internally used development server with a fairly
> default postfix installation. For testing software I want to
> have postfix listen on an additional port and every mail
> incoming on this port should not be delivered as usual but
> instead being forwarded to a single address on the internal
> mail server (different server). Mails incoming on port 25
> instead should be delivered normally.
>
> So I set up another rule in master.cf:
>
> localhost:485 inet n - - - - smtpd
>
> and postfix is now listen to port 485 as well. But now I'm
> stuck. Where do I want to go from here? A transport rule?
> Virtual? Always_bcc? What would be the best/canonical way to
> achieve this?
I would suggest a static: map for virtual_alias_maps, in a separate
instance of Postfix. You might want a transport(5) for the single
target address to the internal server in this instance.
Note: when using static: for virtual_alias_maps, it is necessary to
unset virtual_alias_domains. Google should be able to find one or
more examples of this on this list.
Multiple instance management is greatly improved in 2.6 et seq., so
this might be a time to consider upgrading if you are not already
using 2.7.
http://www.postfix.org/MULTI_INSTANCE_README.html
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
