locked
several recipients email sending problems RRS feed

  • Question

  • Hi Everyone,

    I am experiencing some problems sending email. We work with Exchange 2007 installed in an W2k8 Server.

    We have a send connector to take are emails out of the organization.

    Usually it Works fine, but some times a month we need to send emails to several of our suppliers, something about 150 recipients. When we do this we usuarlly have an email reporting the message could not be sent to any of the recipients, all of them appear in the list.  As long as we know, this is not true, very most of them recieve the email, and only some of them do not.

    Does anyone know why are we not receiveing the right information?

    Is it something that could be configured?

    When these emails are sent, there are only one smtp communication with the outter server that relays these emails, is it posible to configure Exchange to communicate once for each of the recipients, so that we could trust email notifications about sending errors?

    Thank you very much.

    David.

    Tuesday, October 29, 2013 9:55 AM

Answers

  • Hi

    Do you have any restrictions on the number of emails that can be sent by this person?

    You can check globally

    [PS] C:\Windows\System32>Get-TransportConfig | fl

    You can check on Receive Connector

    [PS] C:\Windows\System32>Get-ReceiveConnector -Identity "Name" | fl *MaxRecipient*
    MaxRecipientsPerMessage : 20

    You can check on mailbox level

    [PS] C:\Windows\System32>Get-Mailbox -Identity mroot | fl RecipientLimits

    For Ref: http://social.technet.microsoft.com/Forums/en-US/13799663-163c-4928-a4a9-02fa2a19b99e/recipients-limit-in-exchange-2007

    Tuesday, October 29, 2013 12:16 PM
  • Find the outgoing message in the SMTP protocol logs. Do you see any status codes returned that are 4xx or 5xx for any of the SMTP commands your server sends?

    If the answer is "yes" then it's the receiving MTA that's rejecting the command and you'll have to take up the problem with the administrator(s) at that site.

    If the answer is "no" then check the headers in the NDR. Do you use your ISP as a SMTP relay? Is that server the sender of the NDR? If it is, does the NDR identify the server that rejected the recipients?


    --- Rich Matheisen MCSE&I, Exchange MVP

    Wednesday, October 30, 2013 1:29 AM
  • Unfortunately, your SMTP log file isn't recording sufficient details to make it useful in this situation. Modify the logging parameters to include ALL the properties available instead of just the default set.

    The first "452 4.5.3 Too many recipients" tells me that 194.30.0.6 (is that your ISP?) has a restriction on the number of recipients per message. Do you have a business-class or residential (consumer) class account with the ISP? There shouldn't be any limit on a business-class account.

    The rest of the errors are curious. The "503 5.5.1 Error: need MAIL command" error should have stopped Exchange from sending any further SMTP commands, yet there are more being sent. Is there some software installed between (or on) the Exchange server that's acting as a SMTP proxy or relay?


    --- Rich Matheisen MCSE&I, Exchange MVP

    Thursday, October 31, 2013 9:49 PM

