I am trying to setup the e-mail on the Protector. As a trial, I am setting up the e-mail for the domain ; for which e-mail addresses have not been made public up to now. This way I ca do the setup without interrupting my business.The mailserver is at my ISP hosting the domain. The public IP address of the server is IP.
I have added the mailserver in the e-mail setup. Printscreens are attached.
I also added the involved IP address in the Servers Authorized to Relay tab. Printscreen attached.
I also added the user to the E-mail authorized users.
I configured the MX record as follows: domain - TTL300 - IN - MX - filter.domain (I cannot enter IP addresses for MX records)
I created filter.domain - TTL300 - IN - A - IP (my public IP)
So the idea is that the domain domain hosted on IP, based on MX settings, will transfer e-mails to the Protector on IP. Protector is configured to send out e-mails that have been validated again to IP which also hosts the webmail app.
When sending an e-mail, it is timed out. So it seems that the Protector does not receive the e-mail.
In order to solve this I thought a rule on the Cisco to forward incoming traffic in port 993 (imap port supported by ISP) to the Protector on 192.168.1.2 would solve the issue. But no change.
Please can you help on this?
The MX record is correctly set to filter domain – OK
filter domain points to IP the Protector public IP – OK
As a consequence, the email for domain will be sent to IP, and here, from the public IP, it must be sent to the Protector’s local IP. The protocol is not IMAP, because the Protector acts as a MTA (mail transfer agent), using ports 25 or 465, depending on the settings. So, the rule to create on the Cisco is to forward ports 25 and/or 465.
Another problem could be the username/password configured to forward mail to the mail server IP. The username/password are required by the mail server when we try to relay (send an email to another server through IP). For incoming mail it should not be necessary.
Then, at least for testing, I would remove the restriction on Authorized Users. When the whole mail management works, for incoming and outgoing mail, it can be restored.
Email works, after enabling incoming mail on port 25.