Email server behind pfSense
-
"to use firewall ip as mx, you will need nat or postfix forwarder package"
I need mail server ip (94.55.x.x) as mx. In this case is it possible to configure it from postfix package?
postfix will use server address, if you have 94.55. IP on pfsense, it will work
-
Dear marcelloc,
Don't mind. Actually I am very new in pfSense. What do you mean by 94.55.x.x ip in pfSense? My WAN IP is 94.54.x.x and my internal mail server configured as 10.10.1.5. Domain MX record is on 94.55.x.x and I want to send and receive mail through 94.55.x.x
I checked the postfix forwarder option that takes the Domain name and ip. If I put the domain name and ip (94.55.x.x) there will it work?
Thanks for your help.
-
nahid,
You network diagram shows internal and external ips on your mail server. If this ip is an alias on your pfsense, you just need to configure this alias to postfix forwarder and make an outbound nat (firewall -> nat) to force exchange outgoing ip address to be the same as mx.
att,
Marcello Coutinho -
Thanks Marcello Coutinho.
I will do exactly what you have told on Saturday.
-
Marcello,
How can I configure an aliases in postfix forwarder? Is it the domain where I can give the aliases ip address or something else?
-
Marcello,
How can I configure an aliases in postfix forwarder? Is it the domain where I can give the aliases ip address or something else?
on domain tab you specify internal domains as well internal ips.
do you mean domain aliases like mydomain.com and domain2.com?
-
Dear marcelloc,
I tried how you told to configure it but could able to send email as it marked the wan IP address as spam. I inspected the email headers and it showed that the email was sent from ip address 94.54.x.x what is not my email server ip.
I configured the outbound nat but it failed to send over Email Server IP
-
Using you internal mail server only and having you mx IP as an alias on your pfsense, an outbound nay should work. Remember to configure outbound Nat mode to manual.
-
Dear Marcelloc,
Attached picture where you can find my config. Is there any mistakes there?
-
Change interface to wan and place rule on top
-
Dear marcelloc,
I tried how you instructed but unsuccessful. Is there any way to solve this problem?
-
Do you send email to the internal email server and then use the external as a forwarder, and then use the external as the public email mx and forward all inbound emails to the internal server?
As marcelloc indicated, NAT rules work on first matching. So if the desired effect is below an undesired action, then you will need to move it to the top.
-
Podilarius,
"Do you send email to the internal email server and then use the external as a forwarder, and then use the external as the public email mx and forward all inbound emails to the internal server?"
how can I do that?
-
Nahid,
That is going to depend on the type of email servers you are using. I use 2 email server types; Exchange and Zimbra. The setup for something like this is different in each, but it is possible. I asked to try to figure out what you are trying to accomplish. Are you in control of the 94.55 address where the external mail server is? -
We use MerakMail (IceWarp) mail server. My email Server is installed in a local machine with IP 10.10.1.5. The ISP provider has given us some static IP those we use for our servers. For example 94.55.59.129 is for our webserver but webserver is in our local ip with 10.10.1.11. I natted the 80 port with 94.55.59.129 and it is working with no problem. The same thing I want do is to send from and get mails from 10.10.1.5 but it should use 94.55.59.130 as permitted sender.
I have also natted the IMAP, POP3, and SMTP port forwarding. Could you please describe me the configuration that I need to send mail from 10.10.1.5 behind the pfSense but using the MX record of 94.55.59.130.
If you need further information please let me know.
-
Ah .. okay I see. Looking at the advanced outbound rule you posted, it seems wrong. As the others stated, you need to put this rule above all others in the AON screen. You also need to change the destination port to blank (any). Your server is going to be responding to request on high port with a source port of 25. As others have stated, you also need to change the interface to WAN.
I would open it up first and then lock it down so i would do:Interface: WAN
Source: INTERNALMAILSERVER
SPort: any
Destination: any
DPort: any
NAT Address: SESRICMailServer
NAT Port: blank (any)If that works, then just change SPort to 25 if you only want to NAT smtp.
-
You can get the configuration picture attached.
-
Will the above configuration work or is there anything wrong?
-
The configuration from the pics looks good. If it is not working, try restarting the FW.
-
Nahid,
You have two nats for the same port 80. It will not work.
The rest of your config is fine but you may need to test with bogons rules disabled on wan interface.
