locked
send connector issue RRS feed

  • Question

  • Hi ,

    I want to relay all outgoing emails from exchange to postfix

    So in exchange i setup a send connector as follows :

    in the intended use i chose "Custom:

    in the address space i chose "SMTP Address Space" with an address of "*" with cost of "1"

    in network settings i chose "Route mail through the following smart hosts" and clicked on "add" and inserted the privat IP of my "postfix"

    in smart host authentication settings i chose "none"

    in the source server i chose my exchange server

    i am sending an email to hotmail from exchange , it's not reaching , i am trying to figure out where the email is going to

    which logs do you recommend me to check in exchange ? and were are they ? so that i can figure out if the issue is from postfix or from exchange , because i can send emails to hotmail from postfix ... so i need to know why the sent email is not reaching postfix to be sent (i checked the log for postfix)

    Thanks

     


    Regards, Costa Mitri
    Saturday, May 7, 2011 1:22 PM

Answers

  • Do the messages leave the Exchange Server? Are they bouncing?

    You can always enable protocol logging:

    http://technet.microsoft.com/en-us/library/bb124531.aspx

     

    and of course, check the built in message tracking.

     

    • Marked as answer by Costa Mitri Saturday, May 7, 2011 2:09 PM
    Saturday, May 7, 2011 1:28 PM
  • Do the messages leave the Exchange Server? Are they bouncing?

    You can always enable protocol logging:

    http://technet.microsoft.com/en-us/library/bb124531.aspx

     

    and of course, check the built in message tracking.

     

    from shell i go like :

    Set-SendConnector "Connection from myexchanegdomain.com" -ProtocolLoggingLevel Verbose

     

    right ?

     

    where will these logs be located at ?


    Regards, Costa Mitri


    The Default is:

    C:\Program Files\Microsoft\Exchange Server\V14\TransportRoles\Logs\ProtocolLog

     

    Check out the article I linked for more detail.


    ok actually i got this error:

    2011-05-07T13:40:55.776Z,send all to postfix,08CDDACA3105BBD2,1,,10.10.10.5:25,*,,"Failed to connect. Error Code: 10060, Error Message: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 10.10.10.5:25"

     

    where 10.10.10.5 is my internal ip for postfix

    so i did a : telnet 10.10.10.5 25

    from exchange and got this message : Connecting To 10.10.10.5...Could not open connection to the host, on port 25: Connect failed

    however i can ping 10.10.10.5 with 100% success rate

    so think the issue is from my linux box side right ?

    gutta recheck postfix and iptables configs ...


    Regards, Costa Mitri


    Sounds like 10.10.10.5 has ip restrictions in place.

     

    that's what i'm checking now ...

    i'll keep you posted :)


    Regards, Costa Mitri

    Dont forget any firewalls in between as well!
    yeah of course :)

    Regards, Costa Mitri

    done

    it was an iptables issue


    Regards, Costa Mitri
    • Marked as answer by Costa Mitri Saturday, May 7, 2011 2:02 PM
    Saturday, May 7, 2011 2:02 PM

