๐Ÿ“ฅIncoming email MX server

Each Velocity MTA sending IP listens for incoming email replies on port 25 for authorized receiving domains

conf/receiving_domains In order to accept email for a domain as an incoming MX server, the receiving domain must be listed in velocity-install/conf/receiving_domains, with one domain per line. Any domains not listed in this file will have their email rejected.


Velocity MTA must be restarted for changes to take effect.

Adding MX records to your DNS

In order for mailbox providers like Yahoo to know they can send email replies and complaint feedback loops to your Velocity MTA server, you must create an MX record pointing to your Velocity MTA IP address on your DNS hosting provider.

MX records are idiosyncratic

You must first create a DNS A record that points to your Velocity MTA IP address, then create an MX record that specifies that A record will be the MX record for your sending domain or subdomain.

Using Cloudflare as our example DNS hosting provider, our A record named "MX" will be the MX record for the sending subdomain sendmail.vitamindispatch.com.

MX record priority

MX records require setting a priority, with the lowest number receiving the highest preference. Setting priority 0 will make an MX record the first to be attempted in a load balanced configuration with multiple servers handling a high volume of inbound mail.

Using the terminal command dig we can verify our MX record is active and pointing to the right place.

dig sendmail.vitamindispatch.com MX @
sendmail.vitamindispatch.com. 300 IN	MX	0 mx.vitamindispatch.com.

;; Query time: 85 msec
;; WHEN: Fri Jun 09 04:56:16 PDT 2023
;; MSG SIZE  rcvd: 76

Incoming messages are stored in plain text as individual files in the velocity-install/mail/new directory.

ls -alctr velocity-install/mail/new
total 20
drwxr-xr-x 5 root root 4096 Apr  6 16:00 ..
-rw-r--r-- 1 root root 9231 Apr 17 06:46 c09d311382dcdb2b0784c02c225e34f0

Last updated