Changes between Version 19 and Version 20 of bulk-mail-relay


Ignore:
Timestamp:
Apr 5, 2015, 2:30:01 PM (5 years ago)
Author:
Jamie McClelland
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • bulk-mail-relay

    v19 v20  
    9999=== Flush deferred email from one queue to another queue ===
    100100
    101 If deferred email is building up in one instance, you can move it to another instance. For example if msn-a is deferring email, but msn-b is delivering, you can move all deferred email from msn-a to msn-b by following these steps.
     101If deferred email is building up in one instance (referred to below as the clogged instance), you can move it to another instance (referred to below as the target instance). For example if msn-a is deferring email (clogged), but msn-b is delivering (target), you can move all deferred email from msn-a to msn-b by following these steps.
    102102 
    103103 * Figure out which instance is running with which IP address:
     
    1081080 rustin:~#
    109109}}}
     110 * Ensure that the target instance will accept relayed email from the clogged instance. Edit main.cf on the target instance (in this case /etc/postfix-msn-b/main.cf), adding the clogged instance's IP address (209.51.172.9) in the mynetworks line.
    110111 * Create the file /etc/postfix-msn-a/transport.relay with the contents that instruct the instance to flush all email to the server running on the IP address 216.66.15.4.
    111112{{{