All replies

  • Hi

    Do you have any restrictions on the number of emails that can be sent by this person?

    You can check globally

    [PS] C:\Windows\System32>Get-TransportConfig | fl

    You can check on Receive Connector

    [PS] C:\Windows\System32>Get-ReceiveConnector -Identity "Name" | fl *MaxRecipient*
    MaxRecipientsPerMessage : 20

    You can check on mailbox level

    [PS] C:\Windows\System32>Get-Mailbox -Identity mroot | fl RecipientLimits

    For Ref: http://social.technet.microsoft.com/Forums/en-US/13799663-163c-4928-a4a9-02fa2a19b99e/recipients-limit-in-exchange-2007

    Tuesday, October 29, 2013 12:16 PM
  • Hello,

    thank you very much for your answer,

    I have checked it all and there are no MaxRecipients Limit in Mailboxes. The limit for the receive connector is 200 (below what I am trying to send) and the result for the first instruction was:

    ClearCategories                  : True
    ConvertDisclaimerWrapperToEml    : False
    DSNConversionMode                : UseExchangeDSNs
    GenerateCopyOfDSNFor             : {5.4.8, 5.4.6, 5.4.4, 5.2.4, 5.2.0, 5.1.4}
    InternalSMTPServers              : {}
    JournalingReportNdrTo            : <>
    LegacyJournalingMigrationEnabled : False
    MaxDumpsterSizePerStorageGroup   : 18MB
    MaxDumpsterTime                  : 7.00:00:00
    MaxReceiveSize                   : 20MB
    MaxRecipientEnvelopeLimit        : 250
    MaxSendSize                      : 20MB
    TLSReceiveDomainSecureList       : {}
    TLSSendDomainSecureList          : {}
    VerifySecureSubmitEnabled        : False
    VoicemailJournalingEnabled       : True
    HeaderPromotionModeSetting       : NoCreate
    WritingBrandingInDSNEnabled      : True
    Xexch50Enabled                   : True

    Do you see any wrong ítem? I think configurations are all as they were default.

    The point might be in the information our supplier for the smtp-relay is sending us. Or could be in the send-connector?

    Thank you.

    David

    Tuesday, October 29, 2013 4:26 PM
  • Find the outgoing message in the SMTP protocol logs. Do you see any status codes returned that are 4xx or 5xx for any of the SMTP commands your server sends?

    If the answer is "yes" then it's the receiving MTA that's rejecting the command and you'll have to take up the problem with the administrator(s) at that site.

    If the answer is "no" then check the headers in the NDR. Do you use your ISP as a SMTP relay? Is that server the sender of the NDR? If it is, does the NDR identify the server that rejected the recipients?


    --- Rich Matheisen MCSE&I, Exchange MVP

    Wednesday, October 30, 2013 1:29 AM
  • Hi,

    Thank you very much for your answer,

    we use an ISP as a SMTP relay.

    I have checked in the email and I have plenty of lines like this:

    user@domain.es
    smtp-out4a.ISPdomain.es #503 5.5.1 Error: need RCPT command ##

    So I have contact our ISP and they are checking it. They would call me back son I hope.

    I had outgoing SMTP logs working and there is a line in which I have this, after many lines ending in 2.1.5 Ok; :

    2013-10-31T10:47:16.085Z,sarenet_correo,08D097628B2492F4,239,10.0.1.33:11552,194.30.0.6:25,<,452 4.5.3 Too many recipients,

    2013-10-31T10:47:16.085Z,sarenet_correo,08D097628B2492F4,240,10.0.1.33:11552,194.30.0.6:25,<,503 5.5.1 Error: need MAIL command,

    2013-10-31T10:47:16.085Z,sarenet_correo,08D097628B2492F4,241,10.0.1.33:11552,194.30.0.6:25,<,503 5.5.1 Error: need MAIL command,

    2013-10-31T10:47:16.085Z,sarenet_correo,08D097628B2492F4,242,10.0.1.33:11552,194.30.0.6:25,<,503 5.5.1 Error: need MAIL command,

    2013-10-31T10:47:16.085Z,sarenet_correo,08D097628B2492F4,243,10.0.1.33:11552,194.30.0.6:25,<,503 5.5.1 Error: need MAIL command,

    2013-10-31T10:47:16.085Z,sarenet_correo,08D097628B2492F4,244,10.0.1.33:11552,194.30.0.6:25,<,503 5.5.1 Error: need MAIL command,

    2013-10-31T10:47:16.085Z,sarenet_correo,08D097628B2492F4,245,10.0.1.33:11552,194.30.0.6:25,<,503 5.5.1 Error: need MAIL command,

    2013-10-31T10:47:16.085Z,sarenet_correo,08D097628B2492F4,246,10.0.1.33:11552,194.30.0.6:25,<,503 5.5.1 Error: need MAIL command,

    2013-10-31T10:47:16.085Z,sarenet_correo,08D097628B2492F4,247,10.0.1.33:11552,194.30.0.6:25,<,503 5.5.1 Error: need MAIL command,

    2013-10-31T10:47:16.085Z,sarenet_correo,08D097628B2492F4,248,10.0.1.33:11552,194.30.0.6:25,<,503 5.5.1 Error: need MAIL command,

    2013-10-31T10:47:16.085Z,sarenet_correo,08D097628B2492F4,249,10.0.1.33:11552,194.30.0.6:25,>,DATA,

    2013-10-31T10:47:16.101Z,sarenet_correo,08D097628B2492F4,250,10.0.1.33:11552,194.30.0.6:25,<,503 5.5.1 Error: need RCPT command,

    2013-10-31T10:47:16.132Z,sarenet_correo,08D097628B2492F4,251,10.0.1.33:11552,194.30.0.6:25,>,RSET,

    2013-10-31T10:47:16.132Z,sarenet_correo,08D097628B2492F4,252,10.0.1.33:11552,194.30.0.6:25,*,163310,sending message

    This is because a problem in our Exchange servers?

    Thank you very much.

    Best regards.

    David.

    Thursday, October 31, 2013 11:20 AM
  • Hello again,

    I have had an answer from our ISP and they say they are not recieving a correct RCPT TO command

    Is it something that have to do with the logs I have post before?

    Thank you very much.

    Best regards.

    David.

    Thursday, October 31, 2013 12:59 PM
  • Unfortunately, your SMTP log file isn't recording sufficient details to make it useful in this situation. Modify the logging parameters to include ALL the properties available instead of just the default set.

    The first "452 4.5.3 Too many recipients" tells me that 194.30.0.6 (is that your ISP?) has a restriction on the number of recipients per message. Do you have a business-class or residential (consumer) class account with the ISP? There shouldn't be any limit on a business-class account.

    The rest of the errors are curious. The "503 5.5.1 Error: need MAIL command" error should have stopped Exchange from sending any further SMTP commands, yet there are more being sent. Is there some software installed between (or on) the Exchange server that's acting as a SMTP proxy or relay?


    --- Rich Matheisen MCSE&I, Exchange MVP

    Thursday, October 31, 2013 9:49 PM
  • Hi Rich,

    Thank you very much for your answers again.

    I have been talking to our ISP Technicians, and we found out there is something between our server and theirs one, which make it fail.

    We test this throught another internet connection and it has worked fine.

    Now I have to look at our firewall and routers to find out what happened, but now we are sure it is not a servers problem.

    Thank you very much.

    Best Regards.

    David

    Wednesday, November 6, 2013 11:26 AM
  • Is 194.30.0.6 your ISP? If it isn't then that's where the problem lies.

    --- Rich Matheisen MCSE&I, Exchange MVP

    Wednesday, November 6, 2013 10:28 PM
  • Hi Rich

    194.30.0.6 is our ISP.

    We are now connecting to the same server 194.30.0.6, but using a different Gateway.

    Thank you!

    David

    Thursday, November 7, 2013 1:17 PM
  • So you have a SMTP proxy between the old gateway and the ISP (or the old gateway was a SMTP proxy!).

    Check the firewall that that (or through which) the gateway connects to the Internet and see if it's acting as a SMTP proxy. If it is, either configure it to stop acting as a SMTP proxy or to apply the limits you want to the SMTP traffic passing through it.


    --- Rich Matheisen MCSE&I, Exchange MVP

    Thursday, November 7, 2013 10:31 PM
  • Hi,

    Well, I don't think there is any SMTP Gateway. our servers, as long as I know connects directly to our ISP (194.30.0.6) but in between their and our server there is only a firewall and a router.

    Now I have it working through the other internet connection.

    Thnak you.

    DAvid

    Friday, November 8, 2013 9:03 AM