[#676] colons in config/header.txt
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 2004-10-08 (5274 days ago)
Updated 2004-10-11 (5271 days ago)
Assigned 2004-10-08 (5274 days ago)
Resolved 2004-10-11 (5271 days ago)
Patch No

2004-10-11 22:22:18 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.
2004-10-08 14:53:09 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

2004-10-08 08:26:41 Jan Schneider Comment #2
Assigned to Michael Slusarz
State ⇒ Assigned
Reply to this comment
Would that break any RFCs, Michael?
2004-10-08 07:46:50   New Attachment: imp-3.2.6-colons_in_header.patch Download
2004-10-08 07:42:55 tpeland (at) tkukoulu (dot) fi Comment #1
Type ⇒ Bug
State ⇒ Unconfirmed
Priority ⇒ 1. Low
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, ':', '_');

Saved Queries