Can't receive email + access webmail via domain name

Support WebMail
1

Hi

1- I installed axigen on a server with Nginx web server
I don’t receive email

here is part of the log I think is related to the problem

log.txt (5.0 KB)

2- I have 3 sites on this server
I want to have access to webmail via all of them and by entering their URL
like this:

mysite1:8000
mysite2:8000
mysite3:8000

but now I can only access the webmail via the server ip

2

Hello,

Let’s first clarify your first reported problem - I don’t receive email.

1/ First of all please check if the SMTP-Receiving service is started and have a listener on port 25 - please confirm what IP address is listed on that listener

2/ Secondly double check that there is no firewall (sitting between your server and “internet”) that could prevent TCP traffic on port 25

3/ Lastly please check that the account is configured in Axigen and the domain has the DNS MX record that is “pointing” to your Axigen installation.

HTH,
Ioan

3

Hi

thank you

1/yup it’s started and the ip is my server ip

2/ there is no firewall

3/ I created an A record which is mail.mydomain.com and pointed to my server ip
and created a MX record which is mydomain [dot] com and pointed to mail.mydomain.com
but I don’t know whats your meaning of pointing to axigen installation, how should I do that?

4

Hello,

Excellent than - could you provide us the server IP address so we could open a “telnet” session from our office to port 25?

And, by the way, is the server IP a routable one or it is a ‘private’ one (like 192.168.1.10) - in which case you have to create a NAT rule for port 25?

BR,
Ioan

5
Summary

…

yes it’s routable

6

excellent - than all is fine.

7

Hi

so where is problem?
did you check the IP?

8

Hello,

Yes, I’ve check it and it works fine:

$ telnet a.b.c.d 25
Trying a.b.c.d...
Connected to a.b.c.d.
Escape character is '^]'.
220 abcd.com Axigen ESMTP ready
quit
221-abcd.com Axigen ESMTP is closing connection
221 Good bye
Connection closed by foreign host.

Nevertheless, it seems your current configuration is not a good one as your server is acting as an open relay (you could check here). My current recommendation is to double check if you are allowing relay without authentication (via WebAdmin > Security & Filtering > Acceptance & Routing > Routing Basic Settings > Allow / Disallow relaying) and enable Require authentication in case you find it disabled.

Now, that we confirmed that your server is reachable on port 25, please set the log level for SMTP Receiving service to Protocol Communication and try to send a message from Gmail or any other external mail server to one account from your Axigen hosted domain.

Check your server logs (default location is /var/opt/axigen/log/everything.txt) for any hints of why the message is not delivered to the expected recipient.

If you did not find any clues please share the logs here so we could help to identify the reason(s) for not receiving messages.

HTH,
Ioan

9

Hi

thank you, I just changed the recommended option

and here is what you asked:
New Text Document (2).txt (57.9 KB)

pls remove my server IP and the domain name from your message, for security reasons, thank you

10

Hello,

As you could check yourself there are no SMTP-IN lines into the shared log and this means that there were no SMTP Receiving sessions.

Please double check the MX record of your domain is a hostname that is resolved with the routable IP address of your Axigen server (the one you have mentioned above) as from my checking (see below) it seems this is the explanation of your problem (not receiving messages).

Summary 
$ dig +short MX deelbaab.com
10 mail.deelbaab.com.

$ dig +short A mail.deelbaab.com
185.143.235.5
185.143.232.5

This was mentioned in my first reply (item #3) and it seems you have wrongly acknowledge that all is configured properly.

BR,
Ioan