Can receive emails but cannot send emails to outside domains

So I’m in a bit of a pickle. My domain is epenguin.net, but my mail server runs on mail{dot}epenguin{dot}net even though I have the domain set as epenguin{dot}net. I added a mask for receiving emails as “mail” so I can receive email from outside domains. However, I don’t have an option to do this for sending e-mails. So my outgoing mail doesn’t actually work if its an outside domain. Is there any way to get around this?

Hello,

Your setup is not strange at all but for sure you made something wrong because there is no MX record(s) for the mentioned domain (epenguin.net)

This is strange as you are saying that you are able to receive emails from outside domains - could you please clarify this unclear situation before looking furthermore?

BR,
Ioan

Hi! Thanks for responding! I have nginx running and listening on ports 80 and 443 of epenguin{dot}net, and I have mail{dot}epenguin{dot}net listening on those ports as well for axigen. Incoming e-mails weren’t working originally because axigen runs on mail{dot}epenguin{dot}net even though I have epenguin.net as its primary domain. I added an alias “mail” and it started working (in the smtp receive options). This didn’t fix the issue for sending, though. Maybe I should try adding a MX name in my domain provider.

Just added this MX rule:

No dice unfortunately

I would be happy to provide more information. I’m just not sure what information would be required to debug this. Is there an “attempted to send” log folder for axigen?

Hello,

Adding the MX record is the first step you should take for receiving incoming messages.
Basically you are instructing “external” mail services that they should contact a specific server (in your case mail.epenguin.net) when they need to send messages to an account from epenguin.net domain.

Now, the above record looks fine but from our side we still do not see this record:

$ dig mx epenguin.net @1.0.0.1

; <<>> DiG 9.11.9 <<>> mx epenguin.net @1.0.0.1
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 58038
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;epenguin.net.                  IN      MX

;; AUTHORITY SECTION:
epenguin.net.           600     IN      SOA     ns27.domaincontrol.com. dns.jomax.net. 2020080713 28800 7200 604800 600

;; Query time: 46 msec
;; SERVER: 1.0.0.1#53(1.0.0.1)
;; WHEN: Sat Aug 08 00:14:33 EEST 2020
;; MSG SIZE  rcvd: 121

Are you sure that the MX record was added for the domain you have mentioned (epenguin.net)?

Please advice.

BR,
Ioan

Sorry for the late response. I bunked my axigen setup somehow so now only http, rather than https, works. This is because I stupidly tried to add a subdomain on godaddy, then realized that broke everything, then deleted the subdomain. Now I have to wait for godaddy to stop redirecting my subdomain which they say could take from 2-4 days. I’ll have to wait until then before updating =(