Announcement

Collapse
No announcement yet.

unable to send email using exchange 2003

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • unable to send email using exchange 2003

    I've sbs,exchange 2003 and smtp relay server...I able to receive email but sending...I've checked with my ISP and they're not blocking port 25...I did forward port 25 to my smtp server and even I've tried it without any firewall still am not able to send an email...and also I'm not able to telnet from inside out someone Else's email server....please help....

  • #2
    Re: unable to send email using exchange 2003

    If you can't telnet out to another mailserver then check for a local firewall on the box, a hardware firewall between you and the internet or AV (McAfee VirusScan blocks 25 for example). I realise you state you checked firewalls but they are the most likely culprit.
    cheers
    Andy

    Please read this before you post:


    Quis custodiet ipsos custodes?

    Comment


    • #3
      Re: unable to send email using exchange 2003

      I don't have any antivirus so far, just setting it up... tried it with out firewall and by disabling windows firewall too, still i'm not able to send. I'm not sure if I miss something....
      Thanks,

      Comment


      • #4
        Re: unable to send email using exchange 2003

        Can you telnet to your ISPs SMTP Server?
        ISPs have a habit of lying - so the fact that they have said they are not blocking port 25 outbound does not mean they are not.

        Simon.
        --
        Simon Butler
        Exchange MVP

        Blog: http://blog.sembee.co.uk/
        More Exchange Content: http://exchange.sembee.info/
        Exchange Resources List: http://exbpa.com/
        In the UK? Hire me: http://www.sembee.co.uk/

        Sembee is a registered trademark, used here with permission.

        Comment


        • #5
          Re: unable to send email using exchange 2003

          from other location am able to telnet my isp mail smtp server but from my network am not able to telnet neither my isp nor other mail server...by the way I was able to send email out for couple of days. Do I have to call my ISP....if i have to what should i ask them other than if they block port 25?

          Is there something I need to on my DNS server about MX record?
          Last edited by addiss; 10th December 2008, 14:49.

          Comment


          • #6
            Re: unable to send email using exchange 2003

            MX records would have nothing to do with your ability to send email.
            If you cannot telnet to your ISPs SMTP server then either you are blocking port 25 traffic locally or the ISP has blocked all outbound SMTP traffic for some reason. Often this is done because they think you are spamming.

            Simon.
            --
            Simon Butler
            Exchange MVP

            Blog: http://blog.sembee.co.uk/
            More Exchange Content: http://exchange.sembee.info/
            Exchange Resources List: http://exbpa.com/
            In the UK? Hire me: http://www.sembee.co.uk/

            Sembee is a registered trademark, used here with permission.

            Comment


            • #7
              Re: unable to send email using exchange 2003

              I did called my ISP.. the agent who talked to me said that he is not sure if they blocked port 25 manually...He promised to let me know by tomorrow.

              Comment


              • #8
                Re: unable to send email using exchange 2003

                you were right... after the 4th call they admitted that they manually blocked port 25... they said that my system might infected.....
                -I need one more favor though, what anti virus and anti spam do you recommend me?

                Comment


                • #9
                  Re: unable to send email using exchange 2003

                  The only recommendation that I make on AV and antispam is anything but Symantec, McAfee and Trend. Symantec in particular I find causes many problems, to the point of if it is installed I tell someone that it must be removed as it is the most likely cause of a problem.
                  Antispam is unique to each site. You need to test and evaluate the applications to see what works for you. For some the built in IMF works fine. For others it is useless and they have to use GFI. Then some may find that GFI is useless.

                  If the ISP thinks you are infected, then simply block port 25 on your firewall for everything but the Exchange server. If there is an infected machine then it will quickly fill up the logs.

                  Simon.
                  --
                  Simon Butler
                  Exchange MVP

                  Blog: http://blog.sembee.co.uk/
                  More Exchange Content: http://exchange.sembee.info/
                  Exchange Resources List: http://exbpa.com/
                  In the UK? Hire me: http://www.sembee.co.uk/

                  Sembee is a registered trademark, used here with permission.

                  Comment


                  • #10
                    Re: unable to send email using exchange 2003

                    I really apprecaite... you've been very helpful thanks again for your time....Do I really need SPF?

                    Comment


                    • #11
                      Re: unable to send email using exchange 2003

                      SPF doesn't make much of a difference in my experience - if you set it correctly. It is when you set it incorrectly that things can be troublesome.

                      It does no harm though.

                      Simon.
                      --
                      Simon Butler
                      Exchange MVP

                      Blog: http://blog.sembee.co.uk/
                      More Exchange Content: http://exchange.sembee.info/
                      Exchange Resources List: http://exbpa.com/
                      In the UK? Hire me: http://www.sembee.co.uk/

                      Sembee is a registered trademark, used here with permission.

                      Comment

                      Working...
                      X