# What you can do with an MTA Delivery Policy * [ ] Utilize [Velocity MTA servers](/docs/velocity-mta-basics/adding-a-server-in-the-backend-ui.md) for sending mail over your own home grown infrastructure. * [ ] Create pools of IP addresses and individualized sending configurations for important mailbox providers such as Gmail, Yahoo, and iCloud. * [ ] Place hourly and daily sending volume caps on IP addresses. * [ ] Load balance mail volume across your IP pool by percentage allocation. * [ ] Create individualized deferral waiting periods customized by the content of the SMTP response given by a mailbox provider. * [ ] Create a list of irrelevant SMTP responses to ignore, preventing the initiation of a deferral timeout. * [ ] Throttle the number of simultaneous connections made to a mailbox provider's MX servers based on the MX domain instead of the domain in the email address. * [ ] Automatically increase your deferral waiting period each time you receive a deferral message without any intervening delivery successes. * [ ] Pause mail if successful delivery volume has decreased below an expected threshold. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.emaildelivery.com/docs/velocity-mta-basics/oracle-cloud-and-amazon-lightsail-issues/what-you-can-do-with-an-mta-delivery-policy.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.