none
內部兩台Mail Server互寄會Delay RRS feed

  • 問題

  • Dear all...

    繼上個問題Exchange無法成功安裝的問題解決後,目前應該正常,不過有幾個問題想再請教一下各位 :

    環境 : Win2000 Server-SP4 ,Exchange 2003-SP2。

    主機 : PDC(原是Master, 重灌後為newmaster),mailserver1, mailserver2, website

    1.在同一個網域下由1寄到2會Delay耶,通常都在半小時以上才會寄到,(因為所有的信箱皆在2,而有些程式會由website這台經由1寄出信件,客戶都收到了,但內部同仁卻還沒收到,原來都還Q在1還沒傳到2,這問題該如何解決呢?)

     

    2.有些信在寄出時會出現5.5.0的退信訊息,有設過connection數,time-out時間,使用HELO取代EHLO都試過還是會發生,也請對方幫忙檢查,對方的記錄是:503 No valid recipients specified,至tracking center去查的確是NDR甚至有些沒有NDR,而Event ID只到1020下面就沒了,去比對SMTP的log發現在同一個時間點website寄了幾封信,而卻只有一個HELO,接著幾個MAIL、RCPT,但沒傳出去的卻沒有DATA、QUIT(我想正常來說應該每封信會有HELO-MAIL-RCPT-DATA-QUIT),請問這是因為同一時間點照理應該一封信一個HELO而卻只有一個HELO所造成的嗎?那該如何解決或有其他方法嗎?

     

    3.舊的Master那台目前已照Jammy羅sir說的重format另以新的newmaster裝好加入,但在AUDC內的connect to Domain Controller卻還得到舊的master.xxx.com,這是正常的嗎?或者可以從哪刪掉呢?

     

    4.在新的這台newmaster的事件顯示器內出現這樣的錯誤訊息,這是啥原因呢?

    Event Type: Warning
    Event Source: LicenseService
    Event Category: None
    Event ID: 213
    Date:  11/20/2006
    Time:  3:17:17 PM
    User:  N/A
    Computer: NEWMASTER
    Description:
    Replication of license information failed because the License Logging Service on server master.xxx.com could not be contacted.

     

    以上幾各問題請教一下各位MVP與其他高手,希望能解點一下迷津...謝謝!!

    2006年11月20日 上午 07:58

解答

  • 請確認你有在AD站台及服務中將舊的物件全部刪除

    請確認你有在AD使用者及電腦中的Controller中將舊的物件刪除

    刪除完畢後請確認你的DC GC間有做複寫同步且成功

    如果信件的目的地都是同一個Domain Name,那麼HLO的指令不會是每封都做一次

    也就是說同一封信件寄給aaa.com.tw中的10個不同收件者,實際上只會傳送一封.

    請附上5.5.0完整的NDR內容.

    請提供信件由Mail1寄至Mail2時是Q在那一個Q?應該會有NDR吧

    請確認你的防毒設定是OK的,這通常百分90都是防毒設定錯誤造成的

    http://support.microsoft.com/kb/823166/en-us

    http://support.microsoft.com/kb/245822/en-us 

    最後請節制版面,不要將所有的SMTP Diag log內容都貼上來,那樣太冗長不會有人想要看的

    這又不是在考聯考....

     -Emperor- 寫信:

    Dear all...

    繼上個問題Exchange無法成功安裝的問題解決後,目前應該正常,不過有幾個問題想再請教一下各位 :

    環境 : Win2000 Server-SP4 ,Exchange 2003-SP2。

    主機 : PDC(原是Master, 重灌後為newmaster),mailserver1, mailserver2, website

    1.在同一個網域下由1寄到2會Delay耶,通常都在半小時以上才會寄到,(因為所有的信箱皆在2,而有些程式會由website這台經由1寄出信件,客戶都收到了,但內部同仁卻還沒收到,原來都還Q在1還沒傳到2,這問題該如何解決呢?)

     

    2.有些信在寄出時會出現5.5.0的退信訊息,有設過connection數,time-out時間,使用HELO取代EHLO都試過還是會發生,也請對方幫忙檢查,對方的記錄是:503 No valid recipients specified,至tracking center去查的確是NDR甚至有些沒有NDR,而Event ID只到1020下面就沒了,去比對SMTP的log發現在同一個時間點website寄了幾封信,而卻只有一個HELO,接著幾個MAIL、RCPT,但沒傳出去的卻沒有DATA、QUIT(我想正常來說應該每封信會有HELO-MAIL-RCPT-DATA-QUIT),請問這是因為同一時間點照理應該一封信一個HELO而卻只有一個HELO所造成的嗎?那該如何解決或有其他方法嗎?

     

    3.舊的Master那台目前已照Jammy羅sir說的重format另以新的newmaster裝好加入,但在AUDC內的connect to Domain Controller卻還得到舊的master.xxx.com,這是正常的嗎?或者可以從哪刪掉呢?

     

    4.在新的這台newmaster的事件顯示器內出現這樣的錯誤訊息,這是啥原因呢?

    Event Type: Warning
    Event Source: LicenseService
    Event Category: None
    Event ID: 213
    Date:  11/20/2006
    Time:  3:17:17 PM
    User:  N/A
    Computer: NEWMASTER
    Description:
    Replication of license information failed because the License Logging Service on server master.xxx.com could not be contacted.

     

    以上幾各問題請教一下各位MVP與其他高手,希望能解點一下迷津...謝謝!!

    2006年11月21日 上午 05:54

