메일(메시지) 헤더 분석편 References

   

   

기존에 발송했던, 수신했던 메일을 계속해서 Reply, 혹은 Forward 하는 경우,

기존의 메시지 ID 값이 References 에 쌓인다(들어간다)

아래 메시지 예시는 10번정도 전달이 된것 으로 보면 된다.

   

추가.

Exchange 2013 OWA 버그(?)

동일한 메일을 계속해서 Reply, 혹은 Forward 재사용하는 경우

수백 건의 Reference 값이 쌓이게 된 상황에서

Exchange 2013 OWA에서 해당 메일을 다시 Reply, 혹은 Forward 시도하는 경우

해당 IE 브라우저 Hang 현상발생 브라우저 재시작 필요

   

In-Reply-To: <SNT124-W2664003139C1E520CF4F6787D30@phx.gbl>

References: <SNT124-W2664003139C1E520CF4F6787D30@phx.gbl>

Did you notice?  The values of the In-Reply-To and References headers are taken from the Message-ID header of the original!  Ah, but what happens if I "reply to the reply"?   Well, my message gets its own unique Message-ID, of course...and the Message-ID of the message to which I'm replying goes in my In-Reply-To header (which usually has only one Message-ID)...but that In-Reply-To Message-ID is also APPENDED to the References header.  So, in a lengthy back-and-forth, you might see headers that look like this:

In-Reply-To: <4BE8776D.4080504@kheb.fr>

References: <AANLkTik0c9hCMm2Efyj7rB7Us7hL3ZdESYEhE2GBQCfM@mail.gmail.com>

<20100509165117.GD20976@ovh.net>

<AANLkTins_dUSqRbR371SNnOIPYlatKdTCIVM8oDbtVtX@mail.gmail.com>

<AANLkTimKu7l1AtEG-0CI7Q3Ely9PUL2yuyvYuhcMIuSn@mail.gmail.com>

<AANLkTikJaHXYM_DF8zqdaH0vVnJ-fCpqvJ3OCQweoeAb@mail.gmail.com>

<AANLkTinq7riyV4w3VnCoHyj9GsNf3H7jDzu1awU2PNRb@mail.gmail.com>

<AANLkTilrPTCZPj_Tb7bXO5SLym_QY3KUp4J1jkZd5-ZE@mail.gmail.com>

<4BE72FF3.3030501@kheb.fr>

<4BE7B451.8060700@linuxant.fr>

<4BE8776D.4080504@kheb.fr>

From: XXX <xxx@xxx.xx>

Date: Mon, 10 May 2010 23:20:59 +0200

Message-ID: <AANLkTikC5oN2rO5VTj8HN7U03b2H3HUqt89KYdemGlcJ@mail.gmail.com>

(Notice that this Message-ID isn't in the References header - because no one has yet referenced this message with a reply!)

Surprise - you've just learned how "threaded discussion" email clients work.  Basically, they can look at any message in the thread, grab its References header, and go find the other messages in your mailbox.