jhawk3
asked on
452: Too Many Recipients
I have just upgraded to Exchange 2003 from 5.5. Every things seems alright except when my users try to send out emails with numerous recipients. They recieve a "452 too many recipients" error. I have checked the global setting in Exchange and it is set to unlimited. Is there another setting that I need to adjust?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ignore the <<something less than 120>>
ASKER
No, The box is unchecked. I assume that this means that it is unlimited. Am I correct? Also, The link that you gave is dead. Please repost. Thanks.
ASKER
This article seems like it applies to if I want to put a limit on the amount of recipiets.
RFC 2821 section 4.5.3.1 mandates the minimum number of recipients any SMTP
implementation supports to be 100. This is for inbound.
Exchange 2003 will send outbound as many recipients as the remote server
supports. So essentially, as many recipients until the remote server returns
RFC 2821 452 (Too many recipients) or RFC 821 552 (Incorrect Too many
recipients) also.
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.
implementation supports to be 100. This is for inbound.
Exchange 2003 will send outbound as many recipients as the remote server
supports. So essentially, as many recipients until the remote server returns
RFC 2821 452 (Too many recipients) or RFC 821 552 (Incorrect Too many
recipients) also.
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.
From a newsgroup post:
outbound, there is no way to configure Exchange 2000/2003 to do this.
This was possible in Exchange 5.5. The behavior with Exchange 2003 is to
send as many recipients until a 452 or 552 error. You may be able to
workaround this to suit what you want by installing an IIS SMTP relay server
acting as a smarthost that has a limit of 24 recipients inbound. If Exchange
now sends 900 messages, it will have to split them up in chunks of 24
because the IIS SMTP relay will reject after the 25th recipient.
outbound, there is no way to configure Exchange 2000/2003 to do this.
This was possible in Exchange 5.5. The behavior with Exchange 2003 is to
send as many recipients until a 452 or 552 error. You may be able to
workaround this to suit what you want by installing an IIS SMTP relay server
acting as a smarthost that has a limit of 24 recipients inbound. If Exchange
now sends 900 messages, it will have to split them up in chunks of 24
because the IIS SMTP relay will reject after the 25th recipient.
sorry all i can find is this http://support.microsoft.com/default.aspx?scid=kb;en-us;315119
I believe there is a limit on number of recipients by default, not sure what it is off hand, on the exchange server do you receive any error numbers? other than the 4.5.2 in event viewer?
I believe there is a limit on number of recipients by default, not sure what it is off hand, on the exchange server do you receive any error numbers? other than the 4.5.2 in event viewer?
ASKER
The event log does not show any error on the server. The error is kicked back to the user in a undelivered message format.
My post gave you the awnser.... how many people do your users send email to?
ASKER
There is only one user that is experiencing the problem and he is trying to email 30 people.
Exchange 2003 will send outbound as many recipients as the remote server
supports. So essentially, as many recipients until the remote server returns
RFC 2821 452 (Too many recipients) or RFC 821 552 (Incorrect Too many
recipients) also.
According to this, the problem would be on the other side.. Hmmm, unless your users send these emails locally.
supports. So essentially, as many recipients until the remote server returns
RFC 2821 452 (Too many recipients) or RFC 821 552 (Incorrect Too many
recipients) also.
According to this, the problem would be on the other side.. Hmmm, unless your users send these emails locally.
turn logging on max for transport in exchange server, it may hold the key... or as yan is saying maybe it is out of your control and is a policy at another server.
ASKER
The other side meaning the recipients server? That would be a probably unlikely all 30 are comming back with the same error.
As soon as the other side has a limit of 30, and you go over it, it will do that yes...
try sending it in 2 groups of 15...
ASKER
I will, but the are all to different domains.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I will have user try that. Thanks for the help.