On Mon, 2005-07-11 at 10:09 +0700, Saran Toochinda wrote:
> Hi,
>  I have set up postfix as a gateway mail relay on a linux box at our office. 
> This gateway only connect to the internet during office hours and has no DNS 
> record anywhere. Initially I configure it to send mail directly to the 
> internet without using any intermediate host. It's work fine for most of our 
> client's mail servers. However, some of them refuse our mail because it 
> can't find reverse DNS records of our mail gateway. So I have to use 
> relayhost for these client's (using transport_maps). I used to use 'MDaemon' 
> mail server on W2K machine, it has a nice option saying that 'delivery 
> undelivered mail to this host if it can't directly send for any reason'.

I think that's what 
fallback_relay (default: empty)
        
        Optional list of relay hosts for SMTP destinations that can't be
        found or that are unreachable. 
        
        By default, mail is returned to the sender when a destination is
        not found, and delivery is deferred if a destination is
        unreachable.
        
        The fallback relays must be SMTP destinations. Specify a domain,
        host, host:port, [host]:port, [address] or [address]:port; the
        form [host] turns off MX lookups. If you specify multiple SMTP
        destinations, Postfix will try them in the specified order. 
        
        Note: do not use the fallback_relay feature when relaying mail
        for a backup or primary MX domain. Mail would loop between the
        Postfix MX host and the fallback_relay host when the final
        destination is unavailable. 
        
              * In main.cf specify "relay_transport = relay",
              * In master.cf specify "-o fallback_relay =" (i.e., empty)
                at the end of the relay entry.
              * In transport maps, specify "relay:nexthop..." as the
                right-hand side for backup or primary MX domain entries.
        
        These are default settings in Postfix version 2.2 and later.
        
Is for.
        
>  
> This option is best suite for our need cause we try to avoid intermediate 
> host usage but if we can't avoid it then use it as need but not being used 
> it for all.
>  My question is, is there a way to do this in postfix? As I can see, when 
> remote server say '533 invalid sender' postfix simply bounce the message. 

As it should.  A permanent error is supposed to be bounced.

-- 
Daniel J McDonald, CCIE # 2495, CNX, CISSP # 78281
Austin Energy

[EMAIL PROTECTED]

_______________________________________________
http://lurker.clamav.net/list/clamav-users.html

Reply via email to