Jump to content
fliptop

Message-ID: $null causes reporting tool to sh** the bed

Recommended Posts

Lately I've been getting spam where the last line of the header reads:

 

Message-ID: $null

 

when reporting this using the web form it causes the parser to somehow misinterpret the end of the headers and beginning of the body text.  As a workaround I just remove the $null portion and post the report.  I've kept an example that fails, so if need be I can post the headers for inspection.

 

Thanks, Paul

Share this post


Link to post
Share on other sites

A tracking URL is always helpful to see what the parser is doing

Share this post


Link to post
Share on other sites

here ya go

 

https://www.spamcop.net/sc?id=z6620853362z4a1334258458d03c2ed000ed00bb6c9ez

Share this post


Link to post
Share on other sites

the last header is as mentioned, then there's a blank line, and the first line of text from the message reads:

 

Do you need an Investor?

Share this post


Link to post
Share on other sites
13 hours ago, fliptop said:

the last header is as mentioned, then there's a blank line, and the first line of text from the message reads:

The body of yours seems missing, so I resubmitted with a new body and I get the same thing.  There seems to be a problem somewhere else in the headers that is confusing.  If you look at my completely changed message ID line as below, then you can see that the message body (from the View entire message link) seems to be put onto the end of the messageID line (from the tracking URL).  There seems to be something else than just the $nul that is going on here.

with $nul: https://www.spamcop.net/sc?id=z6620984216z1309884122860acc9adaeae9dbe67578z

without $nul: https://www.spamcop.net/sc?id=z6620984773z5d37101fab5fd6f6b535b8b6f8eca868z

Completely changed message line: https://www.spamcop.net/sc?id=z6620985295z6cd84be9d2a4f3f7ab69843964529431z

Share this post


Link to post
Share on other sites

I included the 1st line of the body in the original submission.  The $null causes the parser to gobble up the blank line separating the headers from the body and incorporate part of the body into the Message-ID: value.  If you remove just the $null from the aforementioned header and resubmit it gets parsed correctly.

 

This is the reason I offered to post the original message instead of the tracking URL.  If doing that will be helpful, let me know.

 

Thanks, Paul

Share this post


Link to post
Share on other sites
3 hours ago, fliptop said:

The $null causes the parser to gobble up the blank line separating the headers from the body and incorporate part of the body into the Message-ID: value. 

Yep.  It does.

blob.png.841ee9befc0fe5e30d7061ef09582622.png

Share this post


Link to post
Share on other sites

Thanks.  I've added this to another ticket that is similar.  It is on the list for the next patch rollout.

RicharD

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×