Size limit for Message-ID

[BShur]

Seems that there is a max for the Message-ID length, and it is not 255 (for backwards compatibility) or 998 (as per RFC4130), but much less.

Our message ID is a GUID@fqdn, so things work fine for the Prod. domain where the ID is GUID@FQDN, but when we tried to send from our test domain, which only differs by 5 characters, GU...@test.FQDN, the report looks like this:

Message Validator	null	null
The file was recognized as a DIRECT message.	ok
javax.mail.internet.ParseException: Expected ';', got "----=3D_NextPart_49187420.393696245186"	error	Error
Validation Summary	null	null
Validation Context: ???;DIRECT;NotUpdateable;CCDA type is	ok
Message Validator Changing the code to remove "test." in front of domain name and sending from the same account on test domain worked fine, which leads me to believe there is some limit...

[Perugini, Julien C.]

Hi,

 

I don’t know what is the problem here, I tested with <GU...@test.FQDN> as message ID and it worked fine for me.

Could you give me the message you used when you got this exception please?

I’ll have a look at that, it seems that JavaMail can’t recognize the message as a MimeMessage.

 

Thanks,

Julien

--
You received this message because you are subscribed to the Google Groups "Transport Testing Tool" group.
To unsubscribe from this group and stop receiving emails from it, send an email to transport-testing...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[Perugini, Julien C.]

 

 

From: Perugini, Julien C.
Sent: Thursday, February 21, 2013 5:10 PM
To: 'Boris@SES'
Subject: RE: Size limit for Message-ID

 

I just read the spec again and it seems that we should allow more than one dot in the right part of the message ID.

I will fix that and it will be in the next release.

 

Thanks again,

Julien

 

 

From: Perugini, Julien

From: Perugini, Julien C.
Sent: Thursday, February 21, 2013 5:10 PM
To: 'Boris@SES'
Subject: RE: Size limit for Message-ID

 

Thank you, I am sorry I misread your previous mail.

The message ID probably fail because there are two dots in the right part of the message ID (after the @).

I need to read the spec again to see if it says something specific about that.

Thank you for pointing this out,

Julien

 

 

From: Boris@SES [mailto:bs...@secureexsolutions.com]
Sent: Thursday, February 21, 2013 4:55 PM
To: Perugini, Julien C.
Subject: Re: Size limit for Message-ID

 

That was the only difference between the two messages - 5 character length diff of msg-id.

On Feb 21, 2013, at 4:52 PM, Boris@SES <bs...@SecureExSolutions.com> wrote:

 

Maybe I made it too obscure or maybe I am not reading your reply correctly…

 

The message ID that worked was something like this: <9f83b28a-35d0-4d51-8a3a-9682fcb792c3@directaddress.net>

but when message ID was changed to <9f83b28a-35d0-4d51-8a3a-9682fcb792c3@test.directaddress.net> it failed.

I would have to set something up specifically to capture the message (we do not keep sent messages on the mail server - they are pretty useless since we do not have the private keys for them) - let me know if you still need it or that my explanation changed that.

 

On Feb 21, 2013, at 4:45 PM, "Perugini, Julien C." <julien....@nist.gov> wrote:

 

Hi,

 

I don’t know what is the problem here, I tested with <GU...@test.FQDN> as message ID and it worked fine for me.

Could you give me the message you used when you got this exception please?

I’ll have a look at that, it seems that JavaMail can’t recognize the message as a MimeMessage.

 

Thanks,

Julien