> For the complete documentation index, see [llms.txt](https://docs.emaildelivery.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.emaildelivery.com/docs/velocity-mta-basics/getting-ready-to-send.md).

# Getting ready to send

**The following steps will be required for an end-to-end Velocity MTA deployment:** 

* [ ] Add a [PTR record ](/docs/what-you-need-to-know-before-you-install-velocity-mta/ptr-records-and-reverse-dns.md)for your Sending IP at your server hosting provider (aka Reverse DNS). 
* [ ] [Install Velocity MTA](/docs/velocity-mta-basics/installing-velocity-mta.md) on a Ubuntu Linux server with at least one IP address that can be used for sending email.
* [ ] Connect your Velocity MTA server in the ESP platform administrator UI under MTA -> Velocity MTA Servers.
* [ ] [Configure DKIM](/docs/velocity-mta-basics/configure-dkim.md).
* [ ] Add SPF and DMARC authentication to your DNS hosting provider, such as Cloudflare, Namecheap, or GoDaddy, by using ChatGPT or another online generator to create your TXT records.
* [ ] Create an MTA Delivery Policy in the ESP platform administrator UI.
* [ ] Assign the MTA Delivery Policy to a [Postal Route](/docs/introduction/postal-routes.md).
* [ ] Assign the Postal Route to a Customer Account.
* [ ] [Send a test message](/docs/velocity-mta-basics/sending-your-first-test-message.md) from the Customer Account through the email marketing platform using the broadcast test widget.
* [ ] Monitor the velocity-install/logs/velocity.log file.