I see problems... 7 main points.
1) I think you are confusing mail server name with mail domains.
It is kind of unusual for someone to send email as
user@mail.somedomain.tld... Normally, they would just use the domain like
user@somedomain.tld.
A mail server can provide email support for many domains, including domains that are not related to it.
It would appear, that your mail server is actually mail.mtgames.org, but that is not really clear.
2) You have an MX record for mtgames.com which is good, you don't for speedofgaming.com. In general it is a good idea to have an MX record that points to the mail server for that mail domain. In some cases, not having an MX record is a negative score item.
3) Not sure if you are sending email out as
user@mail.speedofgaming.com or as
user@speedofgaming.com.
You have a problem if you are using the wrong mail domain since those hostnames point to different IP's.... (you have no MX records to clearly say where email for that domain should go)
mail.speedofsoundgaming.com IN A 96.126.113.71
speedofsoundgaming.com IN A 72.14.189.72
4) As an aside you have some host names which resolve to IP's that have no PTR records...
mtgames.org. 30 IN A 108.162.194.112
mtgames.org. 30 IN A 108.162.194.12
5) You need to make sure that the mail server for your speedofgaming.com mail domain is setup to do validation checks for the email addresses it is sending as. if the remote server can't validate your sending email address, you will get deferred a lot and in some cases never be accepted.
Meaning that if you are sending email as
user@speedofgaming.com the remote server can contact the host (since you have no MX record) speedofgaming.com to see if it says it is valid.
6) in general...... mail server name = IP = mail server name = good.
if your mail server says it is mail.xyz.com the IP it is using should point back to the same name. While web browsers could care less as long as they can find the webserver, Mail servers use that type of check to help validate that the sender is valid and not some bot infected workstation faking the email.
And again the mail server name is not necessarily related to the mail domains you are sending email as.
7) SPF records help your cause. With larger mail systems so do DKIM and other validation signatures.
you can check to see what a server thinks of your email by sending email to:
check-auth2@verifier.port25.comIt will send back a report with results it found for SPF, DomainKeys, DKIM, Sender-ID results.
Note that it includes SpamAssassin result... so you hope to see Ham, not Spam.
More details information on your part would have provided better insight into what your issues.