[quote user="tuaris"]<p>How can I prevent mercury from generating delivery failure notifications for non-local users?</p><p> </p><p>See the following: http://www.backscatterer.org/?target=backscatter </p><p>[/quote]</p><p>Make your domain a domain type account in the domains setup and then set aliases to a local domain for all good users.  </p><p>For example, suppose you have the domain example.com.  You domains setup would look like</p><p>[Domains]</p><p>server : server dm=example :  example.com server : local.example.com</p><p>where example is a local user account.  Now all mail for example.com goes to the user example.   You can now setup alias for the users so that tuaris@example.com goes to tuaris@local.example.com instrad of the domain account since the aliased are processed before the domain.</p><p> With this setup everything for the domain example.com is received, nothing is rejected.</p><p>  That said this is a pain in the rear to manage and rejecting the non-local users at the MercuryS server is a much better idea and is what is desired by the people at backscatter.org in the first place.  This is very difficult to do in a large corporate setup using mail gateways in multiple world-wide locations.  There is no way in the world that the corporate mail gateway server will ever be able to maintain a complete listing of the users on all the internal mail servers so that mail for bad user rejected at the local server may or may not bounce back to something other than the original sending system.</p><p>  </p><p>  </p>

<p>How can I prevent mercury from generating delivery failure notifications for non-local users?</p><p> </p><p>See the following: http://www.backscatterer.org/?target=backscatter </p>