I have Exchange 2010 configured to send email to UTM9, which in turn is configured to send email via Amazon AWS SES configured as a smarthost. Amazon limits the "Maximum number of recipients per message" to 50. If I want to send an email to 75 people, Exchange connects to UTM and sends something like "MAIL FROM: adam@tld.com", "RCPT TO: [list of 75 addreses]". UTM dutifully receives the message, and connects to SES and attempts the same transaction (one envelope, 75 recipients), and SES rejects this with "554 Transaction failed: Recipient count exceeds 50."
I don't see a way to force Exchange to sent at most 50 recipients in one envelope. There is a "Set-TransportConfig -MaxRecipientEnvelopeLimit", but all that does is cause Exchange to reject the email entirely (the user gets a bounce from Exchange that says "too many recipients").
UTM9 in email->SMTP->Advanced down at the bottom has a "Max rcpt/mail" parameter. Setting this to 50 doesn't seem to have any effect on /outgoing/ email (at least, not that I could detect).
Exim documentation says:
recipients_max
Type: integer
Default: 0If this option is set greater than zero, it specifies the maximum number of original recipients for any message. Additional recipients that are generated by aliasing or forwarding do not count. SMTP messages get a 452 response for all recipients over the limit; earlier recipients are delivered as normal. Non-SMTP messages with too many recipients are failed, and no deliveries are done. Note that the RFCs specify that an SMTP server should accept at least 100 RCPT commands in a single message.
Which would seem to do the same sort of thing that Exchange does -- bounce when the number of recipients is > recipients_max, rather than split it up into several envelopes.
ON THE OTHER HAND, Gnu Mailman uses one envelope per recipient (at least the way I have things configured & using postfix). This causes everything to work fine, of course.
Is there a way to configure UTM9 to split outgoing envelopes into each <= 50 recipients? Alternately, to the extent any of you know, is there a way to force Exchange to do this?
This thread was automatically locked due to age.