Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Cannot get incoming email to mail server

    Scheduled Pinned Locked Moved NAT
    6 Posts 2 Posters 1.4k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • S
      scopa
      last edited by

      Incoming email not getting to mail server - I reset states nothing hits the FW - I do not see anything in Logs for destination WAN or internal IP of mail server destination. Any ideas? I can send.

      1:1 NAT of mail server

      WAN 59.59.x.x 192.168.5.220 192.168.5.220 Email NAT

      Port Forwarding for mail server
      WAN TCP * 443 (HTTPS) WAN_email 443 (HTTPS) 192.168.5.220 443 (HTTPS) Mail HTTPS
      WAN TCP * 993 (IMAP/S) WAN_email 993 (IMAP/S) 192.168.5.220 993 (IMAP/S) Mail IMAP/S
      WAN TCP * 465 (SMTP/S) WAN_email 465 (SMTP/S) 192.168.5.220 465 (SMTP/S) Mail SMTP/S
      WAN TCP * 25 (SMTP)         WAN_email 25 (SMTP)  192.168.5.220 25 (SMTP)  Mail SMTP
              WAN TCP * 40809         WAN_email 40809         192.168.5.220 40809         Mail SSH

      Port forwarding configured w/ PureNat  - and rules were automatically added to WAN INT on FW

      These rules on on my WAN INT but they have internal IP added as Destination (rules were added automatically from PortForwarding)

      IPv4 TCP * 443 (HTTPS) 192.168.5.220 443 (HTTPS) * none NAT Mail HTTPS
      IPv4 TCP * 993 (IMAP/S) 192.168.5.220 993 (IMAP/S) * none NAT Mail IMAP/S
      IPv4 TCP * 465 (SMTP/S) 192.168.5.220 465 (SMTP/S) * none NAT Mail SMTP/S
      IPv4 TCP * 40809         192.168.5.220 40809         * none NAT Mail SSH
      IPv4 TCP * 25 (SMTP)         192.168.5.220 25 (SMTP)         * none

      Why can I not receive incoming email to my server with these settings - what am I missing.

      1 Reply Last reply Reply Quote 0
      • D
        doktornotor Banned
        last edited by

        No idea what are you trying to port-forward with 1:1 NAT. Makes no sense. Sounds like you never got the 1:1 NAT working: https://forum.pfsense.org/index.php?topic=94809.0 - not really sure what's the point in starting a new thread.

        1 Reply Last reply Reply Quote 0
        • S
          scopa
          last edited by

          so i dont need to use port forwarding if using 1:1 NAT?

          Just setup the NAT and then the firewall rules?

          1 Reply Last reply Reply Quote 0
          • D
            doktornotor Banned
            last edited by

            https://doc.pfsense.org/index.php/1:1_NAT

            1:1 NAT, aka one-to-one NAT or binat, binds a specific internal address (or subnet) to a specific external address (or subnet). Incoming traffic from the Internet to the specified IP will be directed toward the associated internal IP. Outgoing traffic to the Internet from the specified internal IP will originate from the associated external IP.

            1 Reply Last reply Reply Quote 0
            • S
              scopa
              last edited by

              yes I know what NAT does just not sure if

              1 - I have to use port forwarding w/. NAT or just NAT w/ FW rules.

              Can you delete this post - I will follow up with the other one - just posted screen shots there of my settings

              1 Reply Last reply Reply Quote 0
              • D
                doktornotor Banned
                last edited by

                Did you actually read at least the quoted part!? 1:1 NAT already sends all traffic to the configured host/subnet. Set up the 1:1 NAT and move on! (In fact,  you are overriding the 1:1 NAT with port forwards, and screwing things up.)

                1 Reply Last reply Reply Quote 0
                • First post
                  Last post
                Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.