From: MacShane, Tracy (Tracy.MacshaneAirservicesAustralia.com)
Date: Fri Apr 11 2008 - 03:21:38 CDT

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

I'm running Postfix 2.2, alas, so many of the options for high volume
backlogs in QSHAPE_README <http://www.postfix.org/QSHAPE_README.html>
don't apply.
 
We have a destination domain that starts throttling connections after
more than 30 messages per minute are directed to any specified address.
Unfortunately, we have an application that sends dozens of messages to a
specified address on this domain a day, and the destination servers are
prone to go offline at random intervals (the country does not have a
great internet infrastructure). When the server comes back online, the
large numbers of queued messages attempt to resend, and their limit gets
breached.
 
I've tried implementing the below configuration suggested in
QSHAPE_README, but I'm getting the errors following.
/etc/postfix/main.cf <http://www.postfix.org/postconf.5.html> :
    transport_maps
<http://www.postfix.org/postconf.5.html#transport_maps> =
hash:/etc/postfix/transport

/etc/postfix/transport:
    example.com slow:[badhost.local]

/etc/postfix/master.cf <http://www.postfix.org/master.5.html> :
    # service type private unpriv chroot wakeup maxproc command
    slow unix - - n - 1 smtp
        -o fallback_relay
<http://www.postfix.org/postconf.5.html#fallback_relay> =solomon.com.sb
        -o smtp_connect_timeout
<http://www.postfix.org/postconf.5.html#smtp_connect_timeout> =2
        -o smtp_connection_cache_on_demand
<http://www.postfix.org/postconf.5.html#smtp_connection_cache_on_demand>
=no

Apr 11 17:38:18 smtp4 postfix/smtp[2832]: 2E191216C0B9:
to=<flightsvcsolomon.com.sb>, relay=127.0.0.1[127.0.0.1], delay=0,
status=sent (250 Ok: queued as 44308216C0C2)
Apr 11 17:38:18 smtp4 postfix/smtp[7743]: 44308216C0C2:
to=<flightsvcsolomon.com.sb>, relay=none, delay=0, status=bounced (Host
or domain name not found. Name service error for name=badhost.local
type=A: Host not found)
(We have a content filter)
Does the "dead host" actually need to have a DNS entry, but not accept
mail? I'd rather know if that's what's required, rather than make more
of a mess of it (bouncing any of these emails is not desirable).

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