所有回覆

  • 問題 3 及 4:

    因為「master」的記錄還存在於 AD 資料庫中,故會產生 3 與 4 的狀況,請使用 ntdsutil 將 master 刪除:http://support.microsoft.com/kb/216498

    問題 1:

    從 AD 中刪除 master 後,問題 1 的狀況可能會解決,因為整體來看,應是 master 的問題所致;請看看 mailserver1 及 mailserver2 在 Exchange 系統管理員內開啟 mailserver1 及 mailserver2 的內容視窗,檢視「目錄存取」頁面內顯示的網域控制站資料是否正確。

    問題 2:

    請用 SMTPDiag.exe(http://www.microsoft.com/downloads/details.aspx?displaylang=zh-tw&FamilyID=bc1881c7-925d-4a29-bd42-71e8563c80a9) 在寄信出去的 Exchange Server 上執行,檢視寄信的狀況;若執行後仍抓不出答案,方便的話請將結果 PO 出來讓大家參詳。

    2006年11月20日 上午 08:32
  • 首先謝謝您的回應 ,

    問題 3 及 4:

    關於您回答3與4的問題,我已有照kb216498去動作,使用ntdstuil時已看不到舊的主機(master),目前只有newmaster、mailserver1、mailserver2,而在DNS內也檢查過了,再使用ADSIEdit也看不到master了,亦只有上述幾台server,但有一樣是進入ADUC時還看得到master這台電腦,不過卻無法做刪除的動作,請問該如何解決呢?

    問題 1:

    至該二台mailserver檢查的結果為,在mailserver1下是顯示著

    Domain Controller:mailserver1....TYPE:config ...Port :389

    Domain Controller:mailserver1....TYPE:DC ...Port :389

    Domain Controller:newmaster....TYPE:GC ...Port :3268

    相對著在mailserver2下即為

    Domain Controller:mailserver2....TYPE:config ...Port :389

    Domain Controller:mailserver2....TYPE:DC ...Port :389

    Domain Controller:newmaster....TYPE:GC ...Port :3268

    我想這應該沒有異狀吧...

    問題 2:

    我在二台mailserver都做了測試,得到以下結果,而其中我發覺有二個地方怪怪的,

    250-mailserver1.xxx.com Hello [126.1.2.252]

    250-mailserver2.xxx.com Hello [126.1.1.251]

    不曉得這正不正確,不過仍請各位高手幫忙一下謝謝!!

    ----------------------------------------------------------------------------------

    於 mailserver1下

    D:\>smtpdiag "test@xxx.com" "test@xxx.com" /v

    Searching for Exchange external DNS settings.
    Computer name is MAILSERVER1.
    VSI 1 has the following external DNS servers:
    126.1.1.96,168.95.1.1

    Checking SOA for xxx.com.
    Checking external DNS servers.

    Checking TCP/UDP SOA serial number using DNS server

    [126.1.1.96].
    TCP test succeeded.
    UDP test failed.
    Serial number: 411

    Checking TCP/UDP SOA serial number using DNS server

    [168.95.1.1].
    TCP test succeeded.
    UDP test failed.
    Serial number: 278
    Checking internal DNS servers.

    Checking TCP/UDP SOA serial number using DNS server

    [126.1.1.96].
    TCP test succeeded.
    UDP test failed.
    Serial number: 411
    Serial numbers do not match: 411  278
    SOA serial number match: Failed with one or more failures.

    Checking local domain records.
    Starting TCP and UDP DNS queries for the local domain. This

    test will try to
    validate that DNS is set up correctly for inbound mail.

    This test can fail for
    3 reasons.
        1) Local domain is not set up in DNS. Inbound mail

    cannot be routed to
    local mailboxes.
        2) Firewall blocks TCP/UDP DNS queries. This will not

    affect inbound mail,
    but will affect outbound mail.
        3) Internal DNS is unaware of external DNS settings.

    This is a valid
    configuration for certain topologies.
    Checking MX records using TCP: xxx.com.
      MX:    mailserver2.xxx.com (10)
      MX:    mailserver1.xxx.com (20)
      A:     mailserver2.xxx.com [126.1.2.252]
      A:     mailserver1.xxx.com [126.1.1.251]
    Checking MX records using UDP: xxx.com.
      MX:    mailserver2.xxx.com (10)
      MX:    mailserver1.xxx.com (20)
      A:     mailserver2.xxx.com [126.1.2.252]
      A:     mailserver1.xxx.com [126.1.1.251]
    Both TCP and UDP queries succeeded. Local DNS test passed.

    Checking remote domain records.
    Starting TCP and UDP DNS queries for the remote domain.

    This test will try to
    validate that DNS is set up correctly for outbound mail.

    This test can fail for
    3 reasons.
        1) Firewall blocks TCP/UDP queries which will block

    outbound mail. Windows
    2000/NT Server requires TCP DNS queries. Windows Server

    2003 will use UDP
    queries first, then fall back to TCP queries.
        2) Internal DNS does not know how to query external

    domains. You must
    either use an external DNS server or configure DNS server

    to query external
    domains.
        3) Remote domain does not exist. Failure is expected.
    Checking MX records using TCP: xxx.com.
      MX:    mailserver2.xxx.com (10)
      MX:    mailserver1.xxx.com (20)
      A:     mailserver2.xxx.com [126.1.2.252]
      A:     mailserver1.xxx.com [126.1.1.251]
    Checking MX records using UDP: xxx.com.
      MX:    mailserver2.xxx.com (10)
      MX:    mailserver1.xxx.com (20)
    Both TCP and UDP queries succeeded. Remote DNS test passed.

    Checking MX servers listed for test@xxx.com.
    Connecting to mailserver2.xxx.com [126.1.2.252] on port 25.
    Received:
    220 mailserver2.xxx.com Microsoft ESMTP MAIL Service,

    Version: 5.0.2195.6713 re
    ady at  Mon, 20 Nov 2006 18:59:29 +0800


    Sent:
    ehlo xxx.com

    Received:
    250-mailserver2.xxx.com Hello [126.1.1.251]
    250-TURN
    250-ATRN
    250-SIZE 10485760
    250-ETRN
    250-PIPELINING
    250-DSN
    250-ENHANCEDSTATUSCODES
    250-8bitmime
    250-BINARYMIME
    250-VRFY
    250-X-EXPS GSSAPI NTLM LOGIN
    250-X-EXPS=LOGIN
    250-AUTH GSSAPI NTLM LOGIN
    250-AUTH=LOGIN
    250-X-LINK2STATE
    250-XEXCH50
    250 OK


    Sent:
    mail from: <test@xxx.com>

    Received:
    250 2.1.0 test@xxx.com....Sender OK

    Sent:
    rcpt to: <test@xxx.com>

    Received:
    250 2.1.5 test@xxx.com

    Sent:
    quit

    Received:
    221 2.0.0 mailserver2.xxx.com Service closing transmission

    channel

    Successfully connected to mailserver2.xxx.com.
    Connecting to mailserver1.xxx.com [126.1.1.251] on port 25.
    Received:
    220 mailserver1.xxx.com Microsoft ESMTP MAIL Service,

    Version: 5.0.2195.6713 r
    eady at  Mon, 20 Nov 2006 18:59:29 +0800


    Sent:
    ehlo xxx.com

    Received:
    250-mailserver1.xxx.com Hello [126.1.1.251]
    250-TURN
    250-ATRN
    250-SIZE 10485760
    250-ETRN
    250-PIPELINING
    250-DSN
    250-ENHANCEDSTATUSCODES
    250-8bitmime
    250-BINARYMIME
    250-CHUNKING
    250-VRFY
    250-X-EXPS GSSAPI NTLM LOGIN
    250-X-EXPS=LOGIN
    250-AUTH GSSAPI NTLM LOGIN
    250-AUTH=LOGIN
    250-X-LINK2STATE
    250-XEXCH50
    250 OK


    Sent:
    mail from: <test@xxx.com>

    Received:
    250 2.1.0 test@xxx.com....Sender OK

    Sent:
    rcpt to: <test@xxx.com>

    Received:
    250 2.1.5 test@xxx.com

    Sent:
    quit

    Received:
    221 2.0.0 mailserver1.xxx.com Service closing transmission

    channel

    Successfully connected to mailserver1.xxx.com.

    ---------------------------------------------------------------------------------------
    於 mailserver2下

    D:\>smtpdiag "test@xxx.com" "test@xxx.com" /v

    Searching for Exchange external DNS settings.
    Computer name is MAILSERVER2.
    VSI 1 has the following external DNS servers:
    126.1.1.96,168.95.1.1

    Checking SOA for xxx.com.
    Checking external DNS servers.

    Checking TCP/UDP SOA serial number using DNS server

    [126.1.1.96].
    TCP test succeeded.
    UDP test failed.
    Serial number: 411

    Checking TCP/UDP SOA serial number using DNS server

    [168.95.1.1].
    TCP test succeeded.
    UDP test failed.
    Serial number: 278
    Checking internal DNS servers.

    Checking TCP/UDP SOA serial number using DNS server

    [126.1.1.96].
    TCP test succeeded.
    UDP test failed.
    Serial number: 411
    Serial numbers do not match: 411  278
    SOA serial number match: Failed with one or more failures.

    Checking local domain records.
    Starting TCP and UDP DNS queries for the local domain. This

    test will try to
    validate that DNS is set up correctly for inbound mail.

    This test can fail for
    3 reasons.
        1) Local domain is not set up in DNS. Inbound mail

    cannot be routed to
    local mailboxes.
        2) Firewall blocks TCP/UDP DNS queries. This will not

    affect inbound mail,
    but will affect outbound mail.
        3) Internal DNS is unaware of external DNS settings.

    This is a valid
    configuration for certain topologies.
    Checking MX records using TCP: xxx.com.
      MX:    mailserver2.xxx.com (10)
      MX:    mailserver1.xxx.com (20)
      A:     mailserver2.xxx.com [126.1.2.252]
      A:     mailserver1.xxx.com [126.1.1.251]
    Checking MX records using UDP: xxx.com.
      MX:    mailserver2.xxx.com (10)
      MX:    mailserver1.xxx.com (20)
      A:     mailserver2.xxx.com [126.1.2.252]
      A:     mailserver1.xxx.com [126.1.1.251]
    Both TCP and UDP queries succeeded. Local DNS test passed.

    Checking remote domain records.
    Starting TCP and UDP DNS queries for the remote domain.

    This test will try to
    validate that DNS is set up correctly for outbound mail.

    This test can fail for
    3 reasons.
        1) Firewall blocks TCP/UDP queries which will block

    outbound mail. Windows
    2000/NT Server requires TCP DNS queries. Windows Server

    2003 will use UDP
    queries first, then fall back to TCP queries.
        2) Internal DNS does not know how to query external

    domains. You must
    either use an external DNS server or configure DNS server

    to query external
    domains.
        3) Remote domain does not exist. Failure is expected.
    Checking MX records using TCP: xxx.com.
      MX:    mailserver2.xxx.com (10)
      MX:    mailserver1.xxx.com (20)
      A:     mailserver2.xxx.com [126.1.2.252]
      A:     mailserver1.xxx.com [126.1.1.251]
    Checking MX records using UDP: xxx.com.
      MX:    mailserver2.xxx.com (10)
      MX:    mailserver1.xxx.com (20)
    Both TCP and UDP queries succeeded. Remote DNS test passed.

    Checking MX servers listed for test@xxx.com.
    Connecting to mailserver2.xxx.com [126.1.2.252] on port 25.
    Received:
    220 mailserver2.xxx.com Microsoft ESMTP MAIL Service,

    Version: 5.0.2195.6713 re
    ady at  Mon, 20 Nov 2006 19:03:14 +0800


    Sent:
    ehlo xxx.com

    Received:
    250-mailserver2.xxx.com Hello [126.1.2.252]
    250-TURN
    250-ATRN
    250-SIZE 10485760
    250-ETRN
    250-PIPELINING
    250-DSN
    250-ENHANCEDSTATUSCODES
    250-8bitmime
    250-BINARYMIME
    250-CHUNKING
    250-VRFY
    250-X-EXPS GSSAPI NTLM LOGIN
    250-X-EXPS=LOGIN
    250-AUTH GSSAPI NTLM LOGIN
    250-AUTH=LOGIN
    250-X-LINK2STATE
    250-XEXCH50
    250 OK


    Sent:
    mail from: <test@xxx.com>

    Received:
    250 2.1.0 test@xxx.com....Sender OK

    Sent:
    rcpt to: <test@xxx.com>

    Received:
    250 2.1.5 test@xxx.com

    Sent:
    quit

    Received:
    221 2.0.0 mailserver2.xxx.com Service closing transmission

    channel

    Successfully connected to mailserver2.xxx.com.
    Connecting to mailserver1.xxx.com [126.1.1.251] on port 25.
    Received:
    220 mailserver1.xxx.com Microsoft ESMTP MAIL Service,

    Version: 5.0.2195.6713 r
    eady at  Mon, 20 Nov 2006 19:03:14 +0800


    Sent:
    ehlo xxx.com

    Received:
    250-mailserver1.xxx.com Hello [126.1.2.252]
    250-TURN
    250-ATRN
    250-SIZE 10485760
    250-ETRN
    250-PIPELINING
    250-DSN
    250-ENHANCEDSTATUSCODES
    250-8bitmime
    250-BINARYMIME
    250-VRFY
    250-X-EXPS GSSAPI NTLM LOGIN
    250-X-EXPS=LOGIN
    250-AUTH GSSAPI NTLM LOGIN
    250-AUTH=LOGIN
    250-X-LINK2STATE
    250-XEXCH50
    250 OK


    Sent:
    mail from: <test@xxx.com>

    Received:
    250 2.1.0 test@xxx.com....Sender OK

    Sent:
    rcpt to: <test@xxx.com>

    Received:
    250 2.1.5 test@xxx.com

    Sent:
    quit

    Received:
    221 2.0.0 mailserver1.xxx.com Service closing transmission

    channel

    Successfully connected to mailserver1.xxx.com.

    煩請各位幫幫忙囉,萬分感謝!!

    2006年11月21日 上午 03:12
  • 上述為mailserver1與mailserver2之間以smtpdiag互相測試的結果,

    而以下為mailserver1與mailserver2以smtpdiag測試外面的server的結果。

    於mailserver1下
    D:\>smtpdiag "test@xxx.com" "test@ccc.com" /v

    Searching for Exchange external DNS settings.
    Computer name is MAILSERVER1.
    VSI 1 has the following external DNS servers:
    126.1.1.96,168.95.1.1

    Checking SOA for ccc.com.
    Checking external DNS servers.

    Checking TCP/UDP SOA serial number using DNS server [126.1.1.96].
    TCP test succeeded.
    UDP test failed.
    Serial number: 2085373719

    Checking TCP/UDP SOA serial number using DNS server [168.95.1.1].
    TCP test succeeded.
    UDP test failed.
    Serial number: 2085373719
    Checking internal DNS servers.

    Checking TCP/UDP SOA serial number using DNS server [126.1.1.96].
    TCP test succeeded.
    UDP test failed.
    Serial number: 2085373719
    SOA serial number match: Passed.

    Checking local domain records.
    Starting TCP and UDP DNS queries for the local domain. This test will try to
    validate that DNS is set up correctly for inbound mail. This test can fail for
    3 reasons.
        1) Local domain is not set up in DNS. Inbound mail cannot be routed to
    local mailboxes.
        2) Firewall blocks TCP/UDP DNS queries. This will not affect inbound mail,
    but will affect outbound mail.
        3) Internal DNS is unaware of external DNS settings. This is a valid
    configuration for certain topologies.
    Checking MX records using TCP: xxx.com.
    Warning: The TCP DNS query returned no results.
    Checking MX records using UDP: xxx.com.
    Warning: No MX or A records were found for the local domain. If the records are
    not configured, incoming mail can fail to be delivered to this server.

    Checking remote domain records.
    Starting TCP and UDP DNS queries for the remote domain. This test will try to
    validate that DNS is set up correctly for outbound mail. This test can fail for
    3 reasons.
        1) Firewall blocks TCP/UDP queries which will block outbound mail. Windows
    2000/NT Server requires TCP DNS queries. Windows Server 2003 will use UDP
    queries first, then fall back to TCP queries.
        2) Internal DNS does not know how to query external domains. You must
    either use an external DNS server or configure DNS server to query external
    domains.
        3) Remote domain does not exist. Failure is expected.
    Checking MX records using TCP: ccc.com.
      MX:    mailhost-in.ccc.com (10)
      MX:    mailhost-out.ccc.com (20)
      A:     mailhost-in.ccc.com [zzz.60.170.44]
      A:     mailhost-out.ccc.com [zzz.60.170.45]
    Checking MX records using UDP: ccc.com.
      MX:    mailhost-in.ccc.com (10)
      MX:    mailhost-out.ccc.com (20)
    Both TCP and UDP queries succeeded. Remote DNS test passed.

    Checking MX servers listed for test@ccc.com.
    Connecting to mailhost-in.ccc.com [zzz.60.170.44] on port 25.
    Received:
    220 ccc.com ESMTP ready

    Sent:
    ehlo xxx.com

    Received:
    250-ccc.com
    250-SIZE 83886080
    250-ETRN
    250-ENHANCEDSTATUSCODES
    250-DSN
    250-VRFY
    250-AUTH
    250 8BITMIME


    Sent:
    mail from: <test@xxx.com>

    Received:
    250 2.0.0 test@xxx.com OK

    Sent:
    rcpt to: <test@ccc.com>

    Received:
    250 2.0.0 test@ccc.com OK

    Sent:
    quit

    Received:
    221 2.0.0 ccc.com closing

    Successfully connected to mailhost-in.ccc.com.
    Connecting to mailhost-out.ccc.com [zzz.60.170.45] on port 25.
    Received:
    220 ccc.com ESMTP ready

    Sent:
    ehlo xxx.com

    Received:
    250-ccc.com
    250-SIZE 83886080
    250-ETRN
    250-ENHANCEDSTATUSCODES
    250-DSN
    250-VRFY
    250-AUTH
    250 8BITMIME


    Sent:
    mail from: <test@xxx.com>

    Received:
    250 2.0.0 test@xxx.com OK

    Sent:
    rcpt to: <test@ccc.com>

    Received:
    250 2.0.0 test@ccc.com OK

    Sent:
    quit

    Received:
    221 2.0.0 ccc.com closing

    Successfully connected to mailhost-out.ccc.com.

    -------------------------------------------------------------------------------------

    在mailserver2下
    D:\>smtpdiag "test@xxx.com" "test@yyy.net.id" /v

    Searching for Exchange external DNS settings.
    Computer name is MAILSERVER2.
    VSI 1 has the following external DNS servers:
    126.1.1.96,168.95.1.1

    Checking SOA for idola.net.id.
    Checking external DNS servers.

    Checking TCP/UDP SOA serial number using DNS server [126.1.1.96].
    TCP test succeeded.
    UDP test failed.
    Serial number: 2006112001

    Checking TCP/UDP SOA serial number using DNS server [168.95.1.1].
    TCP test succeeded.
    UDP test failed.
    Serial number: 2006112001
    Checking internal DNS servers.

    Checking TCP/UDP SOA serial number using DNS server [126.1.1.96].
    TCP test succeeded.
    UDP test failed.
    Serial number: 2006112001
    SOA serial number match: Passed.

    Checking local domain records.
    Starting TCP and UDP DNS queries for the local domain. This test will try to
    validate that DNS is set up correctly for inbound mail. This test can fail for
    3 reasons.
        1) Local domain is not set up in DNS. Inbound mail cannot be routed to
    local mailboxes.
        2) Firewall blocks TCP/UDP DNS queries. This will not affect inbound mail,
    but will affect outbound mail.
        3) Internal DNS is unaware of external DNS settings. This is a valid
    configuration for certain topologies.
    Checking MX records using TCP: xxx.com.
      MX:    mailserver2.xxx.com (10)
      MX:    mailserver1.xxx.com (20)
      A:     mailserver2.xxx.com [126.1.2.252]
      A:     mailserver1.xxx.com [126.1.1.251]
    Checking MX records using UDP: xxx.com.
      MX:    mailserver2.xxx.com (10)
      MX:    mailserver1.xxx.com (20)
      A:     mailserver2.xxx.com [126.1.2.252]
      A:     mailserver1.xxx.com [126.1.1.251]
    Both TCP and UDP queries succeeded. Local DNS test passed.

    Checking remote domain records.
    Starting TCP and UDP DNS queries for the remote domain. This test will try to
    validate that DNS is set up correctly for outbound mail. This test can fail for
    3 reasons.
        1) Firewall blocks TCP/UDP queries which will block outbound mail. Windows
    2000/NT Server requires TCP DNS queries. Windows Server 2003 will use UDP
    queries first, then fall back to TCP queries.
        2) Internal DNS does not know how to query external domains. You must
    either use an external DNS server or configure DNS server to query external
    domains.
        3) Remote domain does not exist. Failure is expected.
    Checking MX records using TCP: yyy.net.id.
      MX:    mx1-re.idola.net.id (5)
      MX:    mx2-re.idola.net.id (10)
      A:     mx1-re.idola.net.id [zzz.152.0.9]
      A:     mx2-re.idola.net.id [zzz.152.0.11]
    Checking MX records using UDP: yyy.net.id.
      MX:    mx1-re.idola.net.id (5)
      MX:    mx2-re.idola.net.id (10)
    Both TCP and UDP queries succeeded. Remote DNS test passed.

    Checking MX servers listed for test@yyy.net.id.
    Connecting to mx1-re.idola.net.id [zzz.152.0.9] on port 25.
    Received:
    220 mx1-re.idola.net.id ESMTP Postfix

    Sent:
    ehlo xxx.com

    Received:
    250-mx1-re.idola.net.id
    250-SIZE 10240000
    250-ETRN
    250 8BITMIME

    Sent:
    mail from: <testg@xxx.com>

    Received:
    250 Ok

    Sent:
    rcpt to: <test@yyy.net.id>

    Received:
    250 Ok

    Sent:
    quit

    Received:
    221 Bye

    Successfully connected to mx1-re.idola.net.id.
    Connecting to mx2-re.idola.net.id [zzz.152.0.11] on port 25.
    Received:
    220 mx2-re.idola.net.id ESMTP Postfix

    Sent:
    ehlo xxx.com

    Received:
    250-mx2-re.idola.net.id
    250-SIZE 10240000
    250-ETRN
    250 8BITMIME

    Sent:
    mail from: <test@xxx.com>

    Received:
    250 Ok

    Sent:
    rcpt to: <test@yyy.net.id>

    Received:
    250 Ok

    Sent:
    quit

    Received:
    221 Bye

    Successfully connected to mx2-re.idola.net.id.

     

    再次謝謝大家的幫忙!!

    2006年11月21日 上午 03:52
  • 請確認你有在AD站台及服務中將舊的物件全部刪除

    請確認你有在AD使用者及電腦中的Controller中將舊的物件刪除

    刪除完畢後請確認你的DC GC間有做複寫同步且成功

    如果信件的目的地都是同一個Domain Name,那麼HLO的指令不會是每封都做一次

    也就是說同一封信件寄給aaa.com.tw中的10個不同收件者,實際上只會傳送一封.

    請附上5.5.0完整的NDR內容.

    請提供信件由Mail1寄至Mail2時是Q在那一個Q?應該會有NDR吧

    請確認你的防毒設定是OK的,這通常百分90都是防毒設定錯誤造成的

    http://support.microsoft.com/kb/823166/en-us

    http://support.microsoft.com/kb/245822/en-us 

    最後請節制版面,不要將所有的SMTP Diag log內容都貼上來,那樣太冗長不會有人想要看的

    這又不是在考聯考....

     -Emperor- 寫信:

    Dear all...

    繼上個問題Exchange無法成功安裝的問題解決後,目前應該正常,不過有幾個問題想再請教一下各位 :

    環境 : Win2000 Server-SP4 ,Exchange 2003-SP2。

    主機 : PDC(原是Master, 重灌後為newmaster),mailserver1, mailserver2, website

    1.在同一個網域下由1寄到2會Delay耶,通常都在半小時以上才會寄到,(因為所有的信箱皆在2,而有些程式會由website這台經由1寄出信件,客戶都收到了,但內部同仁卻還沒收到,原來都還Q在1還沒傳到2,這問題該如何解決呢?)

     

    2.有些信在寄出時會出現5.5.0的退信訊息,有設過connection數,time-out時間,使用HELO取代EHLO都試過還是會發生,也請對方幫忙檢查,對方的記錄是:503 No valid recipients specified,至tracking center去查的確是NDR甚至有些沒有NDR,而Event ID只到1020下面就沒了,去比對SMTP的log發現在同一個時間點website寄了幾封信,而卻只有一個HELO,接著幾個MAIL、RCPT,但沒傳出去的卻沒有DATA、QUIT(我想正常來說應該每封信會有HELO-MAIL-RCPT-DATA-QUIT),請問這是因為同一時間點照理應該一封信一個HELO而卻只有一個HELO所造成的嗎?那該如何解決或有其他方法嗎?

     

    3.舊的Master那台目前已照Jammy羅sir說的重format另以新的newmaster裝好加入,但在AUDC內的connect to Domain Controller卻還得到舊的master.xxx.com,這是正常的嗎?或者可以從哪刪掉呢?

     

    4.在新的這台newmaster的事件顯示器內出現這樣的錯誤訊息,這是啥原因呢?

    Event Type: Warning
    Event Source: LicenseService
    Event Category: None
    Event ID: 213
    Date:  11/20/2006
    Time:  3:17:17 PM
    User:  N/A
    Computer: NEWMASTER
    Description:
    Replication of license information failed because the License Logging Service on server master.xxx.com could not be contacted.

     

    以上幾各問題請教一下各位MVP與其他高手,希望能解點一下迷津...謝謝!!

    2006年11月21日 上午 05:54
  • 您好,真是不好意思,給了這麼冗長的內容,造成不便深感抱歉呢...

    關於問題3、4已解決了,完全清除原有的master後,已沒有上述狀況,

    至於問題1:

    沒有NDR產生,狀況為當使用mailserver1去寄信時,此時若只寄外是正常的,但若有cc或者有包含內部人員時,這時會在mailserver1的Queue內看到mailserver2.xxx.com內有信,狀態則為retry,使用force connection,rounting engine restart同樣無法即時傳送,約莫過了30分鐘以上,信才會送到mailserver2,此時內部人員才會收到信。而奇怪的是...這情形只會出現在當IMF kb更新、smtp restart、或者重新開機後才會這樣,時間一久就正常了(通常48小時以上才會正常不會有所DELAY.),因此想請教有哪些原因會造成這樣的現象,或者能如何解決,ps..防毒軟體方面已設定排除。

    而問題2 :

    退信內容只有

    There was a SMTP communication problem with the recipient's email
    server.  Please contact your system administrator.
     <mailserver2.xxx.com #5.5.0>

    通常是發生在若客人一下子下很多單時(mailserver Q了好幾封,此時便會有1、2封會被退,而重寄就ok了),

    另一種狀況則為程式發mail時寄二封給同一個用戶,其中一封會被退,相同的只要再重寄就ok了,

    找了許久都未找到這些問題所在,因為只好再麻煩各位高手幫幫忙囉!!

     

    謝謝!!

    2006年11月22日 上午 07:45
  • 從mail1去Telnet mail2的 TCP 25 port正常嗎?

    從mail1去ping mail 2 host name及FQDN name所解析的IP正常嗎?

    Mail 1 and mail 2哪一台是Master?

    建議你啟用Mail 2 and mail1上的診斷記錄中的MSExchangeTransport下的相關Logging Level設為最高

    然後將Mail 1 and mail2上的Application evne log seize調大一點並先清空

    接著請使用者寄信測試重現您所述之問題

    然後再回到Mail 1 and mail 2上去看Application event log中所記錄的事件內容

    如此應可以清楚的找到問題所在~

     

    2006年11月22日 上午 08:34
  • 您好,謝謝您的回覆!

    1.互相telnet之下是正常的

    2.互相解析之下也是正常的

    3.mailserver2為master

    4.delay的問題因過了48小時以上目前不會delay,試著將smtp restart亦不會delay,因此我想要等到下次重開機才能提供相關訊息了

    5.以下則為將相關level調至最高下其中一個NDR的訊息

    Event Type: Warning
    Event Source: MSExchangeTransport
    Event Category: NDR
    Event ID: 3022

    Computer: MAILSERVER1
    Description:
    A non-delivery report with a status code of 5.5.0 was generated for recipient rfc822;xxx@yyy.co.uk (Message-ID  <3738228.1164193373208.JavaMail.SYSTEM@website>).  
    Cause:  This message indicates a generic protocol error (SMTP error).  For example, the remote SMTP responds to an issued EHLO with a 500 level error and the sending system will QUIT the connection and report this with NDR indicating the remote SMTP server can't handle the protocol.   
    Solution:  View the SMTP log or run a netmon trace to see why the remote SMTP server rejects the protocol request.

    6.再請教一個問題,在mail1與2的事件檢示器中都會有這個錯誤產生,但administrator這個信箱是正常的呢...

    Event Type: Error
    Event Source: MSExchangeIS Mailbox Store
    Event Category: Logons
    Event ID: 1022
    Computer: MAILSERVER1
    Description:
    Logon Failure on database "First Storage Group\Mailbox Store (MAILSERVER1)" - Windows 2000 account XXX\Administrator; mailbox /o=XXX-MailServer/ou=XXX-MailServer/cn=Configuration/cn=Connections/cn=MAILSERVER1-LME-GWISE.(另一個log這地方是NOTES)
    Error: 1010

     

    唉....看起來還蠻多問題的,我也會努力尋找解答,在此麻煩大家了~~真是不好意思,謝謝!!

    2006年11月23日 上午 02:11
  • 關於你的第5點Event ID 3022請參考下列的解決方法

    http://www.microsoft.com/technet/support/ee/transform.aspx?ProdName=Exchange&ProdVer=6.5.7596.0&EvtID=3022&EvtSrc=MSExchangeTransport&LCID=1033

    而第6項不太清楚你現有的架構.你是Notes and Exchange混合mode嗎

    2006年11月23日 上午 02:36
  • 謝謝回應...

    re :5

    可否請問一下,protolog.dll這個檔案是不是要錢呢?我們是正版的exchange standard版本,可以直接跟微軟技術處索取嗎?

    re :6

    當初安裝時是有安裝所有選項(Lotus Notes、Novell Groupwise),不過我並沒有啟動這功能,不知這會有影響嗎?

    PS : 不知exchange有沒有地方可以設定當有好幾封信正同時傳送至同一目的端時,而exchange是一次傳一封,等這一封傳完了再傳送下封的機制呢?

    再次感謝回答與幫助,謝謝!!

    2006年11月23日 上午 03:44
  • 你的問題應該就在這裡吧

    請放入Exchange光碟將Lotus Notes,Novell Groupwise等用不到的Connector移掉,問題應該就解決了!

    標準的SMTP Service都是使用佇列傳送,先到先送,一封送完再送另一封

    所以Exchange Server也是如此

    2006年11月23日 上午 08:11