Jump to content

euphorique

Members
  • Content Count

    19
  • Joined

  • Last visited

Community Reputation

0 Neutral

About euphorique

  • Rank
    Member
  1. euphorique

    "No body text provided" with Bcc: header

    I completely agree on the purpose of Bcc: header, and acknowledge that it can be handled differently in various mail agents, correct or otherwise. Just consider the case with Bcc: header not being the last one in the header block: Received: from mbkd0231.ocn.ad.jp (mbkd0231.ocn.ad.jp. [153.149.233.32]) by mx.google.com with ESMTP id e96si22718016plb.123.2019.02.21.05.54.06; Thu, 25 Feb 2019 05:54:07 -0800 (PST) Bcc: spammer@spam.com From: spammer@spam.com Hey! There is a blank line between the headers and the body! SC parses Bcc: header correctly. The parser is aware that Bcc: header can rightfully contain the real address, and crosses the address out: Skip to Reports Received: from mbkd0231.ocn.ad.jp (mbkd0231.ocn.ad.jp. [153.149.233.32]) by mx.google.com with ESMTP id e96si22718016plb.123.2019.02.21.05.54.06; Thu, 25 Feb 2019 05:54:07 -0800 (PST) Bcc: x From: spammer@spam.com View entire message When Bcc: header is the last one in the header block, the parser chops off the entire message body. I can only speculate on the implementation of the parser, but in my imagination the error is something rather simple and obvious (given the number of 5-line test cases submitted here), and does not require a terrific effort to fix. And yes, for now I remove the Bcc: header if it breaks the parser. Cheers, it's Friday!
  2. euphorique

    "No body text provided" with Bcc: header

    As always, "No body text provided, check format of submission. spam must have body text."
  3. euphorique

    "No body text provided" with Bcc: header

    This one has "validly formed" address in bcc: https://www.spamcop.net/sc?id=z6523551992z5978bb9216921fdbce50eebacde4661az Received: from mbkd0231.ocn.ad.jp (mbkd0231.ocn.ad.jp. [153.149.233.32]) by mx.google.com with ESMTP id e96si22718016plb.123.2019.02.21.05.54.06; Thu, 25 Feb 2019 05:54:07 -0800 (PST) From: spammer@spam.com To: me@mailinator.com Subject: problem with BCC: header BCC: spammer@spam.com Hey! There is a blank line between the headers and the body!
  4. euphorique

    "No body text provided" with Bcc: header

    gvim Just changed the date to future, for others to have more than 48h to examine.
  5. euphorique

    "No body text provided" with Bcc: header

    This is probably because the message is 9 months old, and you get "Sorry, this email is too old" before the parser has a chance to get the bcc: header. Here is the new one: https://www.spamcop.net/sc?id=z6523547462ze5946ba4c2eff5336884fa5afac35a32z Received: from mbkd0231.ocn.ad.jp (mbkd0231.ocn.ad.jp. [153.149.233.32]) by mx.google.com with ESMTP id e96si22718016plb.123.2019.02.21.05.54.06; Thu, 22 Feb 2019 05:54:07 -0800 (PST) From: some-body@linkedin.com To: me@mailinator.com Subject: problem with BCC: header BCC: none Hey! There is a blank line between the headers and the body!
  6. euphorique

    "No body text provided" with Bcc: header

    Yep, the file is attached. Enjoy! SC-parser-Bcc-field-no-body.txt
  7. euphorique

    "No body text provided" with Bcc: header

    The page referred in tracking URL has a link "View entire message" (don't know whether others can see the original). The boundary between headers and body looks like: [--- most of headers skipped ---] Subject: PAYMENT NOTIFICATION OF YOUR FUNDS. To: undisclosed-recipients:; Content-Type: text/plain; charset="UTF-8" Bcc: x@y.com U.S. DEPARTMENT HOMELAND SECURITY, MG Timothy J. Lowenberg,Adjutant General and Director State Military Department Washington Military Dept, Bldg1 Camp Murry ,Wash USA[--- the rest of the body---] There is body. There is blank line between headers and body. The last line of headers is Bcc: I could copy-paste three snippets from my comment of 17th May 2018 but I would rather not. They demonstrated the problem then, and they demonstrate the same problem now.
  8. euphorique

    "No body text provided" with Bcc: header

    Nine months on, the bug is still there. Fresh tracking URL: https://www.spamcop.net/sc?id=z6523123683za99d8a142d504f688c643e1e02f281d8z On the bright side, "Received: by 2002:aXX:..." has been fixed, eventually.
  9. euphorique

    "No body text provided" with Bcc: header

    Four months on, the bug is still there.
  10. euphorique

    The parser finds no links

    I would agree, if I had not tried something minimalistic: https://www.spamcop.net/sc?id=z6471215459zd7977afe893fdf712f42c6b344a6afd1z These are just 4 headers from the original email. "Plain text" is considered "links". They are not fake, except for one.
  11. https://www.spamcop.net/sc?id=z6471208157zab0c11469dbccb0312c128df5eac948ez The parser could not find a single link. Any reason for that?
  12. euphorique

    Invalid certificate of forum.spamcop.net

    Yes, but this is just a non-secure workaround. The certificate 09:C2:9E:50:A7:64:D0:F6:D0:2F:2E:E2:B8:EE:64:19 secures the following domains: DNS Name: www.senderbase.org DNS Name: senderbase.org DNS Name: mailsc.spamcop.net DNS Name: general.spamcop.net DNS Name: charlie.senderbase.org DNS Name: beta.senderbase.org DNS Name: forum.spamcop.net DNS Name: spamcop.net DNS Name: alpha.senderbase.org DNS Name: members.spamcop.net DNS Name: www.spamcop.net It escapes me why forum.spamcop.net server can not be configured properly.
  13. euphorique

    Invalid certificate of forum.spamcop.net

    Any update?
  14. euphorique

    "No body text provided" with Bcc: header

    I provided one in the very first post, but lisati reported above that he could not see the body, only the headers. That report *does* have the body, or at least I can see it. So probably there is another bug lurking. Anyway, for the sake of completeness, here are the links. Again, I am submitting both headers and body (in RFC822 sense). Case 1: https://www.spamcop.net/sc?id=z6465379953zc617c730898b61e14b1fdeb6434218a7z Case 2: https://www.spamcop.net/sc?id=z6465380058zf95de8717cee940fc5bc0a91cb15aaddz Case 3: https://www.spamcop.net/sc?id=z6465380112z1c4ae87f11a33a2ba7dcbef68f944f62z
  15. euphorique

    "No body text provided" with Bcc: header

    Ok, I've put together a minimal example to demonstrate the problem. Make sure the date in the "Received:" header is close to today, otherwise the parser will bail out just after this header. Case 1 Received: from mailb-cd.linkedin.com (mailb-cd.linkedin.com. [108.174.6.148]) by mx.google.com with ESMTPS id some-id-here; Tue, 17 May 2018 12:37:00 -0700 (PDT) From: some-body@linkedin.com To: me@mailinator.com Subject: problem with BCC: header ACC: none Hey! There is a blank line between the headers and the body! Note the "ACC:" header. The result: message source is found, reporting address is found. As expected. Case 2 Received: from mailb-cd.linkedin.com (mailb-cd.linkedin.com. [108.174.6.148]) by mx.google.com with ESMTPS id some-id-here; Tue, 17 May 2018 12:37:00 -0700 (PDT) From: some-body@linkedin.com To: me@mailinator.com Subject: problem with BCC: header BCC: none Hey! There is a blank line between the headers and the body! Note the "BCC:" header. The result: "No body text provided, check format of submission. spam must have body text." Case 3 Received: from mailb-cd.linkedin.com (mailb-cd.linkedin.com. [108.174.6.148]) by mx.google.com with ESMTPS id some-id-here; Tue, 17 May 2018 12:37:00 -0700 (PDT) From: some-body@linkedin.com To: me@mailinator.com BCC: none Subject: problem with BCC: header Hey! There is a blank line between the headers and the body! Note that there is another header after "BCC:" header. The result: message source is found, reporting address is found. As expected.
×