> >> Hello Vilius,
> >> >> Message-ID: <trinity-e379746a-d1b7-41a8-801f-b56e2e1b29a0-
> >> >> 1352796933847@3capp-webde-bs49>
> >>
> >> > That's because it is invalid ID. It doesn't conform to RFC822
> >> > specification.
> >>
> >> You probably wouldn't volunteer to elaborate as to exactly what is wrong
> >> with it right away
> >> without being asked explicitly? :)
>
> > Message-ID should follow a subset of email specification, e.i. it
> > must contain @ and FQDN parts. And this ID obviously doesn't.
>
> FQDN usage isn't required but recommended.
> (in both http://tools.ietf.org/html/rfc2822#section-3.6.4 and the
> newer http://tools.ietf.org/html/rfc5322#section-3.6.4).
> Ritlabs folk might've not paid attention to such tiny details though.
It probably comes from older RFC822 which says that Message-ID is addr-spec
surrounded by <>.
An addr-spec is a specific Internet identifier that contains a
locally interpreted string followed by the at-sign character ("@",
ASCII value 64) followed by an Internet domain. The locally
interpreted string is either a quoted-string or a dot-atom. If the
string can be represented as a dot-atom (that is, it contains no
characters other than atext characters or "." surrounded by atext
addr-spec = local-part "@" domain
________________________________________________________
Current beta is 5.3.2.9 | 'Using TBBETA' information:
http://www.silverstones.com/thebat/TBUDLInfo.html
