Tickets :: [#676] colons in config/header.txt

6.0.0-beta1

7/4/25

Summary	colons in config/header.txt
Queue	IMP
Queue Version	3.2.6
Type	Bug
State	Resolved
Priority	1. Low
Owners	slusarz (at) horde (dot) org
Requester	tpeland (at) tkukoulu (dot) fi
Created	10/08/2004 (7574 days ago)
Due
Updated	10/11/2004 (7571 days ago)
Assigned	10/08/2004 (7574 days ago)
Resolved	10/11/2004 (7571 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch	No

10/11/2004 10:22:18 PM	Michael Slusarz	Comment #4 State ⇒ Resolved	Reply to this comment
I can't remember why I originally did this, but obviously it won't break any RFC's (as long as the header definition is in the form "HeaderName:<space>". This has been fixed in 3.x and HEAD.

10/08/2004 02:53:09 PM	Chuck Hagenbuch	Comment #3	Reply to this comment
I can't see how it could - look at the Subject line from the original email generated for this ticket: Subject: [Tickets ~~#676~~] NEW: colons in config/header.txt (NEW:)

10/08/2004 08:26:41 AM	Jan Schneider	Comment #2 Assigned to Michael Slusarz State ⇒ Assigned	Reply to this comment
Would that break any RFCs, Michael?

10/08/2004 07:46:50 AM		New Attachment: imp-3.2.6-colons_in_header.patch

10/08/2004 07:42:55 AM	tpeland (at) tkukoulu (dot) fi	Comment #1 State ⇒ Unconfirmed Priority ⇒ 1. Low Type ⇒ Bug Summary ⇒ colons in config/header.txt Queue ⇒ IMP	Reply to this comment
When using ipv6 and header.txt like this: X-Originating-IP: %REMOTE_ADDR% you get a header like X-Originating-IP: 2002_c067_6202_8000_207_40ff_fe33_d78 instead of X-Originating-IP: 2002:c067:6202:8000:207:40ff:fe33:d78 There is no good reason to strip the colons from the header. The line to be removed is in lib/IMP.php line 1100 (CVS: lib/MIME/Headers.php, line 144) $val = strtr($val, ':', '_');