From: Micheal E. Jr <mi...@es...> - 2008-01-08 22:09:31
|
Could someone familiar with the code confirm how the script grabs=20 envelop header info like from:, sender:, to: ? I am curious to know if=20 ASSP properly handles spacing between the header field colon and the=20 start of the header data. Here's why, and what I think may be an issue: Certain MTAs will use multiple spaces in order to column justify the=20 header information instead of using a single standard space. I have=20 noticed this because some of my regexps don't always match, and I have=20 begun to realize why. A particular example that may effect others would = be an 'undeliverable' NDRs that contains headers like this: ---------- Date: Tue, 8 Jan 2008 15:59:26 -0500 Message-Id: <***********.*******@senderdomain.tld> Mime-Version: 1.0 Content-Type: text/plain; charset=3Dus-ascii From: "Postmaster" <pos...@se...d> Sender: <pos...@se...d> To: <use...@my...d> Subject: Undeliverable Mail X-Mailer: <SMTP32 v8.22> ---------- Notice that four of the header fields have been space-justified to the=20 11th column. Along with this, the ASSP-added headers contained this: ---------- X-Assp-Envelope-From: ---------- Yes, the header field data is blank. I'm assuming this is because ASSP=20 isn't parsing the field properly in order to handle this type of=20 spacing. Its an assumption based on what I think I am seeing, but if=20 this is true, some of ASSP's tests could possibly be bypassed. |