Jump to content

euphorique

Members
  • Content Count

    11
  • Joined

  • Last visited

Community Reputation

0 Neutral

About euphorique

  • Rank
    Member
  1. euphorique

    "No body text provided" with Bcc: header

    Four months on, the bug is still there.
  2. 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.
  3. https://www.spamcop.net/sc?id=z6471208157zab0c11469dbccb0312c128df5eac948ez The parser could not find a single link. Any reason for that?
  4. 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.
  5. euphorique

    Invalid certificate of forum.spamcop.net

    Any update?
  6. 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
  7. 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.
  8. euphorique

    "No body text provided" with Bcc: header

    No. The blank line *is present*. You can add a BCC: header to your next reported spam and see for yourself.
  9. Hi, This site, https://forum.spamcop.net, uses invalid certificate issued to *.cloudfront.net. The site https://www.spamcop.net uses certificate issued to www.senderbase.org, and it covers www.spamcop.net, spamcop.net, and forum.spamcop.net. I am using Firefox on Linux. Any plans to fix the problem? Thank you.
  10. Hi, If Bcc: header is the last one of the header block, the parser can not find the mail body. See the problem here: https://www.spamcop.net/sc?id=z6465188193z3af57cb725d9442c31200476b3b6538cz When do you plan to fix it? Thank you.
  11. Hi, It looks like the address 2002:ab0:11d9:0:0:0:0:0 belongs to Google, yet Spamcop does not list it among the known addresses. See the problem here: https://www.spamcop.net/sc?id=z6465187313z08acebe658f658913a2727ba46aff928z Any plans to fix it? Thank you.
×