The usual solution to flushing ONE site with a large backlog is to
make a separate transport entry.

    /etc/postfix/main.cf:
        transport_maps = hash:/etc/postfix/transport
        backlogged_destination_concurrency_limit = 0

    /etc/postfix/transport:
        earthlink.net backlogged:

    /etc/postfix/master.cf:
        [same entry as smtp client, but the first field is "backlogged"]

Then postfix reload and watch the drain flush.

        Wietse

Len Conrad:
> Dear Doctor,
>
> Here's where it hurts:
>
> Grand Totals
> ------------
> messages
>
> 26 received
> 2070 delivered
> 0 forwarded
> 18614 deferred (20536 deferrals)
> 1187 bounced
> 0 rejected
>
> 2112k bytes received
> 13574k bytes delivered
> 5 senders
> 4 sending hosts/domains
> 814 recipients
> 12 recipient hosts/domains
>
>
> Per-Hour Traffic Summary
> time received delivered deferred bounced rejected
> --------------------------------------------------------------------
> 0000-0100 6 72 48 84 0
> 0100-0200 2 36 0 55 0
> 0200-0300 2 69 0 98 0
> 0300-0400 1 659 358 270 0
> 0400-0500 5 5 1 0 0
> 0500-0600 0 0 11158 0 0
> 0600-0700 4 81 7464 36 0
> 0700-0800 1 507 369 350 0
> 0800-0900 1 422 788 14 0
> 0900-1000 4 219 350 280 0
> 1000-1100 0 0 0 0 0
>
>
> where mailq shows 17692 total, and 16683 for earthlink.
>
> 114 SMTP processes with 512 megs RAM and 400 SMTP in master.cf.
>
> Is there anyway to "thundering herd" this earhtlink crap out of the queue?
>
> Len
>
>
> -
> To unsubscribe, send mail to majordomopostfix.org with content
> (not subject): unsubscribe postfix-users
>
>

-
To unsubscribe, send mail to majordomopostfix.org with content
(not subject): unsubscribe postfix-users

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