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

    Can't get emails

    Scheduled Pinned Locked Moved NAT
    25 Posts 5 Posters 4.1k 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.
    • B
      Baldur
      last edited by

      @Derelict:

      One reason mail might not be getting in would be because there was a rule on your firewall which prevented POP3 or IMAP from being allowed in.

      You mean allowed out?

      That would make the MUA complain.

      The thing is that I do not know if it's sending. But I'm guessing a giant "Cannot connect to server" would pop up if that were the case.

      1 Reply Last reply Reply Quote 0
      • DerelictD
        Derelict LAYER 8 Netgate
        last edited by

        Considering you blacked out anything useful, it's impossible to tell.

        Email clients make OUTBOUND connections.  The pertinent firewall rules are on LAN, not WAN.  But like I have said at least three times, if it was a problem connecting to the server the email client would be complaining.

        This is a non-problem.  He needs to call his email provider and ask where his mail is.

        Chattanooga, Tennessee, USA
        A comprehensive network diagram is worth 10,000 words and 15 conference calls.
        DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
        Do Not Chat For Help! NO_WAN_EGRESS(TM)

        1 Reply Last reply Reply Quote 0
        • M
          muswellhillbilly
          last edited by

          Your screenshot has blacked out not just the IP addresses but the source/target ports, so it's not really much hlep.

          Ok, now that we've established that your roommate's mail server is hosted outside your LAN, you should forget about port forwarding any protocols inbound. Your out-of-the-box outbound NAT/rules should allow your roommate to connect to his mail server without your having to muck about with inbound NAT rules.

          You can try this test: From a command prompt (any machine in your LAN will do), type 'telent aaa.bbb.ccc.ddd 110', where 'aaa.bbb.ccc.ddd' is the IP address of your roommate's mail server. If you get a 'Connected' message that means your LAN can connect to the remote server successfully via POP3. Likewise with the other ports for SMTP (port 25) and IMAP (port 143). If you don't get a 'Connected' message this may mean there's a problem with the mail server. Unless you have a rule specifically blocking access to these ports then it's unlikely to be the firewall.

          1 Reply Last reply Reply Quote 0
          • B
            Baldur
            last edited by

            @muswellhillbilly:

            Your screenshot has blacked out not just the IP addresses but the source/target ports, so it's not really much hlep.

            Ok, now that we've established that your roommate's mail server is hosted outside your LAN, you should forget about port forwarding any protocols inbound. Your out-of-the-box outbound NAT/rules should allow your roommate to connect to his mail server without your having to muck about with inbound NAT rules.

            You can try this test: From a command prompt (any machine in your LAN will do), type 'telent aaa.bbb.ccc.ddd 110', where 'aaa.bbb.ccc.ddd' is the IP address of your roommate's mail server. If you get a 'Connected' message that means your LAN can connect to the remote server successfully via POP3. Likewise with the other ports for SMTP (port 25) and IMAP (port 143). If you don't get a 'Connected' message this may mean there's a problem with the mail server. Unless you have a rule specifically blocking access to these ports then it's unlikely to be the firewall.

            Might be worth showing us your firewall rules, for that matter.

            The ports are 61109, which I know is not POP3, but I filtered the search to port 110.

            As for rules, there are no firewall rules for the WAN.

            Either way, thank you. I will ping the server tomorrow and see if it gets me anything.

            1 Reply Last reply Reply Quote 0
            • vallumV
              vallum
              last edited by

              @Baldur:

              @Derelict:

              Web server?

              I think you're looking at your local network when the problem lies elsewhere.

              I'm more specifically looking at the PFsense box as a whole. What could the router do to prevent email from getting in. If it's not the problem, then it's not my problem.

              Hey ,
              I guess your friend has configured Offline client(outlook , windows live etc) on LAN PC .
              In order to diagnose first you have to SSH into Pfsense and from Terminal do to a Telnet to MX of mailserver on Port 995 or 110 (this is configured on offline client)  , are you able to do it?

              Manu

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