T
TommyLindqvist
A user of mine got his mail blocked by NIDS-protection. Culprit seems to be
this Message-ID: header.
I have mangled addresses and domains, but retained the national characters
in the TO: fields, in case they have a bearing on why Outlook generates such
an outrageous Message-ID:
Version of Outlook could be seen below. For the user in question, this type
of Message-ID seems to be coupled to the recipients in this case, as he can
send to me without those ID's being generated.
I have yet to make him see the light and try to send a message to the bare
address without the Real Name attached to the To field.
From (e-mail address removed) Tue Aug 31 16:22:28 2004
Return-Path: <[email protected]>
From: =?Windows-1252?Q?My_User=E4ng?= <[email protected]>
To: "=?Windows-1252?Q?'=D8other_User'?=" <[email protected]>
Cc: "=?Windows-1252?Q?'Other_U=E4yh=E4ser'?=" <[email protected]>,
"=?Windows-1252?Q?'Frouth_User=F6m'?=" <[email protected]>
Subject: Recall: Uppdaterad specifikation
Date: Tue, 31 Aug 2004 16:25:51 +0200
Organization: Our Organization Name
Message-ID:
<!~!UENERkVCMDkAAQACAPQAAAAAAAAAOKG7EAXlEBqhuwgAKypWwgAAbXNwc3QuZGxs
AAAAAABOSVRB+b+4AQCqADfZbgAAAABDADoAXABEAG8AYwB1AG0AZQBuAHQAcwAgAGEAbgBkACAAUwBl
AHQAdABpAG4AZwBzAFwAbABvAGYAdABhAGwAXABMAG8AYwBhAGwAIABTAGUAdAB0AGkAbgBnAHMAXABB
AHAAcABsAGkAYwBhAHQAaQBvAG4AIABEAGEAdABhAFwATQBpAGMAcgBvAHMAbwBmAHQAXABPAHUAdABs
AG8AbwBrAFwATwB1AHQAbABvAG8AawAuAHAAcwB0AAAAGAAAAAAAAADB5K+coq6GSrGnjljVv+CtwoAA
ABgAAAAAAAAAweSvnKKuhkqxp45Y1b/grWQoLAAAAAAAEAAAADNgY5hohgpDjmzfDmEpuJwZAAAAVXBw
[email protected]>
MIME-Version: 1.0
Content-Type: multipart/mixed;
boundary="----=_NextPart_000_001B_01C48F77.2EAB3970"
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
X-MS-TNEF-Correlator: 00000000C1E4AF9CA2AE864AB1A78E58D5BFE0ADC4282C00
Expiry-Date: Thu, 2 Sep 2004 16:25:50 +0200
X-IMAPbase: 1094026155 257
Status: O
X-Status:
X-Keywords:
X-UID: 248
this Message-ID: header.
I have mangled addresses and domains, but retained the national characters
in the TO: fields, in case they have a bearing on why Outlook generates such
an outrageous Message-ID:
Version of Outlook could be seen below. For the user in question, this type
of Message-ID seems to be coupled to the recipients in this case, as he can
send to me without those ID's being generated.
I have yet to make him see the light and try to send a message to the bare
address without the Real Name attached to the To field.
From (e-mail address removed) Tue Aug 31 16:22:28 2004
Return-Path: <[email protected]>
From: =?Windows-1252?Q?My_User=E4ng?= <[email protected]>
To: "=?Windows-1252?Q?'=D8other_User'?=" <[email protected]>
Cc: "=?Windows-1252?Q?'Other_U=E4yh=E4ser'?=" <[email protected]>,
"=?Windows-1252?Q?'Frouth_User=F6m'?=" <[email protected]>
Subject: Recall: Uppdaterad specifikation
Date: Tue, 31 Aug 2004 16:25:51 +0200
Organization: Our Organization Name
Message-ID:
<!~!UENERkVCMDkAAQACAPQAAAAAAAAAOKG7EAXlEBqhuwgAKypWwgAAbXNwc3QuZGxs
AAAAAABOSVRB+b+4AQCqADfZbgAAAABDADoAXABEAG8AYwB1AG0AZQBuAHQAcwAgAGEAbgBkACAAUwBl
AHQAdABpAG4AZwBzAFwAbABvAGYAdABhAGwAXABMAG8AYwBhAGwAIABTAGUAdAB0AGkAbgBnAHMAXABB
AHAAcABsAGkAYwBhAHQAaQBvAG4AIABEAGEAdABhAFwATQBpAGMAcgBvAHMAbwBmAHQAXABPAHUAdABs
AG8AbwBrAFwATwB1AHQAbABvAG8AawAuAHAAcwB0AAAAGAAAAAAAAADB5K+coq6GSrGnjljVv+CtwoAA
ABgAAAAAAAAAweSvnKKuhkqxp45Y1b/grWQoLAAAAAAAEAAAADNgY5hohgpDjmzfDmEpuJwZAAAAVXBw
[email protected]>
MIME-Version: 1.0
Content-Type: multipart/mixed;
boundary="----=_NextPart_000_001B_01C48F77.2EAB3970"
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
X-MS-TNEF-Correlator: 00000000C1E4AF9CA2AE864AB1A78E58D5BFE0ADC4282C00
Expiry-Date: Thu, 2 Sep 2004 16:25:50 +0200
X-IMAPbase: 1094026155 257
Status: O
X-Status:
X-Keywords:
X-UID: 248