locked
Problem receiving big attachments like 10MB or More RRS feed

  • Question

  • OK - IP Address resolves to mail.domain1.com, mail.domain2.com
     Warning - Reverse DNS does not match SMTP Banner
     0 seconds - Good on Connection time
    Not an open relay.
     6.302 seconds - Warning on Transaction time

    Any Suggestions?

    Thanks.

    Wednesday, January 25, 2012 8:54 AM

Answers

  • Depending on whether your run an Edge Transport server or not:

    • Any server with the Hub Transport role:
      1. Server configuration -> Hub Transport -> Receive Connectors
      2. Organisation configuration -> Hub Transport -> Send Connectors
    • On any Edge Transport server:
      1. Edge Transport -> Receive Connectors tab
      2. Edge Transport -> Send Connectors
    • From the EMC (on both server role types mentioned above):
      1. Use Get-TransportConfig and Set-TransportConfig -MaxSendSize <value> -MaxReceiveSize <value>

    Are you getting any NDRs? If so, they might already be telling you where the holdup is occurring.

    If you want to find out the status of a sent message, you can run the following from the EMC:

    Get-MessageTrackingLog -Sender sender@domain.com -Start "mm/dd/yyyy hh:mm:ss"

    You should find you have at least two Event Id types no matter the server type: RECEIVE and SEND. If the recipient is internal, then you should also see a DELIVER.

    If you want to get more information and narrow it down to successful deliveries, then you can slightly modify the above and use:

    Get-MessageTrackingLog -Sender sender@domain.com -Start "mm/dd/yyyy hh:mm:ss" -EventId SEND | fl Timestamp,Sender,MessageSubject,RecipientStatus

    Keep in mind that both of these commands are all one line. Be careful of word wrapping in these forums.

    Cheers,
    Lain

    Thursday, January 26, 2012 12:45 AM

All replies

  • To be honest, I'm not really seeing anything based on that limitation that relates to not accepting large messages.

    Have you checked your Receive connector(s) to see if the default of 10MB is being enforced as the limit?

    You can find them here on a typical CAS host:

    Server Configuration -> Hub Transport

    Or under here on an Edge Transport:

    Edge Transport -> Receive Connectors tab

    What you're looking for is the "Maximum message size" setting.

    Cheers,
    Lain

    Wednesday, January 25, 2012 9:19 AM
  • Increased but still the same problem. Is there anything we can use to test where it is being blocked?

    Thanks.

    Wednesday, January 25, 2012 9:17 PM
  • Depending on whether your run an Edge Transport server or not:

    • Any server with the Hub Transport role:
      1. Server configuration -> Hub Transport -> Receive Connectors
      2. Organisation configuration -> Hub Transport -> Send Connectors
    • On any Edge Transport server:
      1. Edge Transport -> Receive Connectors tab
      2. Edge Transport -> Send Connectors
    • From the EMC (on both server role types mentioned above):
      1. Use Get-TransportConfig and Set-TransportConfig -MaxSendSize <value> -MaxReceiveSize <value>

    Are you getting any NDRs? If so, they might already be telling you where the holdup is occurring.

    If you want to find out the status of a sent message, you can run the following from the EMC:

    Get-MessageTrackingLog -Sender sender@domain.com -Start "mm/dd/yyyy hh:mm:ss"

    You should find you have at least two Event Id types no matter the server type: RECEIVE and SEND. If the recipient is internal, then you should also see a DELIVER.

    If you want to get more information and narrow it down to successful deliveries, then you can slightly modify the above and use:

    Get-MessageTrackingLog -Sender sender@domain.com -Start "mm/dd/yyyy hh:mm:ss" -EventId SEND | fl Timestamp,Sender,MessageSubject,RecipientStatus

    Keep in mind that both of these commands are all one line. Be careful of word wrapping in these forums.

    Cheers,
    Lain

    Thursday, January 26, 2012 12:45 AM
  • Hi create_share

    Any update?

    I think it is the problem on FQDN on Receive Connector

    Maybe you can change Internet FQDN for the Exchange Domain

    Cheers

    Zi Feng

    Friday, January 27, 2012 3:07 AM