All replies

  • Do the messages leave the Exchange Server? Are they bouncing?

    You can always enable protocol logging:

    http://technet.microsoft.com/en-us/library/bb124531.aspx

     

    and of course, check the built in message tracking.

     

    • Marked as answer by Costa Mitri Saturday, May 7, 2011 2:09 PM
    Saturday, May 7, 2011 1:28 PM
  • Do the messages leave the Exchange Server? Are they bouncing?

    You can always enable protocol logging:

    http://technet.microsoft.com/en-us/library/bb124531.aspx

     

    and of course, check the built in message tracking.

     

    from shell i go like :

    Set-SendConnector "Connection from myexchanegdomain.com" -ProtocolLoggingLevel Verbose

     

    right ?

     

    where will these logs be located at ?


    Regards, Costa Mitri
    Saturday, May 7, 2011 1:31 PM
  • Do the messages leave the Exchange Server? Are they bouncing?

    You can always enable protocol logging:

    http://technet.microsoft.com/en-us/library/bb124531.aspx

     

    and of course, check the built in message tracking.

     

    from shell i go like :

    Set-SendConnector "Connection from myexchanegdomain.com" -ProtocolLoggingLevel Verbose

     

    right ?

     

    where will these logs be located at ?


    Regards, Costa Mitri


    The Default is:

    C:\Program Files\Microsoft\Exchange Server\V14\TransportRoles\Logs\ProtocolLog

     

    Check out the article I linked for more detail.

    Saturday, May 7, 2011 1:35 PM
  • Do the messages leave the Exchange Server? Are they bouncing?

    You can always enable protocol logging:

    http://technet.microsoft.com/en-us/library/bb124531.aspx

     

    and of course, check the built in message tracking.

     

    from shell i go like :

    Set-SendConnector "Connection from myexchanegdomain.com" -ProtocolLoggingLevel Verbose

     

    right ?

     

    where will these logs be located at ?


    Regards, Costa Mitri


    The Default is:

    C:\Program Files\Microsoft\Exchange Server\V14\TransportRoles\Logs\ProtocolLog

     

    Check out the article I linked for more detail.


    ok actually i got this error:

    2011-05-07T13:40:55.776Z,send all to postfix,08CDDACA3105BBD2,1,,10.10.10.5:25,*,,"Failed to connect. Error Code: 10060, Error Message: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 10.10.10.5:25"

     

    where 10.10.10.5 is my internal ip for postfix

    so i did a : telnet 10.10.10.5 25

    from exchange and got this message : Connecting To 10.10.10.5...Could not open connection to the host, on port 25: Connect failed

    however i can ping 10.10.10.5 with 100% success rate

    so think the issue is from my linux box side right ?

    gutta recheck postfix and iptables configs ...


    Regards, Costa Mitri
    Saturday, May 7, 2011 1:49 PM
  • Do the messages leave the Exchange Server? Are they bouncing?

    You can always enable protocol logging:

    http://technet.microsoft.com/en-us/library/bb124531.aspx

     

    and of course, check the built in message tracking.

     

    from shell i go like :

    Set-SendConnector "Connection from myexchanegdomain.com" -ProtocolLoggingLevel Verbose

     

    right ?

     

    where will these logs be located at ?


    Regards, Costa Mitri


    The Default is:

    C:\Program Files\Microsoft\Exchange Server\V14\TransportRoles\Logs\ProtocolLog

     

    Check out the article I linked for more detail.


    ok actually i got this error:

    2011-05-07T13:40:55.776Z,send all to postfix,08CDDACA3105BBD2,1,,10.10.10.5:25,*,,"Failed to connect. Error Code: 10060, Error Message: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 10.10.10.5:25"

     

    where 10.10.10.5 is my internal ip for postfix

    so i did a : telnet 10.10.10.5 25

    from exchange and got this message : Connecting To 10.10.10.5...Could not open connection to the host, on port 25: Connect failed

    however i can ping 10.10.10.5 with 100% success rate

    so think the issue is from my linux box side right ?

    gutta recheck postfix and iptables configs ...


    Regards, Costa Mitri


    Sounds like 10.10.10.5 has ip restrictions in place.

     or SMTP isnt running on it.


    Saturday, May 7, 2011 1:56 PM
  • Do the messages leave the Exchange Server? Are they bouncing?

    You can always enable protocol logging:

    http://technet.microsoft.com/en-us/library/bb124531.aspx

     

    and of course, check the built in message tracking.

     

    from shell i go like :

    Set-SendConnector "Connection from myexchanegdomain.com" -ProtocolLoggingLevel Verbose

     

    right ?

     

    where will these logs be located at ?


    Regards, Costa Mitri


    The Default is:

    C:\Program Files\Microsoft\Exchange Server\V14\TransportRoles\Logs\ProtocolLog

     

    Check out the article I linked for more detail.


    ok actually i got this error:

    2011-05-07T13:40:55.776Z,send all to postfix,08CDDACA3105BBD2,1,,10.10.10.5:25,*,,"Failed to connect. Error Code: 10060, Error Message: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 10.10.10.5:25"

     

    where 10.10.10.5 is my internal ip for postfix

    so i did a : telnet 10.10.10.5 25

    from exchange and got this message : Connecting To 10.10.10.5...Could not open connection to the host, on port 25: Connect failed

    however i can ping 10.10.10.5 with 100% success rate

    so think the issue is from my linux box side right ?

    gutta recheck postfix and iptables configs ...


    Regards, Costa Mitri


    Sounds like 10.10.10.5 has ip restrictions in place.

     

    that's what i'm checking now ...

    i'll keep you posted :)


    Regards, Costa Mitri
    Saturday, May 7, 2011 1:57 PM
  • Do the messages leave the Exchange Server? Are they bouncing?

    You can always enable protocol logging:

    http://technet.microsoft.com/en-us/library/bb124531.aspx

     

    and of course, check the built in message tracking.

     

    from shell i go like :

    Set-SendConnector "Connection from myexchanegdomain.com" -ProtocolLoggingLevel Verbose

     

    right ?

     

    where will these logs be located at ?


    Regards, Costa Mitri


    The Default is:

    C:\Program Files\Microsoft\Exchange Server\V14\TransportRoles\Logs\ProtocolLog

     

    Check out the article I linked for more detail.


    ok actually i got this error:

    2011-05-07T13:40:55.776Z,send all to postfix,08CDDACA3105BBD2,1,,10.10.10.5:25,*,,"Failed to connect. Error Code: 10060, Error Message: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 10.10.10.5:25"

     

    where 10.10.10.5 is my internal ip for postfix

    so i did a : telnet 10.10.10.5 25

    from exchange and got this message : Connecting To 10.10.10.5...Could not open connection to the host, on port 25: Connect failed

    however i can ping 10.10.10.5 with 100% success rate

    so think the issue is from my linux box side right ?

    gutta recheck postfix and iptables configs ...


    Regards, Costa Mitri


    Sounds like 10.10.10.5 has ip restrictions in place.

     

    that's what i'm checking now ...

    i'll keep you posted :)


    Regards, Costa Mitri

    Dont forget any firewalls in between as well!
    Saturday, May 7, 2011 1:57 PM
  • Do the messages leave the Exchange Server? Are they bouncing?

    You can always enable protocol logging:

    http://technet.microsoft.com/en-us/library/bb124531.aspx

     

    and of course, check the built in message tracking.

     

    from shell i go like :

    Set-SendConnector "Connection from myexchanegdomain.com" -ProtocolLoggingLevel Verbose

     

    right ?

     

    where will these logs be located at ?


    Regards, Costa Mitri


    The Default is:

    C:\Program Files\Microsoft\Exchange Server\V14\TransportRoles\Logs\ProtocolLog

     

    Check out the article I linked for more detail.


    ok actually i got this error:

    2011-05-07T13:40:55.776Z,send all to postfix,08CDDACA3105BBD2,1,,10.10.10.5:25,*,,"Failed to connect. Error Code: 10060, Error Message: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 10.10.10.5:25"

     

    where 10.10.10.5 is my internal ip for postfix

    so i did a : telnet 10.10.10.5 25

    from exchange and got this message : Connecting To 10.10.10.5...Could not open connection to the host, on port 25: Connect failed

    however i can ping 10.10.10.5 with 100% success rate

    so think the issue is from my linux box side right ?

    gutta recheck postfix and iptables configs ...


    Regards, Costa Mitri


    Sounds like 10.10.10.5 has ip restrictions in place.

     

    that's what i'm checking now ...

    i'll keep you posted :)


    Regards, Costa Mitri

    Dont forget any firewalls in between as well!
    yeah of course :)

    Regards, Costa Mitri
    Saturday, May 7, 2011 1:58 PM
  • Do the messages leave the Exchange Server? Are they bouncing?

    You can always enable protocol logging:

    http://technet.microsoft.com/en-us/library/bb124531.aspx

     

    and of course, check the built in message tracking.

     

    from shell i go like :

    Set-SendConnector "Connection from myexchanegdomain.com" -ProtocolLoggingLevel Verbose

     

    right ?

     

    where will these logs be located at ?


    Regards, Costa Mitri


    The Default is:

    C:\Program Files\Microsoft\Exchange Server\V14\TransportRoles\Logs\ProtocolLog

     

    Check out the article I linked for more detail.


    ok actually i got this error:

    2011-05-07T13:40:55.776Z,send all to postfix,08CDDACA3105BBD2,1,,10.10.10.5:25,*,,"Failed to connect. Error Code: 10060, Error Message: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 10.10.10.5:25"

     

    where 10.10.10.5 is my internal ip for postfix

    so i did a : telnet 10.10.10.5 25

    from exchange and got this message : Connecting To 10.10.10.5...Could not open connection to the host, on port 25: Connect failed

    however i can ping 10.10.10.5 with 100% success rate

    so think the issue is from my linux box side right ?

    gutta recheck postfix and iptables configs ...


    Regards, Costa Mitri


    Sounds like 10.10.10.5 has ip restrictions in place.

     

    that's what i'm checking now ...

    i'll keep you posted :)


    Regards, Costa Mitri

    Dont forget any firewalls in between as well!
    yeah of course :)

    Regards, Costa Mitri

    done

    it was an iptables issue


    Regards, Costa Mitri
    • Marked as answer by Costa Mitri Saturday, May 7, 2011 2:02 PM
    Saturday, May 7, 2011 2:02 PM