Remote Server returned '550 5.2.3 RESOLVER.RST.RecipSizeLimit; message too large for this recipient'

%3CLINGO-SUB%20id%3D%22lingo-sub-1289175%22%20slang%3D%22en-US%22%3ERemote%20Server%20returned%20'550%205.2.3%20RESOLVER.RST.RecipSizeLimit%3B%20message%20too%20large%20for%20this%20recipient'%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1289175%22%20slang%3D%22en-US%22%3E%3CP%3EThe%20recipient%20won't%20be%20able%20to%20receive%20this%20message%20because%20it's%20too%20large.%3C%2FP%3E%3CP%3EThe%20maximum%20message%20size%20that's%20allowed%20is%2019%20MB.%20This%20message%20is%2029%20MB.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EOne%20of%20our%20office%20365%20users%20has%20an%20issue%20sending%20an%20email%20with%20attachments%20through%20an%20internal%20SMTP%20receive%20connector.%20the%20message%20size%20of%20her%20email%2C%20the%20receive%20connector%20and%20all%20the%20recipients%20are%20all%20set%20to%2050MB.%20We%20have%20a%20hybrid%20environment.%20The%20receive%20connector%20is%20configured%20on%20an%20on%20premise%20Exchange%202013%20server%20but%20the%20sender%20and%20the%20recipients%20are%20all%20in%20the%20office%20365%20cloud.%20Not%20sure%20what%20the%20issue%20is%20now.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1289175%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EHybrid%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Highlighted
Occasional Visitor

The recipient won't be able to receive this message because it's too large.

The maximum message size that's allowed is 19 MB. This message is 29 MB.

 

 

One of our office 365 users has an issue sending an email with attachments through an internal SMTP receive connector. the message size of her email, the receive connector and all the recipients are all set to 50MB. We have a hybrid environment. The receive connector is configured on an on premise Exchange 2013 server but the sender and the recipients are all in the office 365 cloud. Not sure what the issue is now.

 

 

0 Replies