rfc 5322 2.1.1 550 Maximum line length exceeded
Problem reported by Richard Frank - September 27, 2018 at 8:52 AM
Resolved
rfc 5322 2.1.1
rsp: 550 Maximum line length exceeded

customer of mine replies to an email and includes 6 pictures < 100KB 
and some other attachments with no extension. Probably his Phone uploading this



those attachments without extension contains 4 empty lines in  it. 

the tekst in the mail looks normally.

what can trigger rfc 5322 2.1.1


17 Replies

Reply to Thread
0
Richard Frank Replied
Hello,

I had a second customer using the webmail with this problem.

Curious if other SM users have heard about this problem too.
0
Scarab Replied
Is this the "rsp: 550 Maximum line length exceeded" error?

I've gotten a few of those lately (can't remember as of what minor version of v16). Not enough to panic about, but enough to have me scratching my head. Seems to happen with Multi-Part MIME format messages with attachments. When sent as a Plain-Text message in webmail the problem goes away. I have also seen this happen with sending via an email client to SmarterMail recently too.

0
Richard Frank Replied
Yes, thans Scarab. That's the error. I editted the subject.
I'm gonna open a support ticket
0
Richard Frank Replied
I opened support call and they are working on it.
It's just difficult to replicate, so if you have any extra information like browser or circumstances when this happends please add it to this thread.
0
Kevin McNally Replied
This has also started happening to me since upgrading to 16.3.6841 when I email certain people using webmail.

Kevin

0
Kevin McNally Replied
Is there any update on this? We are not able to forward any emails to our Freshdesk account. They all come back with this error:

Reason: Remote host said: 500 Line length exceeded. See RFC 2821 #4.5.3.1.
1
Employee Replied
Employee Post Marked As Resolution
Hello All,
This issue has been fixed and will be included in our next release. The issue was caused mostly by forwarding messages with base64 attachments.
0
Richard Frank Replied
Great and thanks
Can't wait :)
0
Tiago Dias Replied
this is solved in this version:16.3.6870  ?
1
Robert Emmett Replied
Employee Post
Tiago, it was resolved in 16.3.6855.
Robert Emmett
Software Developer
SmarterTools Inc.
(877) 357-6278
www.smartertools.com
0
Neil Pickles Replied
I have upgraded to 16.3.6855 but am still seeing a few of these errors, though seemingly only from one recipients mail system.

Is anyone else seeing this issue with a version >= 16.3.6855?
0
Richard Frank Replied
nope.. for me it's fixed.with 6855

0
Andrea Rogers Replied
Employee Post
Hello Neil, 

If you're still experiencing this on 16.3.6855, please feel free to submit a ticket to the Support Department for their review. Because your license has active Maintenance and Support, you have unlimited access to submit support tickets for standard issues like this. Just log in here and click New Ticket: https://www.smartertools.com/account/#/support

Andrea Rogers
Customer Operations Manager
SmarterTools Inc.
877-357-6278

www.smartertools.com

0
Webio Replied
Hello,

I'm just letting you know that I've experienced this error on latest SMv17/100 build (7020 - custom build):

Could not deliver message to the following recipient(s): Failed Recipient: XXXXXXXXXXX Reason: Remote host said: 550 Maximum line length exceeded (see RFC 5322 2.1.1)
1
Neil Pickles Replied
We are still seeing this, though only with a few clients emails. As far as I can tell they are all using the same spam filtering service, their mx records point at various mx*.mtaroutes.com, which appears to mean they are using Solarwinds Mail Assure service.

We are still on 16.3.6855.
2
Webio Replied
Exactly. MX was set to *.mtaroutes.com
1
J Lee Replied
550 Maximum line length exceeded - has this issue today

I have seen this in email logs for years in Smartermail and other email servers. My conclusion was this happens in a number or case but the one I see the most is sending to older exchange server have a setting to for max characters in the email header and the encryption keys, dkim key etc will throw this error. The receiving server will just reject the message

J. Sebastian Lee Service2Client LLC 6333 E Mockingbird Ste 147 Dallas, TX 75214 - 877.251.3273

Reply to Thread