outbound messages per connection
in [Microsoft Exchange]
|
Prev: Exchange 2007 (outlook 2003/7) Junk-Email folder retention value by default.. does it have one? 14 days? how to change?
Next: Exchange Server 2003 - Recover of SMTP Relay Exceptions List
From: glenne on 14 Oct 2007 19:08 I'm using Exchange 2007 from a school to send email to a distribution list that includes 32 comcast addresses. The server queues this up and attempts to deliver them as one message to 32 recipients and comcast rejects the message as having too many recipients (limit 20). Is there a way to force exchange 2007 to break up the message to fewer recipients at at time?
From: Rich Matheisen [MVP] on 14 Oct 2007 20:27
glenne(a)engel.org wrote: >I'm using Exchange 2007 from a school to send email to a distribution >list that includes 32 comcast addresses. The server queues this up >and attempts to deliver them as one message to 32 recipients and >comcast rejects the message as having too many recipients (limit 20). >Is there a way to force exchange 2007 to break up the message to fewer >recipients at at time? Comcast rejects the entire message? Or just the recipients in excess of 20? The way this usually works is that the receiving server sets the limits, not the sender. When the limit is reached the remaining RCPT TO commands are rejected (usually with a retryable status code). The sending server then initiates another MAIL FROM with the remaining recipients. That's repeated until all the recipients are either successfully sent or permanently rejected. That 20 is way too low. But convincing Comcast that they're wrong is another matter. This is a quote from RFC2821: recipients buffer The minimum total number of recipients that must be buffered is 100 recipients. Rejection of messages (for excessive recipients) with fewer than 100 RCPT commands is a violation of this specification. The general principle that relaying SMTP servers MUST NOT, and delivery SMTP servers SHOULD NOT, perform validation tests on message headers suggests that rejecting a message based on the total number of recipients shown in header fields is to be discouraged. A server which imposes a limit on the number of recipients MUST behave in an orderly fashion, such as to reject additional addresses over its limit rather than silently discarding addresses previously accepted. A client that needs to deliver a message containing over 100 RCPT commands SHOULD be prepared to transmit in 100-recipient "chunks" if the server declines to accept more than 100 recipients in a single message. If you want to try something, put the recipients into the "Bcc:" header. If Comcast isn't counting the recipinents in the "To:" and "Cc:" headers (which they certainly shouldn't be doing) then the message should be delivered to all the recipients although it may take several MAIL FROM commands to get that to happen. -- Rich Matheisen MCSE+I, Exchange MVP MS Exchange FAQ at http://www.swinc.com/resource/exch_faq.htm Don't send mail to this address mailto:h.pott(a)getronics.com Or to these, either: mailto:h.pott(a)pinkroccade.com mailto:melvin.mcphucknuckle(a)getronics.com mailto:melvin.mcphucknuckle(a)pinkroccade